Early EOF writing to Exabyte EXB-8200 tape
Scott Blachowicz
sure I made it since I haven't seen it back]
Hi-
I had this problem doing dumps (or tars or whatever) to an old Exabyte
8200 tape drive that I've got hooked up to my FreeBSD 3.2R system via a
Symbios 875 based SCSI card and the "sym" driver. I got a new cleaning
cartridge, ran it through a couple times, then did a backup to a new
tape. That worked fine a month or two ago. Lately, it just dies with a
write error (or dump reports "end of tape") near the beginning. So, I
acquired another tape drive and I get the same behavior...so now I wonder
if it was really the tape drive. Any suggestions on what to do now?
My current 'dmesg' output:
sym0: <875> rev 0x03 int a irq 5 on pci0.9.0
sym0: Symbios NVRAM, ID 7, Fast-20, SE, parity checking
sym0: open drain IRQ line driver, using on-chip SRAM
...
Waiting 15 seconds for SCSI devices to settle
(noperiph:sym0:0:-1:-1): SCSI BUS reset delivered.
sa0 at sym0 bus 0 target 3 lun 0
sa0: <EXABYTE EXB-8200 2618> Removable Sequential Access SCSI-CCS device
sa0: 3.300MB/s transfers
changing root device to wd0s1a
cd0 at sym0 bus 0 target 2 lun 0
cd0: <TOSHIBA CD-ROM XM-3501TA 3054> Removable CD-ROM SCSI-2 device
cd0: 4.237MB/s transfers (4.237MHz, offset 16)
cd0: cd present [322167 x 2048 byte records]
da0 at sym0 bus 0 target 1 lun 0
da0: <QUANTUM EMPIRE_1400S 1200> Fixed Direct Access SCSI-2 device
da0: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled
da0: 1335MB (2734996 512 byte sectors: 255H 63S/T 170C)
WARNING: / was not properly dismounted
cd1 at sym0 bus 0 target 6 lun 0
cd1: <PIONEER CD-ROM DRM-602X 2905> Removable CD-ROM SCSI-2 device
cd1: 5.000MB/s transfers (5.000MHz, offset 16)
cd1: cd present [327576 x 2048 byte records]
cd2 at sym0 bus 0 target 6 lun 1
cd2: <PIONEER CD-ROM DRM-602X 2905> Removable CD-ROM SCSI-2 device
cd2: 5.000MB/s transfers (5.000MHz, offset 16)
cd2: cd present [316663 x 2048 byte records]
cd3 at sym0 bus 0 target 6 lun 2
cd3: <PIONEER CD-ROM DRM-602X 2905> Removable CD-ROM SCSI-2 device
cd3: 5.000MB/s transfers (5.000MHz, offset 16)
cd3: cd present [243064 x 2048 byte records]
cd4 at sym0 bus 0 target 6 lun 3
cd4: <PIONEER CD-ROM DRM-602X 2905> Removable CD-ROM SCSI-2 device
cd4: 5.000MB/s transfers (5.000MHz, offset 16)
cd4: cd present [238314 x 2048 byte records]
cd5 at sym0 bus 0 target 6 lun 4
cd5: <PIONEER CD-ROM DRM-602X 2905> Removable CD-ROM SCSI-2 device
cd5: 5.000MB/s transfers (5.000MHz, offset 16)
cd5: cd present [292546 x 2048 byte records]
cd6 at sym0 bus 0 target 6 lun 5
cd6: <PIONEER CD-ROM DRM-602X 2905> Removable CD-ROM SCSI-2 device
cd6: 5.000MB/s transfers (5.000MHz, offset 16)
cd6: Attempt to query device size failed: NOT READY, Medium not present
sa1 at sym0 bus 0 target 4 lun 0
sa1: <EXABYTE EXB-8200 425A> Removable Sequential Access SCSI-CCS device
sa1: 3.300MB/s transfers
da1 at sym0 bus 0 target 5 lun 0
da1: <CDC 94191-15 0136> Fixed Direct Access SCSI-CCS device
da1: 3.300MB/s transfers
da1: 633MB (1296645 512 byte sectors: 64H 32S/T 633C)
(noperiph:sym0:0:-1:-1): SCSI BUS reset detected.
(noperiph:sym0:0:-1:-1): SCSI BUS reset detected.
(sa1:sym0:0:4:0): phase change 2-3 10@07d55c9c resid=9.
(sa1:sym0:0:4:0): READ POSITION. CDB: 34 1 0 0 0 0 0 0 0 0
(sa1:sym0:0:4:0): ILLEGAL REQUEST
(sa1:sym0:0:4:0): WRITE(06). CDB: a 0 0 80 0 0
(sa1:sym0:0:4:0): ILLEGAL REQUEST info?:ffffff
(noperiph:sym0:0:-1:-1): SCSI BUS reset detected.
Thanx,
--
Scott Blachowicz
Scott Blachowicz
Scott> I had this problem doing dumps (or tars or whatever) to an old Exabyte
Scott> 8200 tape drive that I've got hooked up to my FreeBSD 3.2R system via a
Scott> Symbios 875 based SCSI card and the "sym" driver.
Some more data...I upgraded my "sym" SCSI driver from 1.3.2-20000206 to
1.5.0-20000421, but still have problems. I unwrapped a new tape and put
it in the newly acquired drive and was able to do a "gtar" backup to it
until it really DID run out of tape. After that, I rewound the tape and
tried to do a "dump" to it, but just kept getting that "end of media" type
of error. So, I popped the tape out and put it in the original drive and
got the dump to work. Then, I unwrapped another new tape and tried to do
a backup to it, but kept getting EOT errors out of both tape drives.
I'm using just-purchased Exabyte-brand 8mm tapes (112m length) here, so I
don't THINK the tapes would be the problem. I'm getting these problems in
both drives, so I wouldn't think THAT's the problem. So, I'm guessing
that it would have to be in the "sym" driver - a bug and/or a limitation
in its ability to deal with old SCSI-1 tape drives?
So, does anyone have any helpful suggestions? (aside from "go buy a
modern tape drive" :-)...because of other recent failures, my computer
budget is a bit strained at the moment).
Thanx,
--
Scott Blachowicz
peter@icke-reklam.manet.dot..nu
> [I tried posting this to the freebsd-questions mailing list, but I'm not
> sure I made it since I haven't seen it back]
> Hi-
I have been using exabyte 8200 and 8505 some years, notbly with
various adaptec adapters (but that does probebly not matter)
Recently i got simular problems with a 8505 , cleaning did not help
so i replaced the drive with a brand new. Problems over, case closed.
You did switch drive. But whats the probability that the second drive
is broken to ?
My experience with the single drive that failed was simular diagnostics as yours,
but sometimes i cound do a whole backup without errors. Which made me
believe i had tape errors.
Can you confirm that your two drives really are 1 broken and 1 good unit ?
> I had this problem doing dumps (or tars or whatever) to an old Exabyte
> 8200 tape drive that I've got hooked up to my FreeBSD 3.2R system via a
> My current 'dmesg' output:
> Thanx,
> --
> Scott Blachowicz
--
--
Peter Hĺkanson
Manet Networking (At the Riverside of Gothenburg, home of Volvo)
Sorry about my e-mail address, but i'm trying to keep spam out.
echo "peter (at) manet (dot) nu" | sed "s/(at)/@/g " | sed "s/(dot)/\./g"|sed "s/ //g"
Scott Blachowicz
peter> Can you confirm that your two drives really are 1 broken and 1
peter> good unit ?
At this point, no - I can't. I've experienced problems with both drives
and successfully written a tape with both drives. I'm at a loss to
explain it except for a possible problem with the SCSI device driver
losing track of the tape status somehow.
I suppose it's possible that both drives are broken, but I've had one for
a couple years and the other for less than a couple weeks. I could
probably hook one of them up to a Windoze NT or 98 system to do some
verification that way...
--
Scott Blachowicz