[GH-ISSUE #150] DSM 7.2.1-69057 Won't support syno_hdd_db.sh #65

Closed
opened 2026-03-07 19:14:58 +03:00 by kerem · 12 comments
Owner

Originally created by @hari-bo on GitHub (Oct 3, 2023).
Original GitHub issue: https://github.com/007revad/Synology_HDD_db/issues/150

I was running the following M2 in an RAID-1 Volume Kingston NV2 2 TB SSD (SNV2S/2000G) with DSM 7.2-64570-2.
But after upgrading to DSM 7.2.1-69057 the devices aren't detected anymore.

With an SSH session I've runned manually syno_hdd_db.sh -nfr but it won't detect the M2 storage anymore, it seems dat Synology has changed something which prevent non-Synology M2 storage to be used.

HDD/SSD models found: 1
MG07ACA12TE,0103

No M.2 drives found

No M.2 PCIe cards found

No Expansion Units found

Backed up ds918+_host_v7.db
Updated MG07ACA12TE to ds918+_host_v7.db

Backed up synoinfo.conf

Disabled support disk compatibility.

Set max memory to 16384 GB.

Disabled drive db auto updates.

DSM successfully checked disk compatibility.

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

I've tried several reboots and DSM reinstall (rollback to previous version isn't possible without wiping the complete disks).

Originally created by @hari-bo on GitHub (Oct 3, 2023). Original GitHub issue: https://github.com/007revad/Synology_HDD_db/issues/150 I was running the following M2 in an RAID-1 Volume Kingston NV2 2 TB SSD (SNV2S/2000G) with DSM 7.2-64570-2. But after upgrading to DSM 7.2.1-69057 the devices aren't detected anymore. With an SSH session I've runned manually syno_hdd_db.sh -nfr but it won't detect the M2 storage anymore, it seems dat Synology has changed something which prevent non-Synology M2 storage to be used. ``` HDD/SSD models found: 1 MG07ACA12TE,0103 No M.2 drives found No M.2 PCIe cards found No Expansion Units found Backed up ds918+_host_v7.db Updated MG07ACA12TE to ds918+_host_v7.db Backed up synoinfo.conf Disabled support disk compatibility. Set max memory to 16384 GB. Disabled drive db auto updates. DSM successfully checked disk compatibility. You may need to reboot the Synology to see the changes. ``` I've tried several reboots and DSM reinstall (rollback to previous version isn't possible without wiping the complete disks).
kerem closed this issue 2026-03-07 19:14:59 +03:00
Author
Owner

@hari-bo commented on GitHub (Oct 4, 2023):

If I can provide more information just let me know.

<!-- gh-comment-id:1747399123 --> @hari-bo commented on GitHub (Oct 4, 2023): If I can provide more information just let me know.
Author
Owner

@007revad commented on GitHub (Oct 4, 2023):

Which Synology model do you have? Is it a real Synology NAS or Xpenology?

I upgraded from DSM 7.2-64570 to 7.2.1 and my M2 volume survived.

I also managed to rollback to 7.2-64570 without losing any data. See https://github.com/007revad/Synology_HDD_db/issues/149#issuecomment-1746325839

<!-- gh-comment-id:1747444190 --> @007revad commented on GitHub (Oct 4, 2023): Which Synology model do you have? Is it a real Synology NAS or Xpenology? I upgraded from DSM 7.2-64570 to 7.2.1 and my M2 volume survived. I also managed to rollback to 7.2-64570 without losing any data. See https://github.com/007revad/Synology_HDD_db/issues/149#issuecomment-1746325839
Author
Owner

@hari-bo commented on GitHub (Oct 4, 2023):

Which Synology model do you have? Is it a real Synology NAS or Xpenology?

I upgraded from DSM 7.2-64570 to 7.2.1 and my M2 volume survived.

I also managed to rollback to 7.2-64570 without losing any data. See #149 (comment)

I’ve a DS918+ no Xpenogy.

