mirror of
https://github.com/007revad/Synology_enable_M2_volume.git
synced 2026-04-25 21:15:58 +03:00
[GH-ISSUE #99] Not working - 923+, DSM 7.2-64570 Update 1, Samsung 980 Pro #224
Labels
No labels
enhancement
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Synology_enable_M2_volume#224
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 @ghost on GitHub (Jul 31, 2023).
Original GitHub issue: https://github.com/007revad/Synology_enable_M2_volume/issues/99
Followed all instructions, rebooted, not detecting the drive at all.
When I ran the
hdd_db.shscript, it said no M.2 drives found.@007revad commented on GitHub (Jul 31, 2023):
Shut down the Synology then check the M.2 drive is seated correctly. When you boot the Synology you should see the M.2 in storage manager shown as a cache drive.
@ghost commented on GitHub (Aug 1, 2023):
Nothing showing unfortunately. Drive is definitely seated correctly. Also, took it out, placed in another machine and checked it was working + formatted again.
Should I run through the steps again..?
@ghost commented on GitHub (Aug 1, 2023):
Nothing showing unfortunately. Drive is definitely seated correctly. Also, took it out, placed in another machine and checked it was working + formatted again.
Should I run through the steps again..?
@007revad commented on GitHub (Aug 1, 2023):
It wouldn't hurt. A few people have needed to run this script (or the Synology_HDD_db script) a few times before it worked.
You could also try this other script as well: https://github.com/007revad/Synology_HDD_db
@MischaM26 commented on GitHub (Aug 2, 2023):
just finished installation of same M.2, same DSM version on a 723+. Works flawlessly.
Thanks a lot Dave!
@ghost commented on GitHub (Aug 7, 2023):
@007revad sorry to pester again, but still having no luck with either script:
Running multiple times I get the same results, no change in logs, no change in the drives available through UX
@007revad commented on GitHub (Aug 7, 2023):
Sorry I closed this issue. I forgot there were 2 different people commenting.
Did your Samsung 980 Pro show up in storage manager as a cache drive before you ran either script?
Run both scripts with their --restore option and answer y to let the syno_enable_m2_volume script reboot the DS923+
Then check that storage manager shows the Samsung 980 Pro as a cache drive in the Built-In M.2 Slot.
I just had a thought. Maybe if you only have 1 NVMe drive it needs to be in slot 1. See the red circled raised 1 and 2 in this image: https://imgur.com/jJPDBUg
Do the following command list any NVMe drives?
ls /dev/nvme*sudo -i nvme list@ghost commented on GitHub (Aug 7, 2023):
syno_hdd_db,sh hung after the ds923+_host_v7.db, so I had to kill the process.
Yes the HDD is stored in slot 1
--
After rebooting, I tried re-running and i see an extra log underneath "M.2 volume support already enabled"
.
--
!!Now the Storage Manager doesn't seem to exist
I re-ran syno_hdd_db and Storage Manager is showing again, but still no NVME drives avail
@007revad commented on GitHub (Aug 7, 2023):
DSM definitely is not seeing your Samsung 980 Pro.
Can you disable the scheduled tasks for both scripts. Next shut down the DS923+ and move the Samsung 980 Pro to slot 2. Then boot up and check if storage manager now shows your NVMe drive.
@007revad commented on GitHub (Aug 20, 2023):
OP not responding
@007revad commented on GitHub (Aug 20, 2023):
OP not responding
@ghost commented on GitHub (Sep 7, 2023):
Sorry for not replying, had a bit on.
Ok, so this was really starting to bug me. There was weird behaviour, my Storage Manager kept disappearing every time I ran the restore option on this script.
I decided to do a full reset of my device. The 980 Pro is still not detected at all. I pulled an old Intel SSD out of another laptop, and that is working.
I ran the script again on the completely new setup, with the Intel SSD showing in drives and I am able to create a storage pool with the Intel drive.
Going to run down to electronics store and get an enclosure to try some things with this 980 Pro, and get my drives for the storage pool.