Polanskiman

I don't know if it's a kernel panic but I just tried increasing mtu to 9000 and now the NAS wont reboot. At least DSM doesn't seem to boot but I can still ping the NAS. I can't ssh it though as the connection is refused. Any way to solve this other than reinstalling? edit: strangely I can also VPN in it so that means that DSM is actually loaded. I can't ssh though. edit 2: I can't even reinstall as Synology Assistant or find.synology.com do not see the NAS on the network. edit 3: I am also able to access my plex server. Still no luck in accessing dsm itself or ssh.

Simple. Turn off your NAS. Then try a WOL see if it starts up If you don't know what it means then you probably don't have a use for it. Personally I did not have to fiddle with anything to have WOL working. I simply used the real MAC addresses of my 2 NICS and generated the serial with the famous excel serial generating file. WOL works as expected.

Although possible that is bad practice and there is a reason why the password for root access is different from the admin account. If you need root access simply sudo -i or sudo su - You can also set ssh keys to access your NAS which will give you root access but in a much more secure way.

Synology does not allow root access anymore directly in DSM 6. What you can do is: ssh with admin. Once in, issue the following command: sudo -i enter your admin password again. Done. You are now root.

The issue is not about reading the whole thread or asking question about linux commands. That is a problem you will find in any forum. You will always have those who need to be spoon fed constantly. The problem is that there has been several other loaders which have been posted by other members in the thread because Jun did not provided a BIOS compatible loader among other things. It's not a bad thing per say and he probably doesn't have much time as well but it does create confusion on what loader to use, trust etc. Giving the loader a name and version would also make things easier to track. Finally this forum is quite outdated and would need an overhaul but that is another issue.

vid=Vendor ID pid=Product ID You need your USB's vid and pid so you can edit the grub.cfg file. I provided a link in the short tutorial I did earlier on how to obtain those. A google search would have given you the answer much faster.

Can you explain how did you migrate your system? Now I am on DSM 5.2-5644 Update 5 and I want to Migrate my System to DSM 6.0.2-8451. I have install test version on another Server with DSM 6.0.2-8451 but still I am afraid to lose files on my DSM Regards Igor Please read the thread. It's all in here.

Answer has been provided before. This is only needed if your mobo is BIOS only. If Your mobo is UEFI then no need to replace the ramdisk.izma file. Simply use the loader from the OP.

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.

Possible. If you are on Mac it's pretty easy to convert it through the disk utility. On PC there are certainly other software. Google is your friend. Sent from my iPhone using Tapatalk

@nemesis122, @interested and all others who don't read. If you read all 33 pages and still are not sure maybe you should take a step back for the sake of your own data. I will nonetheless try to summarise it again as it has been done countless times in the thread already. This is also meant to those who keep asking the same questions over and over and who do not care to read. Hopefully this will clear up some uncertainties and confusion regarding loader for baremetal. 1 - UEFI scenario: If you have an UEFI board the loader is provided in the OP. Once you have burned the loader's image on a USB key all you need to do is edit the vid, pid, mac, serial, and add SataPortMap=[number of drives in your machine] in the grub.cfg file. I used Win32 Disk Imager to burn the bootable image into a USB key. I am sure that other software to create bootable usb key will work fine too. To edit the grub.cfg file you will either need to have a live CD (ubuntu or whatever linux flavour makes your day) or a MAC computer in order to access the content of the usb. I have a Mac so that's why I used. 2 - BIOS scenario: If you have a BIOS board then you need to use the hybrid loader that is provided on page 10 by setsunakawa. You then need to replace the ramdisk.lzma file with the one that is within the UEFI loader provided in the OP. The grub.cfg file also needs to be edited as mentioned above. If you read the OP till the end Jun recently mentioned that within the grub.cfg file you also need to replace the following: console=uart8250,io,0x3f8,115200n8 with console=ttyS0,115200n8. note 1: FYI once the image is burnt on the USB key there will be 2 partitions. One is empty and the other one contains the loader. This is normal and expected. note 2: Regarding VID and PID there are plenty of tutorials and software on the net on how to obtain those from your usb key be it on a Windows machine, linux or Mac. Here is one example Below is a grub.cfg example. serial --port=0x3F8 --speed=115200 terminal_input serial console terminal_output serial console set default='0' set timeout='2' set fallback='0' menuentry 'Synology DS3615xs' --class os { insmod fat linux /image/DS3615xs/zImage root=/dev/md0 syno_hdd_powerup_seq=0 netif_num=1 HddHotplug=0 SataPortMap=x syno_hw_version=DS3615xs vender_format_version=2 vid=xxxxx pid=xxxxxx console=ttyS0,115200n8 sn=xxxxxxxxxxxx mac1=xxxxxxxxxxxxxxx mac2=xxxxxxxxxxxxx withefi elevator=your_magic_elevator quiet initrd /image/DS3615xs/ramdisk.lzma } ^edit SataPortMap, vid, pid, sn, mac above to match your Xpenology. Once your usb is ready plug it on your Xpenology machine, boot it and then go on another computer that is connected on the same local network than your Xpenology and type find.synology.com in your web browser or simply open your Synology Assistant. Then follow the instructions. Install or migrate as suited. If your Xpenology is not found on your network it is possible that your network card drivers where not included in the loader because Jun only included a limited amount of drivers. This loader is new and as mentioned by Jun himself it needs to be considered unstable. I have been using it already for several days but that is not a warranty that it could crash my system anytime so beware of the risks involved.

Update 2 est aussi ok. Sent from my iPhone using Tapatalk

Working fine for several days on a baremetal gigabyte board H97N-Wifi. I just updated to 6.0.2-8451 Update 2 and all seems to be working fine. I am using the UEFI/Legacy image although it could work with the UEFI image as the board is a UEFI board.

Yes. On my two servers is the same record "reuse_1" in the DSFinder. Strange that so? Well before upgrading to DSM 6 it was written "Volume 1". So I just wonder why that changed and if it has any implications on the volume.

I noticed something strange after upgrading to DSM6. The volume / disk group name changed to reuse_1. See pic: This only shows in the DS Finder app, not through the web interface.

That's so true but the call for an upgrade is always so exciting [emoji12]

Thanks aleksey_z. It works like a charm.

Yes, the installation has a message "that the drives have come from another system" and the need to update the DSM. There is a choice: to migration or clean install. I chose to migration and it worked. I noticed you delete the first section of the grub.cfg file. serial --port=0x3F8 --speed=115200 terminal_input serial console terminal_output serial console Why so? Thanks

Thanks aleksey_z. That is good to know. I did all the changes required to the grub.cfg file. When you get to the synology assistant stage to update DSM were you told that your drives came from another machine and that you needed to install or did you have another screen?

Anyone?

Have a look at the "A new loader for latest dsm" thread.

Has anyone been able to update dsm 5 to dsm 6 with this loader while keeping all settings and apps. So far all my attempts end up requiring that I do an install/migration because supposedly my drives came from another 3615xs machine.

Would upgrading to dsm 6 with this new loader reset all user settings under dsm 5?

Nice to see some light at the end of the tunnel. Looking forward to see a fully functional release of a loader for DSM 6. How can I help?

Nope nothing you can do. Modules aren't loaded at boot. Wait for Xpenoboot to include them in a future release. Sent from my iPhone using Tapatalk