Re: [qubes-users] Upgrading debian instructions are wrong
Hi Ulrich, You should try the following commands: $ sudo sed -i 's/buster/bullseye/g' /etc/apt/sources.list $ sudo sed -i 's/buster/bullseye/g' /etc/apt/sources.list.d/qubes-r4.list And I recommand you to clone your qube first as described. regards, Fred. On 12/16/21 8:43 PM, Ulrich Windl wrote: Hi! Following https://www.qubes-os.org/doc/template/debian/upgrade/ I read: [user@debian- ~]$ sudo sed -i 's///g' /etc/apt/sources.list [user@debian- ~]$ sudo sed -i 's///g' /etc/apt/sources.list.d/qubes-r4.list Continuing the instructions the upgrade was amazingly fast, so I doubt, looking into the files: ser@debian-11:~$ sudo sed -i 's/debian-10/debian-11/g' /etc/apt/sources.list user@debian-11:~$ sudo sed -i 's/debian-10/debian-11/g' /etc/apt/sources.list.d/qubes-r4.list user@debian-11:~$ sudo apt update Hit:1 https://deb.debian.org/debian buster InRelease Get:2 https://deb.debian.org/debian-security buster/updates InRelease [65.4 kB] Hit:3 https://deb.qubes-os.org/r4.0/vm buster InRelease Get:4 https://deb.debian.org/debian-security buster/updates/main amd64 Packages [312 kB] Get:5 https://deb.debian.org/debian-security buster/updates/main Translation-en [165 kB] Fetched 543 kB in 1s (572 kB/s) Reading package lists... Done Building dependency tree Reading state information... Done 1 package can be upgraded. Run 'apt list --upgradable' to see it. user@debian-11:~$ sudo apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages were automatically installed and are no longer required: gstreamer1.0-pulseaudio libjsoncpp1 lightning linux-headers-4.19.0-13-amd64 linux-headers-4.19.0-13-common linux-headers-4.19.0-14-amd64 linux-headers-4.19.0-14-common linux-headers-4.19.0-16-amd64 linux-headers-4.19.0-16-common linux-headers-4.19.0-6-amd64 linux-headers-4.19.0-6-common linux-image-4.19.0-13-amd64 linux-image-4.19.0-14-amd64 linux-image-4.19.0-16-amd64 linux-image-4.19.0-6-amd64 python-daemon python-dbus python-lockfile python-numpy python-olefile python-pil python-pkg-resources python-xdg Use 'sudo apt autoremove' to remove them. The following packages will be upgraded: libnss3 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 1,161 kB of archives. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Get:1 https://deb.debian.org/debian-security buster/updates/main amd64 libnss3 amd64 2:3.42.1-1+deb10u4 [1,161 kB] Fetched 1,161 kB in 1s (1,191 kB/s) Reading changelogs... Done (Reading database ... 220971 files and directories currently installed.) Preparing to unpack .../libnss3_2%3a3.42.1-1+deb10u4_amd64.deb ... Unpacking libnss3:amd64 (2:3.42.1-1+deb10u4) over (2:3.42.1-1+deb10u3) ... Setting up libnss3:amd64 (2:3.42.1-1+deb10u4) ... Processing triggers for libc-bin (2.28-10) ... user@debian-11:~$ sudo apt dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages were automatically installed and are no longer required: gstreamer1.0-pulseaudio libjsoncpp1 lightning linux-headers-4.19.0-13-amd64 linux-headers-4.19.0-13-common linux-headers-4.19.0-14-amd64 linux-headers-4.19.0-14-common linux-headers-4.19.0-16-amd64 linux-headers-4.19.0-16-common linux-headers-4.19.0-6-amd64 linux-headers-4.19.0-6-common linux-image-4.19.0-13-amd64 linux-image-4.19.0-14-amd64 linux-image-4.19.0-16-amd64 linux-image-4.19.0-6-amd64 python-daemon python-dbus python-lockfile python-numpy python-olefile python-pil python-pkg-resources python-xdg Use 'sudo apt autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. user@debian-11:~$ cat /etc/apt/sources.list deb https://deb.debian.org/debian buster main contrib non-free #deb-src https://deb.debian.org/debian buster main contrib non-free deb https://deb.debian.org/debian-security buster/updates main contrib non-free #deb-src https://deb.debian.org/debian-security buster/updates main contrib non-free user@debian-11:~$ cat /etc/apt/sources.list.d/qubes-r4.list # Main qubes updates repository deb [arch=amd64] https://deb.qubes-os.org/r4.0/vm buster main #deb-src https://deb.qubes-os.org/r4.0/vm buster main # Qubes updates candidates repository #deb [arch=amd64] https://deb.qubes-os.org/r4.0/vm buster-testing main #deb-src https://deb.qubes-os.org/r4.0/vm buster-testing main # Qubes security updates testing repository #deb [arch=amd64] https://deb.qubes-os.org/r4.0/vm buster-securitytesting main #deb-src https://deb.qubes-os.org/r4.0/vm buster-securitytesting main # Qubes experimental/unstable repository #deb [arch=amd64] https://deb.qubes-os.org/r4.0/vm buster-unstable main #deb-src https://deb.qubes-os.org/r4.0/vm buster-unstable main # Qubes Tor updates repositories # Main qubes updates repository #deb [arch=amd64]
Re: [qubes-users] Dom0 kernel panic
Thanks for your answer Bernhard, I wonder if I could make a Qube-style backup of the qubes in my hardrive instead of a rsync to restore/add them directly in the new installed Qube system, kind of lazy way ;) BR Le jeu. 4 mars 2021 à 16:34, Bernhard a écrit : > On 3/3/21 3:29 PM, frag face wrote: > > Hi all, > > > > I'm running Qubes 4.0 > > My dom0 doesn't boot anymore (following an aborted Fedora update it > > seems...). > > Boot runs to kernel panic, see attached image. > > > > From a newly installed Qubes on a different disk, I can mount my > > crashed disk, decrypt it and access all my Qubes, DOM0... > > > > I see two options to recover my environment (and would prefer the first): > > 1- Fix my Dom0 environment on my crashed hard drive (I have another > > drive with a newly installed Qubes 4.0-rc3) > > 2- Save my qubes from my crashed disk, and restore them on my new > > 4.0-rc3 install. > > > > Any advise to perform a rescue for option 1 or 2 is welcomed ! > > 1) try to boot from a life system. Mount /boot and, in case of UEFI, > have a look in efi/qubes/xen.cfg or efi/BOOT/xen.cfg you should be > able to select a older kernel. Maybe that allows to reboot. > > 2) emergency backup is a good idea in any case. Open the encrypted > volume (using luks)then runvgchange -ayto activate all > logical volumes. With lvscan you should be able to see the names > (something like qubes-...-work-private > qubes-...-work-root > etc > It is the "private" one that you want. Mount them (they are all in > /dev/mapper/ ) and "rsync -auv" your data to a harddrive in > respective subdirs. That is less safe than the paranoid version > of qubes-backup since its grasps all ".config" files, but at least > you have a full take. > > Good luck! > > -- > 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/6ac3a6b2-9d0f-cb77-0ae0-a62e2f740d7c%40web.de > . > -- 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/CAPrquWt6DK3w40VqYa_DoKHmMbn-P9gFzheK%2BEBQQMwUP%3D3gVA%40mail.gmail.com.
