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".
-----excerpt /var/log/messages --------
Jan 25 20:33:00 lisa2 kernel: (scsi0) <Adaptec AHA-294X Ultra SCSI host
adapter> found at PCI 11/0
Jan 25 20:33:00 lisa2 kernel: (scsi0) Wide Channel, SCSI ID=7, 16/255 SCBs
Jan 25 20:33:00 lisa2 kernel: (scsi0) Downloading sequencer code... 419
instructions downloaded
Jan 25 20:33:00 lisa2 kernel: scsi0 : Adaptec AHA274x/284x/294x
(EISA/VLB/PCI-Fast SCSI) 5.1.2/3.2.4
Jan 25 20:33:00 lisa2 kernel: <Adaptec AHA-294X Ultra SCSI host
adapter>
Jan 25 20:33:00 lisa2 kernel: scsi : 1 host.
Jan 25 20:33:00 lisa2 kernel: Vendor: QUANTUM Model: VIKING II 4.5WLS
Rev: 5520
Jan 25 20:33:00 lisa2 kernel: Type: Direct-Access
ANSI SCSI revision: 02
Jan 25 20:33:00 lisa2 kernel: Detected scsi disk sda at scsi0, channel 0, id
0, lun 0
Jan 25 20:33:00 lisa2 kernel: Vendor: QUANTUM Model: VIKING II 4.5WLS
Rev: 5520
Jan 25 20:33:00 lisa2 kernel: Type: Direct-Access
ANSI SCSI revision: 02
Jan 25 20:33:00 lisa2 kernel: Detected scsi disk sdb at scsi0, channel 0, id
1, lun 0
Jan 25 20:33:00 lisa2 kernel: Vendor: HP Model: T4000s
Rev: 1.08
Jan 25 20:33:00 lisa2 kernel: Type: Sequential-Access
ANSI SCSI revision: 02
Jan 25 20:33:00 lisa2 kernel: Vendor: TOSHIBA Model: CD-ROM XM-6401TA
Rev: 1009
Jan 25 20:33:00 lisa2 kernel: Type: CD-ROM
ANSI SCSI revision: 02
Jan 25 20:33:00 lisa2 kernel: Detected scsi CD-ROM sr0 at scsi0, channel 0,
id 5, lun 0
Jan 25 20:33:00 lisa2 kernel: (scsi0:0:0:0) Synchronous at 40.0 Mbyte/sec,
offset 8.
-----------------------------------------------------
Only problem is that it does not exist!!!! I tried mknod as "mknod -m 0660
sr0 b 5 0" but that just got back a "kernel does not recognise sr0 as a
block device" when tring to mount it. I tried a couple of other things with
about as much effect.
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. 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. :)
Thanks,
Paul Pettit | Opinions and advice expressed are from me
CTO | and are not my employer's.
Consistent Computer Bargains, Inc.
http://www.ccbnpts.com
If you had to identify, in one word, the reason the human race has not
achieved, and never will achieve, its full potential, that word would be:
"meetings." -- Dave Barry
p.s. I am cross posting because the last time I sent something to the
Linux-SCSI help list I got 0 (read zero) response. Thanks for understanding.
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
