vapet Posted December 14, 2014 Share #126 Posted December 14, 2014 Have no time to give it a try to 5.1 by myself, but I can suggest to enable a VGA console in a kernel which you build, then boot process should be more informative. To see how to enable console, you can look through https://github.com/liwei/xpenology-3.x patches which are fresher than sancome's and closer to last nanoboot version. I have built a new kernel from liwei sources with additional driver and it is working on my server now with nanoboot 5.0.3.2 ramdisk. All my tries with sancome's sources was not successfull. Quote Link to comment Share on other sites More sharing options...
Jman420 Posted December 14, 2014 Share #127 Posted December 14, 2014 I've been patching all the source files by hand since a lot of the line numbers seem to have changed from Sancome's patches. The linux-3.x source patches were easy to apply, but some of the scripts in the rd.gz image have changes quite a bit, specifically '/etc/rc'. Judging from the patch file I think the original from Synology should be fine, but I'm not sure if XPEnology relies on any of the code that has been removed. Going to keep plugging away... Quote Link to comment Share on other sites More sharing options...
Jman420 Posted December 14, 2014 Share #128 Posted December 14, 2014 Have no time to give it a try to 5.1 by myself, but I can suggest to enable a VGA console in a kernel which you build, then boot process should be more informative.To see how to enable console, you can look through https://github.com/liwei/xpenology-3.x patches which are fresher than sancome's and closer to last nanoboot version. I have built a new kernel from liwei sources with additional driver and it is working on my server now with nanoboot 5.0.3.2 ramdisk. All my tries with sancome's sources was not successfull. liewei does seem to have more up to date source code. But do you know what version/build of DSM that is building from? I'd like to run a diff against them to figure out what patches he has added. Quote Link to comment Share on other sites More sharing options...
vapet Posted December 15, 2014 Share #129 Posted December 15, 2014 You can see all patches that he done in his github commit history. Some commits after June are not relevant - he tried to play with different FS, i've used his June,1 commit. I don't know exactly from which sources he started, I suggest 4528... Quote Link to comment Share on other sites More sharing options...
liwei Posted December 15, 2014 Share #130 Posted December 15, 2014 Have no time to give it a try to 5.1 by myself, but I can suggest to enable a VGA console in a kernel which you build, then boot process should be more informative.To see how to enable console, you can look through https://github.com/liwei/xpenology-3.x patches which are fresher than sancome's and closer to last nanoboot version. I have built a new kernel from liwei sources with additional driver and it is working on my server now with nanoboot 5.0.3.2 ramdisk. All my tries with sancome's sources was not successfull. liewei does seem to have more up to date source code. But do you know what version/build of DSM that is building from? I'd like to run a diff against them to figure out what patches he has added. It was based on 4493 IIRC, for what I modified from original source, you can reference the commit history. Thanks. Quote Link to comment Share on other sites More sharing options...
Poechi Posted December 15, 2014 Share #131 Posted December 15, 2014 (edited) - Edited July 10, 2015 by Guest Quote Link to comment Share on other sites More sharing options...
sl0n Posted December 15, 2014 Share #132 Posted December 15, 2014 Second try. - I've used sources from Liwei. - Patched the linux-3.x files manually (linux-3.x-xpenology-4418.patch) - ***Patched the rc files manually (rd-with-gnoboot-4458.patch) with RD image from 5.1-5004. - Used cracked synobios from Vortex. ***I can patch everyting (linuxrc.syno, rc.network, rc.subr, rc.volume) execpt for the rc file. Below code is not present in rc file from RD 5.1-5004. diff -ruN rd-orig/etc/rc rd/etc/rc --- rd-orig/etc/rc 2014-03-20 22:19:15.183588205 +0800 +++ rd/etc/rc 2014-03-22 13:27:00.901857747 +0800 @@ -479,6 +479,7 @@ esac if [ -r "/etc.defaults/sysctl.conf" ]; then + [ -e /sbin/sysctl ] && \ /sbin/sysctl -p /etc.defaults/sysctl.conf fi @@ -542,6 +543,7 @@ $SZF_HA_RC prepare-for-upg else # initial findhostd first to report quota check progress, see DS20 bug # + [ -e /usr/syno/etc/rc.d/S98findhostd.sh ] && \ /usr/syno/etc/rc.d/S98findhostd.sh start # checking and Mounting filesystem(s) ... @@ -561,25 +563,33 @@ fi #set time zone information to kernel +[ -e /usr/syno/bin/synokerneltz ] && \ /usr/syno/bin/synokerneltz +[ -e /sbin/sysctl ] && \ /sbin/sysctl -w kernel.core_pattern=/volume1/@%e.core if [ $KERNEL_VCODE -ge $(KernelVersionCode "2.6") ]; then + [ -e /sbin/sysctl ] && \ /sbin/sysctl -w fs.suid_dumpable=2 else + [ -e /sbin/sysctl ] && \ /sbin/sysctl -w kernel.suid_dumpable=2 fi ulimit -c unlimited if [ "$PLATFORM" = "ti816x" ]; then + [ -e /sbin/sysctl ] && \ /sbin/sysctl -w vm.min_free_kbytes=8192 elif [ 1048576 -le "`awk '"MemTotal:"==$1{print $2}' /proc/meminfo`" ]; then # if physical memory size greater than 1GB, and then set vm.min_free_kbytes to 64MB + [ -e /sbin/sysctl ] && \ /sbin/sysctl -w vm.min_free_kbytes=65536 elif [ $KERNEL_VCODE -ge $(KernelVersionCode "2.6.32") ]; then + [ -e /sbin/sysctl ] && \ /sbin/sysctl -w vm.min_free_kbytes=8192 else + [ -e /sbin/sysctl ] && \ /sbin/sysctl -w vm.min_free_kbytes=4096 fi @@ -612,6 +622,7 @@ fi # System log: "System started to boot up." +[ -e /usr/syno/bin/synologset1 ] && \ /usr/syno/bin/synologset1 sys info 0x11100002 # Network UPS: remove upsmaster before hotplug @@ -636,6 +647,7 @@ $_srv start done + [ -e /usr/syno/bin/servicetool ] && \ servicetool --3rdparty start # set boot sequence done also send service ready signal to scemd @@ -673,6 +685,7 @@ fi done #force to disable shortcut + [ -e /proc/sys/kernel/syno_netfilter_status ] && \ echo 1 > /proc/sys/kernel/syno_netfilter_status fi I continued anyway. So far I can boot but no network is present. Maybe I'm missing a driver for the network card HP N54L or maybe it has to do with the rc file not being patched. Open for suggestions. What lsmod says for the old and the new kernels? It sounds like a good progress mate. Quote Link to comment Share on other sites More sharing options...
Poechi Posted December 15, 2014 Share #133 Posted December 15, 2014 (edited) - Edited July 10, 2015 by Guest Quote Link to comment Share on other sites More sharing options...
CtrlAltDel Posted December 15, 2014 Share #134 Posted December 15, 2014 Thanks for keeping us upto date with your efforts. Quote Link to comment Share on other sites More sharing options...
Jman420 Posted December 15, 2014 Share #135 Posted December 15, 2014 I've been doing a lot of the same stuff that Poechi has, but instead of starting with Liwei's source code I started with the 5004 build source and used Liwei's commits from GitHub to patch the 5004 build. I've got my build working, but the IMG that gets built by Sancome's script looks totally different than the one I've been using for DSM 5.0. I'm ganna give it a shot anyway, but does anyone know how to make those FAT32 IMGs? Edit: So the IMG file works and I've edited the grub files so all the references to 5.0-4458 are now 5.1-5004. But I noticed that in one of the menus actually passes a gnoBoot parameter as below: kernel /zImage root=/dev/md0 ihd_num=0 netif_num=4 syno_hw_version=DS3612xs sn=B3J4N01003 loglevel=0 gnoboot_upgrade=5.1-5004 I have changed the version there to reflect the build I used (changed 5.0-4458 to 5.1-5004), but I'm not sure if gnoboot actually uses that for anything. Going to keep going anway... Quote Link to comment Share on other sites More sharing options...
Jman420 Posted December 15, 2014 Share #136 Posted December 15, 2014 Well, I think I'm giving up for the day. I'm at the same point that Poechi is and also once DSM has booted up it no longer recognizes my usb keyboard. I also noticed an issue with rd.volume which is erroring out due to awk not being available. But I think our real issue is synobios failing to load. If anyone wants to play around with here is a git repo with my progress: https://github.com/Jman420/nanoBoot-DSM5.1 Quote Link to comment Share on other sites More sharing options...
vapet Posted December 16, 2014 Share #137 Posted December 16, 2014 awk errors is not a real problem - those errors are normal for installation mode, when normal root having all those utils is not mounted. USB keyboard should be connected to USB 2.0 port, not a 3.0! No network problem should be solved if you include correct mac1 and mac2 parameters to kernel in grub (you can read about calculating them in nanoboot install instructions). Nanoboot uses version in some parts of rc scripts, so it should be better to leave this param to old 5.0 value. Quote Link to comment Share on other sites More sharing options...
Poechi Posted December 16, 2014 Share #138 Posted December 16, 2014 (edited) - Edited July 10, 2015 by Guest Quote Link to comment Share on other sites More sharing options...
Jman420 Posted December 16, 2014 Share #139 Posted December 16, 2014 Is there a way to get more detailed error logs from NanoBoot's boot-up process? I would like to see if there are any details around why synobios is failing to load. Also is there a way to get the detailed error logs from DSM's installation? I'd like to see if there are more details around why the installation is failing. I tried installing through SynologyAssistant last night and got a different error code and error talking about a problem accessing the boot drive or record (can't remember exactly). Quote Link to comment Share on other sites More sharing options...
Poechi Posted December 16, 2014 Share #140 Posted December 16, 2014 (edited) - Edited July 10, 2015 by Guest Quote Link to comment Share on other sites More sharing options...
HommiePeter Posted December 16, 2014 Share #141 Posted December 16, 2014 Is there a way to get more detailed error logs from NanoBoot's boot-up process? I would like to see if there are any details around why synobios is failing to load. Also is there a way to get the detailed error logs from DSM's installation? I'd like to see if there are more details around why the installation is failing. I tried installing through SynologyAssistant last night and got a different error code and error talking about a problem accessing the boot drive or record (can't remember exactly). He Jman in /var/log/dmesg you can find detailed information on the boot process (cat dmesg) of for the last boot you can type dmesg as command After booting the new build image that is based on your excellent work (i found the following maybe interesting logging entries see synoacl warnings) [Tue Dec 16 14:38:00 2014] EXT4-fs (dm-0): synoacl module has not been loaded. Unable to mount with synoacl, vfs_mod status=-1 [Tue Dec 16 14:38:07 2014] EXT4-fs (sdu1): synoacl module has not been loaded. Unable to mount with synoacl, vfs_mod status=-1 [Tue Dec 16 14:38:00 2014] EXT4-fs (dm-0): synoacl module has not been loaded. Unable to mount with synoacl, vfs_mod status=-1 [Tue Dec 16 14:38:00 2014] EXT4-fs (dm-0): barriers disabled [Tue Dec 16 14:38:00 2014] EXT4-fs (dm-0): mounted filesystem with writeback data mode. Opts: usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,synoacl,data=writeback,oldalloc [Tue Dec 16 14:38:07 2014] EXT4-fs (sdu1): synoacl module has not been loaded. Unable to mount with synoacl, vfs_mod status=-1 [Tue Dec 16 14:38:07 2014] EXT4-fs (sdu1): mounted filesystem without journal. Opts: nodelalloc,synoacl,data=ordered,oldalloc [Tue Dec 16 14:38:07 2014] netlink: 12 bytes leftover after parsing attributes. [Tue Dec 16 14:38:08 2014] init: crond main process (10465) killed by TERM signal [Tue Dec 16 14:38:09 2014] init: sshd main process (10608) terminated with status 255 [Tue Dec 16 14:38:09 2014] init: httpd-user main process (13599) killed by TERM signal [Tue Dec 16 14:38:10 2014] eth0: no IPv6 routers present [Tue Dec 16 14:38:14 2014] netlink: 12 bytes leftover after parsing attributes. [Tue Dec 16 14:38:15 2014] loop: module loaded [Tue Dec 16 14:38:15 2014] init: smbd main process (14114) killed by TERM signal [Tue Dec 16 14:38:19 2014] md2: detected capacity change from 55165779968 to 0 [Tue Dec 16 14:38:19 2014] md: md2: set sda5 to auto_remap [0] [Tue Dec 16 14:38:19 2014] md: md2 stopped. [Tue Dec 16 14:38:19 2014] md: unbind [Tue Dec 16 14:38:19 2014] md: export_rdev(sda5) [Tue Dec 16 14:38:19 2014] md: md1 in immediate safe mode [Tue Dec 16 14:38:19 2014] md: md0 in immediate safe mode [Tue Dec 16 14:38:19 2014] init: dsm-services main process (12124) killed by KILL signal [Tue Dec 16 14:38:19 2014] init: tty main process (12400) killed by KILL signal [Tue Dec 16 14:38:19 2014] init: tty main process ended, respawning [Tue Dec 16 14:38:19 2014] init: before-halt main process (16460) killed by KILL signal [Tue Dec 16 14:38:21 2014] init: rc-sysinit main process (16517) terminated with status 255 Further more there is /var/log/scemd.log for internal synology logging which might be interesting. Quote Link to comment Share on other sites More sharing options...
jagwaugh Posted December 17, 2014 Share #142 Posted December 17, 2014 So, I have a VM setup and manage to get though the cross compile steps and generate synoboot_5.1-5004_x64_3612xs.img. What I don't know is what to DO with the .img file to cause a VM to boot from this. I tried vboxmanage convert raw, but that didn't work. How do I get from the .img file to either a bootable .iso, or a bootable .vdi or .vmdk? Andrew Quote Link to comment Share on other sites More sharing options...
idstein Posted December 17, 2014 Share #143 Posted December 17, 2014 So, I have a VM setup and manage to get though the cross compile steps and generate synoboot_5.1-5004_x64_3612xs.img. What I don't know is what to DO with the .img file to cause a VM to boot from this. I tried vboxmanage convert raw, but that didn't work. How do I get from the .img file to either a bootable .iso, or a bootable .vdi or .vmdk? Andrew As this is a kernel image, you can not boot straight forward with it in VirtualBox. VirtualBox simulates a complete virtual machine in opposite to qemu/KVM. Consequently, it directly switches to the boot devices MBR and tries to find a bootloader which is not present in your img file. Take a look at http://wiki.osdev.org/Bootable_El-Torito_CD_with_GRUB_Legacy for further details on how to package your compiled kernel image with GRUB (Legacy) to a bootable ISO. Quote Link to comment Share on other sites More sharing options...
Poechi Posted December 17, 2014 Share #144 Posted December 17, 2014 (edited) - Edited July 10, 2015 by Guest Quote Link to comment Share on other sites More sharing options...
idstein Posted December 17, 2014 Share #145 Posted December 17, 2014 Looking at the patching for rc file. Am I correct that the -e command is for: Use this option to ignore errors about unknown keys.Does this mean if it see an error it ignores it and continues a process, or if you don't use this -e command, the error is detected, not ignored and a process stops? Just want to know if this matters or not. Or if it's just for suppressing error messages. Example for patching rc file. if [ -r "/etc.defaults/sysctl.conf" ]; then + [ -e /sbin/sysctl ] && \ /sbin/sysctl -p /etc.defaults/sysctl.conf No, that basically ensures that the path /sbin/sysctl is present and only if that's the case set the system control values. Actually, at that place I would have placed a -x for checking, that /sbin/sysctl is executable Refer to http://www.thegeekstuff.com/2010/06/bash-conditional-expression/ for further details. Quote Link to comment Share on other sites More sharing options...
Jman420 Posted December 17, 2014 Share #146 Posted December 17, 2014 Looking at the patching for rc file. Am I correct that the -e command is for: Use this option to ignore errors about unknown keys.Does this mean if it see an error it ignores it and continues a process, or if you don't use this -e command, the error is detected, not ignored and a process stops? Just want to know if this matters or not. Or if it's just for suppressing error messages. Example for patching rc file. if [ -r "/etc.defaults/sysctl.conf" ]; then + [ -e /sbin/sysctl ] && \ /sbin/sysctl -p /etc.defaults/sysctl.conf I was wondering about this same thing while I was patching the rc files. I know that commands which are strung together using the '&&' operator must all complete successfully before the next command is executed. So in the case above the '[ -e /sbin/sysctl ]' command has to return true before the '/sbin/sysctl -p /etc.defaults/sysctl.conf' command will execute. So to answer your question, yes, in a way this is used to suppress a command which would generate an error because the necessary file or command doesn't exist. He Jman in /var/log/dmesg you can find detailed information on the boot process (cat dmesg) of for the last boot you can type dmesg as command After booting the new build image that is based on your excellent work (i found the following maybe interesting logging entries see synoacl warnings) [Tue Dec 16 14:38:00 2014] EXT4-fs (dm-0): synoacl module has not been loaded. Unable to mount with synoacl, vfs_mod status=-1 [Tue Dec 16 14:38:07 2014] EXT4-fs (sdu1): synoacl module has not been loaded. Unable to mount with synoacl, vfs_mod status=-1 [Tue Dec 16 14:38:00 2014] EXT4-fs (dm-0): synoacl module has not been loaded. Unable to mount with synoacl, vfs_mod status=-1 [Tue Dec 16 14:38:00 2014] EXT4-fs (dm-0): barriers disabled [Tue Dec 16 14:38:00 2014] EXT4-fs (dm-0): mounted filesystem with writeback data mode. Opts: usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,synoacl,data=writeback,oldalloc [Tue Dec 16 14:38:07 2014] EXT4-fs (sdu1): synoacl module has not been loaded. Unable to mount with synoacl, vfs_mod status=-1 [Tue Dec 16 14:38:07 2014] EXT4-fs (sdu1): mounted filesystem without journal. Opts: nodelalloc,synoacl,data=ordered,oldalloc [Tue Dec 16 14:38:07 2014] netlink: 12 bytes leftover after parsing attributes. [Tue Dec 16 14:38:08 2014] init: crond main process (10465) killed by TERM signal [Tue Dec 16 14:38:09 2014] init: sshd main process (10608) terminated with status 255 [Tue Dec 16 14:38:09 2014] init: httpd-user main process (13599) killed by TERM signal [Tue Dec 16 14:38:10 2014] eth0: no IPv6 routers present [Tue Dec 16 14:38:14 2014] netlink: 12 bytes leftover after parsing attributes. [Tue Dec 16 14:38:15 2014] loop: module loaded [Tue Dec 16 14:38:15 2014] init: smbd main process (14114) killed by TERM signal [Tue Dec 16 14:38:19 2014] md2: detected capacity change from 55165779968 to 0 [Tue Dec 16 14:38:19 2014] md: md2: set sda5 to auto_remap [0] [Tue Dec 16 14:38:19 2014] md: md2 stopped. [Tue Dec 16 14:38:19 2014] md: unbind [Tue Dec 16 14:38:19 2014] md: export_rdev(sda5) [Tue Dec 16 14:38:19 2014] md: md1 in immediate safe mode [Tue Dec 16 14:38:19 2014] md: md0 in immediate safe mode [Tue Dec 16 14:38:19 2014] init: dsm-services main process (12124) killed by KILL signal [Tue Dec 16 14:38:19 2014] init: tty main process (12400) killed by KILL signal [Tue Dec 16 14:38:19 2014] init: tty main process ended, respawning [Tue Dec 16 14:38:19 2014] init: before-halt main process (16460) killed by KILL signal [Tue Dec 16 14:38:21 2014] init: rc-sysinit main process (16517) terminated with status 255 Further more there is /var/log/scemd.log for internal synology logging which might be interesting. Thanks for the complement, but all I really did was manually merge a hundred some odd files and create the patch files using the 'diff -ru' command. The above log dumps you provided do seem helpful since it points to issues mounting the volumes. Unfortunately I think I've hit the limit of my knowledge about this stuff, so I expect progress on my side to slow down a bit. I still think our main problem is synobios not loading, but I could be wrong, obviously another issue is that synoacl isn't loaded (see logs above). I have decent experience with shell scripts so I think the next place I will dig into are the rc scripts. I might clean up those build scripts a bit too, make them more flexible and support multiple DSM builds. Quote Link to comment Share on other sites More sharing options...
idstein Posted December 17, 2014 Share #147 Posted December 17, 2014 I've just been checking on my XPenology NAS that there is a synoacl_ext4, but there isn't diskstation> ll /lib/modules/syno* -rw-r--r-- 1 root root 23840 May 30 2014 /lib/modules/synoacl_vfs.ko -rw-r--r-- 1 root root 66416 Jun 8 2014 /lib/modules/synobios.ko Yet XPenology tries to load the kernel modules synoacl_vfs AND synoacl_ext4. diskstation> lsmod | grep acl synoacl_vfs 16275 2 Consequently, I believe formerly there has been syndical_ext4 module, but as of now it has become part of the kernel ext4 module using the kernel flag CONFIG_EXT4_FS_SYNO_ACL. Could someone check on a real device which modules are available using `ll /lib/modules/syno*`? Thanks! Quote Link to comment Share on other sites More sharing options...
Poechi Posted December 17, 2014 Share #148 Posted December 17, 2014 (edited) - Edited July 10, 2015 by Guest Quote Link to comment Share on other sites More sharing options...
idstein Posted December 17, 2014 Share #149 Posted December 17, 2014 Could also please check the following `ll /lib/libsyno*`? I believe by inspecting a most recent PAT (5010) that there exists a new lib called libsynovfs. That could mean that they have moved the virtual file system to the user space? Quote Link to comment Share on other sites More sharing options...
mreasy2002 Posted December 17, 2014 Share #150 Posted December 17, 2014 DS214Play> ll /lib/libsyno* -rwxr-xr-x 1 root root 47352 Dec 13 03:24 /lib/libsynoacl.so -rwxr-xr-x 1 root root 47352 Dec 13 03:24 /lib/libsynoaclgpl.so lrwxrwxrwx 1 root root 23 Dec 17 14:52 /lib/libsynoautoblock.so -> libsynoautoblock.so.5.1 lrwxrwxrwx 1 root root 23 Dec 17 14:52 /lib/libsynoautoblock.so.5 -> libsynoautoblock.so.5.1 -rw-r--r-- 1 root root 38456 Dec 13 03:24 /lib/libsynoautoblock.so.5.1 lrwxrwxrwx 1 root root 18 Dec 17 14:52 /lib/libsynobackup.so -> libsynobackup.so.1 -rwxr-xr-x 1 root root 3702812 Dec 13 03:24 /lib/libsynobackup.so.1 lrwxrwxrwx 1 root root 23 Dec 17 14:52 /lib/libsynobandwidth.so -> libsynobandwidth.so.5.1 lrwxrwxrwx 1 root root 23 Dec 17 14:52 /lib/libsynobandwidth.so.5 -> libsynobandwidth.so.5.1 -rw-r--r-- 1 root root 54972 Dec 13 03:24 /lib/libsynobandwidth.so.5.1 -rwxr-xr-x 1 root root 634964 Dec 13 03:26 /lib/libsynobluetooth.so lrwxrwxrwx 1 root root 25 Dec 17 14:52 /lib/libsynocacheclient.so -> libsynocacheclient.so.5.1 lrwxrwxrwx 1 root root 25 Dec 17 14:52 /lib/libsynocacheclient.so.5 -> libsynocacheclient.so.5.1 -rw-r--r-- 1 root root 5376 Dec 13 03:26 /lib/libsynocacheclient.so.5.1 lrwxrwxrwx 1 root root 15 Dec 17 14:52 /lib/libsynocgi.so -> libsynocgi.so.5 -rwxr-xr-x 1 root root 120071 Dec 13 03:27 /lib/libsynocgi.so.5 lrwxrwxrwx 1 root root 23 Dec 17 14:52 /lib/libsynocloudclient.so -> libsynocloudclient.so.0 -rwxr-xr-x 1 root root 42736 Dec 13 03:26 /lib/libsynocloudclient.so.0 lrwxrwxrwx 1 root root 24 Dec 17 14:52 /lib/libsynocloudservice.so -> libsynocloudservice.so.1 -rw-r--r-- 1 root root 22040 Dec 13 03:24 /lib/libsynocloudservice.so.1 lrwxrwxrwx 1 root root 23 Dec 17 14:52 /lib/libsynocmsclient.so -> libsynocmsclient.so.5.1 lrwxrwxrwx 1 root root 23 Dec 17 14:52 /lib/libsynocmsclient.so.5 -> libsynocmsclient.so.5.1 -rw-r--r-- 1 root root 71744 Dec 13 03:26 /lib/libsynocmsclient.so.5.1 lrwxrwxrwx 1 root root 17 Dec 17 14:52 /lib/libsynoconfd.so -> libsynoconfd.so.5 -rwxr-xr-x 1 root root 42616 Dec 13 03:24 /lib/libsynoconfd.so.5 -rw-r--r-- 1 root root 196584 Dec 13 03:24 /lib/libsynocore.so.5 -rw-r--r-- 1 root root 146732 Dec 13 03:24 /lib/libsynocoregpl.so.5 lrwxrwxrwx 1 root root 24 Dec 17 14:52 /lib/libsynocredential.so -> libsynocredential.so.5.1 lrwxrwxrwx 1 root root 24 Dec 17 14:52 /lib/libsynocredential.so.5 -> libsynocredential.so.5.1 -rw-r--r-- 1 root root 170416 Dec 13 03:24 /lib/libsynocredential.so.5.1 -rw-r--r-- 1 root root 30172 Dec 3 02:09 /lib/libsynodb.so lrwxrwxrwx 1 root root 22 Dec 17 14:52 /lib/libsynoddnsclient.so -> libsynoddnsclient.so.1 -rwxr-xr-x 1 root root 59688 Dec 13 03:24 /lib/libsynoddnsclient.so.1 lrwxrwxrwx 1 root root 19 Dec 17 14:52 /lib/libsynodrive.so -> libsynodrive.so.5.1 lrwxrwxrwx 1 root root 19 Dec 17 14:52 /lib/libsynodrive.so.5 -> libsynodrive.so.5.1 -rw-r--r-- 1 root root 524188 Dec 13 03:26 /lib/libsynodrive.so.5.1 -rw-r--r-- 1 root root 87796 Dec 13 03:24 /lib/libsynoea.so.5 lrwxrwxrwx 1 root root 24 Dec 17 14:52 /lib/libsynoflashcache.so -> libsynoflashcache.so.5.1 lrwxrwxrwx 1 root root 24 Dec 17 14:52 /lib/libsynoflashcache.so.5 -> libsynoflashcache.so.5.1 -rw-r--r-- 1 root root 54924 Dec 13 03:24 /lib/libsynoflashcache.so.5.1 lrwxrwxrwx 1 root root 17 Dec 17 14:52 /lib/libsynoftp.so -> libsynoftp.so.5.1 lrwxrwxrwx 1 root root 17 Dec 17 14:52 /lib/libsynoftp.so.5 -> libsynoftp.so.5.1 -rw-r--r-- 1 root root 38448 Dec 13 03:24 /lib/libsynoftp.so.5.1 lrwxrwxrwx 1 root root 25 Dec 17 14:52 /lib/libsynoglusterfs-dsm.so -> libsynoglusterfs-dsm.so.5 -rw-r--r-- 1 root root 9464 Dec 13 03:24 /lib/libsynoglusterfs-dsm.so.5 -rw-r--r-- 1 root root 486344 Dec 13 03:24 /lib/libsynogpl.so.5 -rw-r--r-- 1 root root 105468 Dec 13 03:25 /lib/libsynoindex.so -rwxr-xr-x 1 root root 248776 Dec 13 03:24 /lib/libsynoinstallcpp.so lrwxrwxrwx 1 root root 19 Dec 17 14:52 /lib/libsynoiscsiep.so -> libsynoiscsiep.so.5 -rw-r--r-- 1 root root 270120 Dec 13 03:24 /lib/libsynoiscsiep.so.5 lrwxrwxrwx 1 root root 16 Dec 17 14:52 /lib/libsynoldap.so -> libsynoldap.so.5 -rw-r--r-- 1 root root 158236 Dec 13 03:24 /lib/libsynoldap.so.5 lrwxrwxrwx 1 root root 16 Dec 17 14:52 /lib/libsynoldap.so.5.0 -> libsynoldap.so.5 -rw-r--r-- 1 root root 13708 Dec 13 03:24 /lib/libsynolog.so.1 -rwxr-xr-x 1 root root 59436 Dec 13 03:26 /lib/libsynomount.so lrwxrwxrwx 1 root root 16 Dec 17 14:52 /lib/libsynomyds.so -> libsynomyds.so.1 -rw-r--r-- 1 root root 121052 Dec 13 03:24 /lib/libsynomyds.so.1 lrwxrwxrwx 1 root root 20 Dec 17 14:52 /lib/libsynonetcheck.so -> libsynonetcheck.so.5 -rw-r--r-- 1 root root 13760 Dec 13 03:24 /lib/libsynonetcheck.so.5 lrwxrwxrwx 1 root root 19 Dec 17 14:52 /lib/libsynonetwork.so -> libsynonetwork.so.5 -rw-r--r-- 1 root root 974124 Dec 13 03:24 /lib/libsynonetwork.so.5 lrwxrwxrwx 1 root root 17 Dec 17 14:52 /lib/libsynonfs.so -> libsynonfs.so.5.1 lrwxrwxrwx 1 root root 17 Dec 17 14:52 /lib/libsynonfs.so.5 -> libsynonfs.so.5.1 -rw-r--r-- 1 root root 38512 Dec 13 03:24 /lib/libsynonfs.so.5.1 lrwxrwxrwx 1 root root 15 Dec 17 14:52 /lib/libsynopkg.so -> libsynopkg.so.1 -rw-r--r-- 1 root root 445760 Dec 13 03:24 /lib/libsynopkg.so.1 lrwxrwxrwx 1 root root 23 Dec 17 14:52 /lib/libsynoportforward.so -> libsynoportforward.so.0 -rwxr-xr-x 1 root root 96084 Dec 13 03:24 /lib/libsynoportforward.so.0 lrwxrwxrwx 1 root root 19 Dec 17 14:52 /lib/libsynoportmap.so -> libsynoportmap.so.5 -rw-r--r-- 1 root root 178600 Dec 13 03:24 /lib/libsynoportmap.so.5 lrwxrwxrwx 1 root root 17 Dec 17 14:52 /lib/libsynoproxy.so -> libsynoproxy.so.5 -rw-r--r-- 1 root root 21944 Dec 3 02:10 /lib/libsynoproxy.so.5 lrwxrwxrwx 1 root root 17 Dec 17 14:52 /lib/libsynoproxy.so.5.0 -> libsynoproxy.so.5 lrwxrwxrwx 1 root root 21 Dec 17 14:52 /lib/libsynorecycle.so -> libsynorecycle.so.5.1 lrwxrwxrwx 1 root root 21 Dec 17 14:52 /lib/libsynorecycle.so.5 -> libsynorecycle.so.5.1 -rw-r--r-- 1 root root 46736 Dec 13 03:24 /lib/libsynorecycle.so.5.1 lrwxrwxrwx 1 root root 20 Dec 17 14:52 /lib/libsynorelayd.so -> libsynorelayd.so.5.1 lrwxrwxrwx 1 root root 20 Dec 17 14:52 /lib/libsynorelayd.so.5 -> libsynorelayd.so.5.1 -rw-r--r-- 1 root root 229012 Dec 13 03:24 /lib/libsynorelayd.so.5.1 lrwxrwxrwx 1 root root 18 Dec 17 14:52 /lib/libsynoreport.so -> libsynoreport.so.1 -rw-r--r-- 1 root root 112060 Dec 13 03:26 /lib/libsynoreport.so.1 -rwxr-xr-x 1 root root 34328 Dec 13 03:24 /lib/libsynorouter.so lrwxrwxrwx 1 root root 17 Dec 17 14:52 /lib/libsynoscemd.so -> libsynoscemd.so.1 -rw-r--r-- 1 root root 75628 Dec 13 03:26 /lib/libsynoscemd.so.1 lrwxrwxrwx 1 root root 23 Dec 17 14:52 /lib/libsynoscheduler.so -> libsynoscheduler.so.5.1 lrwxrwxrwx 1 root root 23 Dec 17 14:52 /lib/libsynoscheduler.so.5 -> libsynoscheduler.so.5.1 -rw-r--r-- 1 root root 137184 Dec 13 03:24 /lib/libsynoscheduler.so.5.1 lrwxrwxrwx 1 root root 26 Dec 17 14:52 /lib/libsynoschedulercgi.so -> libsynoschedulercgi.so.5.1 lrwxrwxrwx 1 root root 26 Dec 17 14:52 /lib/libsynoschedulercgi.so.5 -> libsynoschedulercgi.so.5.1 -rw-r--r-- 1 root root 26032 Dec 13 03:24 /lib/libsynoschedulercgi.so.5.1 -rw-r--r-- 1 root root 2257928 Dec 13 03:24 /lib/libsynosdk.so.5 lrwxrwxrwx 1 root root 23 Dec 17 14:52 /lib/libsynoserviceutil.so -> libsynoserviceutil.so.5 -rw-r--r-- 1 root root 34388 Dec 13 03:24 /lib/libsynoserviceutil.so.5 lrwxrwxrwx 1 root root 17 Dec 17 14:52 /lib/libsynoshare.so -> libsynoshare.so.5 -rw-r--r-- 1 root root 178792 Dec 13 03:24 /lib/libsynoshare.so.5 -rwxr-xr-x 1 root root 21996 Dec 13 03:24 /lib/libsynosmtp.so -rwxr-xr-x 1 root root 13716 Dec 13 03:24 /lib/libsynosnmp.so.1 lrwxrwxrwx 1 root root 27 Dec 17 14:52 /lib/libsynosocialaccount.so -> libsynosocialaccount.so.5.1 lrwxrwxrwx 1 root root 27 Dec 17 14:52 /lib/libsynosocialaccount.so.5 -> libsynosocialaccount.so.5.1 -rw-r--r-- 1 root root 67300 Dec 13 03:26 /lib/libsynosocialaccount.so.5.1 lrwxrwxrwx 1 root root 19 Dec 17 14:52 /lib/libsynostorage.so -> libsynostorage.so.5 -rw-r--r-- 1 root root 71776 Dec 13 03:24 /lib/libsynostorage.so.5 -rw-r--r-- 1 root root 487516 Dec 13 03:24 /lib/libsynostoragemgmt.so -rwxr-xr-x 1 root root 326340 Dec 13 03:26 /lib/libsynosyslog.so -rwxr-xr-x 1 root root 30264 Dec 13 03:26 /lib/libsynosyslogclient.so lrwxrwxrwx 1 root root 24 Dec 17 14:52 /lib/libsynotifyclient.so -> libsynotifyclient.so.5.1 lrwxrwxrwx 1 root root 24 Dec 17 14:52 /lib/libsynotifyclient.so.5 -> libsynotifyclient.so.5.1 -rw-r--r-- 1 root root 22040 Dec 13 03:26 /lib/libsynotifyclient.so.5.1 lrwxrwxrwx 1 root root 16 Dec 17 14:52 /lib/libsynoudpd.so -> libsynoudpd.so.5 -rw-r--r-- 1 root root 26104 Dec 3 02:13 /lib/libsynoudpd.so.5 lrwxrwxrwx 1 root root 27 Dec 17 14:52 /lib/libsynousbmodem-server.so -> libsynousbmodem-server.so.5 -rw-r--r-- 1 root root 1105812 Dec 13 03:24 /lib/libsynousbmodem-server.so.5 lrwxrwxrwx 1 root root 20 Dec 17 14:52 /lib/libsynousbmodem.so -> libsynousbmodem.so.5 -rw-r--r-- 1 root root 76112 Dec 13 03:24 /lib/libsynousbmodem.so.5 lrwxrwxrwx 1 root root 17 Dec 17 14:52 /lib/libsynoutils.so -> libsynoutils.so.1 -rw-r--r-- 1 root root 46744 Dec 3 02:10 /lib/libsynoutils.so.1 lrwxrwxrwx 1 root root 15 Dec 17 14:52 /lib/libsynovfs.so -> libsynovfs.so.5 -rw-r--r-- 1 root root 191368 Dec 13 03:25 /lib/libsynovfs.so.5 -rwxr-xr-x 1 root root 83552 Dec 13 03:27 /lib/libsynovpnclient.so lrwxrwxrwx 1 root root 28 Dec 17 14:52 /lib/libsynovspace_wrapper.so -> libsynovspace_wrapper.so.5.1 lrwxrwxrwx 1 root root 28 Dec 17 14:52 /lib/libsynovspace_wrapper.so.5 -> libsynovspace_wrapper.so.5.1 -rw-r--r-- 1 root root 26064 Dec 13 03:24 /lib/libsynovspace_wrapper.so.5.1 lrwxrwxrwx 1 root root 19 Dec 17 14:52 /lib/libsynowimax.so -> libsynowimax.so.5.1 -rw-r--r-- 1 root root 17828 Dec 13 03:24 /lib/libsynowimax.so.5.1 lrwxrwxrwx 1 root root 25 Dec 17 14:52 /lib/libsynowireless-core.so -> libsynowireless-core.so.5 -rw-r--r-- 1 root root 59452 Dec 13 03:24 /lib/libsynowireless-core.so.5 lrwxrwxrwx 1 root root 27 Dec 17 14:52 /lib/libsynowireless-usbmodem-server.so -> libsynousbmodem-server.so.5 lrwxrwxrwx 1 root root 27 Dec 17 14:52 /lib/libsynowireless-usbmodem-server.so.5 -> libsynousbmodem-server.so.5 lrwxrwxrwx 1 root root 20 Dec 17 14:52 /lib/libsynowireless-usbmodem.so -> libsynousbmodem.so.5 lrwxrwxrwx 1 root root 20 Dec 17 14:52 /lib/libsynowireless-usbmodem.so.5 -> libsynousbmodem.so.5 lrwxrwxrwx 1 root root 19 Dec 17 14:52 /lib/libsynowireless.so -> libsynonetwork.so.5 lrwxrwxrwx 1 root root 19 Dec 17 14:52 /lib/libsynowireless.so.5 -> libsynonetwork.so.5 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.