[GH-ISSUE #171] synostgpool failed to create storage pool! #240

Closed
opened 2026-03-12 18:22:53 +03:00 by kerem · 5 comments
Owner

Originally created by @maver1ck13 on GitHub (Sep 25, 2024).
Original GitHub issue: https://github.com/007revad/Synology_M2_volume/issues/171

Ive tried several times to create different m.2 volumes but always get this same error.

oncestruck@zimacube:/volume1/homes/oncestruck/other/scripts/Synology_M2_volume-2.0.28$ sudo -s ./syno_create_m2_volume.sh
Synology_M2_volume v2.0.28
SA6400 DSM 7.2.1-69057-5

StorageManager 1.0.0-0017

Using options:

Running from: /volume1/homes/oncestruck/other/scripts/Synology_M2_volume-2.0.28/syno_create_m2_volume.sh

nvme0n1 M.2 Drive 1 - Samsung Samsung SSD 990 PRO 4TB
WARNING Drive has a cache partition

nvme1n1 M.2 Drive 2 - Samsung Samsung SSD 990 PRO 4TB
WARNING Drive has a cache partition

nvme2n1 M.2 Drive 3 - Samsung Samsung SSD 990 PRO 4TB
WARNING Drive has a cache partition

nvme3n1 M.2 Drive 4 - Samsung Samsung SSD 990 PRO 4TB
WARNING Drive has a cache partition

nvme4n1 M.2 Drive 5 - Kingston KINGSTON OM8PGP41024Q-A0
Skipping drive as it is being used by DSM

Unused M.2 drives found: 4

1) SHR 1      3) Basic     5) RAID 0    7) RAID 5    9) RAID 10
2) SHR 2      4) JBOD      6) RAID 1    8) RAID 6   10) RAID F1
Select the RAID type: 5
You selected raid0

You have a choice of Multi Volume or Single Volume Storage Pool
 - Multi Volume Storage Pools allow creating multiple volumes and
   allow you to over provision to make the NVMe drive(s) last longer.
 - Single Volume Storage Pools are easier to recover data from
   and perform slightly faster.

1) Multi Volume (DSM 7 default)
2) Single Volume
Select the storage pool type: 1
You selected Multi Volume storage pool

1) M.2 Drive 1
2) M.2 Drive 2
3) M.2 Drive 3
4) M.2 Drive 4
Select the M.2 drive #1: 1
You selected M.2 Drive 1

1) M.2 Drive 2
2) M.2 Drive 3
3) M.2 Drive 4
Select the M.2 drive #2: 1
You selected M.2 Drive 2

1) M.2 Drive 3
2) M.2 Drive 4
3) Done
Select the M.2 drive #3: 1
You selected M.2 Drive 3

1) M.2 Drive 4
2) Done
Select the M.2 drive #4: 2

Do you want perform a drive check? [y/n]
y

Ready to create RAID 0 storage pool using nvme0n1 nvme1n1 nvme2n1

WARNING Everything on the selected M.2 drive(s) will be deleted.
Type yes to continue. Type anything else to quit.
yes

M.2 volume support already enabled.

