InPlace Upgrade to r4.3rc2 - system hangs in error loop after dom0 update

User Support Testing Release
1

Hi all,
the InPlace Upgrade worked with little problems, what were easy to resolve.

My first step after stage 6 was to reboot. - All ok!
The booted Fedora version was 41.

Thereafter I started qubes-dom0-update. I saw no errors but a few warnings. I forgot the type of the warnings, but when trying to restart a qube I got an error, that qubes.d.service was not running.

I thought it belonging to a version mismatch, because of a needed reboot.

So I did, but that seems to be my biggest fault today:

After giving the password for the qubes-partition the system hangs in an error loop.

I can see the following error messages:

Failed to start accounts.d.on.service.
Failed to start qubesd.service.

No interaction possible. I have to hardkill the computer via powerbutton.

Any ideas how to get into the Qubes system to repair this, possibly with a downgrade?

2

Oooff… I suggest you hit up the Qubes Matrix chat room and ask there. The awesome people there are always helping me out on-the-spot with any issues I encounter.

3

Thanks, I’ll try. Will have to get a client running on systemrescue for this.

4

the Qubes Matrix chat room

Is this bridged to the qubes-os IRC room? IRC should be the common
denominator. Not everyone’s can run resource heavy matrix clients. IRC
is lightweight and people are free to join in the convo with their own
IRC client setups.

5

If you’d like to chat, join us on

  • the #qubes channel on irc.libera.chat or
  • the #qubes:invisiblethingslab.com matrix channel.

these two should be linked/bridged, but for technical reasons currently are not.

According to the official Qubes OS Docs page.

6

possible reason is, that libvirt has problems. you can check if libvirtd is running (dom0:$ systemctl status libvirtd). If not it may be that you can get qubesd running by starting the libvirtd components seperately.
It may also be, that you are missing the package for the hvm stubdom. Not because of your problem description, but because of my upgrade journey. This will show by your HVM domains (e.g. sys-net) not being able to access the pci cards. If that is the case you are unable to install any packages the normal way (because you cant connect to the internet anymore). The fix would be relatively easy, you need to download the package manualy from the qubes os servers, move it to dom0 (this might require accessing a usb drive or similar in dom0, which is a security risk) and then install it manualy with dnf.

7

Thanks for this hint, but my problem is while booting now.

I can’t even see anything on my dom0 root partition, as the rescue system does not find the encrypted partition.

What are the steps in anaconda to start with point “1 - Continue”?

If I know these steps, I can do them one after the other and react on any errrors that will be shown. For now these steps are done in a black box for me, as all output in the different log-panes is cut and I’m not able to walk through the logs to see anything.