Waffelson@lemmy.world to linuxmemes@lemmy.world · 1 year agoWhat is the most difficult problem that you have fixed in linux?lemmy.worldimagemessage-square142fedilinkarrow-up11arrow-down10
arrow-up11arrow-down1imageWhat is the most difficult problem that you have fixed in linux?lemmy.worldWaffelson@lemmy.world to linuxmemes@lemmy.world · 1 year agomessage-square142fedilink
minus-squareNaz@sh.itjust.workslinkfedilinkarrow-up0·1 year agoFull kernel corruption after a botched sudo full-upgrade. I got the wonderful “bailing out you are on your own” shit as well. Read a guide online about a hail mary ext file system journal recovery protocol, I ran it, like most things without reading too deeply. Kernel was successfully repaired, Kubuntu kept on truckin’
minus-squareHadriscus@lemm.eelinkfedilinkarrow-up0·1 year agoWhat is this “bailing out you are on your own” shit ?
minus-squareshikitohno@lemmy.worldlinkfedilinkarrow-up0·1 year agoAn error message you can get if you really manage to mess things up. I got it once a few years ago.
minus-squareDefederateLemmyMl@feddit.nllinkfedilinkEnglisharrow-up0·1 year ago Full kernel corruption What does that even mean? Was the file system on which your kernel resided corrupt, or did something go wrong with a kernel upgrade/installation?
Full kernel corruption after a botched sudo full-upgrade.
I got the wonderful “bailing out you are on your own” shit as well.
Read a guide online about a hail mary ext file system journal recovery protocol, I ran it, like most things without reading too deeply.
Kernel was successfully repaired, Kubuntu kept on truckin’
What is this “bailing out you are on your own” shit ?
An error message you can get if you really manage to mess things up. I got it once a few years ago.
What does that even mean?
Was the file system on which your kernel resided corrupt, or did something go wrong with a kernel upgrade/installation?