boot loop after recent xen-updates in dom0

[gluo...@tuta.io]

Hi!

After the latest xen updates my laptop is stuck in a re-boot loop. 

The messages before the reboot are:

Initram unpacking failed: read error

Kernel panic - not syncing: VFS unable to mount root fs on unknown block (0,0)

CPU: 3 PID: 1 Comm: swapper/0 Not tainted 5.9.14-1.qubes.x86_64 #1

Call trace 

...

Kernel offset: disabled

More details are contained in the screenshot. 

Any ideas how to resolve this? 

[donoban]

Hi,

Maybe your initramfs is corrupt? Try live booting and recreating it.

[gluo...@tuta.io]

> Maybe your initramfs is corrupt? Try live booting and recreating it.

Do you have a hint for me how to recreate it? 

I‘ve found this issue:

https://github.com/QubesOS/qubes-issues/issues/6210

Seems to be related. Will try this. 

[donoban]

On 1/1/21 7:30 PM, gluonium via qubes-users wrote:
>> Maybe your initramfs is corrupt? Try live booting and recreating it.
>
> Do you have a hint for me how to recreate it? 

You need to boot from some live system and chroot your Qubes root
partition which properly mounted EFI partition. Then run:
'dracut -f /boot/efi/EFI/qubes/initramfs-{version}.img {version}'

Maybe a better option is just modifying xen.cfg for booting an older
kernel and then try to reinstall last kernel package after properly
freeing some space.

This way you only need to mount your EFI partition (no LUKS, no LVM,
etc....) and edit the file xen.cfg.