@extenue, @Lennartt, @wenlez, @pateretou, @sashxp, @enzo, @dodo-dk
- Outcome of the update: SUCCESSFUL
- DSM version prior update: 6.1.7 Update 2 with Jun's loader v1.02b
- Loader version and model: Jun's Loader v1.03b - DS3617
- Using custom extra.lzma: NO
- Installation type: VM Proxmox 5.2.6 - Xeon D-1537 (need to pass kvm64 cpu type), passthrough LSI SAS2116 with 5 x WD RED 3TB Raid5, 2 x WD RED 4TB Raid1 & 2 x Intel DC S3700 200GB Raid1
- Additional comments : SeaBIOS, loader on sata and ESXi boot line. Update to U2 ok. Had to replace/delete remnant files from older loaders in /etc/rc.*, /.xpenoboot (see last paragraph below).
Using the usb method, I got a "mount failed" as others on Proxmox, but it was successful when using a sata image disk:
rename the loader with a .raw instead of .img and place it in the VM images folder /var/lib/vz/images/100/ (Proxmox parser does not understand .img)
add a sata0 disk in the vm .conf (/etc/pve/qemu-server/100.conf) :
sata0: local:100/synoboot_ds3617_v1.03b.raw,size=52429K
choose sata0 in Option/Boot Order in the GUI
at start in the GUI console, choose the ESXi boot line
My vm ID is 100, replace it with yours.
I also had to choose the kvm64 cpu type.
A serial port is also a good thing to have for debug. You can access the serial console with the following line (type Ctrl-O to exit):
socat UNIX-CONNECT:/var/run/qemu-server/100.serial0 STDIO,raw,echo=0,escape=0x0f
The serial port was very needed in my case.
After I first updated from 6.1 to 6.2, the VM was starting well (docker and ssh were Ok) but I was not able to logging into DSM, and after ~5 mins from boot, everything was shutting down and I was losing network (as @JBark). I thought it had completely shutdown. But using the serial port, I saw that it just killed everything Synology related even the network config.
With a fresh VM, it was working well, so tried to find differences between the DSM filesystems.
I found that a lot of /etc/rc.* files where referencing old binaries that do not exist anymore so I replaced all the /etc/rc.* files by the ones from the fresh installation. When rebooting, it was still closing down after 5 mins, but I think it was needed in combination with the following removals.
I also saw several /etc/*.sh scripts, and a /.xpenology folder, that were not there in the fresh installation.
After deleting them, and cleaning a little the /etc/synoinfo.conf file (removed support_syno_hybrid_raid option, and some other options, not sure if it had an effect), everything was working great again!
@jun Thanks for the loader!