billat29

Thanks for the update, quicknick. So, everyone, it is clear. Obviously Real Life has caught up with quicknick and while he has the desire to finish it, he just can't find the time at the moment. When he does find the time, he will deliver it. His estimate is a "few weeks" but it's all going to depend on what else he has to do. There's no point in trying to get a better estimate. It will be done when it is done. So in the meantime we can: 1) Stop asking and either 1) Stay on 5.2 2) Use jun's loader 3) Buy a real Synology I expect that when it is ready for release, Quicknick will update the title of the thread and we will all know.

Oh dear! You are at the start of a steep learning curve. So.When you use SSH, you are opening a remote console onto the linux system that underlies DSM. vi and nano are standard linux editors which run on that box and you can use either of them to change one of the files that DSM uses. It's a matter of personal preference which one you choose. If your favourite is not already installed, you can always install your editor of choice. You can also look at WinSCP - a program to install on your windows machine which will allow you to connect to DSM and browse to the files you want to edit. You can right click on the files and then use Notepad++ as your editor. WinSCP will download the file to your Windows machine, allow you to edit, and when you save, put it back on the Xpenology box. Apart from the instructions which say this is the file to edit and these are the changes to make, this is all standard linux stuff, so you should be able to find help on how to do it in that community

Try the first link on the first page of the thread. - xpenology.xyz

The link to the PAT file points to Synology's own servers. So they still work It looks like the files that were hosted there (IMG, ISO etc) aren't currently accessible there. I also looked on xpenology.fr and xpenology.us and they are all down. However, if you goto the first page of the announcement XPEnoboot 5.2-5967.1 you might have more luck.

If you have enough real disk storage, you can copy the vmdk files to back them up before you start attempting recovery. One thought: You can create a new virtual machine with its own virtual disk and install ubuntu. then attach your existing vmdks and follow the instructions on this forum and synology's on how to use ubuntu to recover your data...

1)I have run jun's loader in VMware workstation player for testing. You don't have the flexibility in attaching hardware that ESXi does. But you can attach disks to the virtual machine 2) You don't need vsphere with ESXi 5.5 as you can use the client from earlier releases. That does restrict what you can do. I did try ESXi6 and found a client, but I couldn't say whether I was running vsphere in a time limited evaluation mode or not.

Soon, soon. I am sure that quicknick won't know when it will be ready until it is ready and then the first post will be updated. Patience.

Why not take the HDD out of the enclosure and connect it as a SATA drive?

I am confused about the last part where you say Test with 1 hdd 80 go Test with 4 hdd 500 go Does this mean you always get the same message with the same error sectors if you put different drives in your box? And does it say hd0 or md0. If it says md0, then you need to create the bootloader on another USB stick as yours is not working properly.

Scal, Please tell us what you are doing. Are you installing on a new system or upgrading an existing system? What actions did you perform? At what step do you get the messages? Thanks Bill

I am sure that anyone close to the development would say that it's still not ready for production but we both know that people are using it successfully. I would only consider it if I had a complete backup of all my data and settings and I was prepared to spend all the time rebuilding the whole thing again if it went all wrong. I'm not migrating yet as USB on N54L doesn't seem to work.

I successfully created a DSM6 key and booted my N54L and it is found on the network. So, I guess that there is a problem with the creation of your key. I followed this: ==> viewtopic.php?f=2&t=22100&p=76338#p76338 but the changes I made to grub.cfg were to: set my VID and PID; set sn and mac; Sataportmap to 4 and I got frustrated with trying to set the default boot menu item and just deleted all the ones I didn't want leaving the AMD option.

Hang on. So you originally booted from the DSM 6 key, it was found on the network and you updated it to DSM6 via the web interface. Now after the install, you can no longer find it on the network? Is it still booting with the AMD option?+ And yes, you should be able to mount the disks under linux and recover. TI have seen a post somewhere and sometime on how to use mdadm to do so, but I can't remember where....... sorry

