[GH-ISSUE #57] Unrecognized firmware version still shows after successfully creating volume, then running syno_hdd_db.sh - normal? #205

Closed
opened 2026-03-11 06:20:52 +03:00 by kerem · 0 comments
Owner

Originally created by @thunderstorm654 on GitHub (Jun 3, 2023).
Original GitHub issue: https://github.com/007revad/Synology_enable_M2_volume/issues/57

Successfully used this script to create a SHR pool with two new drives a couple of days ago. I ran the syno_hdd_db.sh script after, which got rid of the general drive warning, but noticed it still shows a message about unrecognized firmware - is this to be expected? It doesn't ping me any notifications about it, just shows in the HDD/SSD page in Storage Manager.

image

On another note, as you can see above, one of my drives has already crashed in the pool. This is a 3 day old drive ha ha! I'm assuming I just got a dud drive, but thought I'd mention that as well anyway in case you've heard of this happening at all when creating these volumes on 'unsupported' models. Thanks for the awesome work btw :)

Edit: the output from the db update script is as follows (I've done a reboot a couple times past few days and scheduled it also):

nas-ds920:~$ sudo -i "/volume1/homes/stef/scripts/syno_hdd_db.sh" --noupdate                               Password:
Synology_HDD_db v2.2.47
DS920+ DSM 7.2-64561
Using options: --noupdate

HDD/SSD models found: 2
WD160EDFZ-11AFWA0,0A81
WD160EDGZ-11B2DA0,0A85

M.2 drive models found: 1
CT500P3SSD8,P9CR30A

No M.2 cards found

No Expansion Units found

Added WD160EDFZ-11AFWA0 to ds920+_host_v7.db
Added WD160EDGZ-11B2DA0 to ds920+_host_v7.db
Added CT500P3SSD8 to ds920+_host_v7.db

Support disk compatibility already enabled.

Support memory compatibility already enabled.

M.2 volume support already enabled.

Disabled drive db auto updates.

DSM successfully checked disk compatibility.

You may need to reboot the Synology to see the changes.
Originally created by @thunderstorm654 on GitHub (Jun 3, 2023). Original GitHub issue: https://github.com/007revad/Synology_enable_M2_volume/issues/57 Successfully used this script to create a SHR pool with two new drives a couple of days ago. I ran the syno_hdd_db.sh script after, which got rid of the general drive warning, but noticed it still shows a message about unrecognized firmware - is this to be expected? It doesn't ping me any notifications about it, just shows in the HDD/SSD page in Storage Manager. ![image](https://github.com/007revad/Synology_enable_M2_volume/assets/16837607/45a0d9d5-4e11-4c06-a3fb-2f528d565a0b) On another note, as you can see above, one of my drives has already crashed in the pool. This is a 3 day old drive ha ha! I'm assuming I just got a dud drive, but thought I'd mention that as well anyway in case you've heard of this happening at all when creating these volumes on 'unsupported' models. Thanks for the awesome work btw :) Edit: the output from the db update script is as follows (I've done a reboot a couple times past few days and scheduled it also): ``` nas-ds920:~$ sudo -i "/volume1/homes/stef/scripts/syno_hdd_db.sh" --noupdate Password: Synology_HDD_db v2.2.47 DS920+ DSM 7.2-64561 Using options: --noupdate HDD/SSD models found: 2 WD160EDFZ-11AFWA0,0A81 WD160EDGZ-11B2DA0,0A85 M.2 drive models found: 1 CT500P3SSD8,P9CR30A No M.2 cards found No Expansion Units found Added WD160EDFZ-11AFWA0 to ds920+_host_v7.db Added WD160EDGZ-11B2DA0 to ds920+_host_v7.db Added CT500P3SSD8 to ds920+_host_v7.db Support disk compatibility already enabled. Support memory compatibility already enabled. M.2 volume support already enabled. Disabled drive db auto updates. DSM successfully checked disk compatibility. You may need to reboot the Synology to see the changes. ```
kerem closed this issue 2026-03-11 06:20:58 +03:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/Synology_enable_M2_volume#205
No description provided.