starred/Synology_M2_volume

Fork 0

mirror of https://github.com/007revad/Synology_M2_volume.git synced 2026-04-25 07:46:05 +03:00

[GH-ISSUE #163] ERROR CREATING STORAGE POOL (synostgpool failed to create storage pool!) #235

New issue

Closed

opened 2026-03-12 18:22:22 +03:00 by kerem · 4 comments

kerem commented

2026-03-12 18:22:22 +03:00

Owner

Originally created by @NoFrills88 on GitHub (Jul 2, 2024).
Original GitHub issue: https://github.com/007revad/Synology_M2_volume/issues/163

I see other people had this problem but unfortunately, the latest version of the script (2.0.27) still yields the same error. Please assist when you get time. TIA

Originally created by @NoFrills88 on GitHub (Jul 2, 2024). Original GitHub issue: https://github.com/007revad/Synology_M2_volume/issues/163 I see other people had this problem but unfortunately, the latest version of the script (2.0.27) still yields the same error. Please assist when you get time. TIA ![Capture](https://github.com/007revad/Synology_M2_volume/assets/58262362/e750dc58-673d-4232-b0d5-654952c9d7b8)

kerem closed this issue

2026-03-12 18:22:27 +03:00

kerem commented

2026-03-12 18:22:33 +03:00

Author

Owner

@NoFrills88 commented on GitHub (Jul 2, 2024):

UPDATE: I deleted the m.2 volume in storage manager and created it again using storage manager. It now works. I will post if the issue resurfaces.

@NoFrills88 commented on GitHub (Jul 2, 2024): UPDATE: I deleted the m.2 volume in storage manager and created it again using storage manager. It now works. I will post if the issue resurfaces.

kerem commented

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

Author

Owner

@007revad commented on GitHub (Jul 2, 2024):

In storage manager are you seeing "Unknown" instead of Patriot and "Unknown firmware version"?

What does the following command return for the vendor id:

nvme id-ctrl /dev/nvme0n1 | grep -E ^vid | awk '{print $NF}'

@007revad commented on GitHub (Jul 2, 2024): In storage manager are you seeing "Unknown" instead of Patriot and "Unknown firmware version"? What does the following command return for the vendor id: ``` nvme id-ctrl /dev/nvme0n1 | grep -E ^vid | awk '{print $NF}' ```

kerem commented

2026-03-12 18:22:43 +03:00

Author

Owner

@NoFrills88 commented on GitHub (Jul 2, 2024):

I will try the command (not so familiar with ssh lol). However, the good thing is that after deleting and manually creating the volume on dsm interface it just worked😆. Perhaps, dsm corrected the part/step that failed on the script?

@NoFrills88 commented on GitHub (Jul 2, 2024): I will try the command (not so familiar with ssh lol). However, the good thing is that after deleting and manually creating the volume on dsm interface it just worked😆. Perhaps, dsm corrected the part/step that failed on the script?

kerem commented

2026-03-12 18:22:48 +03:00

Author

Owner

@007revad commented on GitHub (Jul 3, 2024):

That error looks like a false error because the exit code was 0. If it was a real error it would have been a number greater than 0.

I have seen some changes take up to 20 minutes to appear in storage manager. DSM seems to check the drives every 20 minutes, or when some action is taken. You deleting the volume in storage manager would have triggered the check.

You can run the command in task scheduler.

Go to Control Panel > Task Scheduler > click Create > and select Scheduled Task.
Select User-defined script.
Enter any task name.
Select root as the user (The command needs to run as root).
Untick Enable so it does not run on a schedule.
Click Task Settings.
In the box under User-defined script type nvme id-ctrl /dev/nvme0n1 | grep -E ^vid | awk '{print $NF}'
Click OK to save the settings.
Click on the task - but don't enable it - then click Run.
Then click on Action > View Result.
Once the script has run you can delete the scheduled task.

@007revad commented on GitHub (Jul 3, 2024): That error looks like a false error because the exit code was 0. If it was a real error it would have been a number greater than 0. I have seen some changes take up to 20 minutes to appear in storage manager. DSM seems to check the drives every 20 minutes, or when some action is taken. You deleting the volume in storage manager would have triggered the check. You can run the command in task scheduler. 1. Go to **Control Panel** > **Task Scheduler** > click **Create** > and select **Scheduled Task**. 2. Select **User-defined script**. 3. Enter any task name. 4. Select **root** as the user (The command needs to run as root). 5. Untick **Enable** so it does **not** run on a schedule. 6. Click **Task Settings**. 7. In the box under **User-defined script** type `nvme id-ctrl /dev/nvme0n1 | grep -E ^vid | awk '{print $NF}'` 8. Click **OK** to save the settings. 9. Click on the task - but **don't** enable it - then click **Run**. 10. Then click on **Action** > **View Result**. 11. Once the script has run you can delete the scheduled task.

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

No description provided.

Rows
Columns