Not really installation: I have had HAOS runnning in Virtualbox (currently 7.1.4) on a Gentoo Linux host for over a year, with only the occasional issue. However, starting several days ago, after having had to restart my host PC without proper shutdown, when I try to start the virtual machine, it gets as far as “Waiting for Supervisor to startup …” and then the VM window closes and the status of the VM changes to Aborted. Unfortunately, my whole KDE Plasma session got so hung up It took a sledge hammer to shut things down enough to reboot. However, I’m fairly sure I’ve had to do that in the past, and HAOS started up again without problems. (I concede I may just be imagining that, since if I mis-remember, I suspect the situation would be even less pleasant than I’m afraid it might be.)
I see nothing useful in the VB log, although it’s quite possible I just don’t see it. I have been able to interrupt the boot process and get to maintenance mode (both slots A and B) but I really don’t know what I’m looking for there. I did manage to scp the output from journalctl -xb, and I can post that as well as a VB log if it would be helpful. I do not have a VB Snapshot to roll back to.
I’m willing to reinstall, as long as I can get a backup off the virtual machine. My setup isn’t all that complex, but it took me a great deal of effort to get my four Enbrighton switches set up, and I would not want to do that again. I do request backups for every HA upgrade, if someone can point me to where they are when I’m in maintenance mode.
So - is there anything else I can try to recover and get a successful boot, or what should I post to be useful but not overwhelming. Thanks for any suggestions or assistance.