That's good news. You need a version of the bootloader that matches the version of DSM you are trying to install. If you have the last x86 loader, then the matching DSM version is the latest you can install safely. You need nanoboot usb inserted whenever you boot DSM. It takes the place of the ROM bootloader in a real Synology but it allows you to load DSM on non-Synology hardware.

Hi, I'm not sure why you are doing step 5, but that shouldn't affect things. I have tried to replicate your method but got lost in VMware hell. All I can say is that error 13 is a problem writing the installation to the disk - not big enough, wrong disk type, wrong controller, can't find it, wrong or bad .pat file but I'm sorry that I can't provide a solution. Maybe someone with a greater knowledge can help.....

Sorry mate. I'm really confused about what you say about connecting to port 22 and trying to upload the DSM file. Are you trying to use WinSCP to physically upload the file or are you following the installation wizard that appears in the browser when you connect it to the nanoboot machine?

Ah! I hadn't seen that thread before and now I see what you are doing. I am confused about the steps you have taken and why you are using port 22 at this point. It should be: 1) Boot nanoboot in the VM 2) from your PC run synology assistant to find the DSM instance. 3) Right click on the instance and select connect to open a browser and start the installation process.

Error 13 seems to be "I had some problem writing the installation to disk". 10Gb was probably not big enough. I did try to run up an old VM which was using Nanoboot but it failed and I have changed so much on my PC and network since then that it would probably take an age to debug. However, I did notice that the .pat file I was using was for the DS3612xs and that might be your error 13 problem there. As for x86 support, I think nanoboot was the last, but can't really remember. I would have to hunt through the forum for the 5.0 release - but then you could do that

You need more than 10Gb disk space. Otherwise you get the error 13 message. 20Gb is a safe minimum.

This ? https://www.synology.com/en-uk/knowledg ... motevolume

I'm with Polanskiman on this. I think what you guys are doing is fantastic but please, can we get this under control. I am sure that a small number of you are more than capable of building your own custom loader and getting it to work, but I worry that the vast majority of users have little idea of what is going on (many have just managed to stumble through the tutorials that used to live on fan sites) and it's all going to go horribly wrong for them. Can we mark this thread as "Development Only" or something like that and ask one of you guys to start another thread as he suggests. Please?

The unknown is whether there are likely to be any issues in the jump from 5.0 to 5.2. I suspect most people will have upgraded in smaller steps as new versions became available. If you can test the upgrade using a spare HDD or a VM on your PC, that would give more confidence. Always back up your data first and also backup your configuration from control panel. Be prepared for loss of folder permissions and you might need to reinstall the odd package. Sometimes a hard boot after an upgrade is required. The latest bootloader is always referenced on the first page of this thread: viewtopic.php?f=2&t=5026 and if you follow the first link, you will get to the correct bootloader and the corresponding .pat file which you can download to your PC. There are a couple of fan sites around that have tutorials - although sometimes not always updated regularly. Off the top of my head there are https://xpenology.us/tutorials (seems to be down at the moment) and http://xpenology.me/category/how-to/ but essentially your method is OK. After rebooting, you need to connect to the box (synology assistant or find.synology.com) and it should show as migratable. You can then click the manual install and point to the .pat file you downloaded earlier. Good luck and did I say "back up your data" yet?

5967 is the latest. However, in fixing the BIOS reset problem, the devs stopped power schedules from working. I'm on 5644 which seems to work (although I'm not sure whether the fan runs in quiet mode any more) but if your box is not connected to the internet, I would be tempted to leave it as it is. However if it is accessible from the internet, I would probably move to a later release to get the security fixes.

It might be time to run a file check on the volume. There are some instructions towards the bottom of this post https://tunwinnaing.wordpress.com/2015/ ... le-system/ Disclaimer: I haven't tried it and don't know what effect it might have. However, it's only the second run of e2fsck that actually changes the filesystem. You can run the commands from WinSCP if you like Commands>Open Terminal or download something like putty.

If you enable SSH in control panel>terminal &SNMP and then download WinSCP to your PC, you can log into the system using user:root pwd:. navigate to volume1 and look for the @download folder