BAD LIF MAGIC - problem with recovery from Ignite tape

[Michal Zochowski_1]

I want to recover system from ignite tape.
When I stop booting server and search devices to boot with command:
sea ipl

tape with ipl created in Ignite is seen.
When I start to boot system from tape, I get the message:
Booting...
Boot IO Dependent Code (IODC) revision 1
IPL error: bad LIF magic.
Error Reading IPL
I tried to copy ignite tape from one to another with ignite command
server# copy_boot_tape -u /dev/rmt/0mn -b -d /tmp/tape
Rewinding tape /dev/rmt/0mn.
Extracting the boot area to /tmp/tape/bootimage.
0+0 records in
0+0 records out
Boot file contents.
lifls: Can't list /tmp/tape/bootimage; not a LIF volume
ERROR: lif image corrupted. Tape heads may need cleaning.
Rewinding and ejecting tape(s).
It's important: I can't see the log from make_recovery (no access).

My questions:
1. What is the problem?
2. How to clean heads in tape?

[Zeev Schultz]

copy_boot_tape should have extracted the LIF
sector needed to boot.If it shows 0 records
- means either tape is bad or drive can't read
it.Clean the drive 2-3 times and try again. Can
you boot the tape on another server's tape?

[Michal Zochowski_1]

On another server I perform this:

dd if=/dev/rmt/0m of=/dev/null bs=1k
0+0 records in
0+0 records out

Drive is 100% good.

I think that the tape is completely empty.

[T G Manikandan]

Not sure about the copy_boot_tape.
THe normal dd command would do the job for you.

check the IGNITE FAQ

4.2

http://www.software.hp.com/products/IUX/faq.html#set4

[RolandH]

1. The problem can be that the tape is damaged ord the tape needs cleaning.

2. If the tape needs cleaning you need a cleaning tape. Put it in the tape drive. The cleaning starts and if it is finished the tape drive release the cleaning tape.

How do you know a tape needs cleaning.
Local: You see a flashing red/orange light at the tape drive which indicates it need cleaning.
Remote:If your server is far away you can use the OnlineDiagnostics.
The you can ask for status of tape. ie
# echo "selclass qualifier dds;info;wait;il" | cstm

Then you will get somthing like this:

Hardware path: 0/0/1/0.1.0



Device Qualifier: HPC1537A
Product ID: C1537A Hardware Path: 0/0/1/0.1.0
Device Type: SCSI Tape Logical Unit Number: 0
Vendor: HP Product Rev Level: L111
Firmware Revision: 4.123 Tape Load Count: 2
Correctable Errors: 0 Uncorrectable Errors: 0
Mfg Date Code: 9 Servo Revision: 14.2
Compression Status: Enabled Compression Ratio:
[instant] 3 : 1
[average] 1 : 1
Capacity [M Byte]: 3393617920
Drive Status: Good


HTH
Roland

[Michal Zochowski_1]

Thanks for link.
I tried to copy tape into disk with dd command (to 2 files).
I performed it, but both files are empty (0 Kb).

I think that tape is bad.
Thanks for help.

[john korterman]

Hi,
I just tested your copy_boot_tape command on an ignite tape, and it ran like this:
# copy_boot_tape -u /dev/rmt/0mn -b -d /tmp/tape
Rewinding tape /dev/rmt/0mn.
Extracting the boot area to /tmp/tape/bootimage.
14524+1 records in
14524+1 records out
Boot file contents.
volume ISL10 data size 281239 directory size 3 02/11/14 14:50:50
filename type start size implement created
===============================================================
ISL -12800 16 240 0 02/11/14 14:50:50
AUTO -12289 256 1 0 02/11/14 14:50:50
INDEX BIN 264 1 0 02/11/14 14:50:50
CONFIG BIN 272 34 0 02/11/14 14:50:50
HPUX -12928 312 880 0 02/11/14 14:50:50
INSTALL -12290 1192 26990 0 02/11/14 14:50:57
INSTALLFS -12290 28184 31744 0 02/11/14 14:51:03
FWWKAR BIN 59928 1 0 02/11/14 14:51:03
INSTCMDS BIN 59936 10732 0 02/11/14 14:51:06
SYSCMDS BIN 70672 45473 0 02/11/14 14:51:17
SCRIPTS BIN 116152 42 0 02/11/14 14:51:18

Rewinding and ejecting /dev/rmt/0mn.

which probably is OK and not at all like yours. I'm afraid there is no LIF area - or anything else - on your tape.


regards,
John K.

[john korterman]

I was not patient enough. Just for the record, the following line also appeared:

[C]opy to new tape or [E]xit:

and after exitting I could check the extract like this:

# lifls -l /tmp/tape/*
volume ISL10 data size 281239 directory size 3 02/11/14 14:50:50
filename type start size implement created
===============================================================
ISL -12800 16 240 0 02/11/14 14:50:50
AUTO -12289 256 1 0 02/11/14 14:50:50
INDEX BIN 264 1 0 02/11/14 14:50:50
CONFIG BIN 272 34 0 02/11/14 14:50:50
HPUX -12928 312 880 0 02/11/14 14:50:50
INSTALL -12290 1192 26990 0 02/11/14 14:50:57
INSTALLFS -12290 28184 31744 0 02/11/14 14:51:03
FWWKAR BIN 59928 1 0 02/11/14 14:51:03
INSTCMDS BIN 59936 10732 0 02/11/14 14:51:06
SYSCMDS BIN 70672 45473 0 02/11/14 14:51:17
SCRIPTS BIN 116152 42 0 02/11/14 14:51:18

regards,
John K.

[GK_5]

It could be bad tape or bad tape drive. Clean the drive by cleaning tape. Try recovery again. Try with another tape if you have. Was the Ignite backup done on same tape drive?

-GK-