Problems with Quantum DLT8000 - HP-UX 11 on K-Class

[Philipp Nierkamp]

Hi !

Few days ago I connected a Quantum DLT 8000 to my K-Class HP-UX 11.00 server.
Well, the system detected the new hardware.
But that's it.
If I try to use fbackup, it tells me, that an I/O Error occured.
Does anybody know something about that ?
Thanks in advance !

[Denver Osborn]

I'd download and install stape cumulative patch PHKL_22856, if not already installed. This will add support for the DLT8000 to the stape driver. Is it attached to the HSC bus?

[Philipp Nierkamp]

Hi!

Patch is already installed.
Maybe your're right an the connection could be the problem.
I've got an internal Quantum DLT8000 drive. I put it into an external SCSI-2 tower (as the only device) and connected it with a standard scsi-2 cable to the scsi interface-card.
Is that wrong?

[Denver Osborn]

Can you tar or dd to the tape and get the same results? What about trying another tape in the drive? If it is on the HP-PB it won't work, the DLT8000 has to be on the HSC bus.

[Alan Riggs]

Does the tape devic identify properly with ioscan -fnC tape? Are the appropriate device files created? Rather than fbackup, can you address the device with a simple tar, dd, or cpio command?

[Philipp Nierkamp]

Hi !

Well, tar and dd have the same results. I/O Error.
the DLT itselft should be ok. I plugged it into my NT-Server system, connected by the SCSI-2 bus as a second tape-device in the chain. First tape ist a DDS-2 (C1533 I think). I ran some tests and it worked quite fine. Fast an reliable. So, the DLt itself seems to work and the tape, too.
Patches are installed as recommended.
I'm actually no scsi-expert. What do you exactly mean by HSC-bus? How do I recognize that kind of scsi-bus? And what is HP-PB?

[Denver Osborn]

I'm far from an expert myself, however, we'll want to look at the ioscan -fnCtape... if the driver is stape we should be fine, if it is tape2 it's on the wrong bus. I suspect it'll show tape2. Maybe someone here in the forum might be able to give you pointers on knowing where to physically "connect" your device, since I'm not too familiar with that aspect of it.

[Patrick Wallek]

Check out this thread:
http://forums.itrc.hp.com/cm/QuestionAnswer/1,1150,0x58f4a14d9abcd4118fef0090279cd0f9,00.html

Basically, you have to have to DLT8000 attached to a SCSI card on the GSC or HSC bus I believe. It will not work on an HP-PB bus SCSI card.

[melvyn burnard]

If you run an ioscan what product number is reported for the card the DLT is connected to?
Failing that, is there a product number on the intterface?

If it is something like 28655A or 28696A, then these ar HP-PB bus cards and the DLT 8000 will not work on them.

[Philipp Nierkamp]

Hi !

Ok...
The DLT Tape was connected to the HP-PB Bus SCSI-Cards.
I shutdown the system and plugged it into an unused SCSI port on the HSC-Bus.
(To be precise: A2969A HSC-F/W-SCSI)

BUT!
The system doesn't seem to like that at all.
I turn the system on, it tries to boot, finds it's primary path and then: bang! system panic.

What's wrong now?

Thanks in advance for all your helping!

[melvyn burnard]

could be a bent pin on cable, or you have duplicate scsi id's

What is the panic string?
which card did you plug it into?
have you terminated the bus?

[Philipp Nierkamp]

Hi !

Ok.. I've got two SCSI Connectors an that HP-HSC Bus. Port 0 and Port 1

I plugged it first in Port 0, then I used Port 1. Both resulted in kernel panic
(I attached the detailed panic messages on the console)

Pins seem to be ok.
When plugged into the HP-PB bus, the DLT has the SCSI-ID 5
That SCSI-ID should also be unused on the HP-HSC Bus - as no other device should be plugged in.
Or are the HSC Adapters also the controllers for the devices in the front? 1xCDROM, 1xTape / 4xHDD ???

[Philipp Nierkamp]

Hi !

Maybe this information helps...


Attached the results from the "device search"

[melvyn burnard]

The panic string is:
panic: I/O system hang

This implies a problem on your SCSI bus you are connecting the DLT onto.
I would check for cables/terminations.
DLT's should also NOT be shared on the same bus as discs.

[paul courry]

May I suggest you get a little more basic than you have been?

Use ODE then MAPPER to ensure the tape drive can be seen and the bus is working properly. ODE is available on your support disc and is loaded in place of HP-UX for diagnostic purposes. This will eliminate the operating system as a potential point of failure and leave you just with the drive to contend with. Once you are sure the drive is ok then tackle HP-UX next. Divide and conquer!

[Dave Wherry]

I can't verify this, but will throw it into the mix. Could old firmware on the drive be causing the problem? HP is frequently wanting me to update firmware.
Also, I strongly disagree with one of Denver's comments - "I'm far from an expert myself". Last year I was struggling to get a new DLT library to work. After 3 or 4 calls to the RC I was connected to Denver and the library was working in about 10 minutes. I shy away from self proclaimed experts. I'll rank Denver pretty high.

[Philipp Nierkamp]

It still does not work.
If I connect the DLT8000 to the SCSI adapter on the HP-PB Bus, it is recognised and the systems boots normaly. But I won't do anything. There is always this strange I/O error.
As you told me, that I should not connect it to the HP-PB, I plugged it into both GSC/HSC Adapters (Adress: 8/0 and 10/8). The result: Kernel panic during boot. (kernel panic message: i/o system hang)
Both GSC Adapters are not used. The DLT is the only device.
Whats still wrong? I really don't get it.

I attachted the "device list". (Yes I know... the DLT is connected to the SCSI-Adapter on the HP-PB bus)
Thanks

[Shannon Petry]

This may be too basic, but Is the SCSI type correct on the interface?

My DLT8000 is FW Differential SCSI, and requires a full bus. I had to buy a FWD card and add it to the system.

While it looks like Ultra Wide, it is not. This would cause your IO Hang/Panic as the bus can not report properly.

Regards,
Shannon

[Philipp Nierkamp]

Hi!

Which FWD SCSI-Card did you buy?
You've got a product-nr for me?

Thanks!

Kind Regards
Philipp