DLT4000 ignite problems on K-Class

[MTSU_SAN]

I'm trying to use ignite on my K-Class server. I was able to make_tape_recovery successfully on my DLT4000 (DLTIV) tape drive, but cannot restore from it. SEA finds the drive, but gives me some error when trying to boot from it. Something like "Cannot find IPL". I can dd from the tape.

[Steven E. Protter]

If this tape drive is in a external storageworks or similar device that is not connected to your HP-9000 server via SCSI it will merrily write the tape and not be able to recover from it.

Our Ultrium verion of the same device works the same way because its SCSI connection is to a Windows PC.

After beating on support for a few days we were told that configuration was not supported for Ignite Recovery.

If however the device is direct connected via SCSI then you should check cables, SCSI instance and ioscan and make sure the device is properly set up and claimed.

SEP

[RAC_1]

Just because, you were able to do dd does not mean that tape is OK. Was the recovery completely sucessful. what does recovery.log says??


Just put the tape in drive and do following.

mt -f /dev/rmt/0mn fsf 1
tar -tvf /dev/rmt/0mn

Does it lists the tape contenets??

Anil

[MTSU_SAN]

Yes, recovery was complete--here is the end of the recovery.log
* Creating The Tape Archive
43590+1 records in
43590+1 records out
* /opt/ignite/data/scripts/make_sys_image -c n -d /dev/rmt/0mn -t n -s
local -n 2004-10-08,11:19 -m t -w
/var/opt/ignite/recovery/2004-10-08,11:19/recovery.log -u -R -g
/var/opt/ignite/recovery/2004-10-08,11:19/flist -a 2032140

* Preparing to create a system archive

* Archiving contents of stein.mtsu.edu via tar image to local device/dev/
rmt/0mn.
* Creation of system archive complete

Also, the tar works fine. I bet it is because it is external, but I thought it was on a SCSI port, I'll try to get there this afternoon to check. ANy other ideas?

[RAC_1]

If the case is as SEP says, (tape drive not on SCSI), this is bad.
It should atleast give message at the time of creating a recovery archieve.

HP should do something about it.

Anil

[MTSU_SAN]

Well, duh, I just checked the ioscan, and sure enough, it is SCSI.
ext_bus 1 10/4/4 scsi3 CLAIMED INTERFACE HP 28696A - Wide SCSI ID=7
target 5 10/4/4.5 target CLAIMED DEVICE
tape 0 10/4/4.5.0 tape2 CLAIMED DEVICE Quantum DLT4000
/dev/diag/rmt/c1t5d0 /dev/rmt/c1t5d0BEST
/dev/rmt/0m /dev/rmt/c1t5d0BESTb
So that is not the problem...

[Christopher Rupnik]

You are trying to use the DLT on the NIO (HP-PB bus). You need to use the HSC FW connector. Move the DLT and you are all set.

[MTSU_SAN]

Oh, so if all of my SCSI ports are fully expanded, then I'm out of luck?

[Bill Hassell]

Yes, you're out of luck. The K-class box is really old and enhancements to get the processor ROMs to boot off tape drives that never existed when the K box was manufactured were never done. Tape drives are not nearly as similar as disks, so the boot ROMs must be changed when (yet another) new tape drive comes along. You can get an HSC interface card or you add a DDS drive to use for booting. Such is a common story for older CPUs and new peripherals.