mirror of
https://github.com/007revad/Synology_M2_volume.git
synced 2026-04-26 00:06:14 +03:00
[GH-ISSUE #15] Upgrade DSM test 7.1=> 7.2 with M2 storage pool mounted #199
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#199
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 @aferende on GitHub (Mar 25, 2023).
Original GitHub issue: https://github.com/007revad/Synology_M2_volume/issues/15
Has anyone tested upgrading from 7.1 to 7.2 (now beta) with M2 storage pool already created?
I am in this situation and above the storage pool made with the M2s I have all my VMs.
When the upgrade to version 7.2 (official) comes out I don't want to have any unpleasant surprises.
Thank you
@007revad commented on GitHub (Mar 25, 2023):
I created my M.2 storage pool while on DSM 7.1.1 and after upgrading to DSM 7.2 beta my storage and volume were still there.
I'd still backup anything on the M.2 storage pool just in case.
@aferende commented on GitHub (Mar 25, 2023):
Great news.
Thx!