02-09-2020, 01:42 PM
(02-09-2020, 01:25 PM)Jeremiah Cornelius Wrote: You may be in a tough bind for a quick fix.
Assuming that the libraries to repair this in Sid are since updated and installable, the best bet is to boot an SD with a stable version of the Debian install, and mount a chroot of your encrypted system, from which you can apt update/apt upgrade - ultimately rebuilding your initrd and returning to a bootable state.
When the fix is for an issue that rebuilds initrd, it's also very important that your rescue SD have the same kernel version as your rescue target. With this debian installer, that should be no problem, if you didn't roll-your-own, and stuck with @danielt supplied kernel image.
The trick with this is manually unlocking the luks encrypted volume that your target system is on.
$ sudo cryptsetup luksOpen /dev/<blkdev+partnum>
This will do, if your device has been ID'd when udev started, and there's a corresponding link in /dev/mapper.
Otherwise, if your SD has Gnome Disks or gParted, you can open the encrypted volume with the GUI.
The rest will be regular chroot after mounting /dev/mapper/<cryptvolume> to /mnt, and 'mount -o bind' for /dev /dev/pts /sys and /proc to the corresponding chroot target filesysystem mount-points:
$ sudo mount /dev/mapper/<cryptvolume> /mnt/
$ sudo mount /dev/<CORRECT /BOOT VOLUME!!!!> /mnt/boot <--This is important. If any fix involves an updated initrd, then it must go to right FS!
$ sudo mount -o bind /dev /mnt/dev
$ sudo mount -o bind /dev/pts /mnt/dev/pts
$ sudo mount -t proc none /mnt/proc
$ sudo mount -t sysfs sys /mnt/sys
$ sudo chroot /mnt/ /bin/bash
# apt update && apt upgrade
If you're lucky, this will get fixed updates and set everything again right. Exit the chroot and unmount in reverse order.
Oh man, this seems gnarly. Given that I had barely any mods on the install itself (mesa-git, bluetooth from manjaro, and from testing->sid), I think I might be better off just re-installing, which seems like far less effort, given how simple the installer is. There was a time where I would actually do something like this, but I get the sense that this would be a mistake here, in terms of time tradeoff. Most of the relevant data for my home dir / configuration files were on an external SD anyways. That said, I would really like to get to the bottom of why this happened. I fear others' systems on sid may meet similar fates, given that I did not do much with the system and this happened.