[GH-ISSUE #77] Cannot Create Pool after Raid1 Creation Failure #219

New issue

Closed

opened 2026-03-12 18:10:26 +03:00 by kerem · 1 comment

kerem commented

2026-03-12 18:10:26 +03:00

Owner

Originally created by @cmacnichol on GitHub (Jul 26, 2023).
Original GitHub issue: https://github.com/007revad/Synology_M2_volume/issues/77

I ran the script and unfortunately had a network disconnect of my SSH Session during the Raid1 Drive Sync. Now I cannot create the storage pool or volume from DSM. The script itself thinks the drives are being used by DSM. Using the -a switch allows it to continue, however it will fail to create the system partition. Same error as this issue: #69

[/sbin/sfdisk -N1 -uS -q -f -j256 -z4980480 -tfd -F /dev/nvme0n1] failed. err=255
Create system partitions failed.

ERROR 5 Failed to create syno partitions!

Is there anything I can do to reset everything back to the beginning? I have already tried erasing them in DSM and re-creating them through the script with the above error.

Originally created by @cmacnichol on GitHub (Jul 26, 2023). Original GitHub issue: https://github.com/007revad/Synology_M2_volume/issues/77 I ran the script and unfortunately had a network disconnect of my SSH Session during the Raid1 Drive Sync. Now I cannot create the storage pool or volume from DSM. The script itself thinks the drives are being used by DSM. Using the -a switch allows it to continue, however it will fail to create the system partition. Same error as this issue: #69 [/sbin/sfdisk -N1 -uS -q -f -j256 -z4980480 -tfd -F /dev/nvme0n1] failed. err=255 Create system partitions failed. ERROR 5 Failed to create syno partitions! Is there anything I can do to reset everything back to the beginning? I have already tried erasing them in DSM and re-creating them through the script with the above error.

kerem closed this issue

2026-03-12 18:10:32 +03:00

kerem commented

2026-03-12 18:10:38 +03:00

Author

Owner

@cmacnichol commented on GitHub (Jul 27, 2023):

Closing this out. Multiple reboots fixed something, no idea what. But the script is running a new sync now.

@cmacnichol commented on GitHub (Jul 27, 2023): Closing this out. Multiple reboots fixed something, no idea what. But the script is running a new sync now.

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#219

No description provided.

Rows
Columns