[GH-ISSUE #55] WD-SN850x NvME SSD's not found?

kerem commented

2026-03-07 19:14:08 +03:00

Owner

Originally created by @quadcom on GitHub (Apr 12, 2023).
Original GitHub issue: https://github.com/007revad/Synology_HDD_db/issues/55

Hey all.

I ran the script and the system still cannot see the 2 WD-SN850x NvME drives installed in order to create a cache pool.

Any ideas?

Synology_HDD_db v2.0.35
DS1522+ DSM 7.1.1-42962-4

HDD/SSD models found: 2
ST10000VN0004-1ZD101,SC60
ST14000NM001G-2KJ103,SN03

No M.2 drives found

No M.2 cards found

No Expansion Units found

ST10000VN0004-1ZD101 already exists in ds1522+_host_v7.db
ST10000VN0004-1ZD101 already exists in ds1522+_host_v7.db.new
ST14000NM001G-2KJ103 already exists in ds1522+_host_v7.db
ST14000NM001G-2KJ103 already exists in ds1522+_host_v7.db.new

Disabled support memory compatibility.

Disabled drive db auto updates.

    "ST10000VN0004-1ZD101": {
      "SC60": {
        "compatibility_interval": [
          {
            "compatibility": "support",
            "not_yet_rolling_status": "support",
            "fw_dsm_update_status_notify": false,
            "barebone_installable": true
          }
        ]
      },
      "default": {

    "ST14000NM001G-2KJ103": {
      "SN03": {
        "compatibility_interval": [
          {
            "compatibility": "support",
            "not_yet_rolling_status": "support",
            "fw_dsm_update_status_notify": false,
            "barebone_installable": true
          }
        ]
      },
      "default": {

DSM successfully checked disk compatibility.

Originally created by @quadcom on GitHub (Apr 12, 2023). Original GitHub issue: https://github.com/007revad/Synology_HDD_db/issues/55 Hey all. I ran the script and the system still cannot see the 2 WD-SN850x NvME drives installed in order to create a cache pool. Any ideas? ``` Synology_HDD_db v2.0.35 DS1522+ DSM 7.1.1-42962-4 HDD/SSD models found: 2 ST10000VN0004-1ZD101,SC60 ST14000NM001G-2KJ103,SN03 No M.2 drives found No M.2 cards found No Expansion Units found ST10000VN0004-1ZD101 already exists in ds1522+_host_v7.db ST10000VN0004-1ZD101 already exists in ds1522+_host_v7.db.new ST14000NM001G-2KJ103 already exists in ds1522+_host_v7.db ST14000NM001G-2KJ103 already exists in ds1522+_host_v7.db.new Disabled support memory compatibility. Disabled drive db auto updates. "ST10000VN0004-1ZD101": { "SC60": { "compatibility_interval": [ { "compatibility": "support", "not_yet_rolling_status": "support", "fw_dsm_update_status_notify": false, "barebone_installable": true } ] }, "default": { "ST14000NM001G-2KJ103": { "SN03": { "compatibility_interval": [ { "compatibility": "support", "not_yet_rolling_status": "support", "fw_dsm_update_status_notify": false, "barebone_installable": true } ] }, "default": { DSM successfully checked disk compatibility. ``` ![image](https://user-images.githubusercontent.com/7085931/231602107-9414f65f-dd6d-408b-b4b5-e5bfd585559d.png) ![image](https://user-images.githubusercontent.com/7085931/231602221-ca23aed4-ef9c-43f7-9785-25794c545e61.png) ![image](https://user-images.githubusercontent.com/7085931/231602352-4a5ecf26-ff06-4ba1-8d48-ff74c1729140.png)

kerem closed this issue

2026-03-07 19:14:08 +03:00

kerem commented

2026-03-07 19:14:09 +03:00

Author

Owner

@007revad commented on GitHub (Apr 16, 2023):

What does the following command return:
for d in /sys/block/nvme*; do echo $d; done

It should return /sys/block/nvme0n1 and /sys/block/nvme1n1

If it did see what these commands return:
cat /sys/block/nvme0n1/device/model

cat /sys/block/nvme1n1/device/model

cat /sys/block/nvme0n1/device/firmware_rev

cat /sys/block/nvme1n1/device/firmware_rev

@007revad commented on GitHub (Apr 16, 2023): What does the following command return: `for d in /sys/block/nvme*; do echo $d; done` It should return **/sys/block/nvme0n1** and **/sys/block/nvme1n1** If it did see what these commands return: `cat /sys/block/nvme0n1/device/model` `cat /sys/block/nvme1n1/device/model` `cat /sys/block/nvme0n1/device/firmware_rev` `cat /sys/block/nvme1n1/device/firmware_rev`

kerem commented

2026-03-07 19:14:09 +03:00

Author

Owner

@quadcom commented on GitHub (Apr 16, 2023):

Hmmmm,

not in my case

XXXXX@DS1522:/$ for d in /sys/block/nvme*; do echo $d; done
/sys/block/nvme*
XXXXX@DS1522:/$

@quadcom commented on GitHub (Apr 16, 2023): Hmmmm, not in my case ``` XXXXX@DS1522:/$ for d in /sys/block/nvme*; do echo $d; done /sys/block/nvme* XXXXX@DS1522:/$ ```

kerem commented

2026-03-07 19:14:09 +03:00

Author

Owner

@quadcom commented on GitHub (Apr 16, 2023):

I shut down the system and restarted it. When it came back up, slot 2 found the SSD. But not slot 1.

I then shut down the system to check slot 1 in case I somehow screwed up seating the drive. But I reseated slot 2 first by accident. I reseated slot 1, plugged in power, and fired it back up.

Now it doesn't see either SSD installed again!

Bum unit, perhaps? The problem is, unless I buy an outrageously overpriced Synology SSD, I can't call support to troubleshoot a lemon board! WhyTF are they forcing this position on drive compatibility? I mean, the standards for drives have been around for a long time now. Give a warning, fine but to outright block them. Not cool.

@quadcom commented on GitHub (Apr 16, 2023): I shut down the system and restarted it. When it came back up, slot 2 found the SSD. But not slot 1. I then shut down the system to check slot 1 in case I somehow screwed up seating the drive. But I reseated slot 2 first by accident. I reseated slot 1, plugged in power, and fired it back up. Now it doesn't see either SSD installed again! Bum unit, perhaps? The problem is, unless I buy an outrageously overpriced Synology SSD, I can't call support to troubleshoot a lemon board! WhyTF are they forcing this position on drive compatibility? I mean, the standards for drives have been around for a long time now. Give a warning, fine but to outright block them. Not cool.

kerem commented

2026-03-07 19:14:09 +03:00

Author

Owner

@quadcom commented on GitHub (Apr 16, 2023):

I had a thought, because I was SSH with my user account on the NAS, I tried to sudo the command. But when I do that, it fails.

@DS1522:/$ sudo for d in /sys/block/nvme*; do echo $d; done
-sh: syntax error near unexpected token `do'

@quadcom commented on GitHub (Apr 16, 2023): I had a thought, because I was SSH with my user account on the NAS, I tried to sudo the command. But when I do that, it fails. ``` @DS1522:/$ sudo for d in /sys/block/nvme*; do echo $d; done -sh: syntax error near unexpected token `do' ```

kerem commented

2026-03-07 19:14:09 +03:00

Author

Owner

@quadcom commented on GitHub (Apr 16, 2023):

If this helps figure out what's going on.

DSM 7.1.1-42962 Update 4

XXXX@DS1522:/sys/block$  ls -a
.     dm-1   loop1  loop4  loop7  md2   ram1   ram12  ram15  ram4  ram7  sata1  sata4     zram0
..    dm-2   loop2  loop5  md0    md3   ram10  ram13  ram2   ram5  ram8  sata2  sata5     zram1
dm-0  loop0  loop3  loop6  md1    ram0  ram11  ram14  ram3   ram6  ram9  sata3  synoboot
XXXX@DS1522:/sys/block$

@quadcom commented on GitHub (Apr 16, 2023): If this helps figure out what's going on. DSM 7.1.1-42962 Update 4 ``` XXXX@DS1522:/sys/block$ ls -a . dm-1 loop1 loop4 loop7 md2 ram1 ram12 ram15 ram4 ram7 sata1 sata4 zram0 .. dm-2 loop2 loop5 md0 md3 ram10 ram13 ram2 ram5 ram8 sata2 sata5 zram1 dm-0 loop0 loop3 loop6 md1 ram0 ram11 ram14 ram3 ram6 ram9 sata3 synoboot XXXX@DS1522:/sys/block$ ```

kerem commented

2026-03-07 19:14:09 +03:00

Author

Owner

@quadcom commented on GitHub (Apr 16, 2023):

A long shot, but do you know if a RAM requirement exists for NvME drives to become available? I have the stock 8GB. I never planned on running any containers or apps. This is strictly a file server for video media so I didn't see the need for more RAM.

@quadcom commented on GitHub (Apr 16, 2023): A long shot, but do you know if a RAM requirement exists for NvME drives to become available? I have the stock 8GB. I never planned on running any containers or apps. This is strictly a file server for video media so I didn't see the need for more RAM.

kerem commented

2026-03-07 19:14:09 +03:00

Author

Owner

@007revad commented on GitHub (Apr 16, 2023):

@DS1522:/$ sudo for d in /sys/block/nvme*; do echo $d; done
-sh: syntax error near unexpected token `do'

sudo doesn't like the for command so you need to do this:
sudo sh -c 'for d in /sys/block/nvme*; do echo $d; done'

But it probably won't make a difference to the result you're getting.

@007revad commented on GitHub (Apr 16, 2023): > @DS1522:/$ sudo for d in /sys/block/nvme*; do echo $d; done > -sh: syntax error near unexpected token `do' sudo doesn't like the for command so you need to do this: `sudo sh -c 'for d in /sys/block/nvme*; do echo $d; done'` But it probably won't make a difference to the result you're getting.

kerem commented

2026-03-07 19:14:09 +03:00

Author

Owner

@007revad commented on GitHub (Apr 16, 2023):

do you know if a RAM requirement exists for NvME drives to become available?

Not that I'm aware of. Memory requirements only seem to be for volumes larger than 108TB or when using deduplication or LUNs etc.

Even if the NVMe drives aren't supported they should still show up in storage manager (with a warning saying they're unsupported).

I would try reseating the NVMe drives again. When I upgraded the memory on my DS1821+ I had to reseat the memory twice before it would boot up. And maybe try just 1 NVMe drive at a time to determine if one of the drives is faulty or if one of the M.2 slots is faulty.

@007revad commented on GitHub (Apr 16, 2023): > do you know if a RAM requirement exists for NvME drives to become available? Not that I'm aware of. Memory requirements only seem to be for volumes larger than 108TB or when using deduplication or LUNs etc. Even if the NVMe drives aren't supported they should still show up in storage manager (with a warning saying they're unsupported). I would try reseating the NVMe drives again. When I upgraded the memory on my DS1821+ I had to reseat the memory twice before it would boot up. And maybe try just 1 NVMe drive at a time to determine if one of the drives is faulty or if one of the M.2 slots is faulty.

kerem commented

2026-03-07 19:14:10 +03:00

Author

Owner

@007revad commented on GitHub (Apr 17, 2023):

Have these NVMe drives been used in something else before you installed them in the Synology?

In the past I've installed drives that had been used in a PC and DSM ignored the drives as if they didn't exist. I had to put the drives back in a PC and delete all partitions on the drives. After that DSM saw the drives.

@007revad commented on GitHub (Apr 17, 2023): Have these NVMe drives been used in something else before you installed them in the Synology? In the past I've installed drives that had been used in a PC and DSM ignored the drives as if they didn't exist. I had to put the drives back in a PC and delete all partitions on the drives. After that DSM saw the drives.

kerem commented

2026-03-07 19:14:10 +03:00

Author

Owner

@quadcom commented on GitHub (Apr 17, 2023):

These two were brand new out of the box.

It's too bad we can't see in the bios of the MB to see what hardware it sees.

I held Synology in high regard after I bought my DS1515+. I went and added a DX513 and then a DX517 expansion for it. But this experience, with overly restricting media is pissing me off!

Thinking I should have built my own TruNas box instead!

@quadcom commented on GitHub (Apr 17, 2023): These two were brand new out of the box. It's too bad we can't see in the bios of the MB to see what hardware it sees. I held Synology in high regard after I bought my DS1515+. I went and added a DX513 and then a DX517 expansion for it. But this experience, with overly restricting media is pissing me off! Thinking I should have built my own TruNas box instead!

kerem referenced this issue

2026-03-07 19:17:15 +03:00

[PR #34] [MERGED] Develop #228

kerem referenced this issue

2026-03-11 11:36:26 +03:00

[GH-ISSUE #23] ERROR No drives found! #516

kerem referenced this issue

2026-03-12 16:15:24 +03:00

[GH-ISSUE #23] ERROR No drives found! #724

kerem referenced this issue

2026-03-12 17:39:45 +03:00

[PR #34] [MERGED] Develop #890