4mm DAT will TAR, but not DUMP.

4mm DAT will TAR, but not DUMP.

Post by Stewart Nicho » Sat, 29 Jun 1996 04:00:00



I have an Exabyte EXB-4200T 4mm DAT (yes DAT, not 8mm) scsi tape drive
that is unable to handle dumps.  I can tar to the drive, then read
the tar with no problem, but a dump hangs the machine.  Completely.
(The only thing that the computer will respond to is using ALT-{F1,F2,F3}
to another console - but no cursor is displayed on the alternate
consoles and nothing else can be done with the machine.)

The scsi controller is an adaptec 1522A. (not set for DMA)

I tried placing a DEC TLZ06 DAT drive in its place and the TLZ06
handles the dumps without any problems.

The Exabyte:

  Jun 26 15:31:04 aspirin /kernel: (aic0:5:0): "EXABYTE EXB-4200 " type 1
    removable SCSI 2
  Jun 26 15:31:04 aspirin /kernel: st0(aic0:5:0): Sequential-Access density
    code 0x13, 512-byte blocks, write-enabled

The DEC TLZ06:

  Jun 26 21:15:41 aspirin /kernel: (aic0:5:0): "DEC TLZ06     (C)DEC 0491"
    type 1 removable SCSI 2
  Jun 26 21:15:41 aspirin /kernel: st0(aic0:5:0): Sequential-Access density
    code 0x13, variable blocks, write-enabled

Notice that the Exabyte appears to be fixed-size 512byte blocks.
So I tried passing the block size to dump, but the machine hung
again, anyway.

I was able to write Windows NT backups with the Exabyte drive and read
them with the TLZ06 without problem.  And, as I said, I can write tars
to the Exabyte drive and read them back without problem.

How do I fix/get-around this problem?

stu

 
 
 

4mm DAT will TAR, but not DUMP.

Post by Karl Wieb » Sat, 29 Jun 1996 04:00:00



>I have an Exabyte EXB-4200T 4mm DAT (yes DAT, not 8mm) scsi tape drive
>that is unable to handle dumps.  I can tar to the drive, then read
>the tar with no problem, but a dump hangs the machine.  Completely.
[ ... ]
>The scsi controller is an adaptec 1522A. (not set for DMA)
[ ... ]
>  Jun 26 15:31:04 aspirin /kernel: (aic0:5:0): "EXABYTE EXB-4200 " type 1
>    removable SCSI 2
>  Jun 26 15:31:04 aspirin /kernel: st0(aic0:5:0): Sequential-Access density
>    code 0x13, 512-byte blocks, write-enabled

I would try to isolate the problem to what SCSI command sequences/ioctls
trigger your machine hang. BTW, what kernel is this? Do you have the
SCSI_DEBUG option compiled in?

One place to look at are the mode pages. See scsi(8). Compare the Exabyte
to your other DAT drive. Also, I assume you have h/w docs for your EXB-4200?
You may end up having to change some jumper settings.

Maybe if you post verbose SCSI_DEBUG messages ( if you can get any ) that
occur prior to the system hang. That should give us a bit more to go on.

--Karl
--

"Order is a form of repetition compulsion" --Freud
"Order is a form of repetition compulsion" --Freud
"Order is a form of repetition compulsion" --Freud

 
 
 

4mm DAT will TAR, but not DUMP.

Post by Stewart Nicho » Sat, 29 Jun 1996 04:00:00



Quote:>I would try to isolate the problem to what SCSI command sequences/ioctls
>trigger your machine hang. BTW, what kernel is this?

Oops, sorry.  2.1.0-RELEASE.

Quote:> Do you have the SCSI_DEBUG option compiled in?

No.  What options do I add, and are there any gotchas involved?
Once I have the new kernel (I have done kernel builds many times),
do I need to do any special thing to turn it SCSI_DEBUG on and off?  
CAN it be turned on and off?  Where do the messages go, to "messages"?

Quote:>One place to look at are the mode pages. See scsi(8). Compare the Exabyte
>to your other DAT drive. Also, I assume you have h/w docs for your EXB-4200?
>You may end up having to change some jumper settings.

I don't understand what "mode pages" means here.  I have looked at the
scsi(8) man pages, and I don't know what I need to do with it.  The
man pages for scsi(8) are apparently geared more towards reminding
someone how to use it then instructing someone how to use it.  If you
can give me the syntax to use I will try the commands.

stu

 
 
 

4mm DAT will TAR, but not DUMP.

Post by t.. » Sun, 30 Jun 1996 04:00:00



Quote:>I have an Exabyte EXB-4200T 4mm DAT (yes DAT, not 8mm) scsi tape drive
>that is unable to handle dumps.  I can tar to the drive, then read

[section deleted]

First, is the Exabyte running the most current microcode?  I know that the 8mm
Exabytes both the 8200 and the 8500 have upgradeable microcode, I don't know
if the 4mm series does but I would think it does.

Also, call Exabyte, their amazingly knowledgable and are not anti-Unix, pro
Windoze fortunately.

Also, try running the tape drive in asynchronous mode, I believe there is a
jumper on the 1522 for that.

I take it the usual SCSI stuff like termination is checked?

 
 
 

1. Dump parameters for a 4mm helical scan DAT tape.

As the Subject line reads, I'm looking for the "optimal" dump
parameters for a R-Squared (vendor) 4mm helical scan DAT
tape drive. In particular, the blocking factor, dpi and size
for various tapes.

Also, what brand names would you recommend purchasing for use
in the tape drive?

Please respond by email.

                                Ernest Cisneros
                                (Geologist/Computer Specialist)
                                United States Geological Survey
                                Flagstaff, Arizona
                                (602)556-7022


2. setenv

3. Sybase XI "dump database" to 4mm DAT tapes?

4. RH 7.1: 686-optimized kernel on Duron

5. dump options for 4mm DAT.

6. Connecting Wyse terminal to linux

7. dump to 4mm DAT tapes

8. LINUX, NT and DOS - LILO or NT boot pg

9. dump command and 4mm DAT tape

10. Need larger dump tape length/block size for 2GB 4mm DAT

11. dump parameter for 4mm DAT?

12. Need help with dump and 4mm dat drive.

13. dump parameters for HP 4mm DAT Tape Drive