DLT 8000?

[castro_2]

I installed a DLT 8000, when I do ioscan show me
tape 3 10/4/4.6.0 tape2 CLAIMED DEVICE QUANTUM DLT8000
/dev/diag/rmt/c5t6d0 /dev/rmt/c5t6d0BEST
/dev/rmt/3m /dev/rmt/c5t6d0BESTb
/dev/rmt/3mb /dev/rmt/c5t6d0BESTn
/dev/rmt/3mn /dev/rmt/c5t6d0BESTnb
/dev/rmt/3mnb /dev/rmt/dlt

When I do mt -f /dev/diag/rmt/c5t6d0 status
ioctl SIOC_INQUIRY: I/O error
tape hardware path 10/4/4.6.0.0: Offline during CLOSE. Rewind manually.

When I do mt -f /dev/rmt/3m status
no tape loaded

The last is OK but why?
what is /dev/diag/rmt/c5t6d0 ?
Thanks

[harry d brown jr]

You need to activate "stape" device driver in your kernel.

live free or die
harry

[castro_2]

But the driver is tape2 not stape
I don`t understand
Thanks

[Helen French]

Did you try using /dev/rmt/3m or /dev/rmt/3mn as device files:

# mt -f /dev/rmt/3m status

[Pete Randall]

First, the driver for the DLT8000 is stape. Here's and ioscan from my system:

root# ioscan -kfnCtape
Class I H/W Path Driver S/W State H/W Type Description
======================================================================
tape 0 0/0/1/0.0.0 stape CLAIMED DEVICE HP C1537A
/dev/rmt/0m /dev/rmt/0mn
/dev/rmt/0mb /dev/rmt/0mnb
tape 18 0/4/0/0.6.0 stape CLAIMED DEVICE QUANTUM DLT8000
/dev/rmt/6m /dev/rmt/6mn
/dev/rmt/6mb /dev/rmt/6mnb
tape 8 0/4/0/1.5.0 stape CLAIMED DEVICE QUANTUM DLT8000
/dev/rmt/5m /dev/rmt/5mn
/dev/rmt/5mb /dev/rmt/5mnb
tape 13 1/10/0/0.4.0 stape CLAIMED DEVICE Quantum DLT4000
/dev/rmt/4m /dev/rmt/4mn
/dev/rmt/4mb /dev/rmt/4mnb
tape 9 1/10/0/1.3.0 stape CLAIMED DEVICE QUANTUM DLT8000
/dev/rmt/3m /dev/rmt/3mn
/dev/rmt/3mb /dev/rmt/3mnb
tape 10 1/12/0/0.2.0 stape CLAIMED DEVICE QUANTUM DLT8000
/dev/rmt/2m /dev/rmt/2mn
/dev/rmt/2mb /dev/rmt/2mnb



Second, the /dev/diag device file is for diagnostics (possibly EMS or something) - don't use it, use the conventional device files.

Pete

[Rita C Workman]

Did you set up the kernel with the 'spt' driver for HP-PB bus or 'sctl' for HSC or PCI bus - for your robotic arm????

Just a quick thought,
Rita

cause generally 10/4/4.6.0 is the robotic arm addres....

[castro_2]

How can I do to use the driver stape and not tape2?
Thanks

[Pete Randall]

If stape is already configured into your kernel and ioscan is showing that your DLT is using tape2, then maybe that is what you need. Exactly what problem are you having?

Pete

[castro_2]

Yes the stape is configured but when I do ioscan show me tape2
Thanks

[Pete Randall]

So do you still have a problem?

Pete

[castro_2]

Yes, I still have the problem

[castro_2]

Yes, I still have the problem
How can I change the dirver the tape2 to stape

[Pete Randall]

I'm thinking that you shouldn't change it despite what I said earlier. While my system uses stape for DLT8000 drives, that is probably because my drives are stand-alones. In the case of libraries, the tape2 driver may well be the appropriate one. The system should properly select the appropriate driver as long as it's available in the kernel.

Pete

[jayan_1]

Dear Gurus,

I have a similar problem ,I raise earlier also.
I got a DLT 8000 connected to the inbuilt Fast Wide COntroller of K Class server.But when I try IOSCAN -fnC Tape it shows SOFTWARE STATE as NO_HW.I am unable to write or read any Tapes.

Regards
Jayan

[castro_2]

Jayan
My DLT 8000 don`t support scsi3, but support
c720.
ioscna -fnC tape
tape 3 10/4/4.6.0 tape2 CLAIMED DEVICE QUANTUM DLT8000
/dev/diag/rmt/c5t6d0 /dev/rmt/c5t6d0BEST
/dev/rmt/3m /dev/rmt/c5t6d0BESTb
/dev/rmt/3mb /dev/rmt/c5t6d0BESTn
/dev/rmt/3mn /dev/rmt/c5t6d0BESTnb
/dev/rmt/3mnb /dev/rmt/dlt

The driver is bad tape2, the good should be stape

ioscan -fnk|grep SCSI
ext_bus 5 10/4/4 scsi3 CLAIMED INTERFACE HP 28696A - Wide SCSI ID=7



Thanks

[Frank Slootweg]

You have the correct driver:

The interface ("INTERFACE" in ioscan output) uses the scsi3 driver, so the *internal* bus is a NIO/HPPB interface. For a NIO/HPPB interface you should use the tape2 driver for the tape drive (which is what you have). Other drivers like c720 (interface) and stape (tape drive) are not relevant because they are for *other* *internal* busses (HSC/GSC). SCSI *pass-through* drivers like spt (for NIO/HPPB) and sctl (for HSC/GSC) are also not relevant, because you are not controlling a/the robot.

Back to the original problem:

You should not use /dev/diag/....

Have you tried dev/rmt/3mnb? Shiju suggested a similar device file and you gave him some points but did not report any results.

Can you write to / read from the tape drive, i.e. with things like tar(1) or cpio(1)?