3 ms·
Yes, me! Just a few weeks ago my Thinkpad ran out of battery mid upgrade (`pacman -Syu`) and got corrupted so bad it caused a kernel panic right after the LUKS
by akiselev 5y ago
Yes, me! Just a few weeks ago my Thinkpad ran out of battery mid upgrade (`pacman -Syu`) and got corrupted so bad it caused a kernel panic right after the LUKS prompt. Only took an hour to boot into the live USB, chroot into the disk installation (`arch-chroot`, but don't forget to mount `/boot` afterwards!!!), and reinstall the entire OS with `pacman -Qqn | pacman --overwrite "*" -S -` followed by `pacman -Syyu` (to update bootloader, just in case).
Reinstalled the OS and didn't even have to restore a single dotfile.
Edit: You may have to update your live USB packages first so run `mount -o remount,size=4G /run/archiso/cowspace && pacman -Syu` (cowspace is a ramdisk so make sure you've got the memory)
Edit2: I really hoped "and didn't even have to restore a single dotfile" was enough of a clue that this was tongue-in-cheek. I migrated to Arch a few months ago after two decades of Windows so as far as OS reinstalls go, this was like Microsoft sending me a giant settlement check with triple damages.
- kyruzic 5y agoYou corrupted your kernel. Arch had nothing to do with that, and regardless of the os if you corrupt the kernel you need to reinstall.
- baq 5y agoWow. How’s that a reasonable answer? The OS did a very bad job at upgrading something that should be upgraded in an atomic fashion and blew up on both that and a failsafe boot to previous kernel. Neither should happen.
- kyruzic 5y agoUnplug a windows machine, or any os, while its updating and see what happens. Y
- walteweiss 5y agoHow do you corrupt your kernel? What leads to that?
- SilverRed 5y agoFedora silverblue can recover from this state. The kernel is just a file inside the OS image. If the latest OS image is corrupted due to a power failure, it will just boot the previous image which is still working.