NOT working on Synology 720+ with DSM 6.2.4 update 7.
It will create the storage pool, but the volume is not created. I do not see any option for creating a volume from the SSD storage pool.

Config: two 500GB SSD, configured in RAID 1.

I had this working on DSM 7.1.1 with RAID 0, but I downgraded to DSM 6 and the script is not able to create the volume.

Originally posted by @Ruben-Isai in #52 (comment)

I dowloaded https://github.com/007revad/Synology_M2_volume/archive/refs/tags/v1.3.21.zip
and running it I've got:

There is a newer version of this script available.
Current version: v1.3.20
Latest version:  v1.3.21

Looking at line 83:
scriptver="v1.3.20"

Has anyone tested upgrading from 7.1 to 7.2 (now beta) with M2 storage pool already created?
I am in this situation and above the storage pool made with the M2s I have all my VMs.

When the upgrade to version 7.2 (official) comes out I don't want to have any unpleasant surprises.

Thank you

I added a second NVME and I am trying to change from basic and Raid without losing data and unable to do so.

Any suggestions?

Thanks for this work!

In case you've not seen it before, shellcheck is a great linter for shell, and integrates with a bunch of editors (I use the this extension with vscode, fwiw).

It didn't find anything horrible here--just a few nits:

 shellcheck syno_create_m2_volume.sh 

In syno_create_m2_volume.sh line 79:
[ "$BASH" ] && ! shopt -qo posix || {
            ^-- SC2015 (info): Note that A && B || C is not if-then-else. C may run when A is true.


In syno_create_m2_volume.sh line 127:
    minor=$(get_key_value /etc.defaults/VERSION minor)
    ^---^ SC2034 (warning): minor appears unused. Verify use (or export if used externally).


In syno_create_m2_volume.sh line 151:
args="$@"
     ^--^ SC2124 (warning): Assigning an array to a string! Assign as array, or use * instead of @ to concatenate.


In syno_create_m2_volume.sh line 176:
                log=yes
                ^-^ SC2034 (warning): log appears unused. Verify use (or export if used externally).


In syno_create_m2_volume.sh line 179:
                debug=yes
                ^---^ SC2034 (warning): debug appears unused. Verify use (or export if used externally).


In syno_create_m2_volume.sh line 216:
    dsm72="yes"
    ^---^ SC2034 (warning): dsm72 appears unused. Verify use (or export if used externally).


In syno_create_m2_volume.sh line 348:
                                delerr=1
                                ^----^ SC2034 (warning): delerr appears unused. Verify use (or export if used externally).

For more information:
  https://www.shellcheck.net/wiki/SC2034 -- debug appears unused. Verify use ...
  https://www.shellcheck.net/wiki/SC2124 -- Assigning an array to a string! A...
  https://www.shellcheck.net/wiki/SC2015 -- Note that A && B || C is not if-t...

Feel free to close this issue--I just wanted to stop by and thank you for your work.

(I found this project via https://www.mklibrary.com/synology-nvme-volume/)

Cheers!

Hello friend!

Thanks for the script.
On what versions of the DSM can they be used?
And what awaits us after the update DSM for ex. from 7.1 to 7.2 or 6.2 to 7.x?

Thank you!

DS920+ with Synology DSM 7.2 build 64561
2x Samsung 980 M.2 nvme

Thank you very much!

DS923+
DSM 7.2.1-69057 Update 5

Dear Dave Russell,
I used your script on my synology to create my m2 volume pool but it seems to have some errors. I followed all the instructions shown in the README file and the error message is shown below:

First thank you very much for this cool script. I moved my 2x4TB nvme‘s from cache usage to volume. I had used about 400 GB as cache group before.
I have seen that there seem to be different partition types for cache group and volume. What I would really like is to share my nvme space between cache and volume usage. Is this generally possible or is this something that is technically impossible?

I have already installed two m2 SSDs in my DS1821 and used a script to create storage space. I have now added one e10m20-t1 and inserted the other two m2 SSDs. When I run the script, I can discover the newly added SSDs, but I cannot create storage space. The prompt is that MD10 already exists, and the network card does not appear. I want to use both a 10 Gigabit network card and four SSDs at the same time. I found this post, https://blog.mitsea.com/b3d944ff0c02498c9c341a620b323f1a/ Can it be achieved on 1821?

My device is 1618+, with M2D20 expansion card, the current DSM version is 7.1.1, can I use this script?
I don't see that this model is supported in the current support list. Is it because it is clearly not supported or there is no test object? Thanks to the author for sharing the script.

Hi

My M2 Samsung SSD 970 EVO Plus 500GB Pool stopped working after an update to DSM 7.2-64570.
It was created on older DSM 7.2-64561.
Since I can't roll back to the older one, is there any workaround to fix M2 pool?

Thanks

My motherboard (Lenovo P520 WorkStation) can take 2 nvme on board, plus I have AIC (Asus HyperX M.2 Gen 4 in PCIe slot 2 for burification x4x4x4x4) that takes another 4 nvme. When all 6 are populated I cannot select all 4 of the AIC nvme drives. It only allows me to select first two nvme on the AIC and the 2 nvme on the motherboard. If I remove 2 nvme on motherboard, then I can select all 4 nvme on AIC.

Hello!
I have ds920+ and i won't be able to create volume officially. So, i wonder, is it possible to use my two SSD's partially for creating volume and rest of space for synology cache? I have 2x500GB SSD's and my syno cache advisor says that i need cache of 250GB. I'd like to have an SSD volume of not more than 100GB for Home Assistant use, rest of space i'd use for cache.

Possible?

Hi,

I have used this script to set up a RAID1 array (mirrored). I used some old small M.2 drives as testers and have since ordered two bigger drives. I replaced one today, similar to how I have rebuilt RAID1 arrays in the past, just replace a drive the rebuild through the UI. The problem is I cannot get it to work.

Trying to repair the Storage Pool results in an error saying there are no drives that meet the requirements. Clicking the new drive under HDD/SSD doesn't;t let me do anything other than a SSD Cache (for obvious reasons I'm on a DS918+)

Re-running the script only lets me select one drive (the new one) and the script fails to finish.

Synology_M2_volume v1.2.14
DS918+ DSM 7.1.1-42962-5 

Using options: 
Type yes to continue. Type anything else to do a dry run test.
yes

NVMe M.2 nvme0n1 is Samsung SSD 970 EVO Plus 1TB
No existing partitions on drive

NVMe M.2 nvme1n1 is Samsung SSD 970 EVO Plus 250GB
Skipping drive as it is being used by DSM

Unused M.2 drives found: 1

1) nvme0n1
Select the M.2 drive: 1
You selected nvme0n1

