Crucial CT4000P3SSD8 Unrecognized firmware version

[R-a-K-i]

Hello,

Thank you very much for your great work. Your scripts are very helpful. Maybe you can help me with the following problem:

Although the M.2 SSD and the firmware version were recognized correctly and entered in the DB file, the SSD was not recognized correctly. Is there a solution for this?

Regards Ralph

syno_hdd_db.sh -s

CT4000P3SSD8: { "P9CR30A": { "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 } ] } }

[R-a-K-i]

Synology_HDD_db v3.5.91 DS923+ DSM 7.2.1-69057-5 StorageManager 1.0.0-0017

ds923+_host_v7 version 8041

Using options: -s Running from: /volume1/homes/adminrknas/scripts/syno_hdd_db.sh

HDD/SSD models found: 1 SSD,W0802A0

M.2 drive models found: 1 CT4000P3SSD8,P9CR30A

No M.2 PCIe cards found

No Expansion Units found

SSD already exists in ds923+_host_v7.db CT4000P3SSD8 already exists in ds923+_host_v7.db

Support disk compatibility already enabled.

Support memory compatibility already enabled.

NVMe support already enabled.

M.2 volume support already enabled.

Drive db auto updates already enabled.

SSD: { "W0802A0": { "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 } ] } }

CT4000P3SSD8: { "P9CR30A": { "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 } ] } }

DSM successfully checked disk compatibility.

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

[007revad]

If Storage Manager was already open it needs to be closed and reopened.

You should always run the script with the -n option to prevent DSM updating the drive database.

Interesting that your 2.5 inch SATA SSD shows up as just "SSD" for the model. Does it show in Storage Manager as either:

• VRX SSD (SSD)
• INTENSO SSD (SSD)

[R-a-K-i]

I added the "-n" option (also in the "boot-up" task). After I rebooted the NAS twice, the result is the same. What surprises me is that everything works so far. I can create a volume and also activate deduplication.

Thanks for your help Ralph

Synology_HDD_db v3.5.91 DS923+ DSM 7.2.1-69057-5 StorageManager 1.0.0-0017

ds923+_host_v7 version 8041

Using options: -n -s Running from: /volume1/homes/adminrknas/scripts/syno_hdd_db.sh

HDD/SSD models found: 1 SSD,W0802A0

M.2 drive models found: 1 CT4000P3SSD8,P9CR30A

No M.2 PCIe cards found

No Expansion Units found

SSD already exists in ds923+_host_v7.db CT4000P3SSD8 already exists in ds923+_host_v7.db

Support disk compatibility already enabled.

Support memory compatibility already enabled.

NVMe support already enabled.

M.2 volume support already enabled.

Drive db auto updates already disabled.

SSD: { "W0802A0": { "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 } ] } }

CT4000P3SSD8: { "P9CR30A": { "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 } ] } }

DSM successfully checked disk compatibility.

The INTENSO SSDs are displayed like this:

[jeprojects]

Happening also with my nvme drives: CT1000P3PSSD8

Synology_HDD_db v3.5.91
DS1520+ DSM 7.2.1-69057-5 
StorageManager 1.0.0-0017

ds1520+_host_v7 version 8054

ds1520+_host version 4026

Using options: -n
Running from: /volume1/scripts/syno_hdd_db.sh

WARNING Don't store this script on an NVMe volume!

HDD/SSD models found: 2
ST16000NM001G-2KK103,SN02
ST16000NM001G-2KK103,SN03

M.2 drive models found: 1
CT1000P3PSSD8,P9CR413

No M.2 PCIe cards found

No Expansion Units found

Updated ST16000NM001G-2KK103 in ds1520+_host_v7.db
ST16000NM001G-2KK103 already exists in ds1520+_host.db
ST16000NM001G-2KK103 already exists in ds1520+_host.db.new
Updated ST16000NM001G-2KK103 in ds1520+_host_v7.db
ST16000NM001G-2KK103 already exists in ds1520+_host.db
ST16000NM001G-2KK103 already exists in ds1520+_host.db.new
CT1000P3PSSD8 already exists in ds1520+_host_v7.db
CT1000P3PSSD8 already exists in ds1520+_host.db
CT1000P3PSSD8 already exists in ds1520+_host.db.new

Support disk compatibility already enabled.

Support memory compatibility already enabled.

NVMe support already enabled.

M.2 volume support already enabled.

Drive db auto updates already disabled.

DSM successfully checked disk compatibility.

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

[007revad]

In my experience the "Unrecognized firmware version, please update the drive database." warning normally occurs if:

1. Storage Manager needs to be closed and reopened.
2. Drive db auto updates are enabled and DSM updated the drive database after the script was run.
3. Unknown vendor.
4. Drive is in a PCIe card and drive was not added to card's db file.
5. Drive is in an expansion unit and drive was not added to ebox's db file.
6. There are db files left over from DSM 6.

What does the following command return?

ls /var/lib/disk-compatibility/ds1520+_host*.db

Try running Synology_HDD_db with no options then:

1. Close and reopen Storage Manager.
2. Click on HDD/SSD > Settings > Advanced.
3. Scroll down to Drive Database and click Update Now.
4. Run Synology_HDD_db with the -n option.
5. Close and reopen Storage Manager and check if the warning is gone.

[007revad]

@R-a-K-i

What surprises me is that everything works so far. I can create a volume and also activate deduplication.

I have no idea why everything is working when you're still seeing the "Unrecognized firmware version" warning.

Where is that image from? Is that Active Insight?

My HDD/SS section in Storage Manager looks like this:

[R-a-K-i]

All images are from the Storage Manager:

[jeprojects]

Running ls /var/lib/disk-compatibility/ds1520+_host*.db

/var/lib/disk-compatibility/ds1520+_host.db  /var/lib/disk-compatibility/ds1520+_host_v7.db

Would this mean there is an old v6 db left over?

I also tried your 5 steps listed above and it still shows the warning.

[007revad]

Yes, there'd be a lot of v6 db files left over from DSM 6.

Try:

sudo rm /var/lib/disk-compatibility/ds1520+_host.db

Then close and reopen storage manager.

[cb12tre]

I also have the same problem with a SOLIDIGM drive. In the file syno_hdd_vendor_ids.txt, I had to add a line 0x25e="Solidigm" because my SSD was recognized with this code and not as 0x025e="Solidigm". Now the brand is recognized, but the message "Unrecognized firmware" still appears.

This is the output of the command syno_hdd_db.sh -s

Synology_HDD_db v3.5.93
DS920+ DSM 7.2.1-69057-5
StorageManager 1.0.0-0017

ds920+_host_v7 version 8052

ds920+_host version 4021

Using options: -s
Running from: /volume1/homes/giorgio-admin/scripts/Synology_HDD/syno_hdd_db.sh

HDD/SSD models found: 2
WD60EFRX-68L0BN1,82.00A82
WD60EFZX-68B3FN0,81.00A81

M.2 drive models found: 1
SOLIDIGM SSDPFKNU512GZH,HPS3

No M.2 PCIe cards found

No Expansion Units found

WD60EFRX-68L0BN1 already exists in ds920+_host_v7.db
WD60EFRX-68L0BN1 already exists in ds920+_host.db
WD60EFRX-68L0BN1 already exists in ds920+_host.db.new
WD60EFZX-68B3FN0 already exists in ds920+_host_v7.db
WD60EFZX-68B3FN0 already exists in ds920+_host.db
WD60EFZX-68B3FN0 already exists in ds920+_host.db.new
SOLIDIGM SSDPFKNU512GZH already exists in ds920+_host_v7.db
SOLIDIGM SSDPFKNU512GZH already exists in ds920+_host.db
SOLIDIGM SSDPFKNU512GZH already exists in ds920+_host.db.new

Support disk compatibility already enabled.

Support memory compatibility already enabled.

NVMe support already enabled.

M.2 volume support already enabled.

Re-enabled drive db auto updates.

SOLIDIGM SSDPFKNU512GZH:
{
  "HPS3": {
    "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
      }
    ]
  }
}

WD60EFRX-68L0BN1:
{
  "82.00A82": {
    "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
      }
    ]
  }
}

WD60EFZX-68B3FN0:
{
  "81.00A81": {
    "size_gb": 6000,
    "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": 6000,
    "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.

Regards, Gio.

[007revad]

I see a few potential issues.

You didn't run the syno_hdd_db with the -n option to prevent DSM updating the drive database.

ds920+_host_v7 version 8052 ds920+_host version 4021

Your DS920+ appears to have been running DSM 6 in the past. I can't tell if DSM would be using the old ds920+_host.db file or the ds920+_host_v7.db file.

What do the following commands return:

ls /dev/sata*
ls /dev/sd*

I notice WD60EFZX-68B3FN0 has size_gb. I'll have to check if this was added in DSM 7.2.1 update 5.

WD60EFZX-68B3FN0:
{
  "81.00A81": {
    "size_gb": 6000,

[007revad]

Okay, it's not DSM 7.2.1 update 5. It's the newer host db version.

I notice there's also:

"barebone_installable_v2": "auto",

I'll add size_gb and "barebone_installable_v2": "auto"

[cb12tre]

I confirm that version 6 of DSM was installed in the past. This is the result of the two ls commands:

ls /dev/sata*
/dev/sata1  /dev/sata1p1  /dev/sata1p2  /dev/sata1p5  /dev/sata2  /dev/sata2p1  /dev/sata2p2  /dev/sata2p5
ls /dev/sd*
ls: cannot access '/dev/sd*': No such file or directory

The first time I ran the syno_hdd_db command without the -n option, then later I ran it with the -n option and scheduled it as a shutdown task for the NAS:

The WD60EFZX-68B3FN0 drives are not giving any problems; I've been using them since before using this script.

[007revad]

Delete ds920+_host.db and ds920+_host.db.new

sudo rm /var/lib/disk-compatibility_ ds920+_host.db
sudo rm /var/lib/disk-compatibility_ ds920+_host.db.new

Then delete "volume1/homes/scripts/Synology_HDD/syno_hdd-db.sh -n" from the shutdown task.

Next create bootup task with "volume1/homes/scripts/Synology_HDD/syno_hdd-db.sh -n".

Then reboot.

The WD60EFZX-68B3FN0 is fine. It's the WD60EFRX-68L0BN1 and more importantly the SOLIDIGM SSDPFKNU512GZH that are missing 2 new lines that Synology seem to have been added in host_v7 version 8052:

"size_gb":
"barebone_installable_v2": "auto"

I've almost finished updating the script to include size_gb and barebone_installable_v2 but I have to test it before releasing it.

[cb12tre]

Do I also put syno_enable_m2_volume.sh as a task on boot or leave it on shutdown?

[007revad]

Leave syno_enable_m2_volume.sh as a shutdown task.

But also leave the syno_enable_m2_volume.sh shutdown task disabled for now. You should not need it with a DS920+ running DSM 7.2.1.

[cb12tre]

I deleted the two files, this is the contents of the directory now:

ls -l /var/lib/disk-compatibility/ds920*
-rw-r--r-- 1 root root     50 Oct 12  2021 /var/lib/disk-compatibility/ds920+_e10m20-t1_v7.db
-rw-r--r-- 1 root root      8 Sep 23  2021 /var/lib/disk-compatibility/ds920+_e10m20-t1_v7.release
-rw-r--r-- 1 root root      4 Oct 12  2021 /var/lib/disk-compatibility/ds920+_e10m20-t1_v7.version
-rw-r--r-- 1 root root  12096 Sep 14  2021 /var/lib/disk-compatibility/ds920+_host.db.bak
-rw-r--r-- 1 root root  12362 Sep 14  2021 /var/lib/disk-compatibility/ds920+_host.db.new.bak
-rw-r--r-- 1 root root      8 Sep 14  2021 /var/lib/disk-compatibility/ds920+_host.release
-rw-r--r-- 1 root root 128905 Jul 10 09:33 /var/lib/disk-compatibility/ds920+_host_v7.db
-rw-r--r-- 1 root root 112928 May  4 10:05 /var/lib/disk-compatibility/ds920+_host_v7.db.bak
-rw-r--r-- 1 root root      8 Oct  3  2023 /var/lib/disk-compatibility/ds920+_host_v7.release
-rw-r--r-- 1 root root      4 May  4 10:05 /var/lib/disk-compatibility/ds920+_host_v7.version
-rw-r--r-- 1 root root      4 Sep 14  2021 /var/lib/disk-compatibility/ds920+_host.version
-rw-r--r-- 1 root root     50 Oct 12  2021 /var/lib/disk-compatibility/ds920+_m2d17_v7.db
-rw-r--r-- 1 root root      8 Sep 23  2021 /var/lib/disk-compatibility/ds920+_m2d17_v7.release
-rw-r--r-- 1 root root      4 Oct 12  2021 /var/lib/disk-compatibility/ds920+_m2d17_v7.version
-rw-r--r-- 1 root root     50 Oct 12  2021 /var/lib/disk-compatibility/ds920+_m2d18_v7.db
-rw-r--r-- 1 root root      8 Sep 23  2021 /var/lib/disk-compatibility/ds920+_m2d18_v7.release
-rw-r--r-- 1 root root      4 Oct 12  2021 /var/lib/disk-compatibility/ds920+_m2d18_v7.version
-rw-r--r-- 1 root root     50 Oct 12  2021 /var/lib/disk-compatibility/ds920+_m2d20_v7.db
-rw-r--r-- 1 root root      8 Sep 23  2021 /var/lib/disk-compatibility/ds920+_m2d20_v7.release
-rw-r--r-- 1 root root      4 Oct 12  2021 /var/lib/disk-compatibility/ds920+_m2d20_v7.version

This is the result of running the script at boot:

Synology_HDD_db v3.5.93
DS920+ DSM 7.2.1-69057-5
StorageManager 1.0.0-0017

ds920+_host_v7 version 8052

ds920+_host version 4021

Using options: -n
Running from: /volume1/homes/scripts/Synology_HDD/syno_hdd_db.sh

HDD/SSD models found: 2
WD60EFRX-68L0BN1,82.00A82
WD60EFZX-68B3FN0,81.00A81

M.2 drive models found: 1
SOLIDIGM SSDPFKNU512GZH,HPS3

No M.2 PCIe cards found

No Expansion Units found

WD60EFRX-68L0BN1 already exists in ds920+_host_v7.db
WD60EFZX-68B3FN0 already exists in ds920+_host_v7.db
SOLIDIGM SSDPFKNU512GZH already exists in ds920+_host_v7.db

Support disk compatibility already enabled.

Support memory compatibility already enabled.

NVMe support already enabled.

M.2 volume support already enabled.

Drive db auto updates already disabled.

DSM successfully checked disk compatibility.

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

Storage manager still reports "Unrecognized firmware"

[007revad]

Was storage manager already open? If yes, then close and reopen storage manager.

[cb12tre]

I restarted the NAS to have the script run at startup, so Storage Manager also restarted.

[cb12tre]

Now the volume and the disk are marked as critical. I used this disk on a laptop until last week, and it never caused any problems. Could it be related to the firmware not being recognized?

Later, I'll try to put in another M2 drive to see if the same thing happens.

[007revad]

Unrecognized firmware would not cause the drive to be marked as critical.

You could run https://github.com/007revad/Synology_SMART_info to see why DSM is saying it is critical.

[cb12tre]

Okay, thanks for the help. I have now restarted the NAS and enabled write access to the volume, and it seems to be working normally.

The Synology_SMART_info script shows this result.

Synology_SMART_info v1.1.6 - by 007revad
nas-c DS920+ DSM 7.2.1-69057-5

M.2 Drive 1  SOLIDIGM SSDPFKNU512GZH  PHEH340204TL512A
SMART Error Counter Log:         No Errors Logged
  1 Critical_Warning             0
  2 Temperature                  29 C
  5 Percentage Used              0%
 12 Power On Hours               615
 13 Unsafe Shutdowns             25
 14 Media Errors                 0

Smart Log for NVME device:nvme0n1 namespace-id:ffffffff
critical_warning                    : 0
temperature                         : 29 C
available_spare                     : 100%
available_spare_threshold           : 10%
percentage_used                     : 0%
data_units_read                     : 6,242,505
data_units_written                  : 3,469,406
host_read_commands                  : 65,523,710
host_write_commands                 : 59,868,448
controller_busy_time                : 1,048
power_cycles                        : 5,196
power_on_hours                      : 615
unsafe_shutdowns                    : 25
media_errors                        : 0
num_err_log_entries                 : 72
Warning Temperature Time            : 0
Critical Composite Temperature Time : 0
Temperature Sensor 1                : 0 C
Temperature Sensor 2                : 0 C
Temperature Sensor 3                : 0 C
Temperature Sensor 4                : 0 C
Temperature Sensor 5                : 0 C
Temperature Sensor 6                : 0 C
Temperature Sensor 7                : 0 C
Temperature Sensor 8                : 0 C

The strange thing to me is the 25. "Unsafe Shutdowns"

[007revad]

Only 615 power on hours. It's been used for less than 4 weeks.

I noticed the 25 "Unsafe Shutdowns" too. My NVMe drives have about 5, but it's because I removed the drives while the NAS was powered on.

5,196 power_cycles is an huge amount for a drive with only 615 power on hours. It's as if the NAS continuously power cycled the NVMe drive trying to connect to it.

The 1,048 controller_busy_time is a lot too.

[cb12tre]

This storage device has been connected to the NAS for only a week; previously, it was used on a notebook, so most of the SMART data pertains to that. I believe the 5196 power cycles are related to the notebook's power-saving features.

[007revad]

That makes sense.

Though the 25 "Unsafe Shutdowns" are a concern if you didn't remove the drive while it was powered on 25 times, or maybe the notebook shut down 25 times when it's battery ran too low.

[cb12tre]

Sure, it could have been the laptop running out of battery, as you say. It might be better to compare these results with those from one or two weeks later to determine if there are any actual problems with the disk

[cb12tre]

I connected the new Samsung drive, and it is recognized without any error messages.

The SOLIDIGM, on the other hand, continues to give a firmware warning message. If you want to try to understand why this is happening, I can keep the SOLIDIGM drive connected for a few more days to run some tests before disconnecting it.

Could it be because the drive was recognized as 0x25e instead of 0x025e?

[007revad]

Could it be because the drive was recognized as 0x25e instead of 0x025e?

Yes, definitely. Did the script show you that it was 0x25e ?

Did it always show in Storage Manager as "Solidigm SOLIDIGM SSD SSDPFKNU512GZH"? Or did originally show as "Unknown SOLIDIGM SSD SSDPFKNU512GZH"?

[007revad]

What do the following commands return?

sudo nvme id-ctrl /dev/nvme1 | grep 'vid'
cat /usr/syno/etc/pci_vendor_ids.conf | grep '25e'

And these:

cat /sys/block/nvme1n1/device/firmware_rev
cat /sys/block/nvme1n1/device/rev

[cb12tre]

Yes, originally the disk was recognized as 0x25e and shown as "Unknown". This is what I wrote in my first message two days ago. Maybe you didn't notice it.

I also have the same problem with a SOLIDIGM drive. In the file syno_hdd_vendor_ids.txt, I had to add a line 0x25e="Solidigm" because my SSD was recognized with this code and not as 0x025e="Solidigm". Now the brand is recognized, but the message "Unrecognized firmware" still appears.

This is the result of the commands

giorgio-admin@nas-c:~$ sudo nvme id-ctrl /dev/nvme1 | grep 'vid'
vid     : 0x144d
ssvid   : 0x144d
giorgio-admin@nas-c:~$ cat /usr/syno/etc/pci_vendor_ids.conf | grep '25e'
0x25e="Solidigm"
giorgio-admin@nas-c:~$ cat /sys/block/nvme1n1/device/firmware_rev
EL1QFXV7
giorgio-admin@nas-c:~$ cat /sys/block/nvme1n1/device/rev
cat: /sys/block/nvme1n1/device/rev: No such file or directory

[cb12tre]

I've noticed that the data pertains to Samsung; these should be the ones you're interested in.

giorgio-admin@nas-c:/dev$ sudo nvme id-ctrl /dev/nvme0 | grep 'vid'
vid     : 0x25e
ssvid   : 0x25e
giorgio-admin@nas-c:/dev$ cat /usr/syno/etc/pci_vendor_ids.conf | grep '25e'
0x25e="Solidigm"
giorgio-admin@nas-c:/dev$ cat /sys/block/nvme0n1/device/firmware_rev
HPS3
giorgio-admin@nas-c:/dev$ cat /sys/block/nvme0n1/device/rev
cat: /sys/block/nvme0n1/device/rev: No such file or directory

[007revad]

Try this:

sudo synosetkeyvalue /usr/syno/etc/pci_vendor_ids.conf 0x025e Solidigm
sudo synosetkeyvalue /usr/syno/etc.defaults/pci_vendor_ids.conf 0x025e Solidigm

Then close and reopen storage manager.

[cb12tre]

I still get the same message, I also tried restarting the NAS. Here is the content of the two files if it can be helpful:

giorgio-admin@nas-c:~$ vi /usr/syno/etc.defaults/pci_vendor_ids.conf
0x101c="Western Digital"
0x102f="Toshiba"
0x1042="Micron"
0x104d="Sony"
0x10b5="PLX"
0x10ca="Fujitsu"
0x10cf="Fujitsu"
0x111d="IDT"
0x115f="Maxtor"
0x1179="Toshiba"
0x119e="Fujitsu"
0x11ab="Marvell"
0x11e7="Toshiba"
0x1212="Kingston"
0x126f="Silicon Motion"
0x1344="Micron"
0x13d7="Toshiba"
0x144d="Samsung"
0x14a4="Lite-On/Plextor"
0x151d="Fujitsu"
0x15b7="Sandisk"
0x1734="Fujitsu"
0x177d="Cavium"
0x1aed="SanDisk"
0x1b4b="Marvell"
0x1b85="OCZ"
0x1b96="Western Digital"
0x1bb1="Seagate"
0x1c58="HGST"
0x1c5f="Beijing Memblaze"
0x1cc1="ADATA"
0x1d1d="CNEX Labs"
0x2646="Kingston"
0xc0a9="Crucial"
0x8086="Intel"
0x8087="Intel"
0x25e="Solidigm"
0x025e="Solidigm"

giorgio-admin@nas-c:~$ vi /usr/syno/etc/pci_vendor_ids.conf
0x101c="Western Digital"
0x102f="Toshiba"
0x1042="Micron"
0x104d="Sony"
0x10b5="PLX"
0x10ca="Fujitsu"
0x10cf="Fujitsu"
0x111d="IDT"
0x115f="Maxtor"
0x1179="Toshiba"
0x119e="Fujitsu"
0x11ab="Marvell"
0x11e7="Toshiba"
0x1212="Kingston"
0x126f="Silicon Motion"
0x1344="Micron"
0x13d7="Toshiba"
0x144d="Samsung"
0x14a4="Lite-On/Plextor"
0x151d="Fujitsu"
0x15b7="Sandisk"
0x1734="Fujitsu"
0x177d="Cavium"
0x1aed="SanDisk"
0x1b4b="Marvell"
0x1b85="OCZ"
0x1b96="Western Digital"
0x1bb1="Seagate"
0x1c58="HGST"
0x1c5f="Beijing Memblaze"
0x1cc1="ADATA"
0x1d1d="CNEX Labs"
0x2646="Kingston"
0xc0a9="Crucial"
0x8086="Intel"
0x8087="Intel"
0x25e="Solidigm"
0x025e="Solidigm"

[007revad]

I still get the same message, I also tried restarting the NAS.

That's disappointing.

Try running the script with the -f or --force option (as well as -n). So syno_hdd_db.sh -nf

[cb12tre]

Still the same, the firmware message always appears.

[007revad]

Can you try the following:

1. Run syno_hdd_db without the -n or --noupdate option.
2. Update the drive database from "Storage Manager > HDD/SSD > Settings > Advanced > Update Now".
3. Download https://github.com/007revad/Synology_HDD_db/releases/tag/v3.5.94-RC
4. Run v3.5.94-RC syno_hdd_db with -n or --noupdate option and the -s or --showedits.
5. Reply with the script's output.

[cb12tre]

giorgio-admin@nas-c:~/scripts/Synology_HDD$ sudo -s ./syno_hdd_db.sh
Synology_HDD_db v3.5.93
DS920+ DSM 7.2.1-69057-5
StorageManager 1.0.0-0017

ds920+_host_v7 version 8052

ds920+_host version 4021

Running from: /volume1/homes/giorgio-admin/scripts/Synology_HDD/syno_hdd_db.sh

HDD/SSD models found: 2
WD60EFRX-68L0BN1,82.00A82
WD60EFZX-68B3FN0,81.00A81

M.2 drive models found: 2
SAMSUNG MZALQ512HALU-000L1,EL1QFXV7
SOLIDIGM SSDPFKNU512GZH,HPS3

No M.2 PCIe cards found

No Expansion Units found

WD60EFRX-68L0BN1 already exists in ds920+_host_v7.db
WD60EFZX-68B3FN0 already exists in ds920+_host_v7.db
SAMSUNG MZALQ512HALU-000L1 already exists in ds920+_host_v7.db
SOLIDIGM SSDPFKNU512GZH already exists in ds920+_host_v7.db

Support disk compatibility already enabled.

Support memory compatibility already enabled.

NVMe support already enabled.

M.2 volume support already enabled.

Re-enabled drive db auto updates.

DSM successfully checked disk compatibility.

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

I tried to update the database from Storage Manager but this message appears:

I also tried to download the update file and do it manually but this message appears:

However, I have loaded and executed your new script:

giorgio-admin@nas-c:~/scripts/Synology_HDD_db-3.5.94-RC$ sudo -s ./syno_hdd_db.sh -ns
Password:
Synology_HDD_db v3.5.93
DS920+ DSM 7.2.1-69057-5
StorageManager 1.0.0-0017

ds920+_host_v7 version 8052

ds920+_host version 4021

Using options: -ns
Running from: /volume1/homes/giorgio-admin/scripts/Synology_HDD_db-3.5.94-RC/syno_hdd_db.sh

HDD/SSD models found: 2
WD60EFRX-68L0BN1,82.00A82,6000
WD60EFZX-68B3FN0,81.00A81,6000

M.2 drive models found: 2
SAMSUNG MZALQ512HALU-000L1,EL1QFXV7,512
SOLIDIGM SSDPFKNU512GZH,HPS3,512

No M.2 PCIe cards found

No Expansion Units found

WD60EFRX-68L0BN1 already exists in ds920+_host_v7.db
WD60EFZX-68B3FN0 already exists in ds920+_host_v7.db
SAMSUNG MZALQ512HALU-000L1 already exists in ds920+_host_v7.db
SOLIDIGM SSDPFKNU512GZH already exists in ds920+_host_v7.db

Support disk compatibility already enabled.

Support memory compatibility already enabled.

NVMe support already enabled.

M.2 volume support already enabled.

Disabled drive db auto updates.

SAMSUNG MZALQ512HALU-000L1:
{
  "EL1QFXV7": {
    "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
      }
    ]
  }
}

SOLIDIGM SSDPFKNU512GZH:
{
  "HPS3": {
    "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
      }
    ]
  }
}

WD60EFRX-68L0BN1:
{
  "82.00A82": {
    "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
      }
    ]
  }
}

WD60EFZX-68B3FN0:
{
  "81.00A81": {
    "size_gb": 6000,
    "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": 6000,
    "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.

I disabled the automatic restart scheduling, otherwise it would have run the old script, and I restarted the NAS. The same message about the firmware still appears. 😞

[007revad]

I just downloaded and unpacked the Synology HDD/SSD Offline Update Pack for the DS920+

It contains v7 host db files for 3 different models, each with a different version:

• DS923+ v8041
• DS920+ v8052
• DS918+ v8046

My DS1821+ has v8054

Run these commands:

sudo -i
rm  /var/lib/disk-compatibility/ds920+_host.version
rm  /var/lib/disk-compatibility/ds920+_host.release
rm  /var/lib/disk-compatibility/ds920+_host.db.bak
echo -n 8000 > /var/lib/disk-compatibility/ds920+_host_v7.version
echo -n 20230101 > /var/lib/disk-compatibility/ds920+_host_v7.release
synosetkeyvalue /etc/synoinfo.conf support_disk_compatibility yes
synosetkeyvalue /etc.defaults/synoinfo.conf support_disk_compatibility yes

Then download the latest Synology HDD/SSD Offline Update Pack for the DS920+ near the bottom of this page: https://www.synology.com/en-global/support/download/DS920+?version=7.2#system and do a Manual Install in Package Center.

Finally download this new https://github.com/007revad/Synology_HDD_db/releases/tag/v3.5.94 version and run it with the -ns options.

If Storage manager is already open, close it an reopen it.

[R-a-K-i]

I wanted to reinstall the drive database to start from scratch. The following steps solved my problem by chance:

sudo -s syno_hdd_db.sh --restore rm -R /var/lib/disk-compatibility/* syno_dsm_reinstall.sh reboot Reinstall latest firmware with the current settings

After these steps, no more warnings are displayed:

This is really strange. The drives are no longer listed in the compatibility list.

disk-compatibility.zip

Can anyone explain this?

[007revad]

@R-a-K-i

This is interesting.

That probably worked for you because the DS932+ already supports M.2 volumes and your NVMe volume already existed.

I notice you previously had ds923+_host_v7.db version 8041 and you now have an older version 8028

The difference between the 2 db versions is version 8041 has 2 new keys for each drive in the database:

• size_gb
• barebone_installable_v2

The latest version of the script includes those 2 new keys: https://github.com/007revad/Synology_HDD_db/releases/tag/v3.5.94

But it won't add those keys if the drive model already exists in the db file.

[cb12tre]

I executed these commands without any problems:

sudo -i
rm  /var/lib/disk-compatibility/ds920+_host.version
rm  /var/lib/disk-compatibility/ds920+_host.release
rm  /var/lib/disk-compatibility/ds920+_host.db.bak
echo -n 8000 > /var/lib/disk-compatibility/ds920+_host_v7.version
echo -n 20230101 > /var/lib/disk-compatibility/ds920+_host_v7.release
synosetkeyvalue /etc/synoinfo.conf support_disk_compatibility yes
synosetkeyvalue /etc.defaults/synoinfo.conf support_disk_compatibility yes

Then download the latest Synology HDD/SSD Offline Update Pack for the DS920+ near the bottom of this page: https://www.synology.com/en-global/support/download/DS920+?version=7.2#system and do a Manual Install in Package Center.

When I try to upload the file, I still get this message:

[007revad]

Try this:

sudo -i
synosetkeyvalue /var/packages/SynoOnlinePack_v2/INFO version 744

Then package center should let you install the downloaded SynoOfflinePack

[R-a-K-i]

@007revad You are right. However, the reinstallation brings the old database with it. Even a manual update does not update to version 8041.

[007revad]

What do these commands return?

cat /var/lib/disk-compatibility/ds923+_host_v7.version && echo
cat /var/lib/disk-compatibility/ds923+_host_v7.release && echo

[R-a-K-i]

sh-4.4# cat /var/lib/disk-compatibility/ds923+_host_v7.version && echo 8028 sh-4.4# cat /var/lib/disk-compatibility/ds923+_host_v7.release && echo 20230915 sh-4.4#

[007revad]

That's the version from DSM 7.2.1 (with Update 1).

Interesting that storage manager thinks you have the latest version already.

[cb12tre]

Try this:

sudo -i
synosetkeyvalue /var/packages/SynoOnlinePack_v2/INFO version 744

Then package center should let you install the downloaded SynoOfflinePack

No, same message:

[R-a-K-i]

That's the version from DSM 7.2.1 (with Update 1).

Interesting that storage manager thinks you have the latest version already.

[rylos]

I've the same problem but dedup is ok, just firmware warning. I'm on DS923 7.2.1 update5:

Marco@NAS:/volume2/dev/Synology_HDD_db$ cat /var/lib/disk-compatibility/ds923+_host_v7.release && echo
20230915
Marco@NAS:/volume2/dev/Synology_HDD_db$ cat /var/lib/disk-compatibility/ds923+_host_v7.version && echo
8041

[rylos]

I've made some more tests. If I disable dedupe with syno_enable_dedupe.sh --restore and then reboot my crycial M2 SSD are NOT marked as firmware unknow, all is OK. If i enable dedupe (I actually use syno_enable_dedupe.sh --hdd) when I reboot my crucial M2 SSD get the firmware warning. I've also noticed that with automatic dedupe active on both my volume1 (SSD) and volume2 (HDD) in storage manager I can see only dedupe data for SSD and not for the volume2 HDD, see screen:

Dedupe is active for both volumes:

Will use my docker based "bees" deduplication (https://github.com/Zygo/bees) as before for now, lots of fine tune controls. Who is interested this is my repo with docker for synology: https://github.com/rylos/bees-docker

@007revad