Re: I/O errors with Dell PV122T Autoloader
Hi people,
Sorry my bad english, but my i have received the same messages like Tim, i have contacted Dell suport and first they update the driver, it seemed to correct these erros, but 2 weeks after the update, the messages start to happen again. I called again Dell support and report it to them, then they changed the PowerVault 110T, but it doesn't solved my problem.....what can i do ????....These erros doesn't occurs always, and every other day the backup funct. We have tested with many tapes, but the tapes seems ok. I don't know more what to do.....please...help me....thanks in advance!!!!!
Does anyone have any experience with a Dell PowerVault 122T Autoloader?
I'm trying to get one set up on a Dell PowerEdge 1750 server running
Sarge, but I'm getting I/O errors.
Here's what I've done so far:
1. I've confirmed that the o/s recognizes the autoloader. After a
reboot, a quick check of the syslog (/var/log/messages) shows the
following related to the Dell autoloader:
Jun 9 14:57:56 samba2 kernel: scsi1: scanning scsi channel 4 [P0] for
physical devices.
Jun 9 14:57:56 samba2 kernel: Vendor: DELL Model: PV22XS
Rev: E.17
Jun 9 14:57:56 samba2 kernel: Type: Processor
ANSI SCSI revision: 03
Jun 9 14:57:56 samba2 kernel: scsi1: scanning scsi channel 5 [P1] for
physical devices.
Jun 9 14:57:56 samba2 kernel: Vendor: DELL Model: PV-122T
Rev: K17r
Jun 9 14:57:56 samba2 kernel: Type: Medium Changer
ANSI SCSI revision: 02
Jun 9 14:57:56 samba2 kernel: Vendor: IBM Model: ULTRIUM-TD2
Rev: 53Y3
Jun 9 14:57:56 samba2 kernel: Type: Sequential-Access
ANSI SCSI revision: 03
Jun 9 14:57:56 samba2 kernel: Attached scsi generic sg0 at scsi0,
channel 0, id 0, lun 0, type 0
Jun 9 14:57:56 samba2 kernel: Attached scsi generic sg1 at scsi0,
channel 4, id 6, lun 0, type 3
Jun 9 14:57:56 samba2 kernel: Attached scsi generic sg2 at scsi1,
channel 0, id 0, lun 0, type 0
Jun 9 14:57:56 samba2 kernel: Attached scsi generic sg3 at scsi1,
channel 0, id 1, lun 0, type 0
Jun 9 14:57:56 samba2 kernel: Attached scsi generic sg4 at scsi1,
channel 4, id 6, lun 0, type 3
Jun 9 14:57:56 samba2 kernel: Attached scsi generic sg5 at scsi1,
channel 5, id 5, lun 0, type 8
Jun 9 14:57:56 samba2 kernel: Attached scsi generic sg6 at scsi1,
channel 5, id 6, lun 0, type 1
[....]
Jun 9 14:57:56 samba2 kernel: st0: try direct i/o: yes (alignment 512
B), max page reachable by HBA 1048575
If I run the command 'mt -f /dev/st0 status', I get this:
drive type = Generic SCSI-2 tape
drive status = 1107296256
sense key error = 0
residue count = 0
file number = 0
block number = 0
Tape block size 0 bytes. Density code 0x42 (unknown).
Soft error count since last status=0
General status bits on (41010000):
BOT ONLINE IM_REP_EN
Next, if I try to run 'mt -f /dev/st0 erase' I end up getting an I/O
error after ~10-15 minutes of erasing ('mt: /dev/st0: Input/output
error' is the exact error reported on the commandline), and this shows
up in the syslog:
Jun 9 15:22:42 samba2 kernel: st0: Error 400f3 (sugg. bt 0x0, driver bt
0x0, host bt 0x4).
I contacted Dell about the error messages and their Linux support group
seemed flustered because it was Debian and not SuSE or Red Hat.
Anyone here have any idea what's going on with this issue? My first
thought is that it's a driver issue of some sort, but I haven't gone
down the path of tweaking anything with the kernel yet. I'm comfortable
doing custom kernels, so if that's the solution with this autoloader, I
can handle it. I would appreciate, though, if someone would point in
the right direction as far as what I need to set up in the kernel.
Any help is greatly appreciated!
Tim
Reply to: