NVMe SSDs not showing in Storage manager

[here4info]

I had a virtual DSM running on proxmox, using redpill loader until about a month ago (I do not remember the DSM model or version number but it must be the latest version about a month ago). I have 3 NVMe drives passed through, that was setup as storage volume and everything was working great for couple months (i had lots of files backed up to these volumes and no issues). Until:

about a month ago, my system died, and I got a replacement system, popped back in the original NVMe drives in the new system, proxmox needed some reconfig but I got that to work. However while getting proxmox to work, I deleted the old DSM installation (on a different virtual drive on 4th NVMe drive). I reinstalled DSM using redpill loader again (including option of nvme as storage volume), and this is the current versions:

DSM3622xs+

7.2.2-72803

 

Problem: I can see that NVMe drives are passed through correctly from proxmox to DSM, however I do not see them in DSM storage manager. How do I debug?

[here4info]

 

root@xNAS:/# ls /dev/nvme*
/dev/nvme0      /dev/nvme0n1p2  /dev/nvme1n1    /dev/nvme1n1p3  /dev/nvme2n1p1
/dev/nvme0n1    /dev/nvme0n1p3  /dev/nvme1n1p1  /dev/nvme2      /dev/nvme2n1p2
/dev/nvme0n1p1  /dev/nvme1      /dev/nvme1n1p2  /dev/nvme2n1    /dev/nvme2n1p3

root@xNAS:/# fdisk -l /dev/nvme0n1
Disk /dev/nvme0n1: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors
Disk model: Samsung SSD 990 PRO 4TB
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 1BBD1C0E-1D8D-4C11-BFC6

Device            Start        End    Sectors  Size Type
/dev/nvme0n1p1     8192   16785407   16777216    8G Linux RAID
/dev/nvme0n1p2 16785408   20979711    4194304    2G Linux RAID
/dev/nvme0n1p3 21241856 7813832351 7792590496  3.6T Linux RAID

root@xNAS:/# synopartition --scan-syno-part
/dev/sdb
/dev/sdb1
/dev/sdb2
/dev/sdb3
/dev/sdb5

root@xNAS:/# synopartition --check /dev/nvme0n1
/dev/nvme0n1: partition layout is version 9, list index is 15.

 

As you can see the drives are visible. However synopartition do not see them (sdb is the virtual drive).

 

I do not want to recreate the partitions, since I want to get back original data. I am hoping that if DSM can "see" the drives, it will reconstruct the volume

 

 

 

More info:

 

root@xNAS:/# cat /etc/synoinfo.conf | grep support_m2
support_m2_pool="yes"

root@xNAS:/# cat /etc/synoinfo.conf | grep support_disk_compatibility
support_disk_compatibility="no"

 

 

What else can I check?

Edited September 18 by here4info

[here4info]

solved it. installed DSM 7.2.1 and everything is working automatically. Some problem with 7.2.2

[Peter Suh]

By any chance, what kind of loader did you use?
I tested my DS3622xs+ 7.2.2-72806 with my mshell-TCRP
The two M.2 NVMe are showing up fine.

 

 

Edited September 19 by Peter Suh

[here4info]

35 minutes ago, Peter Suh said:

By any chance, what kind of loader did you use?
I tested my DS3622xs+ 7.2.2-72806 with my mshell-TCRP
The two M.2 NVMe are showing up fine.

 

 

I used Arc loader 

[Peter Suh]

8 hours ago, here4info said:

I used Arc loader 

 

Please double check if you accidentally missed the disks addon in ARC.
If you don't miss it and the problem persists,
try changing the loader to my mshell.
https://github.com/PeterSuh-Q3/tinycore-redpill/releases/tag/v1.0.4.7

[here4info]

Thanks, i built the image three times using the addon. It just wouldn't work.

I switched to DS920+ model and 7.2.1 version and the addon just worked. For me, this is good enough.

On the m2-volume patch git page, i did see that ds3622+ has had this addon working and not working between multiple versions, that's why I decided to switch to ds920+ where was consistently working