Hi
I've run into a nasty problem with kernel panic during boot. I did a fresh installation of F18 last Wednesday and it was a smooth experience, but then yesterday I did a 'yum update' that ended up causing a kernel panic (there wasn't much more happening on the machine at that time) and after that the boot process always terminates in a kernel panic almost immediately after the password for disc encryption has been given. It gives exit code 0x00007F00. I've got two kernel versions to choose from, 3.6.10-4 and 3.7.2.-201, same result with both.
What now, how can I repair the system?
/Markus
On Mon, Jan 21, 2013 at 19:59:30 +0100, Markus Lindholm markus.lindholm@gmail.com wrote:
What now, how can I repair the system?
Normally, you want to reboot with the previous kernel.
Am 21.01.2013 20:01, schrieb Bruno Wolff III:
On Mon, Jan 21, 2013 at 19:59:30 +0100, Markus Lindholm markus.lindholm@gmail.com wrote:
What now, how can I repair the system?
Normally, you want to reboot with the previous kernel
you missed "I've got two kernel versions to choose from, 3.6.10-4 and 3.7.2.-201, same result with both." which means it is not the kernel
there was a systemd upgrade at weekend and "immediately after the password for disc encryption" amkes it most likely here is the problem
some years ago you had the possibility to boot from install DVD in rescue mode and "chroot /sysimage" but these days all this extended options seems to go away or perfectly hidden
Reindl Harald writes:
some years ago you had the possibility to boot from install DVD in rescue mode and "chroot /sysimage" but these days all this extended options seems to go away or perfectly hidden
I'm pretty sure that the F18 install image has a boot option for rescue mode that'll automount everything and give you a shell.
On 22 January 2013 01:22, Sam Varshavchik mrsam@courier-mta.com wrote:
Reindl Harald writes:
some years ago you had the possibility to boot from install DVD in rescue mode and "chroot /sysimage" but these days all this extended options seems to go away or perfectly hidden
I'm pretty sure that the F18 install image has a boot option for rescue mode that'll automount everything and give you a shell.
I could always remove the SSD from the crashed system and mount it on a different machine. But any ideas what to do then? Replacing systemd with an earlier version? And what could have been the reason for the kernel panic in the first place? An unfortunate race condition during 'yum update' that I just happened to run into? Some unfortunate combination of services and configuration?
/Markus