On Tuesday 26 October 2004 9:21 pm, Ted Harding wrote:
This doesn't explain why it should happen when you just boot up normally. Maybe it's something to do with your recent upgrade, or maybe a hardware hiccup. Keep an eye on things!
I am sure you can run into issues with Lilo if something upgrades the kernel and Lilo isn't rerun to rebuild it's block pointer map thing.
It happened to me ages ago, SuSE (or more specifically YoU) expects you to be running Grub, so if it decides to replace the kernel image it doesn't bother to run Lilo afterwards. Due to some reason I can no longer fathom I was running Lilo on my old SuSE box and once after an update the machine refused to boot.