flyride Posted July 21, 2020 Share #126 Posted July 21, 2020 root@archive:/usr/lib# sha1sum -b /lib64/libsynonvme.so.1 8c39cdda125b02688c0fb06f5c9aaaf7e06b5295 */lib64/libsynonvme.so.1 Quote Link to comment Share on other sites More sharing options...
The Chief Posted July 21, 2020 Share #127 Posted July 21, 2020 1 минуту назад, flyride сказал: 8c39cdda125b02688c0fb06f5c9aaaf7e06b5295 It seems to me a strange thing, mystifying… Try attached .so. libsynonvme.so.1 3 Quote Link to comment Share on other sites More sharing options...
The Chief Posted July 21, 2020 Share #128 Posted July 21, 2020 4 минуты назад, The Chief сказал: It seems to me a strange thing, mystifying… It's not anymore. You've patched NEW type .so with an OLD .sh patch. Restore original .so (md1sum e67711740b869bbd27349f56183870c26b2b5a01) and patch it with updated patch. Quote Link to comment Share on other sites More sharing options...
flyride Posted July 21, 2020 Share #129 Posted July 21, 2020 Hmm, not sure how that happened. Can verify it's working correctly now with your libfile. Quote Link to comment Share on other sites More sharing options...
J0hnny Posted August 12, 2020 Share #130 Posted August 12, 2020 (edited) My NAS 918+ worked perfectly with the latest update: 6.2.3-25426 I added an SSD drive (Samsung 970 EVO NVMe M.2 - 250GB) to use as a read cache in the system. I inserted the file (libsynonvme.so.1) what was provided here into the /usr/lib64 directory. The UI stopped working. I initiated a reset. The machine booted (I can SSH into it ), but the web UI still not works. Additionally, when I use the Synology Assistant, it reports "Checking Quota" for the NAS. How long should I have to wait for the "Checking Quota" to finish? Is there anything I can do? Did I do anything wrong? Edited August 12, 2020 by J0hnny update: After 2hours the Synology Assistant reports "Ready" for the NAS. But the web UI still not works, but I can still login with SSH. DS file also not let me in. Quote Link to comment Share on other sites More sharing options...
J0hnny Posted August 12, 2020 Share #131 Posted August 12, 2020 2 hours ago, J0hnny said: My NAS 918+ worked perfectly with the latest update: 6.2.3-25426 I added an SSD drive (Samsung 970 EVO NVMe M.2 - 250GB) to use as a read cache in the system. I inserted the file (libsynonvme.so.1) what was provided here into the /usr/lib64 directory. The UI stopped working. I initiated a reset. The machine booted (I can SSH into it ), but the web UI still not works. Additionally, when I use the Synology Assistant, it reports "Checking Quota" for the NAS. How long should I have to wait for the "Checking Quota" to finish? Is there anything I can do? Did I do anything wrong? Update: I was able to fix the issue by set the file permission of "777" for libsynonvme.so.1 Now the UI is working again Quote Link to comment Share on other sites More sharing options...
NooL Posted September 1, 2020 Share #132 Posted September 1, 2020 When look at var/log/messages my logs seems filled with 2020-09-01T15:00:13+02:00 DiskStation SystemInfo.cgi: nvme_cmd_raw_binary_get.c:54 fread failed 2020-09-01T15:00:13+02:00 DiskStation SystemInfo.cgi: nvme_temperature_get.c:24 Can't get the smart-log raw binary 2020-09-01T15:00:32+02:00 DiskStation synostoraged: nvme_cmd_raw_binary_get.c:54 fread failed 2020-09-01T15:00:32+02:00 DiskStation synostoraged: nvme_temperature_get.c:24 Can't get the smart-log raw binary Any ideas how to fix this? Quote Link to comment Share on other sites More sharing options...
flyride Posted September 1, 2020 Share #133 Posted September 1, 2020 Not a fix per se, but you can suppress the messages if you want. https://xpenology.com/forum/topic/29581-suppress-virtual-disk-smart-errors-from-varlogmessages/ Quote Link to comment Share on other sites More sharing options...
glch_2013 Posted September 5, 2020 Share #134 Posted September 5, 2020 Can be the Nvme M2 change to storage pool? I've patched sucessfully on my DS918+ with 6.2.3-25426, however it allowed me to use as a cache only. Quote Link to comment Share on other sites More sharing options...
venno Posted September 8, 2020 Share #135 Posted September 8, 2020 New install and am running juns 1.04b loader and DSM 6.2.3 25426 PAT file. I have an Optane p800 m2 installed on the PCIE x2 m2 slot in a Supermicro A2SDi-H-TF mobo (its on the 918 supported list), it shows in bios but not in DSM, or even ssh'ing and running 'nvme list'. I tried the libsynonvme.so.1 in /usr/lib64 and reboot but still no change. Can anyone help with suggestions to try ? Quote Link to comment Share on other sites More sharing options...
venno Posted September 8, 2020 Share #136 Posted September 8, 2020 Just found the section by IG88 on the 918 extra files mod to boot drive, works like a charm, posted too quick for help. Quote Link to comment Share on other sites More sharing options...
exclusive213 Posted September 19, 2020 Share #137 Posted September 19, 2020 Hey guys, I am running Jun's 1.04b loader and DSM 6.2.2-24922 update 3 I attempted to follow the thread and didn't run any of the libNVMEpatch.sh and just placed the libsynonvme.so.1 file into the /usr/lib64 directory. I also made sure to chmod the file to 777. My DSM stopped web gui stopped working and so I reboot via SSH. Upon booting back up, the Synology Web Assistant is telling me my NAS is migratable and wants me to reload DSM... Did I do the steps incorrectly? Is my old configuration completely lost? Thanks for any help I can get. 😃 Quote Link to comment Share on other sites More sharing options...
Hackaro Posted November 24, 2020 Share #138 Posted November 24, 2020 On 4/17/2020 at 4:01 PM, The Chief said: Minor changes. Dev Guys now do some more strict PHYSDEV parsing. Nothing special. libNVMEpatch.sh 2.14 kB · 236 downloads Just a recap for those who'll want to try NVMe cache because all the thread is quite messy imho. The above shell script with DSM 6.2.3-25426 Update 2 (on DS918+ , indeed) does not work anymore. At least in my experience it leads in an incorrect state where the two NVMe are not recognised as the same and therefore they cannot be used for a necessary RAID 1 in case of R/W cache. The only thing is really working at the moment is a copy of the libsynonvme.so.1 to the right path. So put this file in a public zone of your volume (this is my case) or wherever you like and then with root's privileges (sudo -i) put the lib in the right place: cp /volume1/public/libsynonvme.so.1 /usr/lib64 cd /usr/lib64 chmod 777 libsynonvme.so.1 shutdown -r now and that's it. The Storage Manager should recognise correctly yours NVMe's and use them as cache. 1 4 1 Quote Link to comment Share on other sites More sharing options...
SupakoolDude Posted November 25, 2020 Share #139 Posted November 25, 2020 First time building a Xpenology system so it took me a while to learn all this new stuff. The following worked for me. Quote cp /volume1/public/libsynonvme.so.1 /usr/lib64 cd /usr/lib64 chmod 777 libsynonvme.so.1 shutdown -r now Thanks flyride & The Chief for all the hard work, also thanks Hackaro for the simple recap. Quote Link to comment Share on other sites More sharing options...
Goby Posted November 27, 2020 Share #140 Posted November 27, 2020 Le 24/11/2020 à 12:14, Hackaro a dit : The only thing is really working at the moment is a copy of the libsynonvme.so.1 to the right path. So put this file in a public zone of your volume (this is my case) or wherever you like and then with root's privileges (sudo -i) put the lib in the right place: cp /volume1/public/libsynonvme.so.1 /usr/lib64 cd /usr/lib64 chmod 777 libsynonvme.so.1 shutdown -r now Hi all, I just did this and manage to have my ssd availble on DSM. But since the system is very slow. If I want to get back to the origin, should I just delete the file libsynonvme.so.1 or does this file was already present and the operation was a replacement of an original file? Thanks for your help. Quote Link to comment Share on other sites More sharing options...
Hackaro Posted November 30, 2020 Share #141 Posted November 30, 2020 On 11/27/2020 at 9:43 PM, Goby said: Hi all, I just did this and manage to have my ssd availble on DSM. But since the system is very slow. If I want to get back to the origin, should I just delete the file libsynonvme.so.1 or does this file was already present and the operation was a replacement of an original file? Thanks for your help. Uhm... why should it become slow? Maybe it needs a bit of time for the cache to just "caching" all your files . I suggest to use the NAS for some days and then decide. Problem is that as you copied the file, in case something is wrong if you haven't done a backup of it you cannot have it back. Quote Link to comment Share on other sites More sharing options...
Outrullers Posted December 15, 2020 Share #142 Posted December 15, 2020 (edited) Цитата cp /volume1/public/libsynonvme.so.1 /usr/lib64 Why /usr/lib64 ? One should place it in /lib64 or GUI will hang as it was already said in this topic В 28.04.2020 в 09:32, indiandave сказал: after you place the file into /usr/lib64 director, the DSM UI will stop working so you have to hard restart the machine Edited December 15, 2020 by Outrullers Quote Link to comment Share on other sites More sharing options...
peter_pan Posted December 26, 2020 Share #143 Posted December 26, 2020 On 9/8/2020 at 9:31 AM, venno said: Just found the section by IG88 on the 918 extra files mod to boot drive, works like a charm, posted too quick for help. Hi @venno I am using DSM 6.2.3-25426 Update 3 (on DS918+) and I have Intel SSD Pro 6000p Series 256GB, M.2 PCIe 3.0 SSD which is installed on motherboard's SSD slot (IBM branded mobo). The SSD appears in BIOS but for doesn't appear in DSM. I even ran the nvme list command but doesn't show anything. Can you please share the link to mod that you have applied to get this SSD to work Many thanks me@mymachine:/$ nvme list Node SN Model Namespace Usage Format FW Rev ---------------- -------------------- ---------------------------------------- --------- -------------------------- ---------------- -------- /dev/nvme0n1 -1 0.00 B / 0.00 B 1 B + 0 B /dev/nvme0n1p1 -1 0.00 B / 0.00 B 1 B + 0 B /dev/nvme0n1p2 -1 0.00 B / 0.00 B 1 B + 0 B /dev/nvme0n1p3 -1 0.00 B / 0.00 B 1 B + 0 B /dev/nvme0n1p4 -1 0.00 B / 0.00 B 1 B + 0 B Quote Link to comment Share on other sites More sharing options...
peter_pan Posted December 27, 2020 Share #144 Posted December 27, 2020 (edited) 17 hours ago, peter_pan said: Hi @venno I am using DSM 6.2.3-25426 Update 3 (on DS918+) and I have Intel SSD Pro 6000p Series 256GB, M.2 PCIe 3.0 SSD which is installed on motherboard's SSD slot (IBM branded mobo). The SSD appears in BIOS but for doesn't appear in DSM. I even ran the nvme list command but doesn't show anything. Can you please share the link to mod that you have applied to get this SSD to work I have found IG-88's thread but there are multiple links and I am struggling to understand which one to use. Can some one please help Edited December 27, 2020 by peter_pan Quote Link to comment Share on other sites More sharing options...
Jaazzz Posted December 31, 2020 Share #145 Posted December 31, 2020 (edited) Does anyone have an idea as to why all the libsynonvme.so.1 files have been deleted? I've tried to create the libNVMEpatch.sh file using the script provided a few pages back but i get this error -ash: ./libNVMEpatch.sh: /bin/ash^M: bad interpreter: No such file or directory Got the file, Wasn't logged in...😛 Edited December 31, 2020 by Jaazzz Spelling Quote Link to comment Share on other sites More sharing options...
peter_pan Posted January 3, 2021 Share #146 Posted January 3, 2021 On 6/11/2020 at 2:46 PM, Hackaro said: Please have a look at posts: 91 / 93 / 98 How do find post number (do you manually count them?). I can only see page number on the page Quote Link to comment Share on other sites More sharing options...
Hackaro Posted January 8, 2021 Share #147 Posted January 8, 2021 On 1/3/2021 at 10:23 AM, peter_pan said: How do find post number (do you manually count them?). I can only see page number on the page I made a recap post above ... and there is all the links you need ... 1 Quote Link to comment Share on other sites More sharing options...
meatball Posted January 30, 2021 Share #148 Posted January 30, 2021 On 4/18/2020 at 6:35 PM, The Chief said: Patched .so.1 — try to directly replace it in /lib64. libsynonvme.so.1 36.76 kB · 330 downloads Hi, I'v pathed libsynonvme.so.1 . But I found that only nvme ssd on the M2A slot can be recognized. So how can I use the M2Q slot? My hardware info: CPU i39100 Motherboard GIGABYTE b365m aorus elite. SSD WD SN750 1T I checked the manual of motherboard, it is said that M2Q slot is connected directly to CPU while M2A slot shares bandwidth with SATA3.0 slot Quote Link to comment Share on other sites More sharing options...
Hackaro Posted February 2, 2021 Share #149 Posted February 2, 2021 (edited) @flyride I have a strange behaviour since I have changed the NVMe disk's brand and updated to new Samsung 970 EVO+: thinks are working correctly in DSM as you can see https://www.dropbox.com/s/nwrfvwdss87zymj/Screenshot 2021-02-02 at 10.46.13.png?dl=0 https://www.dropbox.com/s/fcb8mlzeohwb4bf/Screenshot 2021-02-02 at 10.47.02.png?dl=0 but I don't have the correct list in Terminal: Root@NAS:~$ synonvme --is-nvme-ssd /dev/nvme0n1 It is a NVMe SSD Root@NAS:~$ nvme list Node SN Model Namespace Usage Format FW Rev ---------------- -------------------- ---------------------------------------- --------- -------------------------- ---------------- -------- /dev/nvme0n1 -1 0.00 B / 0.00 B 1 B + 0 B /dev/nvme0n1p1 -1 0.00 B / 0.00 B 1 B + 0 B /dev/nvme1n1 -1 0.00 B / 0.00 B 1 B + 0 B /dev/nvme1n1p1 -1 0.00 B / 0.00 B 1 B + 0 B Root@NAS:~$ synonvme --model-get /dev/nvme0n1 Fail to get disk model 970EVO+ are in Synology support list, even if with a different firmware. So what should I do about it? Thanks in advance! Edited February 2, 2021 by Hackaro Quote Link to comment Share on other sites More sharing options...
flyride Posted February 2, 2021 Share #150 Posted February 2, 2021 I'm not sure there is anything to do about it. The nvme binary is standard Linux accessing the kernel driver and is unaffected by the patch. I would guess that you would see the same behavior with a real DS918+. 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.