[GH-ISSUE #195] synostgpool: command not found #48

Closed
opened 2026-03-07 19:19:52 +03:00 by kerem · 3 comments
Owner

Originally created by @newadventure079 on GitHub (Apr 19, 2025).
Original GitHub issue: https://github.com/007revad/Synology_M2_volume/issues/195

Similar to #194. synostgpool wasn't found

sudo ./syno_create_m2_volume.sh
Synology_M2_volume v2.0.30
DS1821+ DSM 7.2.2-72806-3

StorageManager 1.0.0-00502

Using options:

Running from: /volume1/homes/me/Synology_M2_volume-2.0.30/syno_create_m2_volume.sh

nvme0n1 M.2 Drive 1 - Samsung Samsung SSD 990 PRO with Heatsink 1TB
No existing partitions on drive

Unused M.2 drives found: 1

1) SHR 1
2) Basic
3) JBOD
Select the RAID type: 2
You selected basic

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
Select the M.2 drive: 1
You selected M.2 Drive 1

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

Ready to create Basic storage pool using nvme0n1
Type yes to continue. Type anything else to quit.
yes

Backed up synoinfo.conf

M.2 volume support already enabled.

Starting creation of the storage pool.
./syno_create_m2_volume.sh: line 905: synostgpool: command not found
synostgpool return code: 127


When storage manager has finished creating the storage pool:
  1. Create the volume as you normally would:
       Select the new Storage Pool > Create > Create Volume
  2. Optionally enable TRIM:
       Storage Pool > ... > Settings > SSD TRIM

Important
If you later upgrade DSM and your M.2 drives are shown as unsupported
and the storage pool is shown as missing, and online assemble fails,
you should run the Synology HDD db script:
https://github.com/007revad/Synology_HDD_db
Originally created by @newadventure079 on GitHub (Apr 19, 2025). Original GitHub issue: https://github.com/007revad/Synology_M2_volume/issues/195 Similar to #194. `synostgpool` wasn't found ``` sudo ./syno_create_m2_volume.sh Synology_M2_volume v2.0.30 DS1821+ DSM 7.2.2-72806-3 StorageManager 1.0.0-00502 Using options: Running from: /volume1/homes/me/Synology_M2_volume-2.0.30/syno_create_m2_volume.sh nvme0n1 M.2 Drive 1 - Samsung Samsung SSD 990 PRO with Heatsink 1TB No existing partitions on drive Unused M.2 drives found: 1 1) SHR 1 2) Basic 3) JBOD Select the RAID type: 2 You selected basic 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 Select the M.2 drive: 1 You selected M.2 Drive 1 Do you want perform a drive check? [y/n] y Ready to create Basic storage pool using nvme0n1 Type yes to continue. Type anything else to quit. yes Backed up synoinfo.conf M.2 volume support already enabled. Starting creation of the storage pool. ./syno_create_m2_volume.sh: line 905: synostgpool: command not found synostgpool return code: 127 When storage manager has finished creating the storage pool: 1. Create the volume as you normally would: Select the new Storage Pool > Create > Create Volume 2. Optionally enable TRIM: Storage Pool > ... > Settings > SSD TRIM Important If you later upgrade DSM and your M.2 drives are shown as unsupported and the storage pool is shown as missing, and online assemble fails, you should run the Synology HDD db script: https://github.com/007revad/Synology_HDD_db ```
kerem closed this issue 2026-03-07 19:19:53 +03:00
Author
Owner

@007revad commented on GitHub (Apr 19, 2025):

Fixed in https://github.com/007revad/Synology_M2_volume/releases/tag/v2.1.31

<!-- gh-comment-id:2816907430 --> @007revad commented on GitHub (Apr 19, 2025): Fixed in https://github.com/007revad/Synology_M2_volume/releases/tag/v2.1.31
Author
Owner

@faketraveler commented on GitHub (Apr 20, 2025):

Hi there,

I've noticed that for my DS918+ on DSM 7.2.2, synostgpool is in /usr/syno/sbin/synostgpool instead of /usr/syno/bin/synostgpool. It was a quick fix for me, but wanted to flag it.

<!-- gh-comment-id:2817019062 --> @faketraveler commented on GitHub (Apr 20, 2025): Hi there, I've noticed that for my DS918+ on DSM 7.2.2, synostgpool is in `/usr/syno/sbin/synostgpool` instead of `/usr/syno/bin/synostgpool`. It was a quick fix for me, but wanted to flag it.
Author
Owner

@007revad commented on GitHub (Apr 20, 2025):

Thanks. I've fixed that now, and the version number.

<!-- gh-comment-id:2817027333 --> @007revad commented on GitHub (Apr 20, 2025): Thanks. I've fixed that now, and the version number.
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#48
No description provided.