starred/Synology_enable_M2_volume
1
0
Fork 0
mirror of https://github.com/007revad/Synology_enable_M2_volume.git synced 2026-04-25 13:05:54 +03:00
Code Issues 9 Projects Releases 5 Packages Wiki Activity

[GH-ISSUE #61] PVE, DS3622xs+, 7.2-64561 #12

New issue
Closed
opened 2026-03-07 19:12:01 +03:00 by kerem · 4 comments
kerem commented 2026-03-07 19:12:01 +03:00
Owner
Copy link

Originally created by @hawie on GitHub (Jun 8, 2023).
Original GitHub issue: https://github.com/007revad/Synology_enable_M2_volume/issues/61

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_enable_M2_volume v1.0.6
DS3622xs+ DSM 7.2-64561 

Using options: 
Backup successful.

Checking file.
198666 = 3080a
0003080a: 803E 00B8 0100 0000 7524 488B

Editing file.

Checking if file was successfully edited.
198666 = 3080a
0003080a: 803E 00B8 0100 0000 9090 488B
File successfully edited.

You can now create your M.2 storage pool in Storage Manager.

M.2 volume support already enabled.

The Synology needs to restart.
Type yes to reboot now.
Type anything else to quit (if you will restart it yourself).

Synology_HDD_db v2.2.47

Synology_HDD_db v2.2.47
DS3622xs+ DSM 7.2-64561 
Using options: -nr

HDD/SSD models found: 1
HARDDISK,2.5+

M.2 drive models found: 1
aigo NVMe SSD P7000Z 2TB,H230407a

No M.2 cards found

No Expansion Units found

HARDDISK already exists in ds3622xs+_host_v7.db
aigo NVMe SSD P7000Z 2TB already exists in ds3622xs+_host_v7.db

Re-enabled support disk compatibility.

Support memory compatibility already disabled.

M.2 volume support already enabled.

Drive db auto updates already disabled.

DSM successfully checked disk compatibility.

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

Issue:
There are 2 drives that do not meet the drive requirements.
screenshot:
http://usa1.cyder.club/dsm2.png

additional info:
after reboot:

#cat /run/synostorage/disks/nvme0n1/m2_pool_support
0 
#cat /run/synostorage/disks/nvme1n1/m2_pool_support 
0

force, but no effect:

echo 1 > /run/synostorage/disks/nvme0n1/m2_pool_support
echo 1 > /run/synostorage/disks/nvme1n1/m2_pool_support
Originally created by @hawie on GitHub (Jun 8, 2023). Original GitHub issue: https://github.com/007revad/Synology_enable_M2_volume/issues/61 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_enable_M2_volume v1.0.6 DS3622xs+ DSM 7.2-64561 Using options: Backup successful. Checking file. 198666 = 3080a 0003080a: 803E 00B8 0100 0000 7524 488B Editing file. Checking if file was successfully edited. 198666 = 3080a 0003080a: 803E 00B8 0100 0000 9090 488B File successfully edited. You can now create your M.2 storage pool in Storage Manager. M.2 volume support already enabled. The Synology needs to restart. Type yes to reboot now. Type anything else to quit (if you will restart it yourself). ``` Synology_HDD_db v2.2.47 ``` Synology_HDD_db v2.2.47 DS3622xs+ DSM 7.2-64561 Using options: -nr HDD/SSD models found: 1 HARDDISK,2.5+ M.2 drive models found: 1 aigo NVMe SSD P7000Z 2TB,H230407a No M.2 cards found No Expansion Units found HARDDISK already exists in ds3622xs+_host_v7.db aigo NVMe SSD P7000Z 2TB already exists in ds3622xs+_host_v7.db Re-enabled support disk compatibility. Support memory compatibility already disabled. M.2 volume support already enabled. Drive db auto updates already disabled. DSM successfully checked disk compatibility. You may need to reboot the Synology to see the changes. ``` **Issue**: **There are 2 drives that do not meet the drive requirements.** screenshot: http://usa1.cyder.club/dsm2.png additional info: after reboot: ``` #cat /run/synostorage/disks/nvme0n1/m2_pool_support 0 #cat /run/synostorage/disks/nvme1n1/m2_pool_support 0 ``` force, but no effect: ``` echo 1 > /run/synostorage/disks/nvme0n1/m2_pool_support echo 1 > /run/synostorage/disks/nvme1n1/m2_pool_support ```
kerem closed this issue 2026-03-07 19:12:02 +03:00
kerem commented 2026-03-07 19:12:02 +03:00
Author
Owner
Copy link

@007revad commented on GitHub (Jun 9, 2023):

I didn't know we could passthrough NVME drives to a VM. I think you just made my testing a lot easier.

<!-- gh-comment-id:1583986177 --> @007revad commented on GitHub (Jun 9, 2023): I didn't know we could passthrough NVME drives to a VM. I think you just made my testing a lot easier.
kerem commented 2026-03-07 19:12:02 +03:00
Author
Owner
Copy link

@hawie commented on GitHub (Jun 11, 2023):

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

<!-- gh-comment-id:1586081865 --> @hawie commented on GitHub (Jun 11, 2023): 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
kerem commented 2026-03-07 19:12:02 +03:00
Author
Owner
Copy link

@007revad commented on GitHub (Jun 11, 2023):

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.

<!-- gh-comment-id:1586111926 --> @007revad commented on GitHub (Jun 11, 2023): > **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.
kerem commented 2026-03-07 19:12:02 +03:00
Author
Owner
Copy link

@007revad commented on GitHub (Jun 13, 2023):

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

<!-- gh-comment-id:1588914124 --> @007revad commented on GitHub (Jun 13, 2023): @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.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
develop
v1.1.22
v1.1.21
v1.1.20
v1.1.19
v1.1.18
v1.1.17
v1.1.15
V1.1.14
v1.1.13
v1.1.12-RC
v1.1.11-RC
v1.0.10
v1.0.9
v1.0.8
v1.0.7
v1.0.6
v1.0.5
v1.0.4
v1.0.3
v0.0.2
v0.0.1
Labels
Clear labels   
enhancement

   
pull-request

Mirrored from GitHub Pull Request

No labels
enhancement
pull-request
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/Synology_enable_M2_volume#12
No description provided.