<!-- gh-comment-id:1747447492 --> @hari-bo commented on GitHub (Oct 4, 2023): > Which Synology model do you have? Is it a real Synology NAS or Xpenology? > > I upgraded from DSM 7.2-64570 to 7.2.1 and my M2 volume survived. > > I also managed to rollback to 7.2-64570 without losing any data. See [#149 (comment)](https://github.com/007revad/Synology_HDD_db/issues/149#issuecomment-1746325839) I’ve a DS918+ no Xpenogy.
Author
Owner

@007revad commented on GitHub (Oct 4, 2023):

What do each of the following commands return:

sudo -i nvme list

ls /run/synostorage/disks

ls /run/synostorage/disks/nvme0n1

ls /run/synostorage/disks/nvme1n1

get_key_value /etc.defaults/synoinfo.conf support_m2_pool

get_key_value /etc/synoinfo.conf support_m2_pool

get_key_value /etc.defaults/synoinfo.conf supportnvme

get_key_value /etc/synoinfo.conf supportnvme

<!-- gh-comment-id:1747679178 --> @007revad commented on GitHub (Oct 4, 2023): What do each of the following commands return: `sudo -i nvme list` `ls /run/synostorage/disks` `ls /run/synostorage/disks/nvme0n1` `ls /run/synostorage/disks/nvme1n1` `get_key_value /etc.defaults/synoinfo.conf support_m2_pool` `get_key_value /etc/synoinfo.conf support_m2_pool` `get_key_value /etc.defaults/synoinfo.conf supportnvme` `get_key_value /etc/synoinfo.conf supportnvme`
Author
Owner

@hari-bo commented on GitHub (Oct 5, 2023):

Here's the requested output.

sudo -i nvme list
empty

ls /run/synostorage/disks
sda  sdb  sdc (SATA Storage)

ls /run/synostorage/disks/nvme0n1
ls: cannot access '/run/synostorage/disks/nvme0n1': No such file or directory

ls /run/synostorage/disks/nvme1n1
ls: cannot access '/run/synostorage/disks/nvme1n1': No such file or directory

get_key_value /etc.defaults/synoinfo.conf support_m2_pool
no

get_key_value /etc/synoinfo.conf support_m2_pool
no

get_key_value /etc.defaults/synoinfo.conf supportnvme
yes

get_key_value /etc/synoinfo.conf supportnvme
yes

And i've got Home Assistant with Synology intergration and the M2 is then visible, but within the Storage Manager from DSM not.
Screenshot at Oct 05 12-00-15

<!-- gh-comment-id:1748533917 --> @hari-bo commented on GitHub (Oct 5, 2023): Here's the requested output. ``` sudo -i nvme list empty ls /run/synostorage/disks sda sdb sdc (SATA Storage) ls /run/synostorage/disks/nvme0n1 ls: cannot access '/run/synostorage/disks/nvme0n1': No such file or directory ls /run/synostorage/disks/nvme1n1 ls: cannot access '/run/synostorage/disks/nvme1n1': No such file or directory get_key_value /etc.defaults/synoinfo.conf support_m2_pool no get_key_value /etc/synoinfo.conf support_m2_pool no get_key_value /etc.defaults/synoinfo.conf supportnvme yes get_key_value /etc/synoinfo.conf supportnvme yes ``` And i've got Home Assistant with Synology intergration and the M2 is then visible, but within the Storage Manager from DSM not. ![Screenshot at Oct 05 12-00-15](https://github.com/007revad/Synology_HDD_db/assets/2697468/29d88ae2-e0e5-49d8-be50-bead036e3a5b)
Author
Owner

@007revad commented on GitHub (Oct 5, 2023):

Can you run this script and see if that makes the NVMe drive show in storage manager.
https://github.com/AuxXxilium/arc-extensions/blob/main/nvmecache/all/usr/sbin/nvmecache.sh

download_button

If that works can you then run syno_hdd_db.sh again.

<!-- gh-comment-id:1748601484 --> @007revad commented on GitHub (Oct 5, 2023): Can you run this script and see if that makes the NVMe drive show in storage manager. https://github.com/AuxXxilium/arc-extensions/blob/main/nvmecache/all/usr/sbin/nvmecache.sh ![download_button](https://github.com/007revad/Synology_enable_M2_volume/assets/39733752/f550113a-9d7d-43c2-993a-b1c180a6181e) If that works can you then run syno_hdd_db.sh again.
Author
Owner

@hari-bo commented on GitHub (Oct 5, 2023):

I've runned the script under root user (it gives no output) but within the GUI and running syno_hdd_db.sh shows no M2 device yet.

<!-- gh-comment-id:1748704144 --> @hari-bo commented on GitHub (Oct 5, 2023): I've runned the script under root user (it gives no output) but within the GUI and running syno_hdd_db.sh shows no M2 device yet.
Author
Owner

@007revad commented on GitHub (Oct 5, 2023):

I've runned the script under root user (it gives no output

It should have output something like this:
nvme0 - 0000:00:14.0 - 303030303a30303a31342e30

The only reason it would output nothing is if ls /sys/class/nvme returned nothing.

What do these commands return:

ls /sys/class/nvme

ls /sys/block | grep nvme

I wonder if Synology have blacklisted kingston M2 drives somewhere in DSM 7.2.1. I installed 7.2.1 on my DS720+ and still shows my WD NVMe drive in storage manager. After I ran my syno_enable_m2_volume.sh script I was able to create a volume in storage manager.

Do you want to try https://github.com/007revad/Synology_enable_M2_volume

<!-- gh-comment-id:1748797960 --> @007revad commented on GitHub (Oct 5, 2023): > I've runned the script under root user (it gives no output It should have output something like this: `nvme0 - 0000:00:14.0 - 303030303a30303a31342e30` The only reason it would output nothing is if `ls /sys/class/nvme` returned nothing. What do these commands return: `ls /sys/class/nvme` `ls /sys/block | grep nvme` I wonder if Synology have blacklisted kingston M2 drives somewhere in DSM 7.2.1. I installed 7.2.1 on my DS720+ and still shows my WD NVMe drive in storage manager. After I ran my syno_enable_m2_volume.sh script I was able to create a volume in storage manager. Do you want to try https://github.com/007revad/Synology_enable_M2_volume
Author
Owner

@hari-bo commented on GitHub (Oct 5, 2023):

There's no ouput when requesting the information.
I've runned the script which shows an reboot messaged, after that no M2 storage visible.

./syno_enable_m2_volume.sh -c
Synology_enable_M2_volume v1.0.10
DS918+ DSM 7.2.1-69057

Using options: -c
Running from: /volume2/CUSTOM/Synology_enable_M2_volume/syno_enable_m2_volume.sh
File already backed up.

Checking value in file.
193018 = 2f1fa
0002f1fa: 803E 00B8 0100 0000 9090 488B

File already edited.

Checking value in backup file.
193018 = 2f1fa
0002f1fa: 803E 00B8 0100 0000 7524 488B

Backup file is unedited.

This weekend i will remove the Kingston M2 devices, and will add an spare Adata Xpg Sx8200 Pro 512Gb M.2. Will let you know the outcome.

<!-- gh-comment-id:1748868232 --> @hari-bo commented on GitHub (Oct 5, 2023): There's no ouput when requesting the information. I've runned the script which shows an reboot messaged, after that no M2 storage visible. ``` ./syno_enable_m2_volume.sh -c Synology_enable_M2_volume v1.0.10 DS918+ DSM 7.2.1-69057 Using options: -c Running from: /volume2/CUSTOM/Synology_enable_M2_volume/syno_enable_m2_volume.sh File already backed up. Checking value in file. 193018 = 2f1fa 0002f1fa: 803E 00B8 0100 0000 9090 488B File already edited. Checking value in backup file. 193018 = 2f1fa 0002f1fa: 803E 00B8 0100 0000 7524 488B Backup file is unedited. ``` This weekend i will remove the Kingston M2 devices, and will add an spare Adata Xpg Sx8200 Pro 512Gb M.2. Will let you know the outcome.
Author
Owner

@hari-bo commented on GitHub (Oct 6, 2023):

I've got it working again. I did the following steps.

  1. Shutdown NAS.
  2. Remove all M2 devices.
  3. Power on NAS.
  4. Shutdown NAS.
  5. Add M2 devices Kingston and Adata.
  6. Power on NAS.
  7. Run ./syno_hdd_db.sh -nfr
  8. All M2 devices are detected.
root@DiskStation:/volume2/CUSTOM/Synology# ./syno_hdd_db.sh -nfr
Synology_HDD_db v3.1.64
DS918+ DSM 7.2.1-69057
Using options: -nfr
Running from: /volume2/CUSTOM/Synology/syno_hdd_db.sh

HDD/SSD models found: 1
MG07ACA12TE,0103

M.2 drive models found: 2
ADATA SX8200PNP,32B3T8EA
KINGSTON SNV2S2000G,SBM02103

No M.2 PCIe cards found

No Expansion Units found

MG07ACA12TE already exists in ds918+_host_v7.db
Updated ADATA SX8200PNP to ds918+_host_v7.db
Added KINGSTON SNV2S2000G to ds918+_host_v7.db

Support disk compatibility already disabled.

Max memory already set to 16 GB.

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.
<!-- gh-comment-id:1750641050 --> @hari-bo commented on GitHub (Oct 6, 2023): I've got it working again. I did the following steps. 1. Shutdown NAS. 2. Remove all M2 devices. 3. Power on NAS. 4. Shutdown NAS. 5. Add M2 devices Kingston and Adata. 6. Power on NAS. 7. Run ./syno_hdd_db.sh -nfr 8. All M2 devices are detected. ``` root@DiskStation:/volume2/CUSTOM/Synology# ./syno_hdd_db.sh -nfr Synology_HDD_db v3.1.64 DS918+ DSM 7.2.1-69057 Using options: -nfr Running from: /volume2/CUSTOM/Synology/syno_hdd_db.sh HDD/SSD models found: 1 MG07ACA12TE,0103 M.2 drive models found: 2 ADATA SX8200PNP,32B3T8EA KINGSTON SNV2S2000G,SBM02103 No M.2 PCIe cards found No Expansion Units found MG07ACA12TE already exists in ds918+_host_v7.db Updated ADATA SX8200PNP to ds918+_host_v7.db Added KINGSTON SNV2S2000G to ds918+_host_v7.db Support disk compatibility already disabled. Max memory already set to 16 GB. 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. ```
Author
Owner

@hari-bo commented on GitHub (Oct 6, 2023):

Everything is fine. And donated for the great support, thanks!

<!-- gh-comment-id:1750906493 --> @hari-bo commented on GitHub (Oct 6, 2023): Everything is fine. And donated for the great support, thanks!
Author
Owner

@leginag commented on GitHub (Nov 17, 2023):

Just adding that I had to follow the "physically remove M2 drives" instructions above to fix it on my 920+ when updating to 7.2.1

<!-- gh-comment-id:1816939046 --> @leginag commented on GitHub (Nov 17, 2023): Just adding that I had to follow the "physically remove M2 drives" instructions above to fix it on my 920+ when updating to 7.2.1
Sign in to join this conversation.
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_HDD_db#65
No description provided.