Khad Posted April 5, 2021 Share #1 Posted April 5, 2021 On my VirtualBox test environment I have a Virtual Machine running loader DS918v104b. Installed it with DSM 6.2.3-25426 but I am unable to update it to Update 2 or Update 3. When I try, it gives me this error: I have tried: - Automatic update to DSM 6.2.3-25426 Update 3, this fails - Manual update to DSM 6.2.3-25426 Update 3, this fails - Manual update to DSM 6.2.3-25426 Update 2, this fails - Setting up a new & clean Virtual Machine which I install with DSM 6.2.3-25426 and directly after it finished I've tried updating it. Fails on all above attempts. I even expanded the size of the synoboot.vdi from 50 to 500Mb to test it's size would be the problem, made no difference. Any idea on how to solve this issue? Thanks Quote Link to comment Share on other sites More sharing options...
flyride Posted April 5, 2021 Share #2 Posted April 5, 2021 https://xpenology.com/forum/topic/28183-running-623-on-esxi-synoboot-is-broken-fix-available/ Quote Link to comment Share on other sites More sharing options...
Khad Posted April 6, 2021 Author Share #3 Posted April 6, 2021 10 hours ago, flyride said: https://xpenology.com/forum/topic/28183-running-623-on-esxi-synoboot-is-broken-fix-available/ Thank you for that, it solved my problem! Ran into a small problem with these commands though: 7. Copy the file from your upload location to the target location. # cp /volume1/folder/FixSynoboot.sh /usr/local/etc/rc.d 8. Make the script executable. # chmod 0755 /usr/local/etc/rc.d/FixSynoboot.sh Got an error about no such directory exists or something like that. So I changed directory to /usr/local/etc/rc.d/ and executed # cp /volume1/folder/FixSynoboot.sh FixSynobot.sh and then applied # chmod 0755 /usr/local/etc/rc.d/FixSynoboot.sh Which worked. Shouldn't the command 7 be: # cp /volume1/folder/FixSynoboot.sh /usr/local/etc/rc.d/ With the / at the end? Either way, it's fixed, I now can see $ ls /dev/synoboot* resulting in /dev/synoboot /dev/synoboot1 /dev/synoboot2 And ran the DSM 6.23-25426 Update 3 successful However I still do see the synoboot.vdi virtual disk in my Storage Manager, is that correct? 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.