Paul Pettit wrote:
>
> Hey all,
>
> This one has me stumped.
> Just built a brand new all SCSI machine but during install couldn't get the
> installer to go into second level using the SCSI CDROM. Ended up using a IDE
> one to complete the install but I really wanted to use the SCSI one. So I
> figured that I would chase down the problem after the install was done.
>
> After re-installing the scsi CDROM and starting it up I saw the aic7xxx
> driver see everything just fine?!?! So I tested to see if I could mount the
> CDROM but found that /dev/cdrom was pointing to /dev/hdc (the IDE CDROM now
> gone). OK, I thought and poked around, tried accessing scd0-7 and locked up
> the box once or twice (over confidence will be the death of me). Then went
> looking for clues in the boot up messages. Come to find out that the driver,
> at boot, labels the scsi CDROM as "SCSI device sr0".
It doesn't matter, scd0 is still the correct device to try and open.
> Everything else works fine. Well almost. There seems to be one other oddity
> in that when I access the T4i the 2940 (I assume) goes a little spastic:
> ------another excerpt from /var/log/messages-------
> Jan 25 20:34:49 lisa2 kernel: scsi : aborting command due to timeout : pid
> 3963, scsi0, channel 0, id 0, lun 0 Write (6) 04 70 2a 02 00
> Jan 25 20:34:49 lisa2 kernel: scsi : aborting command due to timeout : pid
> 3964, scsi0, channel 0, id 0, lun 0 Write (6) 05 30 2a 02 00
> Jan 25 20:34:49 lisa2 kernel: scsi : aborting command due to timeout : pid
> 3965, scsi0, channel 0, id 0, lun 0 Write (6) 05 f0 1c 02 00
> Jan 25 20:35:09 lisa2 kernel: scsi : aborting command due to timeout : pid
> 3966, scsi0, channel 0, id 1, lun 0 Write (10) 00 00 5e e5 c4 00 00 02 00
> Jan 25 20:35:09 lisa2 kernel: scsi : aborting command due to timeout : pid
> 3963, scsi0, channel 0, id 0, lun 0 Write (6) 04 70 2a 02 00
> Jan 25 20:35:09 lisa2 kernel: scsi : aborting command due to timeout : pid
> 3964, scsi0, channel 0, id 0, lun 0 Write (6) 05 30 2a 02 00
> Jan 25 20:35:09 lisa2 kernel: scsi : aborting command due to timeout : pid
> 3965, scsi0, channel 0, id 0, lun 0 Write (6) 05 f0 1c 02 00
> Jan 25 20:35:14 lisa2 kernel: scsi : aborting command due to timeout : pid
> 3967, scsi0, channel 0, id 1, lun 0 Write (10) 00 00 5e e3 0a 00 00 02 00
> Jan 25 20:35:29 lisa2 kernel: scsi : aborting command due to timeout : pid
> 3966, scsi0, channel 0, id 1, lun 0 Write (10) 00 00 5e e5 c4 00 00 02 00
> Jan 25 20:35:29 lisa2 kernel: scsi : aborting command due to timeout : pid
> 3963, scsi0, channel 0, id 0, lun 0 Write (6) 04 70 2a 02 00
> --------------------------------------------------------------
> Seems it (RH) is tring to write to sda and sdb but can't. This only happened
> when I gave a "mt -f /dev/st0 retension" command so I can only guess what
> will happen durring a backup.
This is perfectly normal if either A) you don't have disconnection enabled on
that device in the Adaptec BIOS setup area or B) the device doesn't bother to
disconnect from the SCSI bus during lengthy operations (such as a retension).
You can fix A by changing the Adaptec BIOS setting, you can fix B by getting a
new tape drive.
> Weird thing is that after the command ends
> everything goes back to "normal" and RH operates as if nothing happend.
>
> Hardware info:
> Acer AX6B 440LX mb
> PII 350
> AHA-2940UW using both internal connections, 2 x 4.5 SCSI HDD on the UW, a
> T4i and the CDROM on the other
> RH5.2
>
> So is the problem the driver?
> Does it have a problem handling the Ultra and UltraWide ports at the same
> time? How do I fix this?
> Is there a newer aic7xxx driver for RHL?
> Or is this hardware related? Everthing is new except the T4i, and all are on
> the "compatible" list (I think).
> I'm not new to Linux but this is my first *real* crack at a near 100% scsi
> box so I hope someone can enlighten me. :)
Also note that this is an Ultra SCSI bus you are running here, and cable
length could become an issue (the maximum end to end length allowed by the
spec for Ultra SCSI speeds in SE mode is 1.5m).
--
Doug Ledford <[EMAIL PROTECTED]>
Opinions expressed are my own, but
they should be everybody's.
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
