Skip to contentSkip to conversation

/dev/[*]st* does not work with EXBAYTE 8505 with 2.6 kernels

DISCUSSION John Damm Sørensen 2 participants 5 messages Aug 25, 2004 SCSI

lore
Share & tools
lore
#0 lore raw

I have just upgraded from RH9 Linux 2.4 to FC2 Linux 2.6 and now my EXABYTE 8505 no longer works.

If I try to access it with mt (using any device like nst0) I get no such device error message. Same thing with stinit.

The tape drive is found during boot, as this snippet from dmesg shows:
qla1280: QLA12160 found on PCI bus 1, dev 8
ACPI: PCI interrupt 0000:01:08.0[A] -> GSI 11 (level, low) -> IRQ 11 scsi(1): Reading NVRAM
qla1280_isr(): index 1 asynchronous BUS_RESET qla1280_isr(): index 0 asynchronous BUS_RESET
scsi(1:0): Resetting SCSI BUS
scsi(1:1): Resetting SCSI BUS
scsi1 : QLogic QLA12160 PCI to SCSI Host Adapter

       Firmware version: 10.04.32, Driver version 3.24.3

Vendor: EXABYTE Model: EXB-85058SQANXR0 Rev: 0808
Type: Sequential-Access ANSI SCSI revision: 02
scsi(1:0:4:0): Sync: period 50, offset 14

cat of /proc/scsi/scsi also shows the tape device:
Attached devices:
Host: scsi0 Channel: 00 Id: 02 Lun: 00
Vendor: COMPAQ Model: ST34371W Rev: 0682
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi0 Channel: 00 Id: 04 Lun: 00
Vendor: SEAGATE Model: ST39103LW Rev: 0002
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi1 Channel: 00 Id: 04 Lun: 00
Vendor: EXABYTE Model: EXB-85058SQANXR0 Rev: 0808
Type: Sequential-Access ANSI SCSI revision: 02

lsmod seems to contain the necessary driver modules as well:

Module                  Size  Used by
st                     30429  0
qlogicfas408            6473  0
parport_pc             21249  1
lp                      9133  0
parport                35977  2 parport_pc,lp
md5                     3905  1
ipv6                  217349  16
autofs4                20677  0
sunrpc                141861  1
iptable_filter          2369  0
ip_tables              13889  1 iptable_filter
3c59x                  33385  0
dm_mod                 47317  0
button                  4825  0
battery                 7117  0
asus_acpi               9177  0
ac                      3533  0
ext3                   96937  4
jbd                    66521  1 ext3
qla1280                81997  0
sd_mod                 17473  5
scsi_mod              105360  3 st,qla1280,sd_mod

Any hints?
Please don't tell me that the 8505 is no longer supported.

Cheers
John

#1 lore raw

I am moving this thread to linux-scsi where it belongs.

Quoted 6 lines · John Damm Sørensen

I have just upgraded from RH9 Linux 2.4 to FC2 Linux 2.6 and now my EXABYTE 8505 no longer works.

If I try to access it with mt (using any device like nst0) I get no such device error message. Same thing with stinit.

This suggests that the st driver has not found your drive. Your tape drive is recognized as a sequential-access device and lsmod shows that st is loaded. Puzzling.

If you look at the kernel messages, do you see something like this:

st: Version 20040403, fixed bufsize 32768, s/g segs 256 Attached scsi tape st0 at scsi0, channel 0, id 5, lun 0
st0: try direct i/o: yes (alignment 512 B), max page reachable by HBA 268435455

Another thing to check is /sys/class/scsi_tape/. You should see these
files: nst0 nst0a nst0l nst0m st0 st0a st0l st0m

...

Quoted 3 lines

Any hints?
Please don't tell me that the 8505 is no longer supported.

Any well-behaving drive is supported. I have used EXB8505 some years ago and I don't think this problem has anything to do with the drive.

Signature · 5 lines
Kai
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
#2 lore raw
Quoted 15 lines

I am moving this thread to linux-scsi where it belongs.

Quoted 6 lines · John Damm Sørensen

