MarsManden

You're welcome. When installing apps, they usually installs on the first volume you create on your harddrives. Therefore some people create a small volume (a few GBytes) as the very first volume to store only apps. Whether you create this volume on only 1 harddrive or create a RAID1/RAID5 over all your drives is a matter of choice. Most apps with more data has the capability to change the path/share to where it will store these data, so it is able to separate programfiles from actual data. Then create a volume 2 and maybe more to hold any other data-shares you may want. My systems are setup with a small volume 1 to hold apps and a volume 2 using the rest of the space on my disks, in native RAID5. Enjoy your weekend too.

I'm not sure if you understand this correct - or maybe I don't understand your question. The USB stick emulates the boot-prom in a real Synology device. A real synology device is useless without any harddrives - and so is XPEnology. Without any harddrives - no XPEnology. When installing the pat-file from Synology, it is installed on all harddrives in the system, to make the system more robust. There is nothing you can do about this.

I took a slightly different approach. 1. Removed USB stick with 5.1 image - server still running! 2. Wrote new 5.2 image to USB stick 3. Put the USB stick back in the server - server still running 4. Updated manually in DSM with downloaded pat file 5. Server rebooted - the USB stick with the new image did it's job patching files 6. Updated to update 2 through DSM And voila - running 5.2-5565.2 without problems. Did this procedure on 3 different N54L servers.

I have yet to experience any problems on my 2 N54L servers with 5.2-5565.2 - bare metal.

Did you check the shares? And the permissions on the shares? Is Windows file service enabled?

Ip-banning?

I'm using USB sticks with only 64MB or 128MB. That's more than enough, as the bootimage is only 16MB.

I've upgraded two N54L without problems. Both from 5.1U5. Replaced the USB stick with one containing the 5.2.2 bootimage and then upgraded through the DSM GUI. Both uses DHCP. No network problems.

Have you tried another USB stick? Have you tried disconnecting keyboard and/or mouse - if connected? Do you have any other add-ons in your N40L? Networkcard, graphic card, SATA controllers and so on? Do you have any other devices connected to any USB port?

You just make the USB stick the same way as you did the first time. Download the image and use WinDiskImager or whatever tool you like, to transfer it to the USB.

My 2 cents are on the flash drive. Try to remove it (you can do that without any risk, as it is only used when booting), run the command again and check if it is gone. Reinsert and it should be back when you run the command yet again.

Well spoken, icanic. I couldn't agree more.

@ nikolas22t: Just replace your vmdk boot-image with the new one.

Yes, that's normal - nothing to worry about.

Read this thread regarding Xpenoboot. viewtopic.php?f=14&t=5026

Does it unmount the volumes after every reboot? I had same problem after applying one of the updates, but a reboot of the system solved it.

I guess you're missing this thread. viewtopic.php?f=2&t=5026 And then have a look at xpenology.nl for tutorials.

An 8GB drive should do it.

Have you tried selecting Install/Upgrade in the Xpenology boot-menu?

Yes, if you want to upgrade to 5.1, you need a bootloader that is able to handle the DSM version you want to use.

I've updated my 3 N54L's this way without problems. Though I'm using a newer BIOS, O41100113.ROM.

Doesn't work. You need an internal harddrive of at least 8GByte to install DSM.

I have 2 N54L running bare metal and 2 more running under VMware v5.5, also on a N54L. I can't say which guide I followed because I've done it so many times, that I know what to do. But I know there are some fine tutorials on this site. http://www.xpenology.nl/

I'm running DSM 5.1.5022 update 3 on my systems. It is as stable as all the other versions I've had on it. The main difference for me is that with the latest XPEnoboot_DS3615xs_5.1-5022.3, powermanagement on the CPU is working. Which means that instead of always running at 2.2GHz it is now running at 800MHz when no work is to be done - saves power and less heat is produced.

You're at the right spot - the vendor file was used in the old days. Change the serial in the syslinux.cfg file and you're set - it's that easy.