mirror of
https://github.com/007revad/Synology_M2_volume.git
synced 2026-04-25 15:56:06 +03:00
[GH-ISSUE #173] DSM factory reset did not erase the M2 storage pool #238
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#238
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 @turbamulta on GitHub (Oct 19, 2024).
Original GitHub issue: https://github.com/007revad/Synology_M2_volume/issues/173
Not sure if bug or feature, I'm testing my new DS423+ NAS and have been trying a number of things, included this fantastic script.
After satisfied with my testing I did a factory reset to start clean with the final config. I expected the M2 storage pool to be erased like the rest of SP created by DSM but no, after the setup was completed the M2 storage pool was there, safe and sound.
This kind of reset persistence is kind of scary. How is it possible?
DS423+ with Synology DSM 7.2.2-72806.
WD SN700 with 11150WD firmware, 4k native enabled.
@007revad commented on GitHub (Oct 19, 2024):
It would seem to be bug, or feature, in DSM itself.
Can you run https://github.com/007revad/Synology_HDD_db then reboot and create the M2 storage pool and volume in storage manager. Then reset again and see if DSM deletes the M2 storage pool.
By the way, with a DS423+ you should use Synology_HDD_db instead of Synology_M2_volume
@turbamulta commented on GitHub (Oct 20, 2024):
OK, I'll try that!
Really? I undestood that Synology_M2_volume was the main tool and Synology_HDD_db was to fix the SP after DSM updates plus some extras, seems I got it wrong.
@turbamulta commented on GitHub (Oct 20, 2024):
So I did as explained.
So it seems DSM will not touch the M2 storage pool in a factory reset, it only removes and overwrites the SPs in HDD drives. After factory reset it will just detect the M2 SP it and continue using it. Changes made by Synology_HDD_db are indeed reset.
So it is a you said a DSM thing. TBH I would prefer a factory reset to actually remove everything but has nothing to do with Synology_HDD_db or Synology_M2_volume, the scripts work perfectly.
Thanks for clarifying!
@007revad commented on GitHub (Oct 20, 2024):
Models that officially support M2 volumes can create them in storage manager but they need to think the M2 drives are Synology M2 drives. There is a comparison table showing the differences between syno_hdd_db, syno_m2_volume and syno_enable_m2_volume.
https://github.com/007revad/Synology_enable_M2_volume#how-is-this-different-to-the-synology_m2_volume-script