I have just upgraded from RH9 Linux 2.4 to FC2 Linux 2.6 and now my EXABYTE 8505 no longer works.

If I try to access it with mt (using any device like nst0) I get no such device error message. Same thing with stinit.

This suggests that the st driver has not found your drive. Your tape drive is recognized as a sequential-access device and lsmod shows that st is loaded. Puzzling.

Quoted 6 lines

If you look at the kernel messages, do you see something like this:

st: Version 20040403, fixed bufsize 32768, s/g segs 256 Attached scsi tape st0 at scsi0, channel 0, id 5, lun 0
st0: try direct i/o: yes (alignment 512 B), max page reachable by HBA 268435455

Yes, I see this message in dmesg.

Quoted 4 lines

Another thing to check is /sys/class/scsi_tape/. You should see these
files: nst0 nst0a nst0l nst0m st0 st0a st0l st0m

These device files are also present.

Quoted 6 lines

...

Quoted 3 lines

Any hints?
Please don't tell me that the 8505 is no longer supported.

Any well-behaving drive is supported. I have used EXB8505 some years ago and I don't think this problem has anything to do with the drive.

I have also used this drive for a year or two now. Initially with 2.4 I had problems with compression, but that was solved with new firmware that defaults to compression.

With 2.6 the tape drive fails to work with the Qlogic HBA's ISP1040 (the HBA simply doesn't work with 2.6) and QLA12160, but it works with the Symbios/LSI HBA.

/john

Quoted 4 lines

--
Kai

Signature · 6 lines
John Damm Sørensen, Stenkrogen 6, 2800 Kgs. Lyngby, +45 4498 6995

-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
#3 lore raw

On Wed, 25 Aug 2004, John Damm Sørensen wrote:

...

Quoted 9 lines
Quoted 6 lines

If you look at the kernel messages, do you see something like this:

st: Version 20040403, fixed bufsize 32768, s/g segs 256 Attached scsi tape st0 at scsi0, channel 0, id 5, lun 0
st0: try direct i/o: yes (alignment 512 B), max page reachable by HBA 268435455

Yes, I see this message in dmesg.

OK, st has attached the drive.

...

Quoted 4 lines

With 2.6 the tape drive fails to work with the Qlogic HBA's ISP1040 (the HBA simply doesn't work with 2.6) and QLA12160, but it works with the Symbios/LSI HBA.

So, the problem is specific to the Qlogic adapters. Do you see any SCSI error messages? (When st has attached the drive, the device should be present. If it is offlined by failing SCSI error recovery, the device disappears again.)

Signature · 5 lines
Kai
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
#4 lore raw
Quoted 22 lines · Kai Makisara

On Wed, 25 Aug 2004, John Damm Sørensen wrote:

...

Quoted 12 lines
Quoted 8 lines

If you look at the kernel messages, do you see something like this:

st: Version 20040403, fixed bufsize 32768, s/g segs 256 Attached scsi tape st0 at scsi0, channel 0, id 5, lun 0
st0: try direct i/o: yes (alignment 512 B), max page reachable by HBA 268435455

Yes, I see this message in dmesg.

OK, st has attached the drive.

...

Quoted 10 lines
Quoted 6 lines

With 2.6 the tape drive fails to work with the Qlogic HBA's ISP1040 (the HBA simply doesn't work with 2.6) and QLA12160, but it works with the Symbios/LSI HBA.

So, the problem is specific to the Qlogic adapters. Do you see any SCSI error messages? (When st has attached the drive, the device should be present. If it is offlined by failing SCSI error recovery, the device disappears again.)

No, I see no error messages with QLA12160 HBA everything seems to be OK, except that I cannot access the device. I am able to access /proc/scsi/sg/device_strs and read the device string for the tape. As for the ISP1040 the qlogicisp driver simply prevents the system from mounting the root fs, even though the fs resides on an IDE disk. BTW. The QLA1260 is now being used in my PS with WIN98 and seem to work OK with a SCSI disk.
/John

Signature · 6 lines
John Damm Sørensen, Stenkrogen 6, DK-2800 Kgs. Lyngby, 4498 6995

-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html