I have finished --all-pre-reboot stages smoothly. Restarted Qubes, and I am getting 4.3 screen with only linux 7.0.9 f41 entry, while all other - 7.09 (again), 7.06, 6.18.35 are f37(?)
When choosing linux 7.0.9 f41 entry it can’t pass the screen and continuously restart to the menu.
I can boot to f37 entries, but getting lot of errors where nothing works, except dom0, even qubes-qube-manager cannot start
How to start to debug why the system keeps restarting when choosing linux 7.0.9 f41 entry. because I guess that is the one I have to boot to, to finish in-place upgrade.
I would first separate the boot problem from the post-reboot upgrade step. Since the older entries still boot, use one of those only to inspect logs and confirm the new 7.0.9/f41 kernel/initramfs entry was generated correctly, not to make more package changes immediately.
Useful first checks from dom0 are the previous boot logs and the exact grub entry: journalctl -b -1 -p warning…alert, journalctl -k -b -1, and whether /boot has matching vmlinuz/initramfs files for that 7.0.9 entry. If it reboots so fast that logs are empty, try removing quiet/rhgb from the grub entry for one boot so the last message is visible. Then paste that last error here before rerunning the upgrade command.
Hey @NuageQubes81, thanks for your response. I have no means to copy/paste log parts here, but basically what I see is that during boot there are a lot of errors about Firmware Bugs on CPU cores about APIC ID mismatches. Never saw before. Then, respectively tmpfs: Unsupported parameter @huge@Then i915 error that says it failed disable qgv points 0x307, some block groups have wrong amount of free space, then ACPI BIOS Error (bug)" AE_AML_BUFFER_LIMIT… is beyond end of object, then bunch of errors Failed to start qubesd.service - Qubes OS daemon with result ‘exit code’ and finally Device luks-xxxx is still in use with Failed to deactivate it.
Never saw these errors earlier and I was proud to have had a log without errors except proc-thermal_pci xxx error" proc_thermal_add, will continue. But that error was about sensors I don’t have I think I realized at some point, so benign.
