Crucial CT4000P3SSD8 Unrecognized firmware version #306
Comments
|
Synology_HDD_db v3.5.91 ds923+_host_v7 version 8041 Using options: -s HDD/SSD models found: 1 M.2 drive models found: 1 No M.2 PCIe cards found No Expansion Units found SSD 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: CT4000P3SSD8: DSM successfully checked disk compatibility. You may need to reboot the Synology to see the changes. |
|
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:
|
|
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 
Synology_HDD_db v3.5.91 ds923+_host_v7 version 8041 Using options: -n -s HDD/SSD models found: 1 M.2 drive models found: 1 No M.2 PCIe cards found No Expansion Units found SSD 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: CT4000P3SSD8: DSM successfully checked disk compatibility. The INTENSO SSDs are displayed like this: 
|
|
Happening also with my nvme drives: CT1000P3PSSD8 |
|
In my experience the "Unrecognized firmware version, please update the drive database." warning normally occurs if:
What does the following command return? Try running Synology_HDD_db with no options then:
|
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: |
|
All images are from the Storage Manager: 
|
|
Running 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. |
|
Yes, there'd be a lot of v6 db files left over from DSM 6. Try: Then close and reopen storage manager. |
|
I also have the same problem with a SOLIDIGM drive. This is the output of the command syno_hdd_db.sh -s
Regards, Gio. |
|
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.
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: I notice WD60EFZX-68B3FN0 has size_gb. I'll have to check if this was added in DSM 7.2.1 update 5. |
|
Okay, it's not DSM 7.2.1 update 5. It's the newer host db version. I notice there's also: I'll add size_gb and "barebone_installable_v2": "auto" |
|
I confirm that version 6 of DSM was installed in the past. 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. |
|
Delete ds920+_host.db and 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: I've almost finished updating the script to include |
|
Do I also put syno_enable_m2_volume.sh as a task on boot or leave it on shutdown? |
|
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. |
|
I deleted the two files, this is the contents of the directory now: This is the result of running the script at boot: Storage manager still reports "Unrecognized firmware" |
|
Was storage manager already open? If yes, then close and reopen storage manager. |
|
I restarted the NAS to have the script run at startup, so Storage Manager also restarted. |
|
Now the volume and the disk are marked as critical.
Later, I'll try to put in another M2 drive to see if the same thing happens. |
|
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. |
|
Okay, thanks for the help. The Synology_SMART_info script shows this result. The strange thing to me is the 25. "Unsafe Shutdowns" |
|
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. |
|
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. |
|
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. |
|
Sure, it could have been the laptop running out of battery, as you say. |
|
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. 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"? |
|
What do the following commands return? And these: |
That's disappointing. Try running the script with the -f or --force option (as well as -n). So |
|
Still the same, the firmware message always appears. |
|
Can you try the following:
|
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: I disabled the automatic restart scheduling, otherwise it would have run the old script, and I restarted the NAS. |
|
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:
My DS1821+ has v8054 Run these commands: 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. |
|
I wanted to reinstall the drive database to start from scratch. The following steps solved my problem by chance: sudo -s After these steps, no more warnings are displayed: 
This is really strange. The drives are no longer listed in the compatibility list. Can anyone explain this? |
|
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:
The latest version of the script includes those 2 new keys: But it won't add those keys if the drive model already exists in the db file. |
|
I executed these commands without any problems:
When I try to upload the file, I still get this message: |
|
Try this: Then package center should let you install the downloaded SynoOfflinePack |
|
@007revad 
|
|
What do these commands return? |
|
sh-4.4# cat /var/lib/disk-compatibility/ds923+_host_v7.version && echo |
|
That's the version from DSM 7.2.1 (with Update 1). Interesting that storage manager thinks you have the latest version already. |
No, same message: |
|
|
I've the same problem but dedup is ok, just firmware warning. I'm on DS923 7.2.1 update5: |
|
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. 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 |
|
Nice detective work. Now have something to investigate. I've previously suspected that syno_enable_m2_volume was causing the unrecognized firmware issue. Since syno_enable_m2_volume and syno_enable_dedupe are 99% the same it makes sense that it could cause this issue. I've known about the missing "Deduplication Status" and "Deduplication Savings" for SATA SSDs and HDDs for a while. I previously spent a week trying to fix it but it was too difficult. |
|
@rylos , @jeprojects , @cb12tre , @R-a-K-i For those that are seeing "Unrecognized firmware version" but everything else works as it should can you try this script: If storage manager is already open, close it and open it again. And let me know:
If you have a problem you can run it with a If this works for everyone I'll add it to syno_hdd_db |
|
@007revad thanks for the test script (edit_extjs-patch.zip), I am still getting the "Unrecognized firmware version" |
|
The script 'edit_extjs-patch.zip' doesn't resolve the issue on my device either. |
|
I've got a Crucial NVMe drive arriving tomorrow so I can see if I can reproduce the "Unrecognized firmware version". I fIc an reproduce it it will be a lot easier to fix it. |
|
I had the opportunity to replace the disk with a new one, the same brand (SOLIDIGM) and model but with a capacity of 1 TB, and I still get the same message regarding the firmware. Here are the details if they might be useful to you: SMART DATA: |
|
I have test this HDD.sh on SA6400 7.2-64570 update1-4 and the newest 7.2.1-69057-5：
|
|
I have tried this scripts, https://github.com/007revad/Synology_HDD_db/blob/test/edit_extjs-patch.zip |
|
While running some tests with syno_hdd_db, syno_enable_m2_drive and syno_enable_dedupe I remembered, from 18 months ago, a few people needed to run the syno_hdd_db.sh -n 2 or 3 times before their drives all stopped showed as unverified. Make sure to run |
|
Can you try the following:
|
|
Hello, I've the same issue (unrecognized firmware) on a DS1520+ (DSm 7.2.2-72806 update 1) with 2 Crucial P3 Plus 1To SSD
I'm already with latest version of the script. I've tried to restore all change, manually update the drive DB, I'm still having the issue. It's just cosmetic, everything is working fine otherwise. But if you have a solution, it would be great ! Thanks in advance |
|
I have the same issue with Crucial 1TB M.2 PCIe Gen4 NVMe P3 Plus. Cosmetic but still it would be nice to fix it. :) |
|
Yeah, I've got the same issue with the Crucial P3 Plus 1TB NVMe PCIe 4.0 x4 M.2 ( |
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
}
]
}
}
The text was updated successfully, but these errors were encountered: