jun
-
Posts
64 -
Joined
-
Last visited
-
Days Won
32
Posts posted by jun
-
-
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.
-
Please, is there any way to make a loader that uses a version that supports SHR natively?
Maybe DS1815+ or something like that?
I am absolutely willing to test/work on to help, but I am no big linux-whiz I'm afraid...
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
-
Not to be the party pooper here but I think that providing modified loaders from Jun's OP only serves to confuse people and also derails the efforts made so far. I know some are invested into helping others by adding additional drivers and compatibility options but I think it just makes this thread heavier and heavier to follow. I would recommend perhaps those who have the ability to compile code to do it in cooperation with Jun and then post as one. This would have the advantage of greatly improving readability and also making sure there is only one source of the loader. Maybe making a new thread with a proper loader name and versioning system would help. One person would be in charge of updating the OP when required. @jun @setsunakawa @quicknick @sweebee
Please consider this.
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 too worried, maybe, but I presume an unclean shutdown will result in DSM starting a 'parity check' each time, which may take 2 days or so, putting a lot of extra stress on your array for the duration! (Even when it's just 'read', like maybe half the stress of a full rebuild?)
So, while I applaud the OP's brilliant (and most hopeful, so far) initiative, if at all possible, I'd like the 'unclean shutdown' thing resolved too, please.
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.
-
Hi,
I tried to install on bare-metal MSI N3150I ECO ITX board (celeron N3150), but installer always fails at 58% with error "Failed to install the file. The file is probably corrupted. (13)". On same setup i have installed latest 5.2 XPEnoboot without any problems. Any insights on this problem ?
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.
-
Hi,
I tried to install on bare-metal MSI N3150I ECO ITX board (celeron N3150), but installer always fails at 58% with error "Failed to install the file. The file is probably corrupted. (13)". On same setup i have installed latest 5.2 XPEnoboot without any problems. Any insights on this problem ?
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.
-
Trantor,
If you look at a directory diif with meld using the OEM rd.gz, xpenology rd.gz, and Jun's ramdisk.lzma, you can see some of the differences ande how he injected the code, but like you, still waiting on source to include in the kernel and hide the module. Very clever stuff Jun! I am pm'ing you with location to upload source.
I also agree that the source does not include all parts. That is why in very spare time I am working on complete patch from open source kernel and synologies open source kernel so that we can move to any version of kernel and make it easier to include the synology modded and missing stuff.
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.
-
1
-
-
This is very interesting
Unfortunately I'm very busy at work and have no time for XPEnology.
I'm glad that people continue to develop this project.
Don't forget that compiling kernel from Syno sources is very tricky.
Syno don't release all sources, some parts are missing like iscsi and synoacl.
Using original syno kernel + additional modules is very great but should prevent us to edit some part of the kernel.
You can use XPEnoboot 5.2 sources if you want to check how I did to add/update drivers and/or the HARDWARE SUPPORTED LIST to ckeck drivers names.
For exemple Broadcom tg3, bnx2 and bnx2x are higly patched in order to have successful compilation. Intel and realtek are very easy to update.
Keep in mind that including latest version of module/driver allow more hardware support that using sources from kernel tree.
Happy XPEnologing
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.
-
1
-
-
Hi jun,
you seem to know what you are doing so maybe you could help me to understand the protection mechanisms of the Synology DSM 6.
I have a DS710+ (2 bay Intel Atom D410) which does not get any further updates beyond DSM 5.x (5592). I was able to create a pat file to install DSM 6.0 (7321) by just changing the update file for the DS712+ (2 bay Intel Atom D425). I just changed the synoinfo.conf, scemd.conf and manutil.conf according to what I found in the latest DS710+ update and after repacking I was able to update my box to DSM 6.0 version 7321 (and also the subsequent updates to patchlevel 7).
With the same method I was able to create an update file for DSM 6.0.2 version 8451, however now I have the same problems as others reportet here that have accidentially updated to 6.0.1 (7393) or 6.0.2 (8451): existing volumes are gone and cannot be mounted and I cannot create new volumes. I did a little research but I have no clue how I could get around the protection. For example the devices nodes for sda are not created under /dev so scemd complains about not able to access /dev/sda. If I login via ssh and create them with mknod they exist for a while but as soon as I log into the Web UI or only reload it they are gone again.
Do you know if there is documentation about how the protection mechanism works or could you maybe give me some hints how I could make it work? Maybe even your kernel mode dynamic patcher could help me with this? I would appreciate it if you could give me some help.
Best regards,
HellG
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.
-
Pm sent. Compiling the kernel/drivers is the easy part. I have been slowly working a patchable kernel Tree so that we can move to any kernel version more easily and maintain xpenology and Synology modifications.
On a side note, Synology told me 6.0.2 sources will be released soon.
Sent from my SM-N930T using Tapatalk
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.-
1
-
-
- Popular Post
- Popular Post
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.
hereFor 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
Spoilerv1.02a (DS3615xs) is for DSM 6.1 - AMD not compatible - Deprecated
v1.02a (DS3617xs and DS916+) is for DSM 6.1 - AMD not compatible - Deprecated - ('time bomb' bug fixed in v1.02a2)
v1.02a2 (DS3617xs and DS916+) is for DSM 6.1 - AMD not compatible - DeprecatedDO 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:
On 7/6/2017 at 5:47 AM, jun said:please see arch/x86/kernel/cpu/amd.c, it contains all kinds of errata workaround and feature detections. synology kernel does not have it compiled in. will amd cpu work without it? i dont know for sure, seems some works, some does not, and some requires workaround.
---End of addition by polanskiman---
SpoilerI've recently annouce that my work on a kernel mode dynamic patcher in this post
Now seems everything work out of box on VMware, so it's pretty close to an everybody useable loader,
But lots of hardwares drivers are missing, to support as much hardware as possible requires some extra work,
So I hope these is some help from the community to built & test drivers, make it usable for everyone.
AMD users have a look 3rd Post.
I've upload a tar archive of the boot partion, it should be untar in to a usb drive's EFI System Partition.
I prefers EFI bootloader, so I used grub2-efi here, but you can install your prefered ones, even none-EFI ones.
the zImage is a vanilla synology kernel, ramdisk.lzma is repacked to add some network drivers plus my patcher.
you need change sn/mac/vid/pid as usual before installation.
and to make installer happy, usb drive seem should have at least 2 partitions, one for boot, and one for recovery I guess.
I suggest to test it on VM first, then add hardware drivers for boot on bare metals.
Below is how my usb drive looks like
$ sudo gdisk -l /dev/sdc
GPT fdisk (gdisk) version 0.8.8
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Disk /dev/sdc: 32784384 sectors, 15.6 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 4308A165-B0A6-4EC9-8B8E-9BEFB00BF33F
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 32784350
Partitions will be aligned on 2048-sector boundaries
Total free space is 4061 sectors (2.0 MiB)
Number Start (sector) End (sector) Size Code Name
1 2048 31457280 15.0 GiB 8300 Linux filesystem
2 31459328 31868927 200.0 MiB 8300 Linux filesystem
3 31868928 32784350 447.0 MiB EF00 EFI System
$ mount|grep tmp1
/dev/sdc3 on /mnt/tmp1 type vfat (rw)
$ ls -l /mnt/tmp1/
total 24
drwxr-xr-x 3 root root 8192 Sep 18 17:19 EFI
drwxr-xr-x 5 root root 8192 Sep 20 21:16 grub
drwxr-xr-x 3 root root 8192 Sep 20 21:15 image
$ lsusb |grep Flash
Bus 001 Device 010: ID 058f:6387 Alcor Micro Corp. Flash Drive
link
https://mega.nz/#!c8kn3JAL!fy4a0sXuYfcv1Sx7adGbr2OS-guqMS4GLRH3TOFkNfY
Edit:
I add a few popular network & disk drivers, and create a boot image for VM.
Just add some scsi or sata disk, then boot, and follow normal installation process.
https://mega.nz/#!llU23QgA!oGaZQuQLe0fsx1tuGiSBoZ19DSfEQH5Aq3GJXfEjpHE
for esxi, pls use this link
https://mega.nz/#!Agt00ZDT!lN5blyZc4gMaj-mKt-xCxoTtle-7cLF0ui9bF6ZBnY0
Plus a usb boot image for bare metal in UEFI mode. pls consider it unstable, test at your own risk.
https://mega.nz/#!Z4UzWZxZ!hu9SZXpzJBTakHk7lO8pJfyHYb-YgGatI-Em9E3JXWI
EditEdit:
Many people reported that DSM ask you to reinstall forever.
It turn out that lack of a serial port caused the failure. That is really a surprise
.
Anyway, I upload a new ramdisk to workaround the issue.
You should replace the image/DS3615xs/ramdisk.lzma in the boot partiton with this new one.
Edited post
The esxi and bare metal image are updated, so manually replace the ramdisk is not required.
Alternatively, VM users may add a serial port as a workaround.
Bare metal users can enable the serial port in bios if your board has one.
remaining problem:
Login to your DSM via ssh/telnet, your will see these messages in kernel log,
this is another consequence of lack of a serial console.
[ 1360.575754] init: tty main process (13856) terminated with status 1 [ 1360.575823] init: tty main process ended, respawning [ 1370.591635] init: tty main process (13881) terminated with status 1 [ 1370.591755] init: tty main process ended, respawning
To stop it from spam your log, you can stop/disable the tty serivce.
update:
above workaround is not enough for boards without serial port,
these unlucky guys should edit following serivce config manually, replace "console output" with "console none" after installation
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
Another issue:
I've found a hidden check related to console,
everyone should edit grub.cfg, replace console=uart8250,io,0x3f8,115200n8 with console=ttyS0,115200n8
You have to change sn/mac/vid/pid as usual before installation !
If you don't edit vid/pid in grub.conf you will get error 13 (file corruption) during setup.
How to see the value of my VID & PID stick
EDIT by Trantor (10-28-2016):
Updated loader by Arcao latest images (10-28-2016) : https://mega.nz/#F!Oc8TCLgD!IiullNuGs95RlelM9SKd5w
Original post : https://xpenology.com/forum/topic/6253-dsm-602-loader-was-a-new-loader-for-latest-dsm/?do=findComment&comment=55903
Sources for dev:
quicknick : https://github.com/quiknick/7274-kernel
setsunakawa : http://setsunakawa.ddns.net/synology/dsm6/
10/29:
It's time to release a loader with a proper version number now.
Here is my loader v1.0
https://mega.nz/#F!18kB1BTB!1ft3N5Hnrcnqsneu0aQUkA
New features & fix:
Support bios & uefi boot & VMware & ESXI
Fix cmos reset issue( at least on bios mode VMware workstation)
most configurations can be done via grub command line now.
Remember last boot entry.
Autodetect synoboot partitions, not extensively tested. It is still recommended to set correct vid/pid.
AMD CPU support, not extensively tested, there are a few positive report on the forum.
Add grub menu for reinstallation.
Add grub menu to force installation when interrupted due to "Disks Disabled" message, not extensively tested
Automatically apply workaround for boards without serial port.
Fix SATA disk order remap, and allow to set SAS disk starting no, but disk order are still not deterministic between SAS disks.
Fix SAS disk naming, not extensively tested, only with one SAS2008 based HBA and synology provided mpt2sas driver.
Add ata_piix support, tested on VMware and it does not crash, only complain about "Read current link speed fail", so I
assume it works
, this driver requires a bit of patching to the kernel, so I include it in the package.
Integrate up-to-date network drivers compiled by Arcao and Trantor.
Known issue:
When runing on a slow single core machine, there is a race condition causes the patcher loading too late.
the most obvious sign is console not working properly. I don't expected this to happen normally,
the only example is a VM on my laptop when running on battery. If anyone believes have this issue,
please send me a message.
Some ethernet drivers crash when set MTU above about 4096(Jumbo frame), I've not identified the culprit yet.
How to install:
find the vid/pid of your usb drive
Burn the image to the drive, optionally edit grub.cfg to set vid/pid and boot entry, OR
connect monitor/keyboard/serial console to your Box.
Press C during Grub boot menu to enter command line
vid 0xXXXX pid 0xYYYY
to configure pid and vid ("pid" and "vid" are command, and "XXXX", "YYYY" are you usb drive's vid,pid)
(There are a few other options can be config this way, you can read grub.cfg to know more detail.)
Press Esc to go back to boot menu
Select baremeta/baremetal AMD entry, press enter to boot.
If your encounter the "disk port disabled" error during installation, try the force install menu entry.
if both option does not work, you have to fallback to SataPortMap method,
type this line in grub command line, replace XX with appropriate value.
append SataPortMap=XX
11/2:
as I promised, here is v1.01, download link is the same as v1.0
This update contains nothing fancy, mainly for inner peace,
Plus, I revert megaraid_sas mpt3sas to old version.
It's not shining new now, the title is obsolete
-
19
-
4
-
@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:
DSM 6.1.x Loader
in Loaders
Posted
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.