XereX

It would be interesting to see if it had anything to do with the NIC. If possible, try disabling the NIC in the BIOS and see what happends during boot. If you have another NIC around, try that and see if you make any progress!

Have you tried with any of the earlier versions ? Try the 4.3 beta7 build by Trantor. It contains a lot of drivers. Maybe its because of a missing driver or something..

Hi all. Was wondering if its possible to get push notifications to work at all..? From what I can see in the log files, the DSM cannot communicate with Synology's push service. (maybe because the serial number of my Xpenology can't be verified.) But I just want to be sure to hear if anyone had got this working. This is my logfile: Mar 16 22:08:02 Synology entry.cgi_SYNO.Core.Notification.Push.Conf[1].set[685]: pushservice_update_ds_token.c:53 synocloudserviceauth failed(1): failed to get a api key Mar 16 22:08:02 Synology entry.cgi_SYNO.Core.Notification.Push.Conf[1].set[685]: pushservice_update_ds_token.c:172 Can't set api key Mar 16 22:08:02 Synology entry.cgi_SYNO.Core.Notification.Push.Conf[1].set[685]: pushservice_utils.c:315 SYNOPushserviceUpdateDsToken failed. Mar 16 22:08:02 Synology entry.cgi_SYNO.Core.Notification.Push.Conf[1].set[685]: pushservice_utils.c:374 GenerateDsToken Failed Mar 16 22:08:02 Synology entry.cgi_SYNO.Core.Notification.Push.Conf[1].set[685]: Failed to get ds token.

I upgraded from DSM 5.0 beta build 4418 (upgrade 1) "Trantor's build" with NO problems. I have a HP N54L (native installation) Did not loose rights on folders/files either.. Just follow the guide as described. One thing you do need which is not mentioned anywhere is a monitor (VGA or something) AND a keyboard. Then you are ALL good to go.... Happy upgrading!

This is just my best guess: The official package from Synology needs to be modified to be able to run on unofficial hardware. Also, you need something to emulate the boot loader (like a USB Stick) where the original hardware has this on a chip (i think).. Hopefully, someone with a lot more experience will be able to make a working DSM 5.0 soon. (It was released two days ago) In the meantime, you could give DSM 5.0 beta a try as this is the latest working release.

Is anybody working on the official release? Tried to update from within DSM ( DSM 5.0 update 1) I am getting the following info from the logfile: Mar 12 08:06:32 Nas entry.cgi_SYNO.Core.Upgrade[1].start[30298]: Upgrade.cpp:221 Verify checksum of [//upd@te]... Mar 12 08:06:33 Nas entry.cgi_SYNO.Core.Upgrade[1].start[30298]: Upgrade.cpp:226 Pass checksum of //upd@te... Mar 12 08:06:34 Nas entry.cgi_SYNO.Core.Upgrade[1].start[30298]: Upgrade.cpp:302 Executing [//upd@te/updater -v / -x > /dev/null 2>&1] Mar 12 08:06:34 Nas updater: updater.c:4890 Start of the updater... Mar 12 08:06:34 Nas updater: updater.c:4994 This is X86 platform Mar 12 08:06:34 Nas updater: boot/boot_lock.c(225): failed to mount boot device /dev/synoboot2 /tmp/bootmnt (errno:6) Mar 12 08:06:34 Nas updater: updater.c:4833 Failed to mount boot partition Mar 12 08:06:34 Nas updater: updater.c:5490 Failed to accomplish the update! (errno = 2) Mar 12 08:06:34 Nas entry.cgi_SYNO.Core.Upgrade[1].start[30298]: Upgrade.cpp:305 failed to system cmd=[//upd@te/updater -v / -x > /dev/null 2>&1], r=512 Mar 12 08:06:34 Nas entry.cgi_SYNO.Core.Upgrade[1].start[30298]: Upgrade.cpp:474 Failed to unpack firmware. Mar 12 08:06:34 Nas cupsd[31034]: [conf.c:1893] Filter "pstoraster" not found. Mar 12 08:06:36 Nas synorelayd[31189]: synorelayd.cpp:1234 stoped Mar 12 08:06:41 Nas kernel: [33156.841693] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory Mar 12 08:06:41 Nas statd[31471]: Running as root. chown /var/lib/nfs to choose different user Is it possible to update from DSM at all ?