Ready to create volume group on nvme0n1
Type yes to continue. Type anything else to quit.
yes
You chose to continue. You are brave! :)

Using md5 as it's the next available.

Creating Synology partitions on nvme0n1

        Device   Sectors (Version8: SupportRaid)
 /dev/nvme0n11   4980480 (2431 MB)
 /dev/nvme0n12   4194304 (2048 MB)
Reserved size:    260352 ( 127 MB)
Primary data partition will be created.

WARNING: This action will erase all data on '/dev/nvme0n1' and repart it, are you sure to continue? [y/N] y
Cleaning all partitions...
Creating sys partitions...
Creating primary data partition...
Please remember to mdadm and mkfs new partitions.

Creating single drive RAID.
mdadm: Note: this array has metadata at the start and
    may not be suitable as a boot device.  If you plan to
    store '/boot' on this device please ensure that
    your boot-loader understands md/v1.x metadata, or use
    --metadata=0.90
Continue creating array? yes
mdadm: Defaulting to version 1.2 metadata
mdadm: array /dev/md5 started.

Creating a physical volume (PV) on md5 partition
  Physical volume "/dev/md5" successfully created

Creating a volume group (VG) on md5 partition
  /dev/vg5: already exists in filesystem
  Run `vgcreate --help' for more information.

ERROR 5 Failed to create volume group!

Hi,

This works with DS3622xs+, DSM 7.2-64570 Update 1. But not when the NVME drive is installed onto an adapter card with the ASM2824 chip. The script sees the drive and formats it but upon reboot, the drive is not available under Online Assemble.

sudo ls -I ram -I loop* -I dm-* /sys/block

md0 nvme0n1 ram10 ram13 ram2 ram5 ram8 synoboot
md1 ram0 ram11 ram14 ram3 ram6 ram9 zram0
md2 ram1 ram12 ram15 ram4 ram7 sda zram1

Can this be made to work with this type of adapter card that does not rely on PCIe bifurcation?

Thanks,

This is just a note for possibly updating the in-script messaging that currently reads:

SSD TRIM option not available in DSM 7.2 Beta for RAID 0

Otherwise, an excellent scripted process with nothing else unexpected. Thank you!

Is there any way to add support for 2.5in SSDs in the cache trays of a Synology Rack Server?

          > Unfortunately if DSM isn't seeing the PCIe card with synonvme the drive won't show up in storage manager.

That card is very cheap. I might buy one myself to see if I can get it working in my DS1821+

Is it possible to enable it? create RAID5 without official M.2 NVMe adapter card.

Originally posted by @hawie in #76 (comment)

After running the script and creating pool. Will it continue to work if I move the NVME to new NAS?

Hi, first would like to thank you so much for the script ! I created a RAID1 pool with 2x 2T non-synology NVMe SSD. But after creating, I cannot remove the volume nor the pool. (I changed the mind and wanted to create a RAID0 pool with these 2 m.2 SSD , I run the script again but it is said the drive is already being used by DSM).
How to remove the m.2 SSD from the volume/pool ?
Thank you!

@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.

I have a Synology NAS with a Storage Pool 1 where all my data is on slow disks. Added two NVMe drives and used those to create Storage Pool 2 where my docker containers are. Works as advertised. However after adding a new slow drive because Storage Pool 1 was running out of space I could no longer add that drive to expand that pool because the drive requirements are not met. After checking the details it appears that I can only add NVMe drives but not HDDs anymore. Perhaps I'm doing something wrong, but it seems weird as I have not seen such a message before. Below is a screenshot of the requirements. Perhaps there is a way around it?

Hi, after update of Synology 920+ to DSM 7.2-64570 Update 1 my SSD cache was gone and the SSD‘s were shown as „not supported by this DSM version“. I applied the the Synology_HDD_db script made a reboot and applied the syno_create_m2_volume script. After another reboot SSD‘s are shown as „detected“ but Online Assemble fails. Both scripts were running without failure messages. Thanks for support.

Thanks and Great work

Quick question .... Why do Esxternal USB Drives now get picked up as a hardrive to create a Volume , they not reconized as External Devices any longer

Hi Dave, I own a DS1821+ like you, with DSM 7.1 Update 5.
I have already created a storage pool with NVME thanks to your script.

I'm wondering if I need to update that script or run it again in anticipation of 7.2 DSM release. Need?
Thank's for your job

Hello,
I try dry run mode and the result is surprising me.
There is only a RAID1 mode instead of Single mode.

Synology_M2_volume v1.3.15
DS923+ DSM 7.2-64570-3

Using options: -all
Type yes to continue. Type anything else to do a dry run test.
mlkj
*** Doing a dry run test ***

NVMe M.2 nvme0n1 is WD Red SN700 500GB
WARNING Drive has a cache partition

Unused M.2 drives found: 1

1) nvme0n1
2) Done
Select the M.2 drive: 1
You selected nvme0n1

Ready to create RAID 1 volume group using nvme0n1

WARNING Everything on the selected M.2 drive(s) will be deleted.
        *** Not really because we're doing a dry run ***
Type yes to continue. Type anything else to quit.
yes
You chose to continue. You are brave! :)

Using md5 as it's the next available.

Creating Synology partitions on nvme0n1
synopartition --part /dev/nvme0n1 13

Creating the RAID array. This will take a while...
mdadm --create /dev/md5 --level=1 --raid-devices=1 --force /dev/nvme0n1p3
      [====================>]  resync = 100%

Resync Duration: 4 sec

Creating a physical volume (PV) on md5 partition
pvcreate -ff /dev/md5

Creating a volume group (VG) on md5 partition
vgcreate vg5 /dev/md5

M.2 volume support already enabled.


Steps you need to do after running this script:
  1. After the restart go to Storage Manager and select online assemble:
       Storage Pool > Available Pool > Online Assemble
  2. Create the volume as you normally would:
       Select the new Storage Pool > Create > Create Volume
  3. Optionally enable TRIM:
       Storage Pool > ... > Settings > SSD TRIM
     SSD TRIM option is only available in DSM 7.2 Beta for RAID 1

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


Online assemble option may not appear in storage manager     until you reboot.
Type yes to reboot now.
Type anything else to quit (if you will reboot it yourself).
lgh

Is it a problem ?
Can I continue ?
Thank you for your great job.

Hello,
apart form saying thank you for the very nice script you made
Although not sure if I should do it with a submission of "issue", but just wanted to let you know it works fine on

DS920+
DSM 7.1.1-42962
M2 disks: Patriot P310 480GB
Configured as Raid1  BTRFS
It also seemed that I could enable TRIM

hope that helped

Hi, can you add DVA3219 support?

SSD NVMe type intel U.2 INTEL SSDPE2KX010T8

after completing this step
mdadm: Defaulting to version 1.2 metadata
mdadm: array /dev/md5 started.

Creating a physical volume (PV) on md5 partition
Really INITIALIZE physical volume "/dev/md5" of volume group "vg5" [y/n]? y
WARNING: Forcing physical volume creation on /dev/md5 of volume group "vg5"
Physical volume "/dev/md5" successfully created

Creating a volume group (VG) on md5 partition
Volume group "vg5" successfully created

M.2 volume support already enabled.

Steps you need to do after running this script:

1. After the restart go to Storage Manager and select online assemble:
   Storage Pool > Available Pool > Online Assemble
2. Create the volume as you normally would:
   Select the new Storage Pool > Create > Create Volume
3. Optionally enable TRIM:
   Storage Pool > ... > Settings > SSD TRIM
   SSD TRIM option is only available in DSM 7.2 Beta for RAID 1

Nothing shows up
Nas model : 1621+

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.

Would be great to be able to create RAID F1 arrays. Personality [raidF1] seems to be already present (DS1821+ latest stable release)

What is the process to revert an SSD so that it can be used as a cache drive?