mirror of
https://github.com/007revad/Synology_enable_M2_volume.git
synced 2026-04-25 21:15:58 +03:00
[GH-ISSUE #57] Unrecognized firmware version still shows after successfully creating volume, then running syno_hdd_db.sh - normal? #8
Labels
No labels
enhancement
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Synology_enable_M2_volume#8
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.
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):
@007revad commented on GitHub (Jun 3, 2023):
Firstly, if you ran the script previously with an earlier version of DSM and then upgraded to DSM 7.2 do NOT run the script with the --restore option. I'm working a fix for the issue that causes.
It does look like you got 1 faulty NVMe drive.
I wonder if DSM sees the NVMe model as "Crucial CT500P3SSD8" instead of just "CT500P3SSD8".
Can you attach a copy of your ds920+_host_v7.db file
sudo -i cp "/var/lib/disk-compatibility/ds920+_host_v7.db" "/volume1/homes/stef/scripts/ds920+_host_v7.db"You could try running the script with: --noupdate --force
@china-alexmercerli commented on GitHub (Jun 4, 2023):
Hi Dave, my English is not very good, so I can only rely on Google Translate.
I have a little problem,
After I used the Synology_enable_M2_volume script, my M2/HDD firmware appeared Unrecognized firmware version, I used sudo -i /path-to-script/syno_hdd_db.sh --noupdate, my 8T HDD and M2 2T are normal, that is The 4T Samsung SATA HDD still has this prompt, is there a way to solve it?
Remark:
NAS: synology DS920+
system: 7.2-64561
@china-alexmercerli commented on GitHub (Jun 4, 2023):
Below is the command output
Synology_HDD_db v2.2.47
DS920+ DSM 7.2-64561
Using options: -noupdate -showedits
HDD/SSD models found: 2
SSD 870 EVO 4TB,3B6Q
ST8000NM017B-2TJ103,SN02
M.2 drive models found: 1
Samsung SSD 970 EVO Plus 2TB,2B2QEXM7
No M.2 cards found
No Expansion Units found
SSD 870 EVO 4TB already exists in ds920+_host_v7.db
ST8000NM017B-2TJ103 already exists in ds920+_host_v7.db
Samsung SSD 970 EVO Plus 2TB already exists in ds920+_host_v7.db
Support disk compatibility already enabled.
Support memory compatibility 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 commented on GitHub (Jun 4, 2023):
Try the options: --noupdate --showedits --force
Can you run drive_info.sh and reply with the output:
https://github.com/007revad/Synology_HDD_db/blob/test/drive_info.sh
@china-alexmercerli commented on GitHub (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'
@007revad commented on GitHub (Jun 4, 2023):
Good work.
I should have noticed that your screenshot showed SVT03B6Q and the command output showed 3B6Q.
Editing the db file with vi is okay.
@thunderstorm654 commented on GitHub (Jun 4, 2023):
Here's the DB file. After zipping up I did try the --force as well but don't think it changed anything!
Thanks :)
ds920+_host_v7.zip
@thunderstorm654 commented on GitHub (Jun 4, 2023):
Also - have a replacement drive for the crashed one coming today. 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?
Thanks.
@007revad commented on GitHub (Jun 4, 2023):
You will be able to do a repair from storage manager in DSM. You don't need to run the script again.
I'll have a look at your ds920+_host_v7.db later.
@thunderstorm654 commented on GitHub (Jun 4, 2023):
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 commented on GitHub (Jun 7, 2023):
Another update - my replacement drive has now also degraded. Same M2 slot (2). Wondering if there's something buggery about this drive model in particular (Crucial P3) or if that M2 slot on my NAS is screwy (never used it before) or if something is unhappy with the SHR raid configuration on DS920 or something else... Any recommendations? I'm thinking of trying another brand - the performance of Plex is so much better on the SSDs I can't face going back to HDD, but I can't keep replacing drives every few days..!
Thanks.
@thunderstorm654 commented on GitHub (Jun 7, 2023):
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!
@007revad commented on GitHub (Jun 7, 2023):
After reading the comments to your post on reddit I'm glad I didn't buy any Crucial NVMe drives when I bought memory from Crucial.
@thunderstorm654 commented on GitHub (Jun 7, 2023):
I know right 🤣 to be honest, it's put me off their RAM too as that was next on my list, but hopefully, that's different (!).
@007revad commented on GitHub (Jun 7, 2023):
I've had no problem with their RAM. I bought 2x 16GB ECC RAM from Crucial for my DS1821+ (which was actually Micron RAM) and 4GB of Crucial RAM for my Asustor.
I did look at their NVMe drives at the same time but I was turned off by the specs and because it was TLC.