Exabyte 8500c errors

Exabyte 8500c errors

Post by plamber.. » Sat, 25 Apr 1998 04:00:00



I have an Exabyte 10i library with an Exabyte 8500c drive inside.  Right
now, I'm ignoring the library, and just playing with the drive.  (It's
giving me enough problems without the robot being involved!  ;-)

I attempted to write to it with:

% tar -cvf /dev/st0 filename

This appeared to work, but when I tried:

% tar -tvf /dev/st0

I got:

tar: Read error on /dev/st0: No space left on device
tar: At beginning of tape, quitting now
tar: Error is not recoverable: exiting now

So I tried:

% mt -f /dev/st0 status

and got:

/dev/st0: I/O error

After a while, the I/O error clears.

I tried to rewind the tape (this works) but when I try to read it again,
I get the same error.

Looking in my /var/log/messages shows me:

Apr 23 16:13:00 pinky kernel: st0: Error on write filemark.
Apr 23 16:13:31 pinky kernel: scsi : aborting command due to timeout : pid 13702, scsi0, channel 0, id 0, lun 0 Write (6) 02 7b d2 1c 00
Apr 23 16:13:31 pinky kernel: aic7xxx: (abort) Aborting scb 0, TCL 0/0/0
Apr 23 16:13:31 pinky kernel: scsi : aborting command due to timeout : pid 13703, scsi0, channel 0, id 0, lun 0 Write (6) 05 75 b0 02 00
Apr 23 16:13:31 pinky kernel: aic7xxx: (abort) Aborting scb 1, TCL 0/0/0
Apr 23 16:13:46 pinky kernel: scsi : aborting command due to timeout : pid 13702, scsi0, channel 0, id 0, lun 0 Write (6) 02 7b d2 1c 00
Apr 23 16:13:46 pinky kernel: aic7xxx: (abort) Aborting scb 0, TCL 0/0/0
Apr 23 16:13:46 pinky kernel: SCSI host 0 abort (pid 13702) timed out - resetting
Apr 23 16:13:46 pinky kernel: SCSI bus is being reset for host 0 channel 0.
Apr 23 16:13:46 pinky kernel: aic7xxx: (reset) target/channel 0/0
Apr 23 16:13:46 pinky kernel: aic7xxx: (abort_reset) scb state 0x1, Command phase, SCSISIGI = 0x84
Apr 23 16:13:46 pinky kernel: aic7xxx: (abort_scb) asserted ATN - bus device reset in message buffer.
Apr 23 16:13:46 pinky kernel: scsi : aborting command due to timeout : pid 13703, scsi0, channel 0, id 0, lun 0 Write (6) 05 75 b0 02 00
Apr 23 16:13:46 pinky kernel: aic7xxx: (abort) Aborting scb 1, TCL 0/0/0
Apr 23 16:13:46 pinky kernel: SCSI host 0 abort (pid 13703) timed out - resetting
Apr 23 16:13:46 pinky kernel: SCSI bus is being reset for host 0 channel 0.
Apr 23 16:13:46 pinky kernel: aic7xxx: (reset) target/channel 0/0
Apr 23 16:13:46 pinky kernel: aic7xxx: (abort_reset) scb state 0x1, Command phase, SCSISIGI = 0x94
Apr 23 16:13:46 pinky kernel: aic7xxx: (abort_scb) asserted ATN - bus device reset in message buffer.
Apr 23 16:13:48 pinky kernel: SCSI host 0 channel 0 reset (pid 13702) timed out - trying harder
Apr 23 16:13:48 pinky kernel: SCSI bus is being reset for host 0 channel 0.
Apr 23 16:13:48 pinky kernel: aic7xxx: (reset) target/channel 0/0
Apr 23 16:13:48 pinky kernel: aic7xxx: (reset_device) target/channel -1/A, active_scb 2
Apr 23 16:13:48 pinky kernel: aic7xxx: (match_scb) comparing target/channel -1/A to scb 0/A
Apr 23 16:13:48 pinky kernel: aic7xxx: (reset_device) aborting SCB 0, TCL=0/0/0
Apr 23 16:13:48 pinky kernel: aic7xxx: (match_scb) comparing target/channel -1/A to scb 0/A
Apr 23 16:13:48 pinky kernel: aic7xxx: (reset_device) aborting SCB 1, TCL=0/0/0
Apr 23 16:13:48 pinky kernel: aic7xxx: (match_scb) comparing target/channel -1/A to scb 0/A
Apr 23 16:13:48 pinky kernel: aic7xxx: (match_scb) comparing target/channel -1/A to scb 0/A
Apr 23 16:13:48 pinky kernel: aic7xxx: (match_scb) comparing target/channel -1/A to scb 1/A
Apr 23 16:13:48 pinky kernel: aic7xxx: (reset_channel) Resetting current channel A
Apr 23 16:13:48 pinky kernel: aic7xxx: (reset_channel) Channel reset, sequencer restarted
Apr 23 16:13:49 pinky kernel: aic7xxx: (done_aborted_scbs) Aborting scb 0, TCL=0/0/0
Apr 23 16:13:49 pinky kernel: aic7xxx: (done_aborted_scbs) Aborting scb 1, TCL=0/0/0
Apr 23 16:13:49 pinky kernel: aic7xxx: (done_aborted_scbs) Aborting scb 2, TCL=1/0/0
Apr 23 16:13:49 pinky kernel: scsi0: Target 0, channel A, now synchronous at 10.0MHz, offset 15.
Apr 23 16:13:49 pinky kernel: scsi0: Target 1, channel A, now synchronous at 4.0MHz, offset 11.
Apr 23 16:13:49 pinky kernel: st0: Error with sense data: extra data not valid Current error st09:00: sense key Unit Attention
Apr 23 16:13:49 pinky kernel: Additional sense indicates Power on, reset, or bus device reset occurred

