mirror of
https://github.com/007revad/Synology_enable_M2_volume.git
synced 2026-04-25 21:15:58 +03:00
[GH-ISSUE #53] Confirmed working for DS1019+ #7
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#7
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 @angeloalduino on GitHub (Jun 1, 2023).
Original GitHub issue: https://github.com/007revad/Synology_enable_M2_volume/issues/53
DS1019+ on DSM 7.2-64561
2x WD_BLACK 1TB SN770 m.2 using RAID 1
Question: The docs say
After any DSM update you will need to run this script, and the Synology_HDD_db script again.. Can you clarify what will happen if you don't run the scripts again, and when exactly the scripts should be run (before/after shutdown)? If the scripts are not run and the system reboots with a new version, could it cause data loss? Or would we simply run the scripts again and then the volumes would reappear?Thank you!
@007revad commented on GitHub (Jun 1, 2023):
I'd schedule both to run at boot-up in the same scheduled task. But you can run them via SSH if you prefer. You may have to then reboot once more before you see your M2 volume in storage manager.
@angeloalduino commented on GitHub (Jun 1, 2023):
Thanks @007revad! Would be great to make that clear in the docs so others can be more at ease 👍 Thank you so much for your work!
@Fonta commented on GitHub (Jun 20, 2023):
Also works on 1019+ - DSM 7.2-64570 Update 1
@angeloalduino commented on GitHub (Jun 29, 2023):
I had the script scheduled to run at shutdown and then installed
7.2-64570 Update 1. I'm not sure if it ran but when it came back up, the volume critical warning beep was repeating and it said the cache volume was invalid. I ran the script manually, rebooted again, and then everything came up normally.I'm not sure whether the script is running properly at shutdown but I now enabled the 'Save output results' option in Task Manager to debug this in the future.
In summary: for anyone wondering what happens after a DSM update, it seems scary at first but everything comes back to normal after running the script again 👍
@007revad commented on GitHub (Jun 29, 2023):
Thanks @angeloalduino
After DSM 7.2 was released I changed the readme for my Synology_HDD_db script to say to schedule it to run at boot-up, instead of shutdown, but forgot to change the readme for this script. I have changed it now.
@Oujiii commented on GitHub (May 31, 2025):
Hi @angeloalduino and @Fonta is still working for you? #168 mentions that this is only working for one drive and this is also on the README now.
Thanks.
@Fonta commented on GitHub (May 31, 2025):
@Oujiii I have no issues here.