synostgpool failed to create storage pool!

007revad / Synology_M2_volume

Easily create an M.2 volume on Synology NAS

MIT License

776 stars 51 forks source link

synostgpool failed to create storage pool! #150

Closed 007revad closed 2 months ago

007revad commented 2 months ago

@aelmardi wrote:

Hey guys,

I'm facing an issue with my DS923+ on DSM 7.2.1-69057 Update 5. (Seagate Firecuda 530)

I don't have any logs available, but it failed during the storage creation step :

Thanks in advance for your help.

007revad commented 2 months ago

I can see what the issue is. I just need to work why it happened and prevent it happening.

Line 10 in your screenshot shows:

nvme0n1 M.2 Drive /dev/nvme0n1-/dev/nvme0n1 - Seagate Seagate FireCuda 530 ZP2000GM30013

Where it should show:

nvme0n1 M.2 Drive 1 - Seagate Seagate FireCuda 530 ZP2000GM30013

007revad commented 2 months ago

Can you download and run this test version and reply with a screenshot of the output?

https://github.com/007revad/Synology_M2_volume/archive/refs/tags/v10.0.0-TEST.zip

aelmardi commented 2 months ago

Hello,

Got it, here's the screenshot. Thanks for your prompt response.

007revad commented 2 months ago

What does the following command return?

sudo synonvme --get-location /dev/nvme0n1

aelmardi commented 2 months ago

Can't get the location of /dev/nvme0n1

But when I go to /dev/ an run ls command I have the nvme0n1 file : /dev$ ls -lart nvme0* crw------- 1 root root 250, 0 May 5 00:29 nvme0 brw------- 1 root root 259, 0 May 5 00:29 nvme0n1 brw------- 1 root root 259, 1 May 5 00:29 nvme0n1p1 brw------- 1 root root 259, 3 May 5 00:29 nvme0n1p3 brw------- 1 root root 259, 2 May 5 00:29 nvme0n1p2 brw------- 1 root root 259, 4 May 5 00:29 nvme0n1p5

007revad commented 2 months ago

That is strange because the line before that in the script is: synonvme --vendor-get /dev/nvme0n1

So I'm not sure why this line does not work for you: synonvme --get-location /dev/nvme0n1

I've got a new test version for you to test. https://github.com/007revad/Synology_M2_volume/releases/tag/v10.0.0-TEST2

It is the full script with 2 changes:

If synonvme --get-location returns an error it uses "nvme0n1" instead of expecting "M2 Drive 1".
It won't actually run the synostpool command. Instead it will echo the command so I can see what arguments it would have used.

aelmardi commented 2 months ago

Here's the result of the script :

007revad commented 2 months ago

I noticed another bug in your latest screenshot, which would have been the cause of the the synostpool failing.

I've released a new version of the script https://github.com/007revad/Synology_M2_volume/releases/tag/v2.0.27

Bug fix for when synonvme --get-location fails.
Bug fix for synostgpool failed to create storage pool when Single volume storage pool type selected with only 1 M.2 drive.

sin509 commented 2 months ago

hey, i meet a similar problem,like

what can i do?

007revad commented 2 months ago

@sin509

Can you download this version: https://github.com/007revad/Synology_M2_volume/releases/tag/v10.0.0-TEST2

Then run the syno_create_m2_volume_test2.sh file and let me know if it works.

aelmardi commented 2 months ago

With the latest version it doesn't work for me. I'm going to reinstall my DSM to see.

sin509 commented 2 months ago

@sin509

Can you download this version: https://github.com/007revad/Synology_M2_volume/releases/tag/v10.0.0-TEST2

Then run the syno_create_m2_volume_test2.sh file and let me know if it works.

I have reinstalled my DSM from 918+ to 920+, and anything is ok. so maybe it is down to 918+.

aelmardi commented 2 months ago

You can close this issue because I believe the problem is that my M2 is not recognized either. I have created another issue: https://github.com/007revad/Synology_HDD_db/issues/292