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+ #206
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#206
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!