Jump to content
XPEnology Community

NVMe cache support


advin

Recommended Posts

3 hours ago, Loredan said:

 

In 7.2 RC does not work.

DVA3221, v0.9.4.3-2

 

root@NAS:~# curl -L "https://raw.githubusercontent.com/PeterSuh-Q3/tcrp-addons/master/nvme-cache/src/nvme-cache.sh" -O
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  4214  100  4214    0     0  23282      0 --:--:-- --:--:-- --:--:-- 23411
root@NAS:~# chmod +x nvme-cache.sh
root@NAS:~# ./nvme-cache.sh
Collecting 1st nvme paths
Found local 1st nvme with path 0000:00:1b.0
3a31 622e 3000
3162 2e30

Collecting 2nd nvme paths
device node not found
Found local 2nd nvme with path
Not found local 2nd nvme
sed: can't read /etc.defaults/extensionPorts: No such file or directory
cat: /etc.defaults/extensionPorts: No such file or directory
root@NAS:~#

 

 

Fixed error script related to DVA3221.
But in 7.2 RC, NVMe cache is not enabled.
I'll keep looking for the cause.

https://github.com/PeterSuh-Q3/tcrp-addons/commit/f3d61aab34946829099df6624625039eeda8041b

  • Thanks 1
Link to comment
Share on other sites

nvme-cache.sh has been modified again for 7.2 RC.
Re-adjusted the libsynonvme.so.1 hex patch because there was an unrecognized issue on DS918+ / DS1621xs+.
If you are already using the 7.2 RC loader and nvme-cache.sh , you will need to rebuild the loader if you are using M SHELL for TCRP ,
If you use only nvme-cache.sh separately, please proceed with the patch again with the curl command.

 

The location of the PCIE hexacode of 7.2 RC was different, but the value was the same.

 

I think it will be maintained in the official version of 7.2.

I don't see it as a waste of time.
Denverton's unrecognized issue still persists.

  • Thanks 1
Link to comment
Share on other sites

  • 4 weeks later...
Le 06/03/2023 à 14:05, Peter Suh a dit :

I've heard that some ARPL users have had success recognizing the NVMe cache using my nvme-cache.sh.

Hi, thanks guys for this hard work !
I'm using ARPL v1.1-beta2a, DS918+, 7.1.1 build 42962 update 5

I executed bash -c "$(curl "https://raw.githubusercontent.com/PeterSuh-Q3/tcrp-addons/master/nvme-cache/src/nvme-cache.sh")", then I rebooted thru SSH because WebUI was lost, and when rebooted the the Disk Manager show now the 2 NVMe, just the identification is... let's says "random".

 

Before building cache.png

After RW cache enabled.png

Link to comment
Share on other sites

  • 3 weeks later...
7 hours ago, Loredan said:

 

Today I tried ARC (7.2 u1) and noticed that it recognized an m.2 SSD there.

2023-06-27184739.thumb.png.8f9bd9c8b4e183a9d1a34d98c042c6c5.png

 

 

Now this issue is gone even in M-SHELL.
The ability to process "support_m2_pool=yes" in the /etc.defaults/synoinfo.conf file is now added as an Addon.
thank you.

  • Thanks 1
Link to comment
Share on other sites

10 часов назад, Peter Suh сказал:

The ability to process "support_m2_pool=yes" in the /etc.defaults/synoinfo.conf file is now added as an Addon.

Did I understand correctly that in order for the M.2 SSD to appear, I need to set "/etc.defaults/synoinfo.conf -> support_m2_pool=yes"? I checked, and I already had support_m2_pool=yes, but the M.2 drive is not being detected in DSM.

M-Shell (JOT) was built yesterday. Or does it need to be rebuilt?

Link to comment
Share on other sites

1 hour ago, Loredan said:

Did I understand correctly that in order for the M.2 SSD to appear, I need to set "/etc.defaults/synoinfo.conf -> support_m2_pool=yes"? I checked, and I already had support_m2_pool=yes, but the M.2 drive is not being detected in DSM.

M-Shell (JOT) was built yesterday. Or does it need to be rebuilt?

 

 

Refer to the arc disks addon
The script of M shell addon has been supplemented.

https://github.com/AuxXxilium/arc-addons/blob/main/disks/install.sh#L302

https://github.com/PeterSuh-Q3/tcrp-addons/commit/fd00a397058574067c6f2668ec4a995b56995a9a

 

Did not exist as a result of creating the /etc.defaults/extensionPorts file additionally
On the DVA3221, the NVMe cache appeared as shown below.

Try rebuilding the loader now.

 

2023-06-289_53_21.thumb.png.5d694367222362bbb10a8cb5a410fd85.png

 

  • Thanks 1
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...