What is causing the bus resets?  Any ideas?

I've got an Adaptec 2910 card, with a SCSI drive on ID 0 and a CD on 3,
internally, and the library on ID's 1 and 4 externally.

The drive and library functioned flawlessly when I tested them on my Mac
with Retrospect--I backed up 500MB to a tape and restored it with no
problems.

Ideas?  Suggestions?  Pointers?

--Paul L.

 
 
 

Exabyte 8500c errors

Post by Charles Webe » Tue, 28 Apr 1998 04:00:00


I have had no end of trouble with hp and seagate dat drives on adaptec
2940's.  I installed 2.0.33 kernel and latest driver patches and still
got time out errors.  News groups had suggested compiling all scsi
options into kernel rather than as modules and disabling disconnection
in scsi bios.  All to no avail. I used 2 ncrs (810 and 875) and it all
worked great.  Look for MTX package, it works very well on my dat
changer.  If you need details, email me, I have file locations at work.
Chuck Weber

 
 
 

Exabyte 8500c errors

Post by Steve Sparro » Fri, 01 May 1998 04:00:00


You probably won't like my answer.
Our Windows NT group at work has had Exabyte
replace tape library after tape library after tape library
after tape library. Some of the libraries forgot to include
a tape drive.

We have a 15 cartridge DLT library now and everything is boring.

 
 
 

Exabyte 8500c errors

Post by plamber.. » Sat, 02 May 1998 04:00:00



Quote:> You probably won't like my answer.
> Our Windows NT group at work has had Exabyte
> replace tape library after tape library after tape library
> after tape library. Some of the libraries forgot to include
> a tape drive.
> We have a 15 cartridge DLT library now and everything is boring.

Well, I _like_ my answer: the library was free.  I'll live with it.  ;-)

It turns out that the drive was bad.  I replaced it with another free
one, and tested the whole deal on a Mac running Retrospect: it works
flawlessly.

Now I can't get the changer to work on the Linux box.  Ugh.

--Paul L.

 
 
 

1. Strange error with Exabyte 8500c in 10e

I have a problem with a taper which makes me walk the roof...

Connected to one of my RS6K machines is a Exabyte 10e with a 8500c drive
in it.
The latest fixes is applied on 4.1.5.

The problem is: it's impossible to read or write to it with standard
commands
like dd, tar, cat or whatever, it's possible though to run diagnostict
on the
darn device in advanced mode where the tape is 'written' to and 'read'
from...
and no problems reported. The taper is cleaned,  and whatever more can
be
done to the drive without being kinky.

The devicedriver is configured in different ways with both 'density',
'blocksize',
'variablelength' and other options. It's been removed several times and
aix
added it nicely again both at reboot and already running with cfgmgr...

I have tried both old tapes, system tapes and brand new tapes, no luck.

Tar says: 'unable to close /dev/rmt0' and sometimes 'Media surface
error'

errpt says something like:

Probable causes:
TAPE

User causes:
MEDIA DEFECTIVE
DIRTY READ/WRITE HEAD

So, how did the diagnostics program read and write the tape which I know

it did...

I'm about to go bauld soon.

What to do?

Kindly
/S. Lindberg

--
============= FOOS - Chemistry ====================
Stockholm University   URL: www.fos.su.se/~stefan/
FOOS - Chemistry       Phone: +46 8 674 7481
Stefan Lindberg        Cell:  +46 70 491 0223
S-106 91 Stockholm     Office: Arrhenius,c454

      Get PGP public key at my homepage
===================================================

2. /usr/sbin/sys-unconfig broke my system!

3. Exabyte 8500C on SS1000

4. New User Questions - Upgrading Kernel

5. Exabyte 8500C woes in SOlaris 2.3

6. Xconfig for Sony Multiscan 17se

7. Here is a fix for Exabyte 8500c problem

8. netscape usage questions!

9. Exabyte 8500C, Solaris 2.6 and dd

10. Exabyte 8500C

11. Exabyte 8500C and Solaris 2.x

12. exabyte 8500c woes - FIXED!

13. Exabyte 8500c unusable with Solaris 2.3