Tape Drive won't work with Suse 8.0
Hi
I've got a IBM xSeries 225 with RAID 5i and a IBM DLT/VS Tape Drive.
As Operating System i've got Suse 8.0 with KDE installed.
Now here's my Problem: The Tape Drive is recognized by the RAID-Controller, but not by Suse. Tape Drive ist on SCSI BUS 2 ID 6. Some extracts from the console:
$ /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: IBM Model: SERVERAID Rev: 1.00
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi0 Channel: 00 Id: 15 Lun: 00
Vendor: IBM Model: SERVERAID Rev: 1.00
Type: Processor ANSI SCSI revision: 02
Host: scsi0 Channel: 01 Id: 08 Lun: 00
Vendor: IBM Model: 02R0980a S320 1 Rev: 1
Type: Processor ANSI SCSI revision: 02
Host: scsi0 Channel: 02 Id: 06 Lun: 00
Vendor: IBM Model: 02R0980a S320 1 Rev: 1
Type: Processor ANSI SCSI revision: 02
$ cdrecord -scanbus
Cdrecord 1.11a13 (i686-suse-linux) Copyright (C) 1995-2001 Jörg Schilling
Using libscg version 'schily-0.5'
scsibus0:
0,0,0 0) 'IBM ' 'SERVERAID ' '1.00' Disk
0,1,0 1) *
0,2,0 2) *
0,3,0 3) *
0,4,0 4) *
0,5,0 5) *
0,6,0 6) 'BNCHMARK' 'DLT1 ' '5032' Removable Tape
0,7,0 7) *
0,8,0 8) 'IBM ' '02R0980a S320 1' '1 ' Processor
0,15,0 15) 'IBM ' 'SERVERAID ' '1.00' Processor
$ lsmod
Module Size Used by Not tainted
nls_iso8859-1 2880 0 (autoclean)
ipv6 156928 -1 (autoclean)
isa-pnp 27656 0 (unused)
joydev 5792 0 (unused)
evdev 4000 0 (unused)
input 3168 0 [joydev evdev]
st 26452 0 (autoclean) (unused)
sg 24356 4 (autoclean)
usb-uhci 21988 0 (unused)
usbcore 57184 1 [usb-uhci]
bcm5700 64132 1
reiserfs 160576 1
ips 39968 6
$ mt -f /dev/st0 status
mt: /dev/st0: No such device
The Hardware should be ok (Device and cable have been changed, RAID-Controller/BIOS have newest Firmware und a IBM-Technician tried to fix it for 2.5 hours, seems to be a software problem) I've done a new Installation of Suse and set BIOS and RAID back to factory settings.. didn't help either.
One possibility may be an update of the LSI driver, I will test this soon.
Does anyone has a idea/suggestion? Could it be a problem with drivers that Suse uses? how can i check this?
thx
schaf
p.s. please explain in an easy way.. i'm quite new to linux.
|