[GH-ISSUE #128] ERROR 5 Failed to create syno partitions! #225

Closed
opened 2026-03-12 18:15:24 +03:00 by kerem · 4 comments
Owner

Originally created by @paul0261 on GitHub (Feb 19, 2024).
Original GitHub issue: https://github.com/007revad/Synology_M2_volume/issues/128

Dear Dave Russell,
I used your script on my synology to create my m2 volume pool but it seems to have some errors. I followed all the instructions shown in the README file and the error message is shown below:
error

Originally created by @paul0261 on GitHub (Feb 19, 2024). Original GitHub issue: https://github.com/007revad/Synology_M2_volume/issues/128 Dear Dave Russell, I used your script on my synology to create my m2 volume pool but it seems to have some errors. I followed all the instructions shown in the README file and the error message is shown below: ![error](https://github.com/007revad/Synology_M2_volume/assets/48502415/4d387766-a32c-4106-a19f-f2f770c324ad)
kerem closed this issue 2026-03-12 18:15:29 +03:00
Author
Owner

@007revad commented on GitHub (Feb 19, 2024):

Thanks.

I've fixed that bug in v1.3.24 https://github.com/007revad/Synology_M2_volume/releases/tag/v1.3.24

<!-- gh-comment-id:1952378280 --> @007revad commented on GitHub (Feb 19, 2024): Thanks. I've fixed that bug in v1.3.24 https://github.com/007revad/Synology_M2_volume/releases/tag/v1.3.24
Author
Owner

@paul0261 commented on GitHub (Feb 19, 2024):

Thanks for the quick reply! However, I have tried the newest version but there are still error messages. Please see the error page below. I believed I installed this script probably one year ago but the storage pool callapsed because of the system update. Im not sure whether this information helps.
image

<!-- gh-comment-id:1952398955 --> @paul0261 commented on GitHub (Feb 19, 2024): Thanks for the quick reply! However, I have tried the newest version but there are still error messages. Please see the error page below. I believed I installed this script probably one year ago but the storage pool callapsed because of the system update. Im not sure whether this information helps. ![image](https://github.com/007revad/Synology_M2_volume/assets/48502415/2beab1f8-8cc7-4b7a-a2a4-e6fcb34d3b6b)
Author
Owner

@007revad commented on GitHub (Feb 19, 2024):

You actually don't need syno_m2_volume with a DS1821+ running DSM 7.2.1

Use syno_hdd-db instead. It may actually be able to recover your existing NVMe volume. If not, it will allow you to create the storage pool and volume in storage manager. https://github.com/007revad/Synology_HDD_db

Run it with the -n flag to prevent DSM updating the drive databases.

And schedule it to run at bootup so you don't lose your NVMe volume after a DSM update. https://github.com/007revad/Synology_HDD_db/blob/main/how_to_schedule.md

<!-- gh-comment-id:1952411726 --> @007revad commented on GitHub (Feb 19, 2024): You actually don't need syno_m2_volume with a DS1821+ running DSM 7.2.1 Use syno_hdd-db instead. It may actually be able to recover your existing NVMe volume. If not, it will allow you to create the storage pool and volume in storage manager. https://github.com/007revad/Synology_HDD_db Run it with the -n flag to prevent DSM updating the drive databases. And schedule it to run at bootup so you don't lose your NVMe volume after a DSM update. https://github.com/007revad/Synology_HDD_db/blob/main/how_to_schedule.md
Author
Owner

@paul0261 commented on GitHub (Feb 19, 2024):

You actually don't need syno_m2_volume with a DS1821+ running DSM 7.2.1

Use syno_hdd-db instead. It may actually be able to recover your existing NVMe volume. If not, it will allow you to create the storage pool and volume in storage manager. https://github.com/007revad/Synology_HDD_db

Run it with the -n flag to prevent DSM updating the drive databases.

And schedule it to run at bootup so you don't lose your NVMe volume after a DSM update. https://github.com/007revad/Synology_HDD_db/blob/main/how_to_schedule.md

Success! Thank u so much!

<!-- gh-comment-id:1952699909 --> @paul0261 commented on GitHub (Feb 19, 2024): > You actually don't need syno_m2_volume with a DS1821+ running DSM 7.2.1 > > Use syno_hdd-db instead. It may actually be able to recover your existing NVMe volume. If not, it will allow you to create the storage pool and volume in storage manager. https://github.com/007revad/Synology_HDD_db > > Run it with the -n flag to prevent DSM updating the drive databases. > > And schedule it to run at bootup so you don't lose your NVMe volume after a DSM update. https://github.com/007revad/Synology_HDD_db/blob/main/how_to_schedule.md Success! Thank u so much!
Sign in to join this conversation.
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#225
No description provided.