I have two systems lately that after updating with Discover have lead to an unbootable system (Kernel panic - not syncing: Attempted to kill init! exit code=0x00000200). After much searching, I have not able to repair this.
One of these system just had KDE Neon 5.27 installed about two weeks about and an attempt to update it a week ago. I have not done anything with this system since (at the time I just booted an older Neon 20.04 that was installed on another partition).
The other system (my primary computer), same thing happened today after doing an update. The latest Neon was installed on this computer last weekend. I finally got it stable two days ago (after replacing the nouveau with the nvidia drivers because it kept freezing with nouveau). The reason for reinstalling Neon on this system was due to another failed update. Previously Neon 20.04 was installed and I attempted to apply all outstanding 20.04 updates (it had been a while). It was doing a lot of work updating and was hitting the CPU pretty hard (it was updating during the boot procedure). This [old] computer has a problem where it’s CPU (a 10-year old AMD FX-6300) just shuts off when it gets too hot for too long. Well this occurred during the update, and would not boot after being powered back on. I was not able to repair and concluded it was not repairable, hence installing Neon 22.04.
Are there any solutions for the kernel panic before I just install from scratch, again?
My wife’s computer also failed during the update from 20.04 to 22.04 though the result was a completely different error. I just installed Neon 22.04 after 15 minutes of trying to repair it.
On yet another computer (used for work) failed when updating 18.04 to 20.04 (was on 18.04 because the older GCC-6 was needed). I thought there would have no issues updating since I had just updated another Neon 18.04 to 20.04 used for work that was in a VM (on Windows) and there were no issues.