forcefullpower Posted July 1, 2015 Share #1 Posted July 1, 2015 Hi, Anyone tried updating to Version : 5.2-5592. Can the boot image work with this or will we have to wait for an update. Quote Link to comment Share on other sites More sharing options...
thag Posted July 1, 2015 Share #2 Posted July 1, 2015 I get erros when updating, the update fails. luckely everything keeps working Quote Link to comment Share on other sites More sharing options...
koroziv Posted July 1, 2015 Share #3 Posted July 1, 2015 Brave man to test on your working install I was thinking to make another vm with xpenology just for testing stuff, but that is not going to be so soon, not much time these days. Quote Link to comment Share on other sites More sharing options...
bigjohnx Posted July 1, 2015 Share #4 Posted July 1, 2015 Only get the expected result on 5.2.5592.1 No luck to access the DSM login page with 5.2.5592.2 / .3 / .4 Quote Link to comment Share on other sites More sharing options...
Thecapri Posted July 1, 2015 Share #5 Posted July 1, 2015 (edited) the update juste got out today, some of you are very impatient to get in trouble Edited July 2, 2015 by Guest Quote Link to comment Share on other sites More sharing options...
brantje Posted July 1, 2015 Share #6 Posted July 1, 2015 Testing in a virtualbox VM now.. will report back in a few clicks. Quote Link to comment Share on other sites More sharing options...
segarra Posted July 1, 2015 Share #7 Posted July 1, 2015 Testing in a virtualbox VM now.. will report back in a few clicks. We wait your answer.... Quote Link to comment Share on other sites More sharing options...
dodo-dk Posted July 1, 2015 Share #8 Posted July 1, 2015 Online Update and Manual Update not possible. Unknown Error 21 comes on 65%. No Problems after that try. /var/log/messages: Jul 1 22:22:55 XPE_5-2 entry.cgi_SYNO.Core.Upgrade[1].start[15759]: Upgrade.cpp:297 Executing [//upd@te/updater -v -x ] Jul 1 22:22:55 XPE_5-2 updater: updater.c:5483 Start of the updater... Jul 1 22:22:55 XPE_5-2 updater: updater.c:2822 orgBuildNumber = 5565, newBuildNumber=5592 Jul 1 22:22:55 XPE_5-2 updater: updater.c:5615 ==== Start flash update ==== Jul 1 22:22:55 XPE_5-2 updater: updater.c:5619 This is X86 platform Jul 1 22:22:55 XPE_5-2 updater: updater.c:5633 The SynoBoot partitions exist. Jul 1 22:22:55 XPE_5-2 updater: updater.c:3594 SYNORedBootUpdCheckAndApply(3594): Skip bootloader update, no uboot_do_upd.sh exists Jul 1 22:22:55 XPE_5-2 updater: updater.c:551 checksum generated by [/bin/grep -i zImage checksum.syno >> /tmp/checksum.syno.tmp] Jul 1 22:22:55 XPE_5-2 updater: updater.c:570 file [zImage] is being copied to [/tmp/bootmnt] Jul 1 22:22:55 XPE_5-2 updater: updater.c:578 file [/tmp/bootmnt/zImage] process done. Jul 1 22:22:55 XPE_5-2 updater: updater.c:551 checksum generated by [/bin/grep -i rd.gz checksum.syno >> /tmp/checksum.syno.tmp] Jul 1 22:22:55 XPE_5-2 updater: updater.c:570 file [rd.gz] is being copied to [/tmp/bootmnt] Jul 1 22:22:55 XPE_5-2 updater: updater.c:578 file [/tmp/bootmnt/rd.gz] process done. Jul 1 22:22:55 XPE_5-2 updater: updater.c:551 checksum generated by [/bin/grep -i grub_cksum.syno checksum.syno >> /tmp/checksum.syno.tmp] Jul 1 22:22:55 XPE_5-2 updater: updater.c:570 file [grub_cksum.syno] is being copied to [/tmp/bootmnt] Jul 1 22:22:55 XPE_5-2 updater: updater.c:578 file [/tmp/bootmnt/grub_cksum.syno] process done. Jul 1 22:22:55 XPE_5-2 updater: updater.c:565 file [/tmp/bootmnt/hda1.tgz] is being removed Jul 1 22:22:55 XPE_5-2 updater: updater.c:578 file [/tmp/bootmnt/hda1.tgz] process done. Jul 1 22:22:55 XPE_5-2 updater: updater.c:565 file [/tmp/bootmnt/updater] is being removed Jul 1 22:22:55 XPE_5-2 updater: updater.c:578 file [/tmp/bootmnt/updater] process done. Jul 1 22:22:55 XPE_5-2 updater: updater.c:565 file [/tmp/bootmnt/VERSION] is being removed Jul 1 22:22:55 XPE_5-2 updater: updater.c:578 file [/tmp/bootmnt/VERSION] process done. Jul 1 22:22:55 XPE_5-2 updater: updater.c:588 checksum file updated by [/bin/cp -f /tmp/checksum.syno.tmp /tmp/bootmnt/checksum.syno] Jul 1 22:23:02 XPE_5-2 updater: boot/boot_lock.c(225): failed to mount boot device /dev/synoboot1 /tmp/bootmnt (errno:2) Jul 1 22:23:02 XPE_5-2 updater: updater.c:1319 Failed to mount factory partition Jul 1 22:23:02 XPE_5-2 updater: boot/boot_lock.c(225): failed to mount boot device /dev/synoboot1 /tmp/bootmnt (errno:2) Jul 1 22:23:02 XPE_5-2 updater: updater.c:1319 Failed to mount factory partition Jul 1 22:23:02 XPE_5-2 updater: boot/boot_lock.c(225): failed to mount boot device /dev/synoboot1 /tmp/bootmnt (errno:2) Jul 1 22:23:02 XPE_5-2 updater: updater.c:1319 Failed to mount factory partition Jul 1 22:23:02 XPE_5-2 updater: boot/boot_lock.c(225): failed to mount boot device /dev/synoboot1 /tmp/bootmnt (errno:2) Jul 1 22:23:02 XPE_5-2 updater: updater.c:1319 Failed to mount factory partition Jul 1 22:23:02 XPE_5-2 updater: boot/boot_lock.c(225): failed to mount boot device /dev/synoboot1 /tmp/bootmnt (errno:2) Jul 1 22:23:02 XPE_5-2 updater: updater.c:1319 Failed to mount factory partition Jul 1 22:23:02 XPE_5-2 updater: updater.c:5851 fail to upgrade factory partition Jul 1 22:23:02 XPE_5-2 updater: updater.c:676 Restoring [zImage] Jul 1 22:23:02 XPE_5-2 updater: updater.c:687 Copying file [//synob@ckup/zImage] as [/tmp/bootmnt/zImage], result[0] Jul 1 22:23:02 XPE_5-2 updater: updater.c:676 Restoring [rd.gz] Jul 1 22:23:02 XPE_5-2 updater: updater.c:687 Copying file [//synob@ckup/rd.gz] as [/tmp/bootmnt/rd.gz], result[0] Jul 1 22:23:02 XPE_5-2 updater: updater.c:673 Skip restoring [vendor] Jul 1 22:23:02 XPE_5-2 updater: updater.c:676 Restoring [grub_cksum.syno] Jul 1 22:23:02 XPE_5-2 updater: updater.c:687 Copying file [//synob@ckup/grub_cksum.syno] as [/tmp/bootmnt/grub_cksum.syno], result[0] Jul 1 22:23:02 XPE_5-2 updater: updater.c:676 Restoring [hda1.tgz] Jul 1 22:23:02 XPE_5-2 updater: updater.c:690 Removing file [/tmp/bootmnt/hda1.tgz], result[-1] Jul 1 22:23:02 XPE_5-2 updater: updater.c:694 Restore [hda1.tgz] fail, remove it from synoboot Jul 1 22:23:02 XPE_5-2 updater: updater.c:676 Restoring [updater] Jul 1 22:23:02 XPE_5-2 updater: updater.c:690 Removing file [/tmp/bootmnt/updater], result[-1] Jul 1 22:23:02 XPE_5-2 updater: updater.c:694 Restore [updater] fail, remove it from synoboot Jul 1 22:23:02 XPE_5-2 updater: updater.c:676 Restoring [VERSION] Jul 1 22:23:02 XPE_5-2 updater: updater.c:690 Removing file [/tmp/bootmnt/VERSION], result[-1] Jul 1 22:23:02 XPE_5-2 updater: updater.c:694 Restore [VERSION] fail, remove it from synoboot Jul 1 22:23:02 XPE_5-2 updater: updater.c:676 Restoring [checksum.syno] Jul 1 22:23:02 XPE_5-2 updater: updater.c:687 Copying file [//synob@ckup/checksum.syno] as [/tmp/bootmnt/checksum.syno], result[0] Jul 1 22:23:02 XPE_5-2 updater: updater.c:6183 fail to rollback flash (restore) Jul 1 22:23:02 XPE_5-2 updater: updater.c:6219 Failed to accomplish the update! (errno = 21) Jul 1 22:23:02 XPE_5-2 entry.cgi_SYNO.Core.Upgrade[1].start[15759]: Upgrade.cpp:300 failed to execute updater, r=-2498164 Jul 1 22:23:02 XPE_5-2 synoservicecfg: servicecfg_root_object_get.c:115 service config for service [] is not exist Jul 1 22:23:17 XPE_5-2 entry.cgi_SYNO.Core.Upgrade[1].start[15759]: update_cpputil.cpp:806 synoservice: start all packages ... Jul 1 22:23:21 XPE_5-2 entry.cgi_SYNO.Core.Upgrade[1].start[15759]: update_cpputil.cpp:859 synoservice: finish started all packages Jul 1 22:23:21 XPE_5-2 entry.cgi_SYNO.Core.Upgrade[1].start[15759]: Upgrade.cpp:530 Failed to unpack firmware. Quote Link to comment Share on other sites More sharing options...
brantje Posted July 1, 2015 Share #9 Posted July 1, 2015 Online Update and Manual Update not possible.Unknown Error 21 comes on 65%. No Problems after that try. /var/log/messages: Jul 1 22:22:55 XPE_5-2 entry.cgi_SYNO.Core.Upgrade[1].start[15759]: Upgrade.cpp:297 Executing [//upd@te/updater -v -x ] Jul 1 22:22:55 XPE_5-2 updater: updater.c:5483 Start of the updater... Jul 1 22:22:55 XPE_5-2 updater: updater.c:2822 orgBuildNumber = 5565, newBuildNumber=5592 Jul 1 22:22:55 XPE_5-2 updater: updater.c:5615 ==== Start flash update ==== Jul 1 22:22:55 XPE_5-2 updater: updater.c:5619 This is X86 platform Jul 1 22:22:55 XPE_5-2 updater: updater.c:5633 The SynoBoot partitions exist. Jul 1 22:22:55 XPE_5-2 updater: updater.c:3594 SYNORedBootUpdCheckAndApply(3594): Skip bootloader update, no uboot_do_upd.sh exists Jul 1 22:22:55 XPE_5-2 updater: updater.c:551 checksum generated by [/bin/grep -i zImage checksum.syno >> /tmp/checksum.syno.tmp] Jul 1 22:22:55 XPE_5-2 updater: updater.c:570 file [zImage] is being copied to [/tmp/bootmnt] Jul 1 22:22:55 XPE_5-2 updater: updater.c:578 file [/tmp/bootmnt/zImage] process done. Jul 1 22:22:55 XPE_5-2 updater: updater.c:551 checksum generated by [/bin/grep -i rd.gz checksum.syno >> /tmp/checksum.syno.tmp] Jul 1 22:22:55 XPE_5-2 updater: updater.c:570 file [rd.gz] is being copied to [/tmp/bootmnt] Jul 1 22:22:55 XPE_5-2 updater: updater.c:578 file [/tmp/bootmnt/rd.gz] process done. Jul 1 22:22:55 XPE_5-2 updater: updater.c:551 checksum generated by [/bin/grep -i grub_cksum.syno checksum.syno >> /tmp/checksum.syno.tmp] Jul 1 22:22:55 XPE_5-2 updater: updater.c:570 file [grub_cksum.syno] is being copied to [/tmp/bootmnt] Jul 1 22:22:55 XPE_5-2 updater: updater.c:578 file [/tmp/bootmnt/grub_cksum.syno] process done. Jul 1 22:22:55 XPE_5-2 updater: updater.c:565 file [/tmp/bootmnt/hda1.tgz] is being removed Jul 1 22:22:55 XPE_5-2 updater: updater.c:578 file [/tmp/bootmnt/hda1.tgz] process done. Jul 1 22:22:55 XPE_5-2 updater: updater.c:565 file [/tmp/bootmnt/updater] is being removed Jul 1 22:22:55 XPE_5-2 updater: updater.c:578 file [/tmp/bootmnt/updater] process done. Jul 1 22:22:55 XPE_5-2 updater: updater.c:565 file [/tmp/bootmnt/VERSION] is being removed Jul 1 22:22:55 XPE_5-2 updater: updater.c:578 file [/tmp/bootmnt/VERSION] process done. Jul 1 22:22:55 XPE_5-2 updater: updater.c:588 checksum file updated by [/bin/cp -f /tmp/checksum.syno.tmp /tmp/bootmnt/checksum.syno] Jul 1 22:23:02 XPE_5-2 updater: boot/boot_lock.c(225): failed to mount boot device /dev/synoboot1 /tmp/bootmnt (errno:2) Jul 1 22:23:02 XPE_5-2 updater: updater.c:1319 Failed to mount factory partition Jul 1 22:23:02 XPE_5-2 updater: boot/boot_lock.c(225): failed to mount boot device /dev/synoboot1 /tmp/bootmnt (errno:2) Jul 1 22:23:02 XPE_5-2 updater: updater.c:1319 Failed to mount factory partition Jul 1 22:23:02 XPE_5-2 updater: boot/boot_lock.c(225): failed to mount boot device /dev/synoboot1 /tmp/bootmnt (errno:2) Jul 1 22:23:02 XPE_5-2 updater: updater.c:1319 Failed to mount factory partition Jul 1 22:23:02 XPE_5-2 updater: boot/boot_lock.c(225): failed to mount boot device /dev/synoboot1 /tmp/bootmnt (errno:2) Jul 1 22:23:02 XPE_5-2 updater: updater.c:1319 Failed to mount factory partition Jul 1 22:23:02 XPE_5-2 updater: boot/boot_lock.c(225): failed to mount boot device /dev/synoboot1 /tmp/bootmnt (errno:2) Jul 1 22:23:02 XPE_5-2 updater: updater.c:1319 Failed to mount factory partition Jul 1 22:23:02 XPE_5-2 updater: updater.c:5851 fail to upgrade factory partition Jul 1 22:23:02 XPE_5-2 updater: updater.c:676 Restoring [zImage] Jul 1 22:23:02 XPE_5-2 updater: updater.c:687 Copying file [//synob@ckup/zImage] as [/tmp/bootmnt/zImage], result[0] Jul 1 22:23:02 XPE_5-2 updater: updater.c:676 Restoring [rd.gz] Jul 1 22:23:02 XPE_5-2 updater: updater.c:687 Copying file [//synob@ckup/rd.gz] as [/tmp/bootmnt/rd.gz], result[0] Jul 1 22:23:02 XPE_5-2 updater: updater.c:673 Skip restoring [vendor] Jul 1 22:23:02 XPE_5-2 updater: updater.c:676 Restoring [grub_cksum.syno] Jul 1 22:23:02 XPE_5-2 updater: updater.c:687 Copying file [//synob@ckup/grub_cksum.syno] as [/tmp/bootmnt/grub_cksum.syno], result[0] Jul 1 22:23:02 XPE_5-2 updater: updater.c:676 Restoring [hda1.tgz] Jul 1 22:23:02 XPE_5-2 updater: updater.c:690 Removing file [/tmp/bootmnt/hda1.tgz], result[-1] Jul 1 22:23:02 XPE_5-2 updater: updater.c:694 Restore [hda1.tgz] fail, remove it from synoboot Jul 1 22:23:02 XPE_5-2 updater: updater.c:676 Restoring [updater] Jul 1 22:23:02 XPE_5-2 updater: updater.c:690 Removing file [/tmp/bootmnt/updater], result[-1] Jul 1 22:23:02 XPE_5-2 updater: updater.c:694 Restore [updater] fail, remove it from synoboot Jul 1 22:23:02 XPE_5-2 updater: updater.c:676 Restoring [VERSION] Jul 1 22:23:02 XPE_5-2 updater: updater.c:690 Removing file [/tmp/bootmnt/VERSION], result[-1] Jul 1 22:23:02 XPE_5-2 updater: updater.c:694 Restore [VERSION] fail, remove it from synoboot Jul 1 22:23:02 XPE_5-2 updater: updater.c:676 Restoring [checksum.syno] Jul 1 22:23:02 XPE_5-2 updater: updater.c:687 Copying file [//synob@ckup/checksum.syno] as [/tmp/bootmnt/checksum.syno], result[0] Jul 1 22:23:02 XPE_5-2 updater: updater.c:6183 fail to rollback flash (restore) Jul 1 22:23:02 XPE_5-2 updater: updater.c:6219 Failed to accomplish the update! (errno = 21) Jul 1 22:23:02 XPE_5-2 entry.cgi_SYNO.Core.Upgrade[1].start[15759]: Upgrade.cpp:300 failed to execute updater, r=-2498164 Jul 1 22:23:02 XPE_5-2 synoservicecfg: servicecfg_root_object_get.c:115 service config for service [] is not exist Jul 1 22:23:17 XPE_5-2 entry.cgi_SYNO.Core.Upgrade[1].start[15759]: update_cpputil.cpp:806 synoservice: start all packages ... Jul 1 22:23:21 XPE_5-2 entry.cgi_SYNO.Core.Upgrade[1].start[15759]: update_cpputil.cpp:859 synoservice: finish started all packages Jul 1 22:23:21 XPE_5-2 entry.cgi_SYNO.Core.Upgrade[1].start[15759]: Upgrade.cpp:530 Failed to unpack firmware. You see that last line? Upgrade.cpp:530 Failed to unpack firmware. Can you confirm that 5592 is installed? My first try the VM didn't upgrade, now trying for the 2nd time via manual update. edit: Nope it didn't upgrade, i guess we have to wait for a new bootloader. Quote Link to comment Share on other sites More sharing options...
koroziv Posted July 2, 2015 Share #10 Posted July 2, 2015 (edited) I think dodo-dk was referring to the fact that the update failed but he did not lose his data, the previous version was loaded without problems. Edited July 2, 2015 by Guest Quote Link to comment Share on other sites More sharing options...
maxime Posted July 2, 2015 Share #11 Posted July 2, 2015 Same problem. Waiting for a new bootloader.. Quote Link to comment Share on other sites More sharing options...
psychopirate Posted July 2, 2015 Share #12 Posted July 2, 2015 Can confirm that 5592 will not install without new bootloader. Tried on 3 different machines. Fails at 63% after reboot old system is up and running with no problems or loss of data. Tried both manual and automatic installs on all 3 machines. All 3 booted up to old systems with the only change being a warning that it did not install. No loss of functionality or data. Quote Link to comment Share on other sites More sharing options...
djelusion Posted July 3, 2015 Share #13 Posted July 3, 2015 sh shyt glad i noticed....... do not install this update.. Quote Link to comment Share on other sites More sharing options...
vemey Posted July 3, 2015 Share #14 Posted July 3, 2015 Hi to all above, as far as i'am aware off, updating to a new release number 5.2-XXXX always needs a new boot image. Only updates with the same release number are working with the same boot-image. So please be patient - this is my personal advice. Also i would recommend setting your update params to "only important updates" and no automatic update schedule. This will probably cut the postings on this forum to half Quote Link to comment Share on other sites More sharing options...
nemesis122 Posted July 3, 2015 Share #15 Posted July 3, 2015 Hi all Is it possbile to complete deactivate the DSM update? ty for your feedback Michael Quote Link to comment Share on other sites More sharing options...
vemey Posted July 3, 2015 Share #16 Posted July 3, 2015 actually, that is excactly what i meant when i wrote "Also i would recommend setting your update params to "only important updates" and no automatic update schedule." Quote Link to comment Share on other sites More sharing options...
nemesis122 Posted July 6, 2015 Share #17 Posted July 6, 2015 I know this I mean complete deactivate that there is no message for en update in this case that DSM not check if there is a newe Version. Is this possbile ? ty Michael Quote Link to comment Share on other sites More sharing options...
brantje Posted July 6, 2015 Share #18 Posted July 6, 2015 I know this I mean complete deactivate that there is no message for en update in this case that DSM not check if there is a newe Version. Is this possbile ? ty Michael You can disable the *check for update* task. Quote Link to comment Share on other sites More sharing options...
xpenew Posted July 14, 2015 Share #19 Posted July 14, 2015 Request to make this thread sticky so it stays at top as a quick reference for people looking for an update on 5.2-5592 issues Quote Link to comment Share on other sites More sharing options...
taffeys Posted July 15, 2015 Share #20 Posted July 15, 2015 Request to make this thread sticky so it stays at top as a quick reference for people looking for an update on 5.2-5592 issues +1 Quote Link to comment Share on other sites More sharing options...
taffeys Posted July 17, 2015 Share #21 Posted July 17, 2015 Bump Quote Link to comment Share on other sites More sharing options...
knightshade Posted July 17, 2015 Share #22 Posted July 17, 2015 5.2-5592 Update 1 is now out. One of my "real" Synology boxes got the update last night. Quote Link to comment Share on other sites More sharing options...
taffeys Posted July 18, 2015 Share #23 Posted July 18, 2015 Still waiting for a new bootloader like everyone else. Anyone have an update or ETA? Quote Link to comment Share on other sites More sharing options...
segarra Posted July 18, 2015 Share #24 Posted July 18, 2015 5.2-5592 Update 1 is now out. One of my "real" Synology boxes got the update last night. Still waiting for boot Enviado desde mi Nexus 5 mediante Tapatalk Quote Link to comment Share on other sites More sharing options...
R0GGER Posted July 22, 2015 Share #25 Posted July 22, 2015 Any news yet about when or if a new bootloader will developped for 5.2-5592 (Update 1)? Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.