Re: Problem Booting After Install

[Kent West <westk@acu.edu>]

Scott MacMaster wrote:

> ----- Original Message ----- 
> From: "Kent West" <westk@acu.edu>
> To: "debian-user" <debian-user@lists.debian.org>
> Sent: Wednesday, May 28, 2003 12:35 PM
> Subject: Re: Problem Booting After Install
>
>
>  
>
> > Scott MacMaster wrote:
> >
> >    
> >
> > > > > I was able to view the contents of lilo.conf.  Here are the contents
> > > > >
> > > > >
> > > > > lba32
> > > > > boot=/dev/hdb1
> > > > > root=/dev/hdb1
> > > > > install=/boot/boot-menu.b
> > > > > map=/boot/map
> > > > > delay=20
> > > > > vga=normal
> > > > > default=Linux
> > > > > image=/vmlinuz
> > > > >     label=Linux
> > > > >     read-only
> > > > > image=/vmlinuz.old
> > > > >     label=LinuxOLD
> > > > >     read-only
> > > > >     optional
> > > > >
> > > > >
> > > > >          
> > > This is the output lilo gives:
> > >
> > > Warning: /dev/hdb1 is not on the first disk
> > > Added Linux *
> > > Skipping /vmlinuz.old
> > >
> > > However, it still doesn't work.  After the screen goes blank this is the
> > > output I get (when I try to boot off the hd).
> > >
> > > MBR
> > >
> > > L 01 01 01...
> > > 01 01 01...
> > > 01 01 01...
> > > 01 01 01...
> > > .
> > > .
> > > .
> > >
> > >      
> > >
> > >      
> > Try changing the line:
> >
> > boot=/dev/hdb1
> >
> > to
> > boot=/dev/hdb
> >
> > and rerun lilo.
> >    
>
> This didn't work.  I got the same results as before, except it's displaying
> 40 instead of 01.
>
>  
Can your BIOS boot off the slave of the primary controller? I assume it 
can, since you're getting partial results, but still, had to ask.

Has this disk every been "infected" with any non-standard boot loaders, 
like a boot sector virus, or like Bootworks (from Altiris), etc?

You might try "install-mbr /dev/hdb", although I don't really understand 
the ins-and-outs of this utility (see "man install-mbr"), so I'm not 
sure what the result will be. Still, I'd try it.

--
Kent