Hello! So over the past couple of days I have been trying to upgrade my system to 4.3-rc1 and I’ve faced a couple of issues. Here’s what they are:
When running the post-reboot part of the upgrade for the first time, I accidentally quit because my system got locked, and afterwards, whenever I try to upgrade via the post-reboot again, it simply defaults to
[*date and time*] qrexec-client[35513]:qrexec-daemon-common.c:232:connect_unix_socket: connect /var/run/qubes/qrexec.[*template or standalone name here*]: No such file or directory
[*date and time*] qrexec-client[35513]:qrexec-daemon-common.c:232:negotiate connection_params: write daemon: Bad file descriptor
ERROR: A general error occured while upgrading [*qube*] (exit code 125).
and after doing that a couple of times it writes
E0F
and stops.
After qubes-dist-upgrade fails I have to restart dom0 update qube because the command complains:
ERROR: UpdateVM [*qube name here*] should on a template that have 'dnf' installed - at least Fedora 37, Debian, or Whonix 16.
which can only be solved by shutting the qube in question down and letting it get turned on automatically again when running the command.
I don’t really get how the --only-update option works. It says “comma-separated list” and I’ve tried several of those possible lists and none seem to have worked. I would appreciate a clarification.
And for the final one, when I decided to have a go at running stage 5, at the LVM devices cache phase it goes
/usr/lib/qubes/qubes-dist-upgrade-r4.3.sh: line 45: vgimportdevices: command not found
And now I can’t even restore from backup because any qube I try (except for dom0, but sending my backup to dom0 would both require expanding it’s size and would be quite insecure) keeps outputting:
Error Command 'qubes.SelectFile' returned non-zero exit status 125. occured.
Hello, so I have done some investigation, and the problems seems to lie withing qrexec, since qubes.SelectFile is a qrexec service. I have tried reinstalling coreutils in dom0 and in the affected machines and it doesn’t seem to help. What do I do?
Since you can reinstall packages in dom0, this shows your update mechanism is working. And it is highly likely that you should be able to install untouched templates. I guess you should be able to download & an untouched official templates (if minimal, then additional packages are required), use it for sys-usb (or actually use that template for your default-dvm). Then you should be able to restore your backups from external USB storage.
probably, but it is extremely unreliable and I cannot update anything via the GUI.
restore your backups from external usb storage
Does it have to be a usb mounted to a qube? Won’t it be ok to sync up the backup from my other computer onto a qube and then use it like that?
Anyhow thank you for your responce. I don’t really know how to install an extra untouched template, but I will give it a try. Thank you.
UPDATE: when I looked in the Qubes Template Manager it read out:
Failed to fetch template list:
[Qrexec] *current date and time* qrexec-client[12479]: qrexec-daemon-common.c:232:connect_unix_socket: connect /var/run/qubes/qrexec.sys-firewall: No such file or directory
[Qrexec] *current date and time* qrexec-client[12479]: qrexec-daemon-common.c:29:negotiate_connection_params: write daemon: Bad file descriptor
ERROR: qrexec call 'qubes.TemplateSearch' failed.
Anyhow, this makes me unsure whether I actually managed to reinstall coreutils in dom0. I shall try again and respond soon.