Tom Oehser wrote:

> > > Without realizing I needed a "boot" disk, as well as the
> > > emergency disk, I allowed Windows to blow away my mbr.  My
> > > Linux is on sdb1, by itself, WIN is on sda1 by itself. Now
> > > I got tomsrtbt as someone advised here, and it boots up,
> > > but I can't even seem to see sdbx. or mount it, or anything.
> > > But it looks like it sees sda, so the scsi driver must work.
> > > (Scsi card is Adaptec 2940.)  How can I troubleshoot/fix
> > > this?  A simple, fool-proof, step-by-step instruction
> > > would help.  BTW, the machine is all scsi. TIA--doug
>
> Start with 'cat /proc/scsi/scsi'.
> Then 'fdisk -l' or 'fdisk -l /dev/sdb'.
>
> My first guess is that you may have linux on the first extended logical
> partition, sdb5, not sdb1.  If sda and sdb are on the same controller, and
> sda works, then forget scsi issues...
>
> > step would be to make sure that you can get to the drives.  I have not
> > had to do this with a scsi drive and don't remember off hand what tom's
> > does to mount hard drives.  Fist look to make sure the card is seen.
>
> tomsrtbt does nothing.  You must do all mounts manually.
>
> > My guess is that you will need to load the module for the adaptec card.
> > It looks like it is the aic7xxx.o.Check to see if it is loaded first:
>
> tomsrtbt always attempts to load an aic7xxx module on bootup.
>
> > OK so far?  Now we get even more over my head.  The issue I am uncertain
> > about is whether or not lilo needs to have a device mounted inorder to
> > install itself.  I am assumming that it needs to be installed on the
> > first scsi device where your windows lives.  Makes sense to me or windows
> > will continue to load first.  If your setup was working it looks like to
> > me from the lilo docs that doing a
> >
> > lilo -r /linux -v
>
> No.  This is the wrong way to do it.  You are likely to get a version
> conflict as you will be running the lilo executable on tomsrtbt against
> the boot.b file on your system.  The correct way is:
>
>         chroot /linux /sbin/lilo
>
> which will run your system's lilo as it normally would be run.
>
> > will chroot to your newly mounted linux partition and then do the lilo
> > thing.  as I said, I just don't know for sure what mbr lilo will write
> > to.  I don't have time to read the docs but am curious.
>
> It will do the correct expected thing as far as which mbr, that is, as
> specified in the lilo.conf file.  Of course, if the devices changed, you
> may have to edit /linux/etc/lilo.conf.
>
> -Tom

Thanks for the clarifications, Tom.  I have not felt comfortable since I sent
the note since I was doing it all from memory and guess work.  I try not to
respond to emails unless I either know what I am doing pretty well or no one
else is trying to help. Tom's boot disk is way cool BTW.  How big of a deal is
it to install ssh client on it so i can get to another machine on my network
to look at something?


Bret


-- 
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.

Reply via email to