mirror of
https://github.com/007revad/Synology_enable_M2_volume.git
synced 2026-04-25 13:05:54 +03:00
[GH-ISSUE #102] Not working - 918+, DSM 7.2-64570 #22
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#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 @jerrell851 on GitHub (Aug 11, 2023).
Original GitHub issue: https://github.com/007revad/Synology_enable_M2_volume/issues/102
see picture.
@007revad commented on GitHub (Aug 12, 2023):
Did storage manager see the NVMe drives before you ran the scripts?
@jerrell851 commented on GitHub (Aug 12, 2023):
no.but syno_hdd_db.sh scripts can see.
@007revad commented on GitHub (Aug 12, 2023):
Some people have had issues with 7.2 update 2 or 7.2 update 3 not seeing their NVMe drives.
Do you want to roll back to 7.2 update 1 and see if storage manager then shows your NVMe drives? You won't lose any settings or data.
@jerrell851 commented on GitHub (Aug 12, 2023):
Followed the steps but the downgrade failed, including the script to upgrade to version 1.08.
1、run re-install scripts.
2、upload dsm os.(DS918+
3、wait restart
4、After restarting, control panel information.
5、Run hdd.sh
6、run enable.sh
7、storage manager not NVMe drives
@007revad commented on GitHub (Aug 12, 2023):
What does the following command return:
sudo -i nvme listCan you downgrade to DSM 7.2 (with Update 1) again but this time disable DSM Auto Updates and don't run the scripts.
If step 5 shows the NVMe drives, then run syno_hdd_db script.
@007revad commented on GitHub (Aug 13, 2023):
Also, what does the following command return:
ls /run/synostorage/disksAnd these:
@jerrell851 commented on GitHub (Aug 13, 2023):
Affected the use, test next time. But my downgrade steps are the same as you described, 1. disable automatic updates, 2. run the reinstall script, 3. manually install 7.2-64570-1-NanoPacked. However, the system information does not change to update 1.
@007revad commented on GitHub (Aug 15, 2023):
I just tested downgrading from 7.2 Update 2 to 7.2 (with Update 1) and after it rebooted it had 7.2 Update 3 installed (even though I have DSM set to notify me instead of auto updating. It looks like Synology consider update 3 is a critical update and is forcing it on people when they update to DSM 7.2.
I might try it again but this time with my Internet disconnected so it can't update to Update 3.
Do you have a real DS918+ or is DSM running in expenology?
What do each of the following commands return:
sudo -i nvme listls /run/synostorage/disksls /run/synostorage/disks/nvme0n1ls /run/synostorage/disks/nvme1n1get_key_value /etc.defaults/synoinfo.conf support_m2_poolget_key_value /etc/synoinfo.conf support_m2_poolget_key_value /etc.defaults/synoinfo.conf supportnvmeget_key_value /etc/synoinfo.conf supportnvme@jerrell851 commented on GitHub (Aug 16, 2023):
i'm running expenology.
There is currently no 918 operating environment, so the command you gave cannot be tested.
@007revad commented on GitHub (Aug 18, 2023):
There's a post on the xpenology forum here that says Peter Suh's M SHELL for TCRP FRIEND includes NVMe cache automatic recognition.
@MeowPerth commented on GitHub (Sep 17, 2023):
I had the same problem and it didn't work properly after using the “Synology_enable_M2_volume”. At present, I am in the DSM 7.2-64570 Update 3 version. The information obtained by executing these commands is for your reference.
@007revad commented on GitHub (Sep 19, 2023):
The
0 @drive model is a problem. I've seen something similar in syno_hdd_db before.I'll create a debug version of the script so we can see where it's getting that
0 @drive model from.@MeowPerth commented on GitHub (Sep 20, 2023):
'0 @ 'should be the reason why the firmware of my hard disk has been flashed, which causes the HDD model to be recognized as '0 @'.
However, this hard disk can be recognized and used normally, and DSM can also recognize and use it.
@MeowPerth commented on GitHub (Sep 20, 2023):
In addition, I would like to add some information:
I also tried to use " Synology_M2_volume", and the script ran normally, but after restarting, it was the same as before, and M was not recognized.
@007revad commented on GitHub (Sep 20, 2023):
Did the NVMe drive show in storage manager before you updated to DSM 7.2 Update 3?
Do the following commands list your NVMe drive?
ls /run/synostorage/disksls /sys/block | grep nvme@MeowPerth commented on GitHub (Sep 20, 2023):
None in synostorage, only HDD hard disk
@007revad commented on GitHub (Sep 21, 2023):
Can you try running syno_hdd_db with the -n option
./volume/OS/Script/syno_hdd_db.sh -nThen reboot.
@MeowPerth commented on GitHub (Sep 21, 2023):
NVME is also not working properly.
PS: I added a SATA SSD "S100Pro 1TB" and it works.
@007revad commented on GitHub (Sep 25, 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
@MeowPerth commented on GitHub (Sep 26, 2023):
It's working！It appears that “libsynonvme.so.1” must be modified.
@007revad commented on GitHub (Sep 26, 2023):
Excellent