Major Problem: Boot Loop after Upgrading dom0

[799]

Hello,

After Upgrading my AppVMs to Fedora 28 yesterday I tried to upgrade dom0.

During the update I ran into problems with the kernel upgrade.

As the process seem to be stuck I interrupted with STRG + C.

Upon next reboot I run into a bootloop after passing Grub menu.

Any idea how to proceed?

[799]

[qube...@go-bailey.com]

That sounds similar to what happened to others when the kernel update
process was interrupted. Perhaps:

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

might help if you try what marmarek suggested and boot into an older
kernel and generate initramfs if not there and then run the grub2 command.

[schnuren...@gmail.com]

You should choose in grub menu an older kernel and do the grub2-mkconfig command as suggested.

[799]

Hello,

<schnuren...@gmail.com> schrieb am Mo., 28. Mai 2018, 19:18:

On Monday, May 28, 2018 at 6:00:05 PM UTC+2, [ 799 ] wrote:,

>
> After Upgrading my AppVMs to Fedora 28 yesterday I tried to upgrade dom0.
> During the update I ran into problems with the kernel upgrade.
> As the process seem to be stuck I interrupted with STRG + C.
>
> Upon next reboot I run into a bootloop after passing Grub menu.
>
> Any idea how to proceed?

You should choose in grub menu an older kernel and do the grub2-mkconfig command as suggested.

Ok, when booting up I see the following menu:

1) Qubes, with Xen Hypervisor

2) advanced Options for Qubes with Xen Hypervisor

Choosing 2) I see another menu:

1) Xen Hypervisor, version 4.8.3

2) Xen Hypervisor, version 4.8.3.config

3) Xen Hypervisor, version 4.8

I have chosen 1 and then I can see different kernels:

I'll try to boot those.

[799]

[799]

On 28 May 2018 at 21:35, 799 <one7...@gmail.com> wrote:

Boot Loop after interrupting qubes-dom0-update

Luckily I was able to boot into Qubes with an older kernel.

No I need to know how to fix the broken one.

I thought that I will just run sudo qubes-dom0-update again, but unfortunately this only results in the message:

[...]

Nothing to do.

Complete

[...]

What do I need to reinstall the latest kernel?

[799]

[[799]]

Hello,

luckily I was able to restore my system and fixing the damaged kernel.
Here the solution for the google groups forum.

On 05/28 10:18, schnuren...@gmail.com wrote:
> On Monday, May 28, 2018 at 6:00:05 PM UTC+2, [ 799 ] wrote:
> > Hello,
> >
> >
> > After Upgrading my AppVMs to Fedora 28 yesterday I tried to upgrade dom0.
> > During the update I ran into problems with the kernel upgrade.
> > As the process seem to be stuck I interrupted with STRG + C.> >
> > Upon next reboot I run into a bootloop after passing Grub menu.
>

> You should choose in grub menu an older kernel and do the grub2-mkconfig command as suggested.

after I couldn't boot into my default kernel, I booted an older kernel during grub boot menu.
Using the old kernel, I was able to launch dom0 and then uninstalling the kernels:

sudo dnf remove kernel-4.14.35 kernel-qubes-vm-4.14.35

I got some error messages and it looks like only the last package was uninstalled.
Next step was to run

sudo dnf reinstall kernel-4.14.35 kernel-qubes-vm-4.14.35

This took some time, but worked without throwing any error messages.
I then rebooted and was able to use the new kernel.

Not shure if it is really needed to remove the damaged kernel before or if you can just use the reinstall-command.

[799]