[nSLUG] Boot problem

Donald Teed dteed at artistic.ca
Wed Jan 28 07:49:03 AST 2004

You've done a thorough job of troubleshooting this one.

My only idea is that if you did the rerun of lilo from
the chroot on the P133, try it again from a rescue CD
and the PII.  It looks like you tried that and this
failed.  That is a clue I guess.  If the chipset on the
boards effects the way the geometry is seen, then this might
be an essential step.  Also, try explicitly listing lba32
in the lilo.conf if you didn't already do that.

An off hand idea, but if the PII machine's chipset 
is somehow not well supported by the kernel on
your rescue CD, it might be giving you problems.
Try an alternate rescue CD.  Gentoo makes a decent
Live CD these days with plenty o' tools.

On Wed, 28 Jan 2004, Mike Spencer wrote:

> So I installed Slackware 8.0/2.4 kernel on a P133 on a new 20G HD.
> Some hassles with X but eventually got it sorted out.  Boots cleanly,
> X, emacs, Gimp, PPP dialup all work fine.
> So I removed the HD from the P133 and put it into a PII (replacing
> another HD as hda).  Nothing I know how to do will get it to boot in
> the PII.  The PII still boots fine from its original HD if I swap it
> back in.  The Slackware HD will mount and is readable as hdb if
> installed as the primary slave in the PII.  If I put it back into the
> P133, it boots fine once again.
>   # Got the HD jumpers right: check
>   # Got /etc/fstab right: As sure as I can be
>   # Boot off a  rescue disk and do 
>         chroot /mnt/new-hd /sbin/lilo -l -b /dev/hda
>     check
> The PII CMOS seems to correctly recognize the new HD (or both if
> they're both installed.)
> The only clues I have are:
> +    lilo complains about sectors greater than 1024 and aborts if I
>      run lilo when the hd is installed in the PII.  Adding "linear" or
>      -l causes it to warn but execute.  No abort or warning when
>      installed in the P133.  lilo just does its thing.
> +    The boot failure occurs after  "LILO" and the "boot: linux"
>      prompt.  An error message flickers too fast too see that looks
>      like "Error 0x48".
> Both HDs are Maxtor 20G but not identical models.  Both are relatively
> new and lightly used.
> Any pointers welcome.  Very welcome. 
> - Mike
> -- 
> Michael Spencer                  Nova Scotia, Canada       .~. 
>                                  (902) 543-8375            /V\ 
> mspencer at tallships.ca                                     /( )\
> http://home.tallships.ca/mspencer/                        ^^-^^
> _______________________________________________
> nSLUG mailing list
> nSLUG at nslug.ns.ca
> http://nslug.ns.ca/cgi-bin/mailman/listinfo/nslug

More information about the nSLUG mailing list