Hello 'Haaber' & Qubes OS community, Am Di., 20. Feb. 2024 um 20:12 Uhr schrieb Viktor Ransmayr < viktor.ransm...@gmail.com>:
> ... > Am Di., 20. Feb. 2024 um 11:10 Uhr schrieb 'haaber' via qubes-users < > qubes-users@googlegroups.com>: > >> ... >> >> all updates go via tor network (sys-whonix) by default. You could click >> on the blue qube widget -> sys-wonix -> run terminal and see if sys-whonix >> has network. But I guess not. Here is why: >> >> https://www.qubes-os.org/doc/firewall/ >> >> I wild-guess that you are in a "half-state" where one part of the system >> expects iptables, another one nftables ... >> >> Did you download / start to download new (debian/fedora) Templates or are >> they the "old" ones? >> >> I did not see any other user jump to your help, and I am not good enough >> to fix that alone for you. So honestly, at your place I would >> >> (1) backup data (again) >> >> (2) extract the list of manually installed packages in each of your >> templates and stock them on your backup drive >> >> ("apt-mark showmanual > manual.packages.list" in a terminal is your >> friend, no root priv needed) >> >> (3) re-install a clean 4.2 >> >> (4) replay your manual installs of packages in your templates: >> >> "cat manual.packages.list | apt-get install " or something of this >> type should work (run as root) >> >> (5) restore your data. >> >> It's a pain and takes half a day, but I fear that it is, at the end of >> the day, faster than any other solution... >> >> good luck! >> > > Thanks a lot ! > > This is exactly the feedback I was hoping for. > > I'll investigate further on my side & will provide an update from my side > before the end of the week ... > It took much longer due to private reasons - but - I can report that I was able to fully recover from the backups ! What I did different than suggested was that I started with a clean re-install of Qubes OS 4.1 ... Now I've started a second attempt of an in-place upgrade - and - are already running into issues again at STAGE 1: Here is the dom0 - log: ### [vr@dom0 ~]$ [vr@dom0 ~]$ sudo qubes-dist-upgrade --update WARNING: /!\ MAKE SURE YOU HAVE MADE A BACKUP OF ALL YOUR VMs AND dom0 DATA /!\ -> Launch upgrade process? [y/N] y ---> Allow shutdown of unnecessary VM (use --keep-running to exclude some): fedora-feedly-vm fedora-qubes-study-vm? [y/N] y ---> (STAGE 1) Do you want to make a dom0 snapshot? [y/N] y WARNING: Sum of all thin volume sizes (<2.83 TiB) exceeds the size of thin pools and the size of whole volume group (<475.34 GiB). Logical volume "Qubes41UpgradeBackup" created. --> If upgrade to 4.2 fails, you can restore your dom0 snapshot with sudo lvconvert --merge qubes_dom0/Qubes41UpgradeBackup. Reboot after restoration. ---> (STAGE 1) Updating dom0... Using sys-firewall as UpdateVM to download updates for Dom0; this may take some time... Qubes OS Repository for Dom0 2.9 MB/s | 3.0 kB 00:00 Qubes OS Repository for Dom0 6.7 MB/s | 192 kB 00:00 kernel-latest.x86_64 1000:6.7.7-1.qubes.fc32 qubes-dom0-cached kernel-latest-devel.x86_64 1000:6.7.7-1.qubes.fc32 qubes-dom0-cached kernel-latest-modules.x86_64 1000:6.7.7-1.qubes.fc32 qubes-dom0-cached kernel-latest-qubes-vm.x86_64 1000:6.7.7-1.qubes.fc32 qubes-dom0-cached qubes-usb-proxy-dom0.noarch 1.2.0-1.fc32 qubes-dom0-cached Qubes OS Repository for Dom0 2.9 MB/s | 3.0 kB 00:00 Dependencies resolved. ================================================================================ Package Arch Version Repository Size ================================================================================ Installing: kernel-latest x86_64 1000:6.7.7-1.qubes.fc32 qubes-dom0-cached 12 M kernel-latest-devel x86_64 1000:6.7.7-1.qubes.fc32 qubes-dom0-cached 15 M kernel-latest-modules x86_64 1000:6.7.7-1.qubes.fc32 qubes-dom0-cached 76 M kernel-latest-qubes-vm x86_64 1000:6.7.7-1.qubes.fc32 qubes-dom0-cached 18 M Upgrading: qubes-usb-proxy-dom0 noarch 1.2.0-1.fc32 qubes-dom0-cached 25 k Transaction Summary ================================================================================ Install 4 Packages Upgrade 1 Package Total size: 121 M Is this ok [y/N]: y Downloading Packages: Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction Preparing : 1/1 Installing : kernel-latest-modules-1000:6.7.7-1.qubes.fc32.x86_64 1/6 Running scriptlet: kernel-latest-modules-1000:6.7.7-1.qubes.fc32.x86_64 1/6 Installing : kernel-latest-devel-1000:6.7.7-1.qubes.fc32.x86_64 2/6 Running scriptlet: kernel-latest-devel-1000:6.7.7-1.qubes.fc32.x86_64 2/6 Installing : kernel-latest-qubes-vm-1000:6.7.7-1.qubes.fc32.x86_6 3/6 Running scriptlet: kernel-latest-qubes-vm-1000:6.7.7-1.qubes.fc32.x86_6 3/6 --> Building files for 6.7.7-1.qubes.fc32.x86_64 in /var/lib/qubes/vm-kernels/6.7.7-1.fc32 ---> Generating modules.img resize2fs 1.45.5 (07-Jan-2020) --> Done. Installing : kernel-latest-1000:6.7.7-1.qubes.fc32.x86_64 4/6 Upgrading : qubes-usb-proxy-dom0-1.2.0-1.fc32.noarch 5/6 Cleanup : qubes-usb-proxy-dom0-1.1.5-1.fc32.noarch 6/6 Running scriptlet: kernel-latest-1000:6.7.7-1.qubes.fc32.x86_64 6/6 /usr/lib/kernel/install.d/20-grub.install: line 81: grub2-get-kernel-settings: command not found cat: /sys/power/resume: No such file or directory Generating grub configuration file ... Found theme: /boot/grub2/themes/qubes/theme.txt Found linux image: /boot/vmlinuz-6.7.7-1.qubes.fc32.x86_64 Found initrd image: /boot/initramfs-6.7.7-1.qubes.fc32.x86_64.img Found linux image: /boot/vmlinuz-6.6.2-1.qubes.fc32.x86_64 Found initrd image: /boot/initramfs-6.6.2-1.qubes.fc32.x86_64.img Found linux image: /boot/vmlinuz-6.1.75-1.qubes.fc32.x86_64 Found initrd image: /boot/initramfs-6.1.75-1.qubes.fc32.x86_64.img Found linux image: /boot/vmlinuz-6.1.12-1.qubes.fc32.x86_64 Found initrd image: /boot/initramfs-6.1.12-1.qubes.fc32.x86_64.img Found linux image: /boot/vmlinuz-5.15.94-1.qubes.fc32.x86_64 Found initrd image: /boot/initramfs-5.15.94-1.qubes.fc32.x86_64.img Found linux image: /boot/vmlinuz-6.7.7-1.qubes.fc32.x86_64 Found initrd image: /boot/initramfs-6.7.7-1.qubes.fc32.x86_64.img Found linux image: /boot/vmlinuz-6.6.2-1.qubes.fc32.x86_64 Found initrd image: /boot/initramfs-6.6.2-1.qubes.fc32.x86_64.img Found linux image: /boot/vmlinuz-6.1.75-1.qubes.fc32.x86_64 Found initrd image: /boot/initramfs-6.1.75-1.qubes.fc32.x86_64.img Found linux image: /boot/vmlinuz-6.1.12-1.qubes.fc32.x86_64 Found initrd image: /boot/initramfs-6.1.12-1.qubes.fc32.x86_64.img Found linux image: /boot/vmlinuz-5.15.94-1.qubes.fc32.x86_64 Found initrd image: /boot/initramfs-5.15.94-1.qubes.fc32.x86_64.img done Generating grub configuration file ... Found theme: /boot/grub2/themes/qubes/theme.txt Found linux image: /boot/vmlinuz-6.7.7-1.qubes.fc32.x86_64 Found initrd image: /boot/initramfs-6.7.7-1.qubes.fc32.x86_64.img Found linux image: /boot/vmlinuz-6.6.2-1.qubes.fc32.x86_64 Found initrd image: /boot/initramfs-6.6.2-1.qubes.fc32.x86_64.img Found linux image: /boot/vmlinuz-6.1.75-1.qubes.fc32.x86_64 Found initrd image: /boot/initramfs-6.1.75-1.qubes.fc32.x86_64.img Found linux image: /boot/vmlinuz-6.1.12-1.qubes.fc32.x86_64 Found initrd image: /boot/initramfs-6.1.12-1.qubes.fc32.x86_64.img Found linux image: /boot/vmlinuz-5.15.94-1.qubes.fc32.x86_64 Found initrd image: /boot/initramfs-5.15.94-1.qubes.fc32.x86_64.img Found linux image: /boot/vmlinuz-6.7.7-1.qubes.fc32.x86_64 Found initrd image: /boot/initramfs-6.7.7-1.qubes.fc32.x86_64.img Found linux image: /boot/vmlinuz-6.6.2-1.qubes.fc32.x86_64 Found initrd image: /boot/initramfs-6.6.2-1.qubes.fc32.x86_64.img Found linux image: /boot/vmlinuz-6.1.75-1.qubes.fc32.x86_64 Found initrd image: /boot/initramfs-6.1.75-1.qubes.fc32.x86_64.img Found linux image: /boot/vmlinuz-6.1.12-1.qubes.fc32.x86_64 Found initrd image: /boot/initramfs-6.1.12-1.qubes.fc32.x86_64.img Found linux image: /boot/vmlinuz-5.15.94-1.qubes.fc32.x86_64 Found initrd image: /boot/initramfs-5.15.94-1.qubes.fc32.x86_64.img done Running scriptlet: qubes-usb-proxy-dom0-1.1.5-1.fc32.noarch 6/6 Verifying : kernel-latest-1000:6.7.7-1.qubes.fc32.x86_64 1/6 Verifying : kernel-latest-devel-1000:6.7.7-1.qubes.fc32.x86_64 2/6 Verifying : kernel-latest-modules-1000:6.7.7-1.qubes.fc32.x86_64 3/6 Verifying : kernel-latest-qubes-vm-1000:6.7.7-1.qubes.fc32.x86_6 4/6 Verifying : qubes-usb-proxy-dom0-1.2.0-1.fc32.noarch 5/6 Verifying : qubes-usb-proxy-dom0-1.1.5-1.fc32.noarch 6/6 Upgraded: qubes-usb-proxy-dom0-1.2.0-1.fc32.noarch Installed: kernel-latest-1000:6.7.7-1.qubes.fc32.x86_64 kernel-latest-devel-1000:6.7.7-1.qubes.fc32.x86_64 kernel-latest-modules-1000:6.7.7-1.qubes.fc32.x86_64 kernel-latest-qubes-vm-1000:6.7.7-1.qubes.fc32.x86_64 Complete! ---> (STAGE 1) Updating Templates VMs and StandaloneVMs... debian-11-podman: OK debian-11-docker-desktop: OK debian-12-vrsq: OK debian-12-minimal: OK debian-11: OK fedora-38-minimal-vr: OK debian-12: OK fedora-38-minimal-vr-vscodium: ERROR (exception No such domain: 'disp-mgmt-fedora-38-minimal-vr-') fedora-38-minimal-vr-podman: OK fedora-39-minimal: ERROR (exit code 20, details in /var/log/qubes/mgmt-fedora-39-minimal.log) fedora-39: OK fedora-38: OK fedora-38-vrsq: OK whonix-gw-16: ERROR (exit code 20, details in /var/log/qubes/mgmt-whonix-gw-16.log) vrqt-fl39-01: OK vrqt-fl39-02: OK whonix-ws-16: OK [vr@dom0 ~]$ ### Is it save to proceed ? With kind regards, Viktor -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/CAAeSrGJOrPc975pEvX0-At%2BP7tr24Z3%2Bsijw12MB9N9Xm0y8Ew%40mail.gmail.com.
