or you could just configure the transfer rate to be one notch lower than
your current level. had to do that with my 4 U2W drives in a hotswap box
w/ a tekram dc390u2b (symbios chipset).
-s
Peter Pregler wrote:
>
> Hi,
>
> I had similar problems (actually your messages could be a cut-and-paste of
> my old logs) with my box at the beginning. The actual problems was that
> the scsi-bus did not fullfill the specifications. Replacing some hardware
> (hot-swap boxes) solved it. BTW, all worked well under DOS in the
> test-environment shipped. But as soon as linux got on the box and did
> _really_ use the bandwidth on the bus the troubles showed up (timeouts,
> renegotiation, slowdown ...).
>
> -Peter
>
> On 01-Feb-2000 Mike Black wrote:
> > Try turning off SYNC mode on ALL your drives in the SCSI BIOS. I had a
> > similar problem this last weekend with 2.2.14 and 5.1.21 AIC-7xxx and
> > async
> > mode fixed it. I had been previously running SYNC mode with no
> > problems,
> > but I added two new drives and couldn't get the mkraid to finish without
> > hitting the same errors you're seeing. All my drives are now running
> > async
> > and are happy. Slow, but happy. Previously (on 2.2.14 and prior) they
> > were
> > running happy in sync mode but I was upgrading this weekend and had to
> > do a
> > mkraid again (which really bangs the SCSI bus during resync). I tried
> > several times with different sync/async combos with no joy. I thought
> > this
> > was just my config on the one machine but, this morning I had a problem
> > on
> > another box which is a 3x50G 2940U2W setup. I accidentally left it NFS
> > mounted and during the attempted backup it also hit some SCSI timeouts
> > -- it
> > recovered though. This box has been flawless for a long time (I think
> > it
> > must've been the network I/O causing this -- no proof yet -- just
> > suspicion).
> >
> > Jan 28 08:47:57 medusa kernel: scsi : aborting command due to timeout :
> > pid
> > 248989, scsi0, channel 0, id 3, lun 0 Write (6) 19 f3 b4
> > 80 00
> > Jan 28 08:47:57 medusa kernel: scsi : aborting command due to timeout :
> > pid
> > 248991, scsi0, channel 0, id 5, lun 0 Write (6) 19 f3 b4
> > 80 00
> > Jan 28 08:47:57 medusa kernel: scsi : aborting command due to timeout :
> > pid
> > 248992, scsi0, channel 0, id 3, lun 0 Write (6) 19 f4 34
> > 04 00
> >
> >
> >
> > ________________________________________
> > Michael D. Black Principal Engineer
> > [EMAIL PROTECTED] 321-676-2923,x203
> > http://www.csihq.com Computer Science Innovations
> > http://www.csihq.com/~mike My home page
> > FAX 321-676-2355
> > ----- Original Message -----
> > From: "Rainer Mager" <[EMAIL PROTECTED]>
> > To: "Linux-RAID" <[EMAIL PROTECTED]>
> > Sent: Monday, January 31, 2000 9:07 PM
> > Subject: Argh, more problems with SCSI and RAID
> >
> >
> > Hi all,
> >
> > I'm trying to do 2 things with SCSI/RAID both of which are having
> > problems. Any help would be greatly appreciated. My system is 2.2.14
> > with
> > the 5.1.22 Adaptec AIC-7xxx drivers.
> >
> >
> > First, I'm trying to get 4 SCSI drives working. Forget RAID, forget
> > anything complex, I just want them working. I actually had 5 until
> > yesterday
> > when one decided to start making loud noises which I intrepreted as
> > death
> > throws. Anyway, the problem is that after I start up my 4 drives, at
> > some
> > point, I get this:
> >
> > Feb 1 02:48:01 dual kernel: scsi : aborting command due to timeout :
> > pid
> > 10920, scsi1, channel 0, id 0, lun 0 Read (6) 00 06 df 60 00
> > Feb 1 02:48:03 dual kernel: scsi : aborting command due to timeout :
> > pid
> > 10921, scsi1, channel 0, id 1, lun 0 Read (6) 00 07 c7 08 00
> > Feb 1 02:48:03 dual kernel: scsi : aborting command due to timeout :
> > pid
> > 10922, scsi1, channel 0, id 1, lun 0 Read (6) 00 07 d7 48 00
> >
> >
>
> -------------------------------
> Email: [EMAIL PROTECTED]
> WWW: http://www.risc.uni-linz.ac.at/people/ppregler
