During an update some weeks ago of Dom0 via the Qubes updater, the system froze. The screen was frozen and the keyboard no longer responded to the Caps Lock key. Since the fan was still running at full load, I let the PC run for another hour, but nothing more happened, so I shut it down. It booted up again and restarted the update and the same thing happened again except that it could not boot up again *after the froze from the last update attempt.
Is it possible to repair the system so Dom0 via the rescue disk?
Otherwise i would have to manually save the changed data since the last back up.
I couldn’t see any errors because, as i said, the screen was frozen. My first assumption was that it has to do with the graphics drivers, so that only the screen was frozen but the system was still running because the fan was still running at 100% and the CPU was generating heat, but the numpad or the Caps Lock key were also no longer responding (so the lights on the keyboard no longer activated when the buttons were pressed, which is usually the case).
Oh I’m sorry, you must mean what error occurs when the PC tries to boot. Well I only see the loading bar, which doesn’t go any further even after hours.
Remove the rhgb quiet from the kernel command line options and add plymouth.enable=0 option in GRUB during Qubes OS boot like this: Autostart troubleshooting | Qubes OS
You’ll be able to see the boot log and check where it fails.
Sorry I must have overlooked this, I had searched for it but couldn’t find it.
When I deactivated the interface, the system booted up normally without any problems and there were no errors or anything similar. However, when the interface is activated, and only since the update, the system no longer boots up, or at least I don’t see it.
It is due to the external monitors, if the monitors are not connected to the laptop it works but if they are connected it does not work if the interface is activated.