MarsManden

Got the exact same problem - But I've got no answer on how to fix it or what is wrong. I've got an installation on a N54L native (no ESXi) upgraded from 4.3 (L2TP working) and an installation on ESXi installed from scratch - both fails with the same errors as yours. PPTP also works fine on my installations.

http://cyanlabs.co.uk/tutorials/xpenolo ... ial-number or http://thedarkcloud.net/configuring-gno ... -addresss/ Or you could read this thread: viewtopic.php?f=2&t=1353

Then I have to show a link to this guide, as it has done the trick for me. http://thedarkcloud.net/configuring-gno ... -addresss/

No, this is not possible. DSM is installed on ALL drives in the server, thus taking a little space on each disk. DSM is mirroring itself to all disks - nothing you can do about it.

I have had DSM 4.3 3810/Trantor running on my N54L server since mid oktober 2013 - rock solid! Last weekend I did an upgrade from 4.3 build 3810 Update 4, Trantor to 5.0 4458 Gnoboot 10.5 on my HP N54L native (no VMware). Did a no-no - selected upgrade instead of doing a clean configuration. Well, most of it went fine - no dataloss at all! But a lot of settings did not make it through the upgrade, so I had to check all settings again anyway. Missing admin rights on shares. Missing http user-group - my web-server did not respond. Packages were there - but all needed upgrade/reinstall. PhotoStation had to be reinstalled. System hang on reboot because of bad packages - had to kill some tasks to get the system up and running and to uninstall VPN and PhotoStation. Thanks to all the posts here on XPEnology forum, I've got my system up and running again. What a great forum this is. Next time I will follow the guidelines - and do a FRESH configuration install. Document your settings and set everything up again from the bottom. I have DSM 5.0 4458/Gnoboot 10.5 running on my N54lL native and have another instance running on ESXi for test. I followed this guide for using a unique serial and mac-address: http://thedarkcloud.net/configuring-gno ... -addresss/ Check out the rest of the guide on http://thedarkcloud.net - a lot of stuff to learn! Also check out the great guides on http://cyanlabs.co.uk/. Check out both sites and combine them - that's what I did. And BIG BIG thanks to Trantor and Gnoboot for making this possible at all! You guys rocks!!

@Burner1977 - thanks! Think I'm going to give it a try - the upgrade from 4.3 to 5.0.

I've read number of times that the admin rights disappear when doing the upgrade - but from where do you reassign the admin rights? The command line or from the GUI somewhere. Please enlighten me.

why do you say it's not supported? does Xpenology not able to detect the drives? does other hard drive work? @ALAMAPSTIEKS - 4TB WD Red is supported. My system (see my sig) is running on 5 of them - and has been for the last 4 month.

I also have absolutely no problems with WD Red 4TB. My system (see my sig) is running on 5 of these disks - and have been for the last 4 month. No problems at all. I don't use SHR - I use native Raid5.

Yep, that's pretty much it. See this: viewtopic.php?f=2&t=2049&start=80#p12991

That is 100 read OR 100 write - not simultaneously - and I've reached this speed using only the 250GB disk, that came with the N54L. So I think HDMann has a good point - it is the entire chain that has to be able to deliver.

That is 100 read OR 100 write - not simultaneously - and I've reached this speed using only the 250GB disk, that came with the N54L. So I think HDMann has a good point - it is the entire chain that has to be able to deliver.

I can't see anywhere if you're running Xpenology native on the N54L or running under ESXi. I'm experiencing 100+ MByte/sec on my N54L from Windows 8.1, native install, on WD Red disks. See my sig.

What software do you use for the transfer? Direct transfer between the two units or by another computer? The N54L is not the problem - I have transfer speeds around 100MByte/sec to and from my N54L, from a Windows computer.

Also running 4.3 on my N54L - 100% stable. If you want to be on the bleeding edge, then go for 5.0 beta.

Sounds good, send me a pm with address and I will pop it up on my host for a while Or let me know - I have plenty of room/bandwith to host the file.

Nope. When installing DSM it sometimes tries to initialize the USB stick as well as the HDDs. The solution is to reformat the stick and put the image back on. Remember to change the vender file if you want another MAC address.

Found a changelog under one of the other models. http://www.synology.com/en-global/relea ... odel/DS414

Just upgraded to Update 4 - no problems so far.

Disable scheduled power-off and WOL. I have no problems with the BIOS - but I don't use WOL or scheduled power-off.

I've seen a post that it should be possible to restore the configuration from a backup taken under DSM 4.2 to DSM 4.3. As for the packages, I would suspect that you have to reinstall them manually. Maybe if you install your packages BEFORE restoring configuration, the package configuration will be restored as well.

You can't upgrade, but you can install 4.3 without loosing data, which is what I did. All settings in DSM and all additional packages and their settings are removed in the process. The "upgrade" is like installing DSM from the beginning. Backup your data and DSM settings. Put the img-file from 4.3 on the USB stick and boot the N54L. From Synology Assistant install the 4.3 pat-file - you should not get any messages regarding creating new filesystems. When 4.3 is installed, you should see your volumes and shares. Reapply your settings and packages and you should be done.

Ahh, thanks. I don't mess around with WOL or any other automatic start/stop, as my server runs 24/7. That's why I haven't seen any BIOS corruptions I guess.

Thanks - for the link to the new BIOS!

fonix232 - please explain - or link. I haven't heard about the "pinkeye problem"? And I'm curious if there is a newer BIOS to my little baby - what have been changed. HP only states that a hang issue in Win2012R2 has been solved. At the moment I'm using TheBay 041, which is working as expected.