I updated my Tumbleweed install on Monday mid-day PST.
And it broke so much that I am not sure I can recover data from it.
Upon reboot it first prompted me to accept new Nvidia driver MOK, which I did.
After that and another reboot I got
“Malformed security header
Failed to load header: Invalid parameter
Failed to load image: Invalid parameter
start_image{} returned Invalid Parameter, falling back to default loader”
which pushed me to the Windows bootloader, rather than GRUB.
Then I disabled Secure Boot and rebooted. Still the same problem.
I booted into a Live USB (tried both Tumbleweed and Kubuntu) and tried copying the little bit of data that wasn’t backed up out.
TW was installed in an LVM volume inside a LUKS-encrypted container. When I decrypt the container and mount the “system” volume (only other volume is “swap”), it indicates just as full as it was before (~4 GiB free of 1.2 TiB), but I don’t see any of my files (in fact if I get the size of all folders via Dolphin I get just ~35 GiB). The /home directory is empty. Using “ls -a” doesn’t show anything extra anywhere around the file system.
Any tips on accessing my files would be welcome. At this point, I am not even trying to recover the system. I just want to back up a few files and will likely do a clean install afterwards.
kubuntu@kubuntu:~$ sudo btrfs subvolume get-default /media/kubuntu/25c5c7b7-d523-41f9-9f04-9132d79ea589
ID 518 gen 299861 top level 265 path @/.snapshots/186/snapshot
also from mount, the mount point:
/dev/mapper/system-root on /media/kubuntu/25c5c7b7-d523-41f9-9f04-9132d79ea589 type btrfs (rw,nosuid,nodev,relatime,ssd,space_cache=v2,subvolid=518,subvol=/@/.snapshots/186/snapshot)
I also tried
kubuntu@kubuntu:~$ sudo mount -t btrfs /dev/mapper/dec /mnt/btrfs
mount: /mnt/btrfs: wrong fs type, bad option, bad superblock on /dev/mapper/dec, missing codepage or helper program, or other error.
dmesg(1) may have more information after failed mount system call.
and
kubuntu@kubuntu:~$ sudo dmesg | grep BTRFS
[ 533.932435] BTRFS: device fsid 25c5c7b7-d523-41f9-9f04-9132d79ea589 devid 1 transid 299860 /dev/mapper/system-root (252:2) scanned by pool-udisksd (3749)
[ 533.932780] BTRFS info (device dm-2): first mount of filesystem 25c5c7b7-d523-41f9-9f04-9132d79ea589
[ 533.932809] BTRFS info (device dm-2): using crc32c (crc32c-intel) checksum algorithm
[ 533.932816] BTRFS info (device dm-2): using free-space-tree
[ 534.171195] BTRFS info: devid 1 device path /dev/mapper/system-root changed to /dev/dm-2 scanned by (udev-worker) (3764)
[ 534.172000] BTRFS info: devid 1 device path /dev/dm-2 changed to /dev/mapper/system-root scanned by (udev-worker) (3764)
try to recover whole system by just going back in time with snapper
kubuntu@kubuntu:~$ sudo btrfs subvolume list /media/kubuntu/25c5c7b7-d523-41f9-9f04-9132d79ea589
ID 256 gen 118682 top level 5 path @
ID 257 gen 299852 top level 256 path @/var
ID 258 gen 299841 top level 256 path @/usr/local
ID 259 gen 285590 top level 256 path @/srv
ID 260 gen 299393 top level 256 path @/root
ID 261 gen 299852 top level 256 path @/opt
ID 262 gen 299852 top level 256 path @/home
ID 263 gen 289771 top level 256 path @/boot/grub2/x86_64-efi
ID 264 gen 251383 top level 256 path @/boot/grub2/i386-pc
ID 265 gen 299844 top level 256 path @/.snapshots
ID 298 gen 251383 top level 257 path @/var/lib/machines
ID 518 gen 299861 top level 265 path @/.snapshots/186/snapshot
ID 524 gen 213266 top level 265 path @/.snapshots/192/snapshot
ID 589 gen 289783 top level 265 path @/.snapshots/255/snapshot
ID 590 gen 289798 top level 265 path @/.snapshots/256/snapshot
ID 591 gen 289810 top level 265 path @/.snapshots/257/snapshot
ID 592 gen 289845 top level 265 path @/.snapshots/258/snapshot
ID 595 gen 293040 top level 265 path @/.snapshots/261/snapshot
ID 596 gen 293043 top level 265 path @/.snapshots/262/snapshot
ID 597 gen 299383 top level 265 path @/.snapshots/263/snapshot
ID 598 gen 299843 top level 265 path @/.snapshots/264/snapshot
ls -l /media/kubuntu/25c5c7b7-d523-41f9-9f04-9132d79ea589
Yes, you most likely need to mount this subvolume to get access to your old /home content. Although to be absolutely sure you would need to check (or show) the content of /etc/fstab on your roor filesystem.
When you need to recover you need to have more control and be sure you know exactly what you are doing. Not blindly trust GUI to do something.
My lacking knowledge of sub-volumes was to blame. All I needed to do was
sudo mount -o subvol=/@/home /dev/mapper/system-root /mnt/m0
What I couldn’t do is use snapper to try and restore older snapshots from before it broke (kept getting errors that it can’t find a config), but ok, I decided to reinstall anyhow.