and finally rebooted into Feisty - where the failed kernel update repeated itself. Fortunately, I could still work on the problem because the system hadn't been rebooted.
This time, I solved the problem by removing a section of my lilo.conf file corresponding to a windows boot. I am not sure why the windows section was there (perhaps as a courtesy?) because I didn't add it (when I want to boot from windows, I just select the windows boot device from BIOS). In fact, I have never touched the lilo.conf file before today.
In any case, I think the lilo configuration was no longer valid because the order of the drives (as reported by BIOS?) was changed between kernel updates - possibly relating to an issue documented in bug #8497.
Anyway, good news today. So until next time - hope NOT to see you so soon.
Problem solved (again)
I used the liveCD from Gutsy to boot, and re-assembled the array using info from this page:
http:// ubuntuforums. org/showthread. php?t=408461
mounted the volume and then ran lilo following some information I found here:
http:// www.syrlug. org/contrib/ boot-loaders. html#LILO
and finally rebooted into Feisty - where the failed kernel update repeated itself. Fortunately, I could still work on the problem because the system hadn't been rebooted.
This time, I solved the problem by removing a section of my lilo.conf file corresponding to a windows boot. I am not sure why the windows section was there (perhaps as a courtesy?) because I didn't add it (when I want to boot from windows, I just select the windows boot device from BIOS). In fact, I have never touched the lilo.conf file before today.
In any case, I think the lilo configuration was no longer valid because the order of the drives (as reported by BIOS?) was changed between kernel updates - possibly relating to an issue documented in bug #8497.
Anyway, good news today. So until next time - hope NOT to see you so soon.