Then you can observe the complete boot process with a simple "qm terminal ".Ģ/ When doing so, I discovered what was happening: I've been iddle some time but I'm coming back with some responses I discovered by researching this a little bit.ġ/ In order to have a *full* serial console, you need to uncomment/comment these lines in grub.cfg: Could somebody confirm?Īnd a second question: I was successfully using serial console on Proxmox to monitorize the booting process (qm terminal ) on 1.02b, but it seems not to work for 1.03b loader. But I tried it and it isn't working, so maybe I'm wrong with that, and 1.03b only support 6.2. What's the procedure to update to DSM 6.2? I thought that new 1.03b loader would support both DSM 6.2 (and 6.1) so my idea was to burn 1.03b loader, start DSM 6.1, test new loader in that environment, and finally upgrade DSM (via GUI). ![]() I'd recommend this environment so if your proxmox fails, you can pick up your phisical disks (I'm currently passing them thru to proxmox) and the usb stick and start directly in the server (even another new server!). I'm using an usb stick (with synoboot.img burnt), which can work both on baremetal and Proxmox so I can switch between starting DSM on HP Gen8 without any virtualization layer, or starting DSM from Proxmox (running over HP Gen8). I have DSM 6.1 (1.02b loader) on HP Gen8.
0 Comments
Leave a Reply. |