mirror of
https://github.com/007revad/Synology_HDD_db.git
synced 2026-04-25 13:45:59 +03:00
[GH-ISSUE #56] Nvme detected but no disk #22
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Synology_HDD_db#22
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Lesiu76 on GitHub (Apr 13, 2023).
Original GitHub issue: https://github.com/007revad/Synology_HDD_db/issues/56
Hi,
I don't know what i'm doing wrong.
after running script my nvme installed on pci card is detected and added to compatibility list. However disk is not shown in dsm 7 under hdd/ssd and can't create pool or cache.
Can it be that i'm using some simple pci converter to nvme ? Not approved by Synology.
RS1221+
DSM 7.1.1 u4
Script - latest
M2 drive ssd 960 pro samsung
Also when running script: i have error on line 500 /run/synostorage/disk/$(basename -- "$d")/m2_pool_support: No such file or directory
Script also reporting:
No M.2 cards found
No Expansion Units found
@007revad commented on GitHub (Apr 16, 2023):
That error is interesting because to get that far your Synology must have a /sys/block/nvme device but no /run/synostorage/disks/nvme active disk.
I would assume it is definitely because the PCIe card is not a Synology PCIe card. I do have another script that may trick DSM into thinking your PCIe card is a Synology card. https://github.com/007revad/Synology_enable_M2_volume
@007revad commented on GitHub (Apr 26, 2023):
OP not responding