Synology_enable_M2_volume: Unrecognized firmware version still shows after successfully creating volume, then running syno_hdd_db.sh - normal?

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.

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.

About this issue

Original URL
State: closed
Created a year ago
Comments: 15 (6 by maintainers)

Most upvoted comments

Come to the conclusion the drives are just not up to the job anyway. Going to try another model, so I’ll close this for now and reopen if run into any issues with the scripts next time Thanks for your support and great work!

thunderstorm654 on Jun 7, 2023

Will I be able to just put it in and do a repair through DSM, or will I need to re-run the volume script?

You will be able to do a repair from storage manager in DSM. You don’t to run the script again.

I’ll have a look at your ds920+_host_v7.db later.

Awesome, it let me repair the volume immediately and back up and running with two 😃. Had to run the db update script again to get rid of unrecognized drive warning, now just back to the unrecognized firmware note against each.

thunderstorm654 on Jun 4, 2023

@007revad Thank you for your reply

I tried the following options: --noupdate --showedits --force, it still doesn’t work, but I seem to find where the problem is.

The script will change the serial number of my Samsung SATA SSD 4T to 3B6Q, but the serial number displayed in the DSM is SVT03B6Q, so I directly modify the .db file with the vi command and change it to SVT03B6Q. After restarting, the error disappears and it looks normal up.

Is it possible to directly modify it with the vi command, and will there be any risks or failures? If there is no risk, so be it.

The following is the output of the drive_info.sh command:

nvme0n1 NVMe Model: ‘Samsung SSD 970 EVO Plus 2TB’ NVMe Model: ‘Samsung SSD 970 EVO Plus 2TB’ NVMe Firmware: ‘2B2QEXM7’ NVMe Firmware: ‘2B2QEXM7’

sata1 Model: ‘SSD’ Firmware: ‘3B6Q’

sata2 Model: ‘ST8000NM017B-2TJ103’ Firmware: ‘SN02’

china-alexmercerli on Jun 4, 2023