[NTLUG:Discuss] aic7xxx: infinite timed-out, ressetting on Red Hat install

[Mike]

Since I posted the initial message, I got some more info on Ultra160
drives. I didn't know this was a SCSI-3 drive. I am not sure what
support there is for this kind of drive. I think the problem might go
away if I just got an Ultra2 drive. I kind of just asked for "a SCSI
drive" from the people at Fry's, and they gave me a very nice one. But I
don't think I will, or even can, make use of 160 Mb/sec with the
hardware I have.

All along, I have just wanted to get this machine up and running on
Linux, bask in the light of the accomplishment, and then after the mail,
database, and web servers are all doing their thing, ...then get a finer
appreciation of all things SCSI. So I may just go back tomorrow and ask
for a more modest drive, and get on with it.

Kevin Brannen wrote:
> 
> Mike wrote:
> >
> > This is my first SCSI machine. I got a Micron NetFrame 3400, with a
> > Mylex RAID controller. According to Mylex, I learned that Red Hat will
> > boot on the RAID device only if there are 3 or fewer partitions. They
> > suggested adding another drive on the SCSI controller and installing the
> > OS on it. Then I could partition the RAID device and mount them
> > wherever. So I got a Seagate Barracuda 18 Gig ST318436LW Ultra 160 from
> > Fry's.
> 
> Internal or external?
> 
> >
> > I disabled the Adaptec bios for the RAID controller, as told by Micron.
> 
> That assumes you have E/IDE drives on your system too.  If you have
> only SCSI, I believe you'll need the BIOS turned on for ID-0.
> 
> >
> > Now, when the Red Hat installer tries to load the aic7xxx driver, it
> > just sits there. When I look on console 3, it says:
> 
> So Mylex emulates an Adaptec 29xx?  (I think that's the right mapping,
> but it's from memory.)
> 
> >
> > SCSI host 0 abort (PID 0) timed out - resetting
> >    SCSI bus is being reset for host 0 channel 0
> 
> I've gotten this before.  It's usually after I warm-boot after being
> in Windows (to play some special game, which is all it good for isn't
> it? :-) and Windows has left the SCSI card in some "weird" state.
> I've always been able to "fix" it by powering off the machine,
> counting to 5, then turning it back on so that it starts in a "good"
> state.
> 
> >
> > ...over and over on ad infinitum. Micron says that the hardware is set
> > up correctly, and that's it, good-bye.
> 
> Windows is actually good for something other than games occassionally;
> like testing.  Can it see the drive?
> 
> >
> > Now I haven't a clue. I have put the drive on the same cable as the tape
> > drive, and my understanding is that the tape drive provides proper
> > termination. I also bought a cable and terminator. I tried installing
> > the drive on the alternate LVDS controller as such, but got the same
> > result.
> >
> > I am at wits end. Anyone have any ideas?
> 
> SCSI problems are generally attributible to 3 things:
> 1. ID settings.
> 2. Termination.
> 3. Cables.
> 
> Make sure all SCSI devices on that controller are different, not set
> to 7, and that the controler is set to 7.  If an internal chain,
> triple check that only the last device (tape?) on the cable is
> terminated, and that none of the others are.  If external, make sure
> none of the devices are terminated, as there will be a terminator
> "plug" on the back of the external case.  Lastly, bad cables are
> sometimes a problem.
> 
> Also try to run the system with just the tape drive (was that how it
> was before or did you add them both?).  If it works that way, then the
> problem has something to do with the HD, i.e. it is conflicting with
> something.  Try running it with just the HD & not the tape device
> (after setting termination if internal).  This will help to clue you
> into if it's just the HD or a conflict between the HD & the tape.  You
> might also try getting it to work without RAID.
> 
> I really like SCSI devices, they generally aren't that hard to get
> working most of the time.
> 
> HTH,
> Kevin
> 
> _______________________________________________
> http://ntlug.org/mailman/listinfo/discuss