mirror of
https://github.com/007revad/Synology_enable_M2_volume.git
synced 2026-04-25 13:05:54 +03:00
[GH-ISSUE #57] Unrecognized firmware version still shows after successfully creating volume, then running syno_hdd_db.sh - normal? #205
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#205
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):