[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Suggestion for Sarge Release Notes



Am Sonntag, 10. Juli 2005 00.38 schrieb Rohan Mars:
> Hi Again

Good morning

> > Can you explain _why_ lilo needs to be run during the upgrade?
>
> Initially, I was upgrading my VMWare woody dev boxes for testing. I had
> the problem that after the upgrade, the lilo boot loader (from what I have
> read the second stage) would get suck at "li". Normally, you would get
> "lilo:". After lots of re-imaging (VMWare is good for that) I solved the
> problem by reinstalling the kernel. I thought it was just a VMWare bug.
>
> Then I upgraded a real server and ran lilo at the end of the process.
> Rebooted and all was well. I did this because I was cleaning up the
> installed kernels. Then I upgraded a second server, but did not run lilo.
> Same thing. Stuck at "li". I had to use a recuse disk to mount the disk
> and run lilo. Once I did this the machine booted correctly.
>
> In my case I wasn't upgrading the kernel so no lilo command was run. It
> looks like the lilo version is upgraded in the Sarge update but the MBR
> has been generated off the old version (or something like that).

I want to second that.

When I installed Debian with a woody cd some days ago and then upgraded to 
sarge (without rebooting) I had the same problem.
After rebooting lilo stopped with "LI" and I then had to execute lilo from a 
knoppix chroot.

> I found the following link on the net which I eventually used to solve my
> problem:
>
> http://www.linuxquestions.org/questions/history/333584
>
> Kind Regards
>
> Rohan

griits
Mario



Reply to: