[GH-ISSUE #63] M.2 drive appears then disappears shortly after #130

Open
opened 2026-03-12 15:33:13 +03:00 by kerem · 0 comments
Owner

Originally created by @acseven on GitHub (Apr 20, 2025).
Original GitHub issue: https://github.com/007revad/Synology_enable_M2_card/issues/63

Hi,

Hardware:

  • Synology DS1819+ DSM 7.2.2-72806-3
  • Synology E10M20-T1 PCIe card, detected,, 10Gbe in use with no issues.
  • Crucial P3 2TB M.2 NVMe (CT2000P3SSD801)

I fitted a Crucial P3 2TB M.2 NVMe (CT2000P3SSD801) in it but it isn't being recognized properly in DSM after running the m.2_enable script. I have since then pulled it out and tried refitting it.

In essence, after rebooting the drive appears but it soon disappears again; when I try to create a volume with it it has disappeared by the time I reach the drive selection.

Image

Image

Image

Image

I also added both M.2_enable and HDD db scripts to a task scheduler triggered task on shutdown.

M.2_enable first run:

Synology_enable_M2_volume v1.1.22
DS1819+ DSM 7.2.2-72806-3

StorageManager 1.0.0-00502

Using options:
Running from: /volume2/homes/me/syno_m.2_scripts/Synology_enable_M2_volume/syno_enable_m2_volume.sh
Backup successful.

Checking file.
193162 = 2f28a
0002f28a: 803E 00B8 0100 0000 7524 488B

Editing file.

Checking if file was successfully edited.
193162 = 2f28a
0002f28a: 803E 00B8 0100 0000 9090 488B
File successfully edited.

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

Enabled M.2 volume support.

The Synology needs to restart.

HDD db first run

Synology_HDD_db v3.6.111
DS1819+ x86_64 DSM 7.2.2-72806-3
StorageManager 1.0.0-00502

ds1819+_host_v7 version 8054

ds1819+_host version 4018

Using options: --noupdate
Running from: /volume2/homes/me/syno_m.2_scripts/Synology_HDD_db/syno_hdd_db.sh

HDD/SSD models found: 4
HDWG11A,0603,10000 GB
ST2000DL003-9VT166,CC32,2000 GB
WD30EFRX-68EUZN0,80.00A80,3000 GB
WD30EFRX-68EUZN0,82.00A82,3000 GB

No M.2 drives found

No M.2 PCIe cards found

No Expansion Units found

HDWG11A already exists in ds1819+_host_v7.db
HDWG11A already exists in ds1819+_host.db
HDWG11A already exists in ds1819+_host.db.new
ST2000DL003-9VT166 already exists in ds1819+_host_v7.db
ST2000DL003-9VT166 already exists in ds1819+_host.db
ST2000DL003-9VT166 already exists in ds1819+_host.db.new
Updated WD30EFRX-68EUZN0 in ds1819+_host_v7.db
WD30EFRX-68EUZN0 already exists in ds1819+_host.db
WD30EFRX-68EUZN0 already exists in ds1819+_host.db.new
Updated WD30EFRX-68EUZN0 in ds1819+_host_v7.db
WD30EFRX-68EUZN0 already exists in ds1819+_host.db
WD30EFRX-68EUZN0 already exists in ds1819+_host.db.new

Support disk compatibility already enabled.

Drive db auto updates already disabled.

DSM successfully checked disk compatibility.

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

M.2_enable secondrun:

Synology_enable_M2_volume v1.1.22
DS1819+ DSM 7.2.2-72806-3

StorageManager 1.0.0-00502

Using options:
Running from: /volume1/downloads/_scripts/syno_m.2_scripts/Synology_enable_M2_volume/syno_enable_m2_volume.sh
File already backed up.

Checking file.
193162 = 2f28a
0002f28a: 803E 00B8 0100 0000 9090 488B

File already edited.
Originally created by @acseven on GitHub (Apr 20, 2025). Original GitHub issue: https://github.com/007revad/Synology_enable_M2_card/issues/63 Hi, Hardware: - Synology DS1819+ DSM 7.2.2-72806-3 - Synology E10M20-T1 PCIe card, detected,, 10Gbe in use with no issues. - Crucial P3 2TB M.2 NVMe (CT2000P3SSD801) I fitted a Crucial P3 2TB M.2 NVMe (CT2000P3SSD801) in it but it isn't being recognized properly in DSM after running the m.2_enable script. I have since then pulled it out and tried refitting it. In essence, after rebooting the drive appears but it soon disappears again; when I try to create a volume with it it has disappeared by the time I reach the drive selection. ![Image](https://github.com/user-attachments/assets/0d002c8d-7457-43f9-a631-5b1696439b21) ![Image](https://github.com/user-attachments/assets/3c26e1e3-8a67-4896-88d4-0ea62c1d179b) ![Image](https://github.com/user-attachments/assets/c1e41411-5b48-4335-b9b7-c1d77a628a4a) ![Image](https://github.com/user-attachments/assets/79edcf3a-84ee-428c-b81a-29a0c4710844) I also added both M.2_enable and HDD db scripts to a task scheduler triggered task on shutdown. *M.2_enable first run:* ``` Synology_enable_M2_volume v1.1.22 DS1819+ DSM 7.2.2-72806-3 StorageManager 1.0.0-00502 Using options: Running from: /volume2/homes/me/syno_m.2_scripts/Synology_enable_M2_volume/syno_enable_m2_volume.sh Backup successful. Checking file. 193162 = 2f28a 0002f28a: 803E 00B8 0100 0000 7524 488B Editing file. Checking if file was successfully edited. 193162 = 2f28a 0002f28a: 803E 00B8 0100 0000 9090 488B File successfully edited. You can now create your M.2 storage pool in Storage Manager. Enabled M.2 volume support. The Synology needs to restart. ``` *HDD db first run* ``` Synology_HDD_db v3.6.111 DS1819+ x86_64 DSM 7.2.2-72806-3 StorageManager 1.0.0-00502 ds1819+_host_v7 version 8054 ds1819+_host version 4018 Using options: --noupdate Running from: /volume2/homes/me/syno_m.2_scripts/Synology_HDD_db/syno_hdd_db.sh HDD/SSD models found: 4 HDWG11A,0603,10000 GB ST2000DL003-9VT166,CC32,2000 GB WD30EFRX-68EUZN0,80.00A80,3000 GB WD30EFRX-68EUZN0,82.00A82,3000 GB No M.2 drives found No M.2 PCIe cards found No Expansion Units found HDWG11A already exists in ds1819+_host_v7.db HDWG11A already exists in ds1819+_host.db HDWG11A already exists in ds1819+_host.db.new ST2000DL003-9VT166 already exists in ds1819+_host_v7.db ST2000DL003-9VT166 already exists in ds1819+_host.db ST2000DL003-9VT166 already exists in ds1819+_host.db.new Updated WD30EFRX-68EUZN0 in ds1819+_host_v7.db WD30EFRX-68EUZN0 already exists in ds1819+_host.db WD30EFRX-68EUZN0 already exists in ds1819+_host.db.new Updated WD30EFRX-68EUZN0 in ds1819+_host_v7.db WD30EFRX-68EUZN0 already exists in ds1819+_host.db WD30EFRX-68EUZN0 already exists in ds1819+_host.db.new Support disk compatibility already enabled. Drive db auto updates already disabled. DSM successfully checked disk compatibility. You may need to reboot the Synology to see the changes. ``` *M.2_enable secondrun:* ``` Synology_enable_M2_volume v1.1.22 DS1819+ DSM 7.2.2-72806-3 StorageManager 1.0.0-00502 Using options: Running from: /volume1/downloads/_scripts/syno_m.2_scripts/Synology_enable_M2_volume/syno_enable_m2_volume.sh File already backed up. Checking file. 193162 = 2f28a 0002f28a: 803E 00B8 0100 0000 9090 488B File already edited. ```
Sign in to join this conversation.
No labels
pull-request
No milestone
No project
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_card#130
No description provided.