Volume2 (NVME SHR1) lost after reinstallation of DSM

[MikeyMan83]

Hi,

I'm in the process of replacing all my drives in volume1. Needed to go from ext4 to btrfs.
So i had two NVME's in volume 2, which worked great.

However, after installation and running the HDD DB script, the disks are available, but the volume is not there.

Can i run the M2 volume script to fix this? Or any other ideas to go with?

[MikeyMan83]

Tried it, got the following:

admin@NAS:/volumeUSB1/usbshare/Scripts/Synology_M2_volume-2.1.31$ sudo ./syno_create_m2_volume.sh
Synology_M2_volume v2.1.31
DS1520+ DSM 7.2.2-72806-3

StorageManager 1.0.0-00502

Using options:

Running from: /volumeUSB1/usbshare/Scripts/Synology_M2_volume-2.1.31/syno_create_m2_volume.sh

nvme0n1 M.2 Drive 2 - Sandisk WD Red SN700 500GB
Skipping drive as it is being used by DSM

nvme1n1 M.2 Drive 1 - Sandisk WD Red SN700 500GB
Skipping drive as it is being used by DSM

Unused M.2 drives found: 0

admin@NAS:/volumeUSB1/usbshare/Scripts/Synology_M2_volume-2.1.31$

Think i'm screwed...

[MikeyMan83]

Got the disk mounted through 500 lines of AI supported code, so that's good.
Apparently something went wrong with the VG naming...

root@NAS:/volumeUSB1/usbshare/Scripts/Synology_HDD_db-3.6.111# ./syno_hdd_db.sh
Synology_HDD_db v3.6.111
DS1520+ x86_64 DSM 7.2.2-72806-3
StorageManager 1.0.0-00502

ds1520+_host_v7 version 8063

Running from: /volumeUSB1/usbshare/Scripts/Synology_HDD_db-3.6.111/syno_hdd_db.sh
WARNING: Duplicate VG name vg1: Existing 6UmLvI-bnni-p9Vn-RQwo-9ZH0-Go6k-jbeDCW (created here) takes precedence over RRXmoV-jx5Q-BySe-OWcr-T8To-sC4d-W8y61f
WARNING: Duplicate VG name vg1: Existing 6UmLvI-bnni-p9Vn-RQwo-9ZH0-Go6k-jbeDCW (created here) takes precedence over RRXmoV-jx5Q-BySe-OWcr-T8To-sC4d-W8y61f
WARNING: Duplicate VG name vg1: Existing RRXmoV-jx5Q-BySe-OWcr-T8To-sC4d-W8y61f (created here) takes precedence over 6UmLvI-bnni-p9Vn-RQwo-9ZH0-Go6k-jbeDCW
WARNING: Duplicate VG name vg1: Existing 6UmLvI-bnni-p9Vn-RQwo-9ZH0-Go6k-jbeDCW (created here) takes precedence over RRXmoV-jx5Q-BySe-OWcr-T8To-sC4d-W8y61f
WARNING: Duplicate VG name vg1: Existing 6UmLvI-bnni-p9Vn-RQwo-9ZH0-Go6k-jbeDCW (created here) takes precedence over RRXmoV-jx5Q-BySe-OWcr-T8To-sC4d-W8y61f
WARNING: Duplicate VG name vg1: Existing 6UmLvI-bnni-p9Vn-RQwo-9ZH0-Go6k-jbeDCW (created here) takes precedence over RRXmoV-jx5Q-BySe-OWcr-T8To-sC4d-W8y61f

HDD/SSD models found: 1
ST12000VN0008-2YS101,SC60,12000 GB

M.2 drive models found: 1
WD Red SN700 500GB,111150WD,500 GB

No M.2 PCIe cards found

No Expansion Units found

ST12000VN0008-2YS101 already exists in ds1520+_host_v7.db
WD Red SN700 500GB already exists in ds1520+_host_v7.db

Support disk compatibility already enabled.

Support memory compatibility already enabled.

NVMe support already enabled.

M.2 volume support already enabled.

Drive db auto updates already enabled.

DSM successfully checked disk compatibility.

You may need to reboot the Synology to see the changes.

Moral of the story... A full reinstall will mess this up :P

[007revad]

Pity DSM didn't offer to migrate the storage pool.

[MikeyMan83]

Yes definitely. And quite unexpected.

any ideas why it wouldnt be restored?

[007revad]

Usually running Synology_HDD_db will get your NVMe storage pool, and volume, to reappear.

Interesting that it says RRXmoV-jx5Q-BySe-OWcr-T8To-sC4d-W8y61f takes precedence over 6UmLvI-bnni-p9Vn-RQwo-9ZH0-Go6k-jbeDCW once.

But 5 times it says the opposite 6UmLvI-bnni-p9Vn-RQwo-9ZH0-Go6k-jbeDCW (created here) takes precedence over RRXmoV-jx5Q-BySe-OWcr-T8To-sC4d-W8y61f

On a DS1520+ running DSM 7.2.2 you should have been able to create an NVMe volume in storage manager, without the need to create it with Synology_M2_volume.

[MikeyMan83]

@007revad As far as i know only the 1522+ and beyond supports NVME volume creation.

https://kb.synology.com/en-global/DSM/tutorial/Which_models_support_M_2_SSD_storage_pool

The 'unique' situation i was in is that i did a full clear of my disks, added a clean volume1.

The VG1 name can only be used once inside a pool, and somehow i wasn't able to get the ssd volume2 to get added to a second pool.
After renaming the VG1 to VG2 i could get it mounted and get the data off. Which helped a lot. The M2 volume script couldn't be run because DSM was locking the disks somehow.

But a bit unexpeceted that it didnt just pop up in the new install. Maybe good to mention in the readme that a full DSM reinstall could cause the volume to break.

Ended up clearing and formatting the SSD's, re-ran the M2 volume script. All back in order now. Just took a day or two extra.

[007revad]

Officially there's only 13 models that support NVMe volumes. But after running Synology_HDD_db 53 older models can also create NVMe volumes in storage manager. https://github.com/007revad/Synology_Information_Wiki/blob/main/pages/Models-that-support-M.2-Volumes.md