Unable to create SSD storage pool [DS920+; DSM 7.1.1-42962 Update 5]

[jhlchu]

DS920+ on DSM 7.1.1-42962 Update 5. 1 Intel SSD (M.2 slot 2) as read-cache before buying and installing another SSD (Firecuda 530) in M.2 slot 1.

I following the sequence:

1. Installed the new SSD and booted up.
2. SSD recognized already before running script. Shows as Cache Device 1 in Storage Manager.
3. Moved the script to /volume1/homes/{username}/scripts/. Run the script from Putty.
4. Checked Storage Manager again (drive still recognized) and rebooted.
5. Drive still recognized in Storage Manager. Allocation Not Initialized. Click Manage Available Drives > Create Storage Pool, dialog "Cannot perform this action. No drives are available or meet the requirements"
6. Created on boot task to automatically run the script.
7. Reboot again. Same issue as 5.
8. Run the script again, reboot. Same issue as 5.
9. Download and run Synology_M2_volume, reboot, same error as 5.

Both drives are still recognized as Cache device.

Terminal outputs

_Synology_HDDdb

> sudo -s /volume1/homes/{username}/scripts/syno_hdd_db.sh -nr --showedits
Synology_HDD_db v3.5.93
DS920+ DSM 7.1.1-42962-5
ds920+_host_v7 version 8052

Using options: -nr --showedits
Running from: /volume1/homes/{username}/scripts/syno_hdd_db.sh

HDD/SSD models found: 1
ST16000NE000-2RW103,EN02

M.2 drive models found: 2
INTEL MEMPEK1J032GA,K4110400
Seagate FireCuda 530 ZP2000GM30023,SU6SM005

No M.2 PCIe cards found

No Expansion Units found

Backed up ds920+_host_v7.db.new
ST16000NE000-2RW103 already exists in ds920+_host_v7.db
Edited unverified drives in ds920+_host_v7.db
ST16000NE000-2RW103 already exists in ds920+_host_v7.db.new
Edited unverified drives in ds920+_host_v7.db.new
Added INTEL MEMPEK1J032GA to ds920+_host_v7.db
Added INTEL MEMPEK1J032GA to ds920+_host_v7.db.new
Added Seagate FireCuda 530 ZP2000GM30023 to ds920+_host_v7.db
Added Seagate FireCuda 530 ZP2000GM30023 to ds920+_host_v7.db.new

Backed up synoinfo.conf

Support disk compatibility already enabled.

Disabled support memory compatibility.

Set max memory to 20 GB.

NVMe support already enabled.

Enabled M.2 volume support.

Disabled drive db auto updates.

INTEL MEMPEK1J032GA:
{
  "K4110400": {
    "compatibility_interval": [
      {
        "compatibility": "support",
        "not_yet_rolling_status": "support",
        "fw_dsm_update_status_notify": false,
        "barebone_installable": true,
        "smart_test_ignore": false,
        "smart_attr_ignore": false
      }
    ]
  },
  "default": {
    "compatibility_interval": [
      {
        "compatibility": "support",
        "not_yet_rolling_status": "support",
        "fw_dsm_update_status_notify": false,
        "barebone_installable": true,
        "smart_test_ignore": false,
        "smart_attr_ignore": false
      }
    ]
  }
}

Seagate FireCuda 530 ZP2000GM30023:
{
  "SU6SM005": {
    "compatibility_interval": [
      {
        "compatibility": "support",
        "not_yet_rolling_status": "support",
        "fw_dsm_update_status_notify": false,
        "barebone_installable": true,
        "smart_test_ignore": false,
        "smart_attr_ignore": false
      }
    ]
  },
  "default": {
    "compatibility_interval": [
      {
        "compatibility": "support",
        "not_yet_rolling_status": "support",
        "fw_dsm_update_status_notify": false,
        "barebone_installable": true,
        "smart_test_ignore": false,
        "smart_attr_ignore": false
      }
    ]
  }
}

ST16000NE000-2RW103:
{
  "EN02": {
    "size_gb": 16000,
    "compatibility_interval": [
      {
        "compatibility": "support",
        "not_yet_rolling_status": "support",
        "fw_dsm_update_status_notify": false,
        "barebone_installable": true,
        "barebone_installable_v2": "auto",
        "smart_test_ignore": false,
        "smart_attr_ignore": false
      }
    ]
  },
  "default": {
    "size_gb": 16000,
    "compatibility_interval": [
      {
        "compatibility": "support",
        "not_yet_rolling_status": "support",
        "fw_dsm_update_status_notify": false,
        "barebone_installable": true,
        "barebone_installable_v2": "auto",
        "smart_test_ignore": false,
        "smart_attr_ignore": false
      }
    ]
  }
}

DSM successfully checked disk compatibility.

You may need to reboot the Synology to see the changes.

_Synology_M2volume

> sudo -s /volume1/homes/{username}/scripts/syno_enable_m2_volume.sh
Synology_enable_M2_volume v1.1.22
DS920+ DSM 7.1.1-42962-5

Using options:
Running from: /volume1/homes/{username}/scripts/syno_enable_m2_volume.sh
Backup successful.

Checking file.
180462 = 2c0ee
0002c0ee: 803E 00B8 0100 0000 7520 488B

Editing file.

Checking if file was successfully edited.
180462 = 2c0ee
0002c0ee: 803E 00B8 0100 0000 9090 988B
File successfully edited.

You can now create your M.2 storage pool in Storage Manager.

M.2 volume support already enabled.

[007revad]

DS920+ on DSM 7.1.1-42962 Update 5

Upgrade to DSM 7.2.1 and it will work with just Synology_HDD_db

https://global.synologydownload.com/download/DSM/release/7.2.1/69057-1/DSM_DS920%2B_69057.pat

[jhlchu]

I was concerned about upgrading to 7.2.1 because of https://github.com/007revad/Synology_HDD_db/issues/292. They are using the same drive, therefore I was hesitant in updating as that OP had to downgrade back to 7.1.1 for drives to be recognized again.

Was the source of their issue identified? Should I do any prep work on 7.1.1 to ensure that I don't have "missing in syno_slot_mapping and /run/synostorage/disks"? (e.g. _remove the script edited files from Synology_M2_volume or Synology_HDDdb, restore some default values before updating, disable scheduled task)

[007revad]

I was concerned about upgrading to 7.2.1 because of #292. They are using the same drive, therefore I was hesitant in updating as that OP had to downgrade back to 7.1.1 for drives to be recognized again.

They have a DS923+ which officially supported M.2 volumes in DSM 7.1.1

I'm fairly sure DSM for the DS920+ did not have the necessary files until DSM 7.2 (which was when storage manager became a package).

[jhlchu]

That was indeed the issue. Disabled schedule task, updated to 7.2.1, ran the script, reboot, drive now shows as M.2 Drive.