mirror of
https://github.com/007revad/Synology_enable_M2_volume.git
synced 2026-04-25 21:15:58 +03:00
[GH-ISSUE #143] Works on my DS 920+ 7.2.1-69057 Update 3 #36
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#36
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 @thetigeregg on GitHub (Jan 7, 2024).
Original GitHub issue: https://github.com/007revad/Synology_enable_M2_volume/issues/143
Meant to update to 7.2.1-69057 Update 1 but got Update 3 instead. Upon first boot after updating DSM, the M2 volume was unrecognized, and DSM was complaining about it. I rebooted again and every was good again. I have a task scheduled to run this script (and the DB script) on shutdown, so that's probably why.
@007revad commented on GitHub (Jan 7, 2024):
DSM has a setting to enable/disable minor updates when installing DSM... but Synology can override the setting if they think the minor update is important. The only way to prevent it is to disconnect your router from the Internet once the DSM update has started (it needs an Internet connection to start the update).
I edited the title to change "me" to "my" for you 😄