Closed hawie closed 1 year ago
I didn't know we could passthrough NVME drives to a VM. I think you just made my testing a lot easier.
SSD Cache: http://usa1.cyder.club/ssd-cache-yes.png
Storage Pool: http://usa1.cyder.club/no-storage-pool.png
maybe the problem is similar to: https://github.com/007revad/Synology_enable_M2_volume/issues/62
Issue: There are 2 drives that do not meet the drive requirements. screenshot: http://usa1.cyder.club/dsm2.png
It looks like Synology have decided not to allow M.2 storage pools in PCIe cards. Maybe they're only blocking it on enterprise models, or maybe it's a new change in DSM 7.2. I'll see if I can figure out how they are blocking them - because it worked in 7.2 beta.
@hawie From your screenshots it looks like you have the M.2 drives in a PCIe card... but Synology_HDD_db v2.2.47 didn't detect any M.2 PCIe cards. That might be because it's running DSM in a VM.
Synology support have informed me that creating volumes is not supported for M.2 drives in a PCIe card (M2D20, M2D18 and E10M20-T1). They can, officially, only be used for a cache.
My Synology_M2_volume script should be able to create a storage pool on the M.2 drives in a M2D20, M2D18 and E10M20-T1. https://github.com/007revad/Synology_M2_volume You'd then go into storage manager and do an online assemble then create your volume.
use a virtual machine environment for testing convenience.
env: PVE 7.4-3 with latest kernel: 6.2.11-2-pve Virtual Machine: DS3622xs+ DSM 7.2-64561, PCIe passthrough: M2. NVME
log: Synology_enable_M2_volume v1.0.6
Synology_HDD_db v2.2.47
Issue: There are 2 drives that do not meet the drive requirements. screenshot: http://usa1.cyder.club/dsm2.png
additional info: after reboot:
force, but no effect: