starred/Synology_M2_volume

Fork 0

mirror of https://github.com/007revad/Synology_M2_volume.git synced 2026-04-25 15:56:06 +03:00

[GH-ISSUE #191] Unable to remove the volume nor the storage pool #243

New issue

Closed

opened 2026-03-12 18:23:30 +03:00 by kerem · 2 comments

kerem commented

2026-03-12 18:23:30 +03:00

Owner

Originally created by @zey0n on GitHub (Mar 7, 2025).
Original GitHub issue: https://github.com/007revad/Synology_M2_volume/issues/191

Hi, thanks for this script. I was able to use the M.2 SSD.

Now, when I try to remove this volume or storage pool using the UI, I get an error and am unable to remove either.

I found an old response suggesting resetting the storage pool using the following command, but even after the script runs successfully, the volume remains as it is:
sudo -i /volume1/media/script/Synology_M2_volume-2.0.30/syno_create_m2_volume.sh --all

I ran it a few times, but the pool is still intact with the old volume and data.
Is there a way to undo what this script does?

Also, for 20+ year onwards models, is this script needed, or can we use Synology_HDD_db script?

Originally created by @zey0n on GitHub (Mar 7, 2025). Original GitHub issue: https://github.com/007revad/Synology_M2_volume/issues/191 Hi, thanks for this script. I was able to use the M.2 SSD. Now, when I try to remove this volume or storage pool using the UI, I get an error and am unable to remove either. I found an old response suggesting resetting the storage pool using the following command, but even after the script runs successfully, the volume remains as it is: `sudo -i /volume1/media/script/Synology_M2_volume-2.0.30/syno_create_m2_volume.sh --all` I ran it a few times, but the pool is still intact with the old volume and data. Is there a way to undo what this script does? Also, for 20+ year onwards models, is this script needed, or can we use [Synology_HDD_db](https://github.com/007revad/Synology_HDD_db) script?

kerem closed this issue

2026-03-12 18:23:35 +03:00

kerem commented

2026-03-12 18:23:41 +03:00

Author

Owner

@007revad commented on GitHub (Mar 7, 2025):

For 20+ year onwards models, you only need the Synology_HDD_db

The easiest solution for you would be:

Shut down the Synology.
Remove the M.2 SSD.
Boot the Synology.
Mute the beep.
Open Storage Manager and delete the missing M.2 storage pool.
Shut down the Synology.
Install the M.2 SSD.
Boot the Synology.
Run run Synology_HDD_db
Create your M.2 storage pool and volume in Storage Manager.

@007revad commented on GitHub (Mar 7, 2025): For 20+ year onwards models, you only need the Synology_HDD_db The easiest solution for you would be: 1. Shut down the Synology. 2. Remove the M.2 SSD. 3. Boot the Synology. 4. Mute the beep. 5. Open Storage Manager and delete the missing M.2 storage pool. 6. Shut down the Synology. 7. Install the M.2 SSD. 8. Boot the Synology. 9. Run run Synology_HDD_db 10. Create your M.2 storage pool and volume in Storage Manager.

kerem commented

2026-03-12 18:23:46 +03:00

Author

Owner

@zey0n commented on GitHub (Mar 7, 2025):

This fixed it!! Thanks

@zey0n commented on GitHub (Mar 7, 2025): This fixed it!! Thanks

No labels

bug

pull-request

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/Synology_M2_volume#243

No description provided.

Rows
Columns