Jump to content
XPEnology Community

NVMe cache support


advin

Recommended Posts

Thanks for all the efford. Works on "6.2.3-25426".

 

Just one question, I can not select R/W cache. It is disabled, any guess why ?

 

123.PNG

 

 

I'll answer my question. It will help next hits. It is greyed out because I only have one nvme drive installed that is why I am limited with the read-only cache.

 

Edited by Jlozde
Link to comment
Share on other sites

I am having some problem with the configuration of my nvme in a clean installation 6.2.3

 

through ssh it is seen that the system recognizes the disk but in the storage manager it does not appear

 

I have tried the script provided in previous pages but I don't get anything: S

 

root@abc:~# nvme list
Node             SN                   Model                                    Namespace Usage                      Format           FW Rev
---------------- -------------------- ---------------------------------------- --------- -------------------------- ---------------- --------
/dev/nvme0n1     1842E1D1E662         CT500P1SSD8                              1         500.11  GB / 500.11  GB    512   B +  0 B   P3CR010
/dev/nvme0n1p1   1842E1D1E662         CT500P1SSD8                              1         500.11  GB / 500.11  GB    512   B +  0 B   P3CR010
/dev/nvme0n1p2   1842E1D1E662         CT500P1SSD8                              1         500.11  GB / 500.11  GB    512   B +  0 B   P3CR010
/dev/nvme0n1p3   1842E1D1E662         CT500P1SSD8                              1         500.11  GB / 500.11  GB    512   B +  0 B   P3CR010

 

Link to comment
Share on other sites

On 6/5/2020 at 12:55 PM, AsTuRkInG said:

I don't know whay i'm doing wrong

 

I put libNVMEpatch.sh on /usr/local/etc/rc.d/ with 0755 permisions and reboot.

 

This isn't enough?

The drive must be with a partition table specific or something?

 

Please have a look at posts: 91 / 93 / 98 

Link to comment
Share on other sites

  • 2 weeks later...
22 minutes ago, mervincm said:

Synology does not permit the use of NVME as storage, only cache, at lease in the 918+

Yes, I understand that but before applying the NVME patch, synology recognize nvme drives as normal drives only available to use as storage drives. So, I'm just wondering if there's a way to remove the patch.

Link to comment
Share on other sites

That is incorrect. Without the patch they are not recognized at all by Synology's utilities (they are accessible by Linux).  You can hack them in as storage but it is not supported or safe, and it does not matter whether the patch is installed or not.  If you want to remove the patch, put the original file back.

Edited by flyride
  • Like 1
Link to comment
Share on other sites

7 hours ago, flyride said:

That is incorrect. Without the patch they are not recognized at all by Synology's utilities (they are accessible by Linux).  You can hack them in as storage but it is not supported or safe, and it does not matter whether the patch is installed or not.  If you want to remove the patch, put the original file back.

Thank you so much for clearification.

Link to comment
Share on other sites

  • 2 weeks later...
  • 3 weeks later...
root@archive:/usr/lib# ls -la *nvme*
lrwxrwxrwx 1 root root    16 May 19 19:54 libsynonvme.so -> libsynonvme.so.1
-rw-r--r-- 1 root root 37642 Jul 18 11:15 libsynonvme.so.1
-rw-r--r-- 1 root root 37642 Jul 18 11:15 libsynonvme.so.1.bak
root@archive:/usr/lib# diff libsynonvme.so.1 libsynonvme.so.1.bak
Binary files libsynonvme.so.1 and libsynonvme.so.1.bak differ
root@archive:/usr/lib# tail -5 /var/log/messages
2020-07-21T09:03:41-07:00 archive synostoraged: nvme_slot_info_get.c:119 Fail to strip the address of device from PHYSDEVDRIVER=nvme
2020-07-21T09:03:41-07:00 archive synostoraged: nvme_slot_info_get.c:119 Fail to strip the address of device from PHYSDEVDRIVER=nvme
2020-07-21T09:04:41-07:00 archive synostoraged: SYSTEM: Last message 'nvme_slot_info_get.c' repeated 1 times, suppressed by syslog-ng on archive
2020-07-21T09:04:41-07:00 archive synostoraged: nvme_slot_info_get.c:119 Fail to strip the address of device from PHYSDEVDRIVER=nvme
2020-07-21T09:04:41-07:00 archive synostoraged: nvme_slot_info_get.c:119 Fail to strip the address of device from PHYSDEVDRIVER=nvme
root@archive:/usr/lib#

 

Link to comment
Share on other sites

root@archive:/usr/lib# nvme list
Node             SN                   Model                                    Namespace Usage                      Format           FW Rev
---------------- -------------------- ---------------------------------------- --------- -------------------------- ---------------- --------
/dev/nvme0n1     PHBT721608GH016D     INTEL MEMPEK1W016GA                      1          14.40  GB /  14.40  GB    512   B +  0 B   K3110310
/dev/nvme0n1p1   PHBT721608GH016D     INTEL MEMPEK1W016GA                      1          14.40  GB /  14.40  GB    512   B +  0 B   K3110310
root@archive:/usr/lib# udevadm info /dev/nvme0
P: /devices/pci0000:00/0000:00:13.0/0000:01:00.0/nvme/nvme0
N: nvme0
E: DEVNAME=/dev/nvme0
E: DEVPATH=/devices/pci0000:00/0000:00:13.0/0000:01:00.0/nvme/nvme0
E: MAJOR=250
E: MINOR=0
E: PHYSDEVBUS=pci
E: PHYSDEVDRIVER=nvme
E: PHYSDEVPATH=/devices/pci0000:00/0000:00:13.0/0000:01:00.0
E: SUBSYSTEM=nvme
E: SYNO_INFO_PLATFORM_NAME=apollolake
E: SYNO_KERNEL_VERSION=4.4
E: USEC_INITIALIZED=212638

root@archive:/usr/lib#

 

Link to comment
Share on other sites

I applied -2 patch to my test system via auto update and , as a test, I even left the read-only cache on NVME enabled. For some strange reason it failed to restart correctly (OS didnt appear to start) but with a physical power down and power up, everythings seems to be working, NVME R-O cache still working.

 

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...