Topic: Recover from failed update - kernal panic

[Paperguides]

I have just applied the latest update to my server (8.0) and on reboot I get:

Unable to load SELinux Policy.  Machine is in enforcing mode. Haulting now.
Kernal Panic : not syncing. Attempting to halt init!

Research suggest the kernal update failed.  How can I recover to a working server?

Thanks,

tony

[janet]

Paperguides

Boot up in rescue mode.
Check installed rpm versions against what should be installed ie versions in the updates repo.
/sbin/e-smith/audittools/newpms

Report a bug as upgrades should work correctly

[CharlieBrady]

I have just applied the latest update to my server (8.0) and on reboot I get:

Unable to load SELinux Policy.  Machine is in enforcing mode.

The system should not be booting in SElinux enforcing mode. The kernel command line should say "selinux=0". If it doesn't, you can add that interactively, starting by typing 'a' at the right time during the boot sequence. Someone else here (or google) can probably find you documentation on how to do that.

Once you disable selinux, the boot should get further, and you can make a more permanent solution to the problem.

Alternatively, you could boot in rescue mode from the CDROM, then do "chroot /mnt/syslinux' when prompted, and then 'pico /etc/grub.conf' to edit the grub file. Then 'exit' and 'exit' to reboot.

But there is still a mystery as to why your system is in this state. Nobody else has ever encountered that.

[Paperguides]

That fixed if it so I now have a 'working' system.  I've logged bug (8217).

There was no line in the grub.conf file about selinux.

Having looked at newrpms and other logs, based on the dates I found I'm pretty certain it wasn't a kernal update that caused the problem.

Thanks for the advice.