[GH-ISSUE #114] Still getting the Firmware message :(

kerem commented

2026-03-11 11:52:40 +03:00

Owner

Originally created by @ghost on GitHub (Jul 9, 2023).
Original GitHub issue: https://github.com/007revad/Synology_HDD_db/issues/114

Hi there,

awesome scripts - thank you for your work! I was successful in activating my Crucial NVME SSD for pool storage on my DS920+.
However I do it, though, I still get the following error message:

What can I do about that? Other than that, everything is working fine, so it's not the end of the world. But would be nice to get it fixed. :)

Thank you again!!!

Originally created by @ghost on GitHub (Jul 9, 2023). Original GitHub issue: https://github.com/007revad/Synology_HDD_db/issues/114 Hi there, awesome scripts - thank you for your work! I was successful in activating my Crucial NVME SSD for pool storage on my DS920+. However I do it, though, I still get the following error message: <img width="728" alt="Bildschirmfoto 2023-07-09 um 15 02 19" src="https://github.com/007revad/Synology_HDD_db/assets/139054748/1cb5a029-2dd5-4119-a30e-6b2560fe36e2"> What can I do about that? Other than that, everything is working fine, so it's not the end of the world. But would be nice to get it fixed. :) Thank you again!!!

kerem closed this issue

2026-03-11 11:52:45 +03:00

kerem commented

2026-03-11 11:52:51 +03:00

Author

Owner

@007revad commented on GitHub (Jul 10, 2023):

What does the following command return:
sudo -i jq . /var.defaults/lib/disk-compatibility/ds920+_host_v7.db | grep -A 1 CT500P3PSSD8

@007revad commented on GitHub (Jul 10, 2023): What does the following command return: `sudo -i jq . /var.defaults/lib/disk-compatibility/ds920+_host_v7.db | grep -A 1 CT500P3PSSD8`

kerem commented

2026-03-11 11:52:56 +03:00

Author

Owner

@ghost commented on GitHub (Jul 10, 2023):

So I executed the mentioned command and the output.log is completely empty. Am I doing that wrong or is that plausible?

@ghost commented on GitHub (Jul 10, 2023): So I executed the mentioned command and the output.log is completely empty. Am I doing that wrong or is that plausible?

kerem commented

2026-03-11 11:53:01 +03:00

Author

Owner

@007revad commented on GitHub (Jul 10, 2023):

Try this version: https://github.com/007revad/Synology_HDD_db/releases/tag/v3.1.60-RC

@007revad commented on GitHub (Jul 10, 2023): Try this version: https://github.com/007revad/Synology_HDD_db/releases/tag/v3.1.60-RC

kerem commented

2026-03-11 11:53:06 +03:00

Author

Owner

@ghost commented on GitHub (Jul 10, 2023):

Issue persists. Executed the script multiple times and restarted the NAS. Firmware message remains.
The grep command still gives me an empty log-file.

@ghost commented on GitHub (Jul 10, 2023): Issue persists. Executed the script multiple times and restarted the NAS. Firmware message remains. The grep command still gives me an empty log-file.

kerem commented

2026-03-11 11:53:11 +03:00

Author

Owner

@007revad commented on GitHub (Jul 10, 2023):

Can you run the script again with the -snf options syno_hdd_db.sh -snf them copy the output and paste it in your reply.

@007revad commented on GitHub (Jul 10, 2023): Can you run the script again with the -snf options `syno_hdd_db.sh -snf` them copy the output and paste it in your reply.

kerem commented

2026-03-11 11:53:16 +03:00

Author

Owner

@ghost commented on GitHub (Jul 10, 2023):

Synology_HDD_db v3.1.60
DS920+ DSM 7.2-64570-1
Using options: -snf

HDD/SSD models found: 3
ST16000NM000J-2TW103,SCE2
ST4000VN008-2DR166,SC60
WD40EFPX-68C6CN0,81.00A81

M.2 drive models found: 1
CT500P3PSSD8,P9CR40A

No M.2 PCIe cards found

No Expansion Units found

[0;33mST16000NM000J-2TW103[0m already exists in [0;36mds920+_host.db[0m
[0;33mST16000NM000J-2TW103[0m already exists in [0;36mds920+_host_v7.db[0m
[0;33mST16000NM000J-2TW103[0m already exists in [0;36mds920+_host_v7.db.new[0m
[0;33mST16000NM000J-2TW103[0m already exists in [0;36mds920+_host.db.new[0m
[0;33mST4000VN008-2DR166[0m already exists in [0;36mds920+_host.db[0m
[0;33mST4000VN008-2DR166[0m already exists in [0;36mds920+_host_v7.db[0m
[0;33mST4000VN008-2DR166[0m already exists in [0;36mds920+_host_v7.db.new[0m
[0;33mST4000VN008-2DR166[0m already exists in [0;36mds920+_host.db.new[0m
[0;33mWD40EFPX-68C6CN0[0m already exists in [0;36mds920+_host.db[0m
[0;33mWD40EFPX-68C6CN0[0m already exists in [0;36mds920+_host_v7.db[0m
[0;33mWD40EFPX-68C6CN0[0m already exists in [0;36mds920+_host_v7.db.new[0m
[0;33mWD40EFPX-68C6CN0[0m already exists in [0;36mds920+_host.db.new[0m
[0;33mCT500P3PSSD8[0m already exists in [0;36mds920+_host.db[0m
[0;33mCT500P3PSSD8[0m already exists in [0;36mds920+_host_v7.db[0m
[0;33mCT500P3PSSD8[0m already exists in [0;36mds920+_host_v7.db.new[0m
[0;33mCT500P3PSSD8[0m already exists in [0;36mds920+_host.db.new[0m

Disabled support disk compatibility.

Support memory compatibility already enabled.

M.2 volume support already enabled.

Drive db auto updates already disabled.

  "model": "ST16000NM000J-2TW103",
  "firmware": "",
  "rec_intvl": [

  "model": "ST4000VN008-2DR166",
  "firmware": "SC60",
  "rec_intvl": [

  "model": "WD40EFPX-68C6CN0",
  "firmware": "",
  "rec_intvl": [

  "model": "CT500P3PSSD8",
  "firmware": "",
  "rec_intvl": [

DSM successfully checked disk compatibility.

You may need to [0;36mreboot the Synology[0m to see the changes.

@ghost commented on GitHub (Jul 10, 2023): Synology_HDD_db v3.1.60 DS920+ DSM 7.2-64570-1 Using options: -snf HDD/SSD models found: 3 ST16000NM000J-2TW103,SCE2 ST4000VN008-2DR166,SC60 WD40EFPX-68C6CN0,81.00A81 M.2 drive models found: 1 CT500P3PSSD8,P9CR40A No M.2 PCIe cards found No Expansion Units found [0;33mST16000NM000J-2TW103[0m already exists in [0;36mds920+_host.db[0m [0;33mST16000NM000J-2TW103[0m already exists in [0;36mds920+_host_v7.db[0m [0;33mST16000NM000J-2TW103[0m already exists in [0;36mds920+_host_v7.db.new[0m [0;33mST16000NM000J-2TW103[0m already exists in [0;36mds920+_host.db.new[0m [0;33mST4000VN008-2DR166[0m already exists in [0;36mds920+_host.db[0m [0;33mST4000VN008-2DR166[0m already exists in [0;36mds920+_host_v7.db[0m [0;33mST4000VN008-2DR166[0m already exists in [0;36mds920+_host_v7.db.new[0m [0;33mST4000VN008-2DR166[0m already exists in [0;36mds920+_host.db.new[0m [0;33mWD40EFPX-68C6CN0[0m already exists in [0;36mds920+_host.db[0m [0;33mWD40EFPX-68C6CN0[0m already exists in [0;36mds920+_host_v7.db[0m [0;33mWD40EFPX-68C6CN0[0m already exists in [0;36mds920+_host_v7.db.new[0m [0;33mWD40EFPX-68C6CN0[0m already exists in [0;36mds920+_host.db.new[0m [0;33mCT500P3PSSD8[0m already exists in [0;36mds920+_host.db[0m [0;33mCT500P3PSSD8[0m already exists in [0;36mds920+_host_v7.db[0m [0;33mCT500P3PSSD8[0m already exists in [0;36mds920+_host_v7.db.new[0m [0;33mCT500P3PSSD8[0m already exists in [0;36mds920+_host.db.new[0m Disabled support disk compatibility. Support memory compatibility already enabled. M.2 volume support already enabled. Drive db auto updates already disabled. "model": "ST16000NM000J-2TW103", "firmware": "", "rec_intvl": [ "model": "ST4000VN008-2DR166", "firmware": "SC60", "rec_intvl": [ "model": "WD40EFPX-68C6CN0", "firmware": "", "rec_intvl": [ "model": "CT500P3PSSD8", "firmware": "", "rec_intvl": [ DSM successfully checked disk compatibility. You may need to [0;36mreboot the Synology[0m to see the changes.

kerem commented

2026-03-11 11:53:22 +03:00

Author

Owner

@ghost commented on GitHub (Jul 10, 2023):

Rebooted the NAS after this and the firmware message still persits.

@ghost commented on GitHub (Jul 10, 2023): Rebooted the NAS after this and the firmware message still persits.

kerem commented

2026-03-11 11:53:27 +03:00

Author

Owner

@007revad commented on GitHub (Jul 10, 2023):

I can see you previously had DSM 6 installed before updating to DSM 7

It's interesting (to me) that the last db file edited was an old DSM 6 file so the script showed edits made to the old ds920+_host.db file instead of the ds920+_host_v7.db file.

If you run this command again what does it output?
sudo -i jq . /var.defaults/lib/disk-compatibility/ds920+_host_v7.db | grep -A 1 CT500P3PSSD8

@007revad commented on GitHub (Jul 10, 2023): I can see you previously had DSM 6 installed before updating to DSM 7 It's interesting (to me) that the last db file edited was an old DSM 6 file so the script showed edits made to the old ds920+_host.db file instead of the ds920+_host_v7.db file. If you run this command again what does it output? `sudo -i jq . /var.defaults/lib/disk-compatibility/ds920+_host_v7.db | grep -A 1 CT500P3PSSD8`

kerem commented

2026-03-11 11:53:32 +03:00

Author

Owner

@ghost commented on GitHub (Jul 10, 2023):

Yea, that's correct. I upgraded from DSM 6 to 7 RC and then to the final version.
The log is empty for sudo -i jq . /var.defaults/lib/disk-compatibility/ds920+_host_v7.db | grep -A 1 CT500P3PSSD8

@ghost commented on GitHub (Jul 10, 2023): Yea, that's correct. I upgraded from DSM 6 to 7 RC and then to the final version. The log is empty for sudo -i jq . /var.defaults/lib/disk-compatibility/ds920+_host_v7.db | grep -A 1 CT500P3PSSD8

kerem commented

2026-03-11 11:53:37 +03:00

Author

Owner

@ghost commented on GitHub (Jul 10, 2023):

Tried the same for the non-"v7".db:
jq: error: Could not open file /var.defaults/lib/disk-compatibility/ds920+_host.db: No such file or directory

@ghost commented on GitHub (Jul 10, 2023): Tried the same for the non-"v7".db: jq: error: Could not open file /var.defaults/lib/disk-compatibility/ds920+_host.db: No such file or directory

kerem commented

2026-03-11 11:53:42 +03:00

Author

Owner

@007revad commented on GitHub (Jul 10, 2023):

I'm assuming you have home folders enabled on your Synology.

Do NOT run the following as root. Run them as an admin or user.

Can you run these 2 commands:

mkdir $HOME/var.defaults
sudo -i cp /var.defaults/lib/disk-compatibility/* $HOME/var.defaults/

Then run these 2 commands:

mkdir $HOME/var
sudo -i cp /var/lib/disk-compatibility/* $HOME/var/

Then go to your home folder and zip or tar the var.defaults and var folders and attach the zip or tar files to your reply.

@007revad commented on GitHub (Jul 10, 2023): I'm assuming you have home folders enabled on your Synology. Do NOT run the following as root. Run them as an admin or user. Can you run these 2 commands: ``` mkdir $HOME/var.defaults sudo -i cp /var.defaults/lib/disk-compatibility/* $HOME/var.defaults/ ``` Then run these 2 commands: ``` mkdir $HOME/var sudo -i cp /var/lib/disk-compatibility/* $HOME/var/ ``` Then go to your home folder and zip or tar the **var.defaults** and **var** folders and attach the zip or tar files to your reply.

kerem commented

2026-03-11 11:53:47 +03:00

Author

Owner

@ghost commented on GitHub (Jul 10, 2023):

So I've been executing all of those commands via task scheduler. I haven't been able to do this with your latest commands.
Could you please let me know how to do that there? Just copying these commands there and executing results in no "var" folder being created in the HOMES-folder, nor in the specific user's folders.

@ghost commented on GitHub (Jul 10, 2023): So I've been executing all of those commands via task scheduler. I haven't been able to do this with your latest commands. Could you please let me know how to do that there? Just copying these commands there and executing results in no "var" folder being created in the HOMES-folder, nor in the specific user's folders.

kerem commented

2026-03-11 11:53:52 +03:00

Author

Owner

@007revad commented on GitHub (Jul 10, 2023):

If your user name in DSM is Yousif you would run the following 4 lines in task scheduler as root:

mkdir /var/services/homes/Yousif/var.defaults 
cp /var.defaults/lib/disk-compatibility/* /var/services/homes/Yousif/var.defaults/
mkdir /var/services/homes/Yousif/var 
cp /var/lib/disk-compatibility/* /var/services/homes/Yousif/var/

Obviously if your user name is not Yousif you'd change Yousif to your user name.

@007revad commented on GitHub (Jul 10, 2023): If your user name in DSM is Yousif you would run the following 4 lines in task scheduler as root: ``` mkdir /var/services/homes/Yousif/var.defaults cp /var.defaults/lib/disk-compatibility/* /var/services/homes/Yousif/var.defaults/ mkdir /var/services/homes/Yousif/var cp /var/lib/disk-compatibility/* /var/services/homes/Yousif/var/ ``` Obviously if your user name is not Yousif you'd change Yousif to your user name.

kerem commented

2026-03-11 11:53:57 +03:00

Author

Owner

@ghost commented on GitHub (Jul 10, 2023):

Got the following output:
cp: -r not specified; omitting directory '/var.defaults/lib/disk-compatibility/rules'
cp: -r not specified; omitting directory '/var/lib/disk-compatibility/rules'

Folders were created, though. PFA

home.zip

@ghost commented on GitHub (Jul 10, 2023): Got the following output: cp: -r not specified; omitting directory '/var.defaults/lib/disk-compatibility/rules' cp: -r not specified; omitting directory '/var/lib/disk-compatibility/rules' Folders were created, though. PFA [home.zip](https://github.com/007revad/Synology_HDD_db/files/12002118/home.zip)

kerem commented

2026-03-11 11:54:02 +03:00

Author

Owner

@007revad commented on GitHub (Jul 11, 2023):

Can you try these commands:

hdmodel=CT500P3PSSD8
sed -i "s/$hdmodel\",\"firmware\":\"/$hdmodel\",\"firmware\":\"P9CR40A/" "/var/lib/disk-compatibility/ds920+_host.db"

Then reboot.

@007revad commented on GitHub (Jul 11, 2023): Can you try these commands: ``` hdmodel=CT500P3PSSD8 sed -i "s/$hdmodel\",\"firmware\":\"/$hdmodel\",\"firmware\":\"P9CR40A/" "/var/lib/disk-compatibility/ds920+_host.db" ``` Then reboot.

kerem commented

2026-03-11 11:54:07 +03:00

Author

Owner

@ghost commented on GitHub (Jul 11, 2023):

Still the same :(

@ghost commented on GitHub (Jul 11, 2023): Still the same :(

kerem commented

2026-03-11 11:54:12 +03:00

Author

Owner

@007revad commented on GitHub (Jul 12, 2023):

Have you previously run the Synology_enable_M2_volume script?

If yes, then run it with the --restore option then reboot. Note: the Synology may take up to 10 minutes to reboot.

@007revad commented on GitHub (Jul 12, 2023): Have you previously run the Synology_enable_M2_volume script? If yes, then run it with the --restore option then reboot. Note: the Synology may take up to 10 minutes to reboot.

Rows
Columns

[GH-ISSUE #114] Still getting the Firmware message :( #545