Starting creation of the storage pool.
0 synostgpool failed to create storage pool!
oncestruck@zimacube:/volume1/homes/oncestruck/other/scripts/Synology_M2_volume-2.0.28$
Originally created by @maver1ck13 on GitHub (Sep 25, 2024). Original GitHub issue: https://github.com/007revad/Synology_M2_volume/issues/171 Ive tried several times to create different m.2 volumes but always get this same error. ``` oncestruck@zimacube:/volume1/homes/oncestruck/other/scripts/Synology_M2_volume-2.0.28$ sudo -s ./syno_create_m2_volume.sh Synology_M2_volume v2.0.28 SA6400 DSM 7.2.1-69057-5 StorageManager 1.0.0-0017 Using options: Running from: /volume1/homes/oncestruck/other/scripts/Synology_M2_volume-2.0.28/syno_create_m2_volume.sh nvme0n1 M.2 Drive 1 - Samsung Samsung SSD 990 PRO 4TB WARNING Drive has a cache partition nvme1n1 M.2 Drive 2 - Samsung Samsung SSD 990 PRO 4TB WARNING Drive has a cache partition nvme2n1 M.2 Drive 3 - Samsung Samsung SSD 990 PRO 4TB WARNING Drive has a cache partition nvme3n1 M.2 Drive 4 - Samsung Samsung SSD 990 PRO 4TB WARNING Drive has a cache partition nvme4n1 M.2 Drive 5 - Kingston KINGSTON OM8PGP41024Q-A0 Skipping drive as it is being used by DSM Unused M.2 drives found: 4 1) SHR 1 3) Basic 5) RAID 0 7) RAID 5 9) RAID 10 2) SHR 2 4) JBOD 6) RAID 1 8) RAID 6 10) RAID F1 Select the RAID type: 5 You selected raid0 You have a choice of Multi Volume or Single Volume Storage Pool - Multi Volume Storage Pools allow creating multiple volumes and allow you to over provision to make the NVMe drive(s) last longer. - Single Volume Storage Pools are easier to recover data from and perform slightly faster. 1) Multi Volume (DSM 7 default) 2) Single Volume Select the storage pool type: 1 You selected Multi Volume storage pool 1) M.2 Drive 1 2) M.2 Drive 2 3) M.2 Drive 3 4) M.2 Drive 4 Select the M.2 drive #1: 1 You selected M.2 Drive 1 1) M.2 Drive 2 2) M.2 Drive 3 3) M.2 Drive 4 Select the M.2 drive #2: 1 You selected M.2 Drive 2 1) M.2 Drive 3 2) M.2 Drive 4 3) Done Select the M.2 drive #3: 1 You selected M.2 Drive 3 1) M.2 Drive 4 2) Done Select the M.2 drive #4: 2 Do you want perform a drive check? [y/n] y Ready to create RAID 0 storage pool using nvme0n1 nvme1n1 nvme2n1 WARNING Everything on the selected M.2 drive(s) will be deleted. Type yes to continue. Type anything else to quit. yes M.2 volume support already enabled. Starting creation of the storage pool. 0 synostgpool failed to create storage pool! oncestruck@zimacube:/volume1/homes/oncestruck/other/scripts/Synology_M2_volume-2.0.28$ ```
kerem closed this issue 2026-03-12 18:22:59 +03:00
Author
Owner

@007revad commented on GitHub (Oct 1, 2024):

Try commenting out lines 898 and 904 to change:
exit 1

to:
# exit 1

<!-- gh-comment-id:2384774710 --> @007revad commented on GitHub (Oct 1, 2024): Try commenting out lines 898 and 904 to change: ` exit 1` to: `# exit 1`
Author
Owner

@albertusQuelle commented on GitHub (Dec 24, 2024):

I have the same problem.
So i shall out commet all 6 lines? And not just "exit 1"?

image

<!-- gh-comment-id:2560748255 --> @albertusQuelle commented on GitHub (Dec 24, 2024): I have the same problem. So i shall out commet all 6 lines? And not just "exit 1"? ![image](https://github.com/user-attachments/assets/b1d6d6fa-ca14-4b7d-a268-c16e61f3e4ed)
Author
Owner

@007revad commented on GitHub (Dec 24, 2024):

@albertusQuelle

No. Just comment out the 2 "exit 1" lines.

<!-- gh-comment-id:2560756454 --> @007revad commented on GitHub (Dec 24, 2024): @albertusQuelle No. Just comment out the 2 "exit 1" lines.
Author
Owner

@007revad commented on GitHub (Dec 24, 2024):

@albertusQuelle

Try https://github.com/007revad/Synology_M2_volume/releases/tag/v2.0.29

  • Improved checking if creating storage was okay.
  • Now skips exiting if creating storage pool failed.

The only thing the script does after creating the storage pool is show the steps you need to do to create the volume in storage manager. So there really is no reason for the script to exit if it thinks creating the storage pool failed.

<!-- gh-comment-id:2560790146 --> @007revad commented on GitHub (Dec 24, 2024): @albertusQuelle Try https://github.com/007revad/Synology_M2_volume/releases/tag/v2.0.29 - Improved checking if creating storage was okay. - Now skips exiting if creating storage pool failed. The only thing the script does after creating the storage pool is show the steps you need to do to create the volume in storage manager. So there really is no reason for the script to exit if it thinks creating the storage pool failed.
Author
Owner

@albertusQuelle commented on GitHub (Dec 24, 2024):

Thanks Dave, i am already in creating the new volume. Unfortunately after reboot it crashed completely, now i ran your update_hdd_db and then this one with v2.0.28 and outcommented exit 1

image

ps: wish you happy xmas :-)

<!-- gh-comment-id:2560791836 --> @albertusQuelle commented on GitHub (Dec 24, 2024): Thanks Dave, i am already in creating the new volume. Unfortunately after reboot it crashed completely, now i ran your update_hdd_db and then this one with v2.0.28 and outcommented exit 1 ![image](https://github.com/user-attachments/assets/7254897f-e082-4035-b7e3-556fa89e8561) ps: wish you happy xmas :-)
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#240
No description provided.