jun

I'm not sure what the problem is so I can't suggest any alternative solution. I have tried to explain what worked for me the best I can. Beyond that I can't really help sorry. Now after i reboot and try again i get the message that i must reinstall the dsm... but i still get the 13 error... maybe is this the installation loop from old posts? I think error 13 means your vid/pid does not match your usb stick. for peoples have a hard time to edit grub.cfg, they can at least enjoy the VM build.

DSM seems by default create system raid arrary with big endian metadata, and normally x86 devices use little endian metadata on these arrays so /dev/md0 can not be auto detected by normal linux distributions, unless you could find a big endian linux box But linux hackers are kind enough to provide some obscure command line options to make peoples life easier. you can use follow command to exam foreign endian arrary members mdadm -Ee0.swap /dev/sda1 and use follow command to assemble an arrary and fix byte order in one go mdadm -AU byteorder /dev/md0 /dev/sda1 /dev/sdb1 ... DSM will convert it back to its preferred endian on next boot, so no further action requried.

You dont need a DS1815+ for SHR support just edit /etc.defaults/synoinfo.conf comment out/delete supportraidgroup="yes" then add support_syno_hybrid_raid="yes" press F5 on you web browser

I think something like wiki works best for this kind of work-in-progress community efforts. The essential part is already there, and I will rely on the community for further improvement.

Not that I've seen.. Disks and CPU are zero % after booting up - every time - after seeing this message about the improper shutdown. I don't think it's doing a parity check - or anything, really. My box was powered down using either the power option on the console, the shutdown or poweroff commands (at a SSH terminal), so it was 'going down properly'.. It didn't suddenly switch itself off and reboot.. Personally, I think it's a bug (and there have been previous notifications on 'actual' synology devices about this bug) but it would be nice to resolve it.. #H After testing the dual UEFI/Legacy build (bare metal) on motherboards with/without a physical serial port, I don't see the errors with motherboards that have a physical serial port. No errors are displayed or logged after a reboot or a shutdown/restart. I do see the errors with motherboards that don't have a physical serial port. After doing some research on some of the Synology NAS models, it appears some models do have a physical serial port. This is not exposed to the user. I have read articles where some owners have opened their Synology NAS's to physically connect up the serial comm port. The main reason for doing this was to recover from a "Bricked Unit". On reboot or shutdown/restart the following is logged in the "messages" logs for motherboards without a physical serial port. 2016-10-02T19:34:23-04:00 Test-NAS60 synoscgi_SYNO.Core.System_1_shutdown[12971]: system_sys_init.c:90 synopoweroff: System is going to poweroff 2016-10-02T19:34:23-04:00 Test-NAS60 [ 320.740657] init: synonetd main process (4969) killed by TERM signal 2016-10-02T19:34:23-04:00 Test-NAS60 [ 320.741148] init: synostoraged main process (9548) terminated with status 15 2016-10-02T19:34:23-04:00 Test-NAS60 [ 320.742680] init: hotplugd main process (11016) killed by TERM signal 2016-10-02T19:34:23-04:00 Test-NAS60 [ 320.743111] init: smbd main process (11382) killed by TERM signal 2016-10-02T19:34:23-04:00 Test-NAS60 [ 320.835177] init: syno_poweroff_task main process (13011) terminated with status 1 Logs from motherboard with physical serial port 2016-09-27T20:18:29-05:00 Test-NAS48 [ 1373.178048] init: synonetd main process (5536) killed by TERM signal 2016-09-27T20:18:29-05:00 Test-NAS48 [ 1373.178468] init: synostoraged main process (10964) terminated with status 15 2016-09-27T20:18:29-05:00 Test-NAS48 [ 1373.179553] init: hotplugd main process (12425) killed by TERM signal 2016-09-27T20:18:29-05:00 Test-NAS48 [ 1373.184887] init: smbd main process (12631) killed by TERM signal 2016-09-27T20:18:29-05:00 Test-NAS48 syno_poweroff_task: System is acting poweroff. Also, as stated in the post from jun on Page 1, if your motherboard does not have a physical serial port the logs will fill up with the following, if you don't stop/disable the tty service: 2016-10-02T19:33:46-04:00 Test-NAS60 [ 283.376096] init: tty main process ended, respawning 2016-10-02T19:33:56-04:00 Test-NAS60 [ 293.377424] init: tty main process (12828) terminated with status 1 2016-10-02T19:33:56-04:00 Test-NAS60 [ 293.377449] init: tty main process ended, respawning 2016-10-02T19:34:06-04:00 Test-NAS60 [ 303.378699] init: tty main process (12846) terminated with status 1 To see if you are getting the tty errors, you can check your logs. SSH in, use the following command "dmesg | grep tty" Hope this information is helpful. Right, this is another issue of missing console, I am thinking about a proper (out of box) workaround. root@test:~# grep -r "^console output$" /usr/ 2> /dev/null /usr/share/init/syno_poweroff_task.conf:console output /usr/share/init/burnin_loader.conf:console output /usr/share/init/udevtrigger.conf:console output /usr/share/init/bs-poweroff.conf:console output /usr/share/init/udevd.conf:console output Notice that above service want to output to a console, so they will failed to start for the unlucky guys . Simply change "console output" to "console none" should work. I thought most board had a serial port, even if not populated, could always be seen by software if enabled, it is a standard part of PC, is that not the case? In my case, all of my boards have serial headers, I just need to enable it somewhere in BIOS. OK, my boards are mainly Asrock ones, so maybe my observation is biased. For debugging purpose, I add a DB9 connector to the serial header, but that is not required for normal users.

maybe you did not change the vid/pid, so the installation process can not find the synoboot partitions. I should make it clear that you need to change vid/pid BEFORE installation. PS: DS716/916 should have better compatibility with your hardware, I'll release a DS916 version later when I can test it properly. You were right, somehow I really did miss to change vid/pid. Now installation goes smooth but after restart synology complains that my disks were moved from another DS3615xs and wants to reinstall/update os. Seem it can not mount /dev/md0 in the boot process, so falls back to installer, but in the installation process, disks are recognized correctly. So it looks a timing issue to me, will look into it. EDIT: I've found the root cause, and updated my thread, you may want to take another chance to see if it works.

maybe you did not change the vid/pid, so the installation process can not find the synoboot partitions. I should make it clear that you need to change vid/pid BEFORE installation. PS: DS716/916 should have better compatibility with your hardware, I'll release a DS916 version later when I can test it properly.

DSM mainly checks /proc/bus/pci/devices, /sys/bus/pci/devices, /proc/cmdline and /dev/ttyS1. You should provide the list of devices to first 2 pseudo files/folder, and hide unwanted entries from /proc/cmdline plus /dev/ttyS1 should looks as if a mcu is attached on the other side (I am not very clear about the detail). A bit of reverse engineering skill and kernel programming kung fu is all you need.

Thanks for your advice. Yes, dynamic patching has its obvious limitations. So the proper source code is still very usefull. I have to admit I do not have time to maintain a large list of supported drivers either.

Hi, The are various check around DSM programs, especially in Web Interface, maybe some are still not found out. One kind is to make sure you are running on real DSM hardwares, specifically, it checks that you have pci devices the model should have. This check is a bit forgiving, i.e., if you only have 9 out of the 10 devices, you may still pass the check. Some models have mcu to control powers, leds, fans, DSM also checks that it can communicate with the controller properly. Another kind of check is to make sure your system does not have any clue that you pretend to be a DSM model, for example has some file named xpenoboot somewhere,or has pid, vid in kernel cmdline, these should not exists in a real DSM devices. Sometimes, it also checksum each other to make sure system executables are not patched. If DSM determines that is is not run on intended hardware, it will try to unmount all your volumes, shutdown the system, sometimes also corrupt some DSM system files etc. No sign of intentionally breaking user data is observed though. Clearly, your DSM software thinks that it is not running on a real DS712+ device, so it unmounts all your volumes. And what I did is to make sure DSM gets what it wants, so it will run happlily and ignorantly.

I can not send PM, so I opened a thread, any question pls ask there

10/28: Recently, I've implenmented an advanced patching method, its interesting in principle. So I utilize it to add AMD cpu support, hope it works . This is the updated zImage, please test and send your feedback. https://mega.nz/#!Vk0E2RrL!eFRPWcnaXn9b ... Sihf5BTRG0

Loader Download: here / (link updated due to directory structure change of mega share) -- by jun 2-28 I've uploaded a 6.1 alpha build to mega, for brave guys only . (Note: AMD needs extra work.) scripts I use to generate bootable image https://github.com/kref/scripts ---Beginning of addition by polanskiman--- Tutorials by polanskiman: Install/Upgrade DSM 5.2 to DSM 6.0.2 here Install/Upgrade DSM 5.2 to DSM 6.1 here Loader download mirrors: Managed by Polanskiman. includes .iso format images made by myself. here Managed by Trantor. This mirror is currently offline. here For info: v1.01 (DS3615xs) is for DSM 6.0.2 - AMD compatible - Latest version for DSM 6.0.2 v1.02b (DS3615xs, DS3617xs and DS916+) is for DSM 6.1 - AMD loosely compatible and with Bios tweaks - Latest version for DSM 6.1 DO NOT install DSM updates on your working machine BEFORE looking into the forum or testing the update on a test rig/vm. DO NOT update to DSM 6.2 with loader v.1.02b. It will not work. I repeat. DO NOT update to DSM 6.2 Further explanation by jun on AMD compatibly for loader v1.02a, v1.02a2 and v1.02b: ---End of addition by polanskiman---

@oktisme sovled the problem through userland, and I want to try a different approch. I recently wrote a linux kernel module to dynamically patch the dsm kernel. With this hack, we only need to repack rd.gz to load this special module at early stage, zImage & pat is used as is, so changes are kept minimal. Now it works on latest version DSM 6.0.2-8451, sort of. I mean every feature looks healthy, but drivers for bare metals are not included, there are simply to many, and I am too lazy. These drivers can be build with the beta source, I notice there is one floating around on the github. Personally I only build a few network drivers to test on a VM, but I am pretty sure it works for other drivers. If any hacker want to test it, pls contact me. I mean peoples who comfort to build kernel modules, pack & unpack ramdisk, have serial console if want to test on bare metal. TODO: hide any trace of the module, since I am sure it will be on the blacklist if it become popular. Below is the console log for installing on a VM with UEFI bootloader & PXE GNU GRUB version 2.02~beta3 +----------------------------------------------------------------------------+ | Synology PXE | | Synology DS916+ | |*Synology DS3615xs | | | | | | | | | | | | | | | | | | | +----------------------------------------------------------------------------+ Use the ^ and v keys to select which entry is highlighted. Press enter to boot the selected OS, `e' to edit the commands before booting or `c' for a command-line. The highlighted entry will be executed automatically in 0s. Booting `Synology DS3615xs' error: no suitable video mode found. Booting in blind mode early console in decompress_kernel Decompressing Linux... Parsing ELF... done. Booting the kernel. [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Initializing cgroup subsys cpuacct [ 0.000000] Linux version 3.10.77 (root@build1) (gcc version 4.9.3 20150311 (prerelease) (crosstool-NG 1.20.0) ) #8451 SMP Wed Aug 17 05:12:41 CST 2016 [ 0.000000] Command line: BOOT_IMAGE=(tftp,192.168.200.2)/grub/../image/DS3615xs/zImage root=/dev/md0 syno_hdd_powerup_seq=0 netif_num=1 HddHotplug=0 syno_hw_version=DS3615xs vender_format_version=2 vid=0x058f pid=0x6387 console=uart,io,0x3f8,115200n8 sn=C7LWN09761 mac1=0011322CA785 withefi elevator=your_magic_elevator quiet [ 0.000000] KERNEL supported cpus: [ 0.000000] Intel GenuineIntel [ 0.000000] Disabled fast string operations [ 0.000000] e820: BIOS-provided physical RAM map: [ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x0000000000000fff] ACPI NVS [ 0.000000] BIOS-e820: [mem 0x0000000000001000-0x000000000009ffff] usable [ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000000dd80fff] usable [ 0.000000] BIOS-e820: [mem 0x000000000dd81000-0x000000000dd85fff] ACPI NVS [ 0.000000] BIOS-e820: [mem 0x000000000dd86000-0x000000000ef1ffff] usable [ 0.000000] BIOS-e820: [mem 0x000000000ef20000-0x000000000ef3ffff] type 20 [ 0.000000] BIOS-e820: [mem 0x000000000ef40000-0x000000000ef8ffff] reserved [ 0.000000] BIOS-e820: [mem 0x000000000ef90000-0x000000000efabfff] ACPI data [ 0.000000] BIOS-e820: [mem 0x000000000efac000-0x000000000efaffff] ACPI NVS [ 0.000000] BIOS-e820: [mem 0x000000000efb0000-0x000000003fffffff] usable [ 0.000000] BIOS-e820: [mem 0x00000000ffc00000-0x00000000ffc17fff] reserved [ 0.000000] Early serial console at I/O port 0x3f8 (options '115200n') [ 0.000000] bootconsole [uart0] enabled START /linuxrc.syno Insert basic USB modules... :: Loading module usb-common ... [ OK ] :: Loading module usbcore ... [ OK ] :: Loading module ehci-hcd ... [ OK ] :: Loading module ehci-pci ... [ OK ] :: Loading module uhci-hcd ... [ OK ] :: Loading module xhci-hcd ... [ OK ] :: Loading module etxhci-hcd ... [ OK ] Insert net driver(Mindspeed only)... Starting /usr/syno/bin/synocfgen... /usr/syno/bin/synocfgen returns 0 Partition Version=8 /sbin/e2fsck exists, checking /dev/md0... 54 inodes used (0.03%, out of 155648) 3 non-contiguous files (5.6%) 0 non-contiguous directories (0.0%) # of inodes with ind/dind/tind blocks: 0/0/0 Extent depth histogram: 45/1 209209 blocks used (33.61%, out of 622544) 0 bad blocks 1 large file 36 regular files 9 directories 0 character device files 0 block device files 0 fifos 0 links 0 symbolic links (0 fast symbolic links) 0 sockets ------------ 45 files /sbin/e2fsck returns 0 Mounting /dev/md0 /tmpRoot ------------upgrade Begin upgrade procedure Found an upgrade file on data volume. Begin upgrade Checksum of system tarball verified. /tmpRoot//etc -> /tmpRoot/.upd@te/etc/ mv: can't rename '/tmpRoot//etc/.[^.]*': No such file or directory /tmpRoot//var -> /tmpRoot/.upd@te/var/ mv: can't rename '/tmpRoot//var/*': No such file or directory Removing /tmpRoot/.upd@te//etc/ftpusers... Removing /tmpRoot/.upd@te//etc/rc... Removing /tmpRoot/.upd@te//etc/rc.network... Removing /tmpRoot/.upd@te//usr/syno/etc/rc.atalk... Removing /tmpRoot/.upd@te//usr/syno/etc/.htpasswd... Removing /tmpRoot/.upd@te//usr/syno/etc/lpd/lpd.conf... Removing /tmpRoot/.upd@te//usr/syno/etc/printcap... Removing /tmpRoot/.upd@te//usr/syno/etc/ups.conf... Removing /tmpRoot/.upd@te//usr/syno/etc/upsd.conf... Removing /tmpRoot/.upd@te//usr/syno/etc/upsd.users... Removing /tmpRoot/.upd@te//usr/syno/etc/upsmon.conf... Removing /tmpRoot/.upd@te//usr/syno/etc/upssched.conf... Removing /tmpRoot/.upd@te//etc/lvm/lvm.conf... Removing /tmpRoot/.upd@te//usr/local/etc/rc.d/SynoEnablePersonalServices.sh... Removing /tmpRoot/.upd@te//etc/rc.network_routing... Removing /tmpRoot/.upd@te//usr/syno/etc/rc.tun... Removing /tmpRoot/.upd@te//usr/syno/etc/afpd.conf... Removing /tmpRoot/.upd@te//etc/pam.d/samba... Removing /tmpRoot/.upd@te//etc/ppp/ip-up... Removing /tmpRoot/.upd@te//etc/ppp/ip-down... Removing /tmpRoot/.upd@te//etc/ppp/ip-function... Removing /tmpRoot/.upd@te//etc/ppp/ipv6-up... Removing /tmpRoot/.upd@te//etc/ppp/ipv6-down... Removing /tmpRoot/.upd@te//etc/ppp/options... Removing /tmpRoot/.upd@te//usr/local/cups/mime.types... Removing /tmpRoot/.upd@te//usr/local/cups/mime.convs... Removing /tmpRoot/.upd@te//etc/cups/cupsd.conf... Removing /tmpRoot/.upd@te//usr/local/cups/cupsd.conf... Removing /tmpRoot/.upd@te//usr/local/cups/testprint... Removing /tmpRoot/.upd@te//usr/local/cups/filter/bannertops... Removing /tmpRoot/.upd@te//usr/local/cups/filter/commandtops... Removing /tmpRoot/.upd@te//usr/local/cups/filter/gziptoany... Removing /tmpRoot/.upd@te//usr/local/cups/filter/imagetops... Removing /tmpRoot/.upd@te//usr/local/cups/filter/imagetoraster... Removing /tmpRoot/.upd@te//usr/local/cups/filter/pdftops... Removing /tmpRoot/.upd@te//usr/local/cups/filter/pstops... Removing /tmpRoot/.upd@te//usr/local/cups/filter/rastertoepson... Removing /tmpRoot/.upd@te//usr/local/cups/filter/rastertohp... Removing /tmpRoot/.upd@te//usr/local/cups/filter/rastertolabel... Removing /tmpRoot/.upd@te//usr/local/cups/filter/rastertopwg... Removing /tmpRoot/.upd@te//usr/local/cups/filter/texttops... Removing /tmpRoot/.upd@te//usr/local/cups/filter/hpgltops... Removing /tmpRoot/.upd@te//etc/hostapd/stainfo.sh... Removing /tmpRoot/.upd@te//etc/hostapd/mac_filter/mfscript.sh... Removing /tmpRoot/.upd@te//usr/syno/etc/rfkill.sh... Removing /tmpRoot/.upd@te//usr/syno/etc/iptables_guest_net.sh... Removing /tmpRoot/.upd@te//etc/ld.so.preload... Removing /tmpRoot/.upd@te//etc/tc/default.cmd... Removing /tmpRoot/.upd@te//usr/syno/etc/ssl/mkcert.sh... Removing /tmpRoot/.upd@te//usr/syno/etc/ssl/mkcgikey.sh... Removing /tmpRoot/.upd@te//etc/logrotate.conf... Removing /tmpRoot/.upd@te//usr/syno/etc/usbmodem/wcdma_list.json... Removing /tmpRoot/.upd@te//usr/syno/etc/usbmodem/usb_modeswitch.d/*... Removing /tmpRoot/.upd@te//etc/php/php.ini... Removing /tmpRoot/.upd@te//etc/php/php-fpm.conf... Removing /tmpRoot/.upd@te//etc/php/conf.d/opcache.ini... Removing /tmpRoot/.upd@te//usr/syno/etc/synoservice.d/global.setting... Removing /tmpRoot/.upd@te//usr/syno/etc/synoservice.d/system.cfg... Removing /tmpRoot/.upd@te//usr/syno/etc/ssdp/dsm_desc.xml... Removing /tmpRoot/.upd@te//usr/syno/etc/iptables_time_ctrl.sh... Removing /tmpRoot/.upd@te//etc/profile... Removing /tmpRoot/.upd@te//etc/inputrc... Removing /tmpRoot/.upd@te//etc/dhclient/dhclient-script... Removing /tmpRoot/.upd@te//etc/dhclient/ipv4/dhclient.conf... Removing /tmpRoot/.upd@te//etc/dhclient/ipv6/dhclient.conf... Removing /tmpRoot/.upd@te//usr/syno/etc/www/SSLProfile.json... Removing /tmpRoot/.upd@te//etc/vimrc... Removing /tmpRoot/.upd@te//usr/syno/etc/cacert.pem... Removing /tmpRoot/.upd@te//usr/syno/etc/iptables_modules_list... Removing /tmpRoot/.upd@te//usr/syno/etc/iptables_chain_list... Removing /tmpRoot/.upd@te//usr/local/bin/python*... Removing /tmpRoot/.upd@te//etc/pam.d... Removing /tmpRoot/.upd@te//usr/syno/etc/vfs... Removing /tmpRoot/.upd@te//var/run... Removing /tmpRoot/.upd@te//var/state/ups... Removing /tmpRoot/.upd@te//usr/syno/etc/ups... Removing /tmpRoot/.upd@te//var/spool/postfix... Removing /tmpRoot/.upd@te//usr/local/cups/backend... Removing /tmpRoot/.upd@te//usr/local/cups/mime... Removing /tmpRoot/.upd@te//etc/fw_security/sysconf... Removing /tmpRoot/.upd@te//etc/init... Removing /tmpRoot/.upd@te//etc/logrotate.d... Removing /tmpRoot/.upd@te//etc/syslog-ng... Removing /tmpRoot/.upd@te//var/lib/dpkg... Removing /tmpRoot/.upd@te//etc/httpd/conf... Removing /tmpRoot/.upd@te//etc/postgresql... Removing /tmpRoot/.upd@te//etc/nginx... Removing /tmpRoot/.upd@te//etc/wide-dhcpv6... Removing /tmpRoot/.upd@te//etc/apparmor.d... Removing /tmpRoot/.upd@te//usr/syno/etc/synoservice.d... Removing /tmpRoot/.upd@te//var/dynlib... Removing /tmpRoot/.upd@te//etc/iproute2/script... Removing /tmpRoot/.upd@te//etc/ssl/certs... Removing /tmpRoot/.upd@te//etc/dbus-1... Removing /tmpRoot/.upd@te//usr/syno/etc/dbus-1... Removing /tmpRoot/.upd@te//etc/avahi... Removing /tmpRoot/.upd@te//usr/syno/etc/synovpnclient/scripts... Removing /tmpRoot/.upd@te//var/lib/apparmor... Removing /tmpRoot/.upd@te//usr/syno/etc/www/app.d... Removing /tmpRoot/.upd@te//usr/syno/etc/rc.d... Removing /tmpRoot/.upd@te//usr/syno/etc/bluetooth/... Removing /tmpRoot/.upd@te//usr/syno/etc/smallupdate_patch... Removing /tmpRoot/.upd@te//etc/ImageMagick-6... chmod: /tmpRoot/.upd@te/root: No such file or directory cp: can't stat '/tmpRoot/etc.defaults/VERSION': No such file or directory cp: can't stat '/tmpRoot/etc.defaults/synoinfo.conf': No such file or directory cp: can't stat '/tmpRoot/.system_info': No such file or directory Setting up swapspace version 1, size = 2147414016 bytes Untaring /tmpRoot/.SynoUpgrade.tar... cp: can't create '/tmpRoot/*': No such file or directory mknod: /dev/synobios: File exists Starting /usr/syno/bin/synohdcfgen... /usr/syno/bin/synohdcfgen returns 0 End upgrade procedure ============upgrade Wait 2 seconds for synology manufactory device Mon Sep 19 11:08:39 UTC 2016 /dev/md0 /tmpRoot ext4 rw,relatime,journal_checksum,data=ordered 0 0 none /sys/kernel/debug debugfs rw,relatime 0 0 sys /sys sysfs rw,relatime 0 0 none /dev devtmpfs rw,relatime,size=506848k,nr_inodes=126712,mode=755 0 0 proc /proc proc rw,relatime 0 0 linuxrc.syno executed successfully. Post init ==================== start udevd ==================== ===== trigger device plug event ===== Mon Sep 19 04:09:08 2016 DiskStation login: [ 428.997868] BTRFS: has skinny extents [ 429.262141] BTRFS: has skinny extents System is going to reboot. [ 655.113869] Restarting system. GNU GRUB version 2.02~beta3 +----------------------------------------------------------------------------+ | Synology PXE | | Synology DS916+ | |*Synology DS3615xs | | | | | | | | | | | | | | | | | | | +----------------------------------------------------------------------------+ Use the ^ and v keys to select which entry is highlighted. Press enter to boot the selected OS, `e' to edit the commands before booting or `c' for a command-line. The highlighted entry will be executed automatically in 0s. Booting `Synology DS3615xs' error: no suitable video mode found. Booting in blind mode early console in decompress_kernel Decompressing Linux... Parsing ELF... done. Booting the kernel. [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Initializing cgroup subsys cpuacct [ 0.000000] Linux version 3.10.77 (root@build1) (gcc version 4.9.3 20150311 (prerelease) (crosstool-NG 1.20.0) ) #8451 SMP Wed Aug 17 05:12:41 CST 2016 [ 0.000000] Command line: BOOT_IMAGE=(tftp,192.168.200.2)/grub/../image/DS3615xs/zImage root=/dev/md0 syno_hdd_powerup_seq=0 netif_num=1 HddHotplug=0 syno_hw_version=DS3615xs vender_format_version=2 vid=0x058f pid=0x6387 console=uart,io,0x3f8,115200n8 sn=C7LWN09761 mac1=0011322CA785 withefi elevator=your_magic_elevator quiet [ 0.000000] KERNEL supported cpus: [ 0.000000] Intel GenuineIntel [ 0.000000] Disabled fast string operations [ 0.000000] e820: BIOS-provided physical RAM map: [ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x0000000000000fff] ACPI NVS [ 0.000000] BIOS-e820: [mem 0x0000000000001000-0x000000000009ffff] usable [ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000000dd80fff] usable [ 0.000000] BIOS-e820: [mem 0x000000000dd81000-0x000000000dd85fff] ACPI NVS [ 0.000000] BIOS-e820: [mem 0x000000000dd86000-0x000000000ef1ffff] usable [ 0.000000] BIOS-e820: [mem 0x000000000ef20000-0x000000000ef3ffff] type 20 [ 0.000000] BIOS-e820: [mem 0x000000000ef40000-0x000000000ef8ffff] reserved [ 0.000000] BIOS-e820: [mem 0x000000000ef90000-0x000000000efabfff] ACPI data [ 0.000000] BIOS-e820: [mem 0x000000000efac000-0x000000000efaffff] ACPI NVS [ 0.000000] BIOS-e820: [mem 0x000000000efb0000-0x000000003fffffff] usable [ 0.000000] BIOS-e820: [mem 0x00000000ffc00000-0x00000000ffc17fff] reserved [ 0.000000] Early serial console at I/O port 0x3f8 (options '115200n') [ 0.000000] bootconsole [uart0] enabled START /linuxrc.syno Insert basic USB modules... :: Loading module usb-common ... [ OK ] :: Loading module usbcore ... [ OK ] :: Loading module ehci-hcd ... [ OK ] :: Loading module ehci-pci ... [ OK ] :: Loading module uhci-hcd ... [ OK ] :: Loading module xhci-hcd ... [ OK ] :: Loading module etxhci-hcd ... [ OK ] Insert net driver(Mindspeed only)... Starting /usr/syno/bin/synocfgen... /usr/syno/bin/synocfgen returns 0 [ 4.501095] md: invalid raid superblock magic on sdb3 Partition Version=8 /sbin/e2fsck exists, checking /dev/md0... 28547 inodes used (18.34%, out of 155648) 11 non-contiguous files (0.0%) 9 non-contiguous directories (0.0%) # of inodes with ind/dind/tind blocks: 0/0/0 Extent depth histogram: 25896/2 222659 blocks used (35.77%, out of 622544) 0 bad blocks 1 large file 22671 regular files 2926 directories 2 character device files 0 block device files 0 fifos 1315 links 2939 symbolic links (2639 fast symbolic links) 0 sockets ------------ 29853 files /sbin/e2fsck returns 0 Mounting /dev/md0 /tmpRoot ------------upgrade Begin upgrade procedure No upgrade file exists End upgrade procedure ============upgrade Wait 2 seconds for synology manufactory device Mon Sep 19 11:20:01 UTC 2016 /dev/md0 /tmpRoot ext4 rw,relatime,journal_checksum,data=ordered 0 0 none /sys/kernel/debug debugfs rw,relatime 0 0 sys /sys sysfs rw,relatime 0 0 none /dev devtmpfs rw,relatime,size=506848k,nr_inodes=126712,mode=755 0 0 proc /proc proc rw,relatime 0 0 linuxrc.syno executed successfully. Post init ==================== start udevd ==================== ===== trigger device plug event ===== [ 31.001996] BTRFS: has skinny extents vm login: vm Password: