mirror of
https://github.com/007revad/Synology_M2_volume.git
synced 2026-04-26 00:06:14 +03:00
[GH-ISSUE #70] Synology NAS DS1019+ DSM 7.2-64570 Update-1 support #216
Labels
No labels
bug
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Synology_M2_volume#216
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 @totsamyroma on GitHub (Jul 12, 2023).
Original GitHub issue: https://github.com/007revad/Synology_M2_volume/issues/70
Hi
My M2 Samsung SSD 970 EVO Plus 500GB Pool stopped working after an update to DSM 7.2-64570.
It was created on older DSM 7.2-64561.
Since I can't roll back to the older one, is there any workaround to fix M2 pool?
Thanks
@totsamyroma commented on GitHub (Jul 12, 2023):
@totsamyroma commented on GitHub (Jul 12, 2023):
@007revad commented on GitHub (Jul 12, 2023):
Run the https://github.com/007revad/Synology_HDD_db script with the -fn options.
Ideally you should setup a schedule that runs at boot-up and runs the Synology_HDD_db script - so after a DSM update you won't have to remember to run it again. https://github.com/007revad/Synology_HDD_db/blob/main/how_to_schedule.md
@007revad commented on GitHub (Jul 12, 2023):
If the Synology_HDD_db script on it's own doesn't solve your problem you can also run the https://github.com/007revad/Synology_enable_M2_volume script.
And setup both scripts to run from the same schedule: https://github.com/007revad/Synology_enable_M2_volume/blob/main/how_to_schedule.md
@totsamyroma commented on GitHub (Jul 12, 2023):
@007revad it worked! 👍
Thank you for your rapid response 🙏