topic Re: RECOVERY ERROR in Operating System - HP-UX

RECOVERY ERROR

khilari — Thu, 16 Mar 2006 16:33:44 GMT

Hi Guys, well i had a successful make_tape_recovery. Now, when i tried to check it by booting from the tape, i am getting errors. If i boot from p3 i get IODC Entry_init failed.Error status -5. And when i try doing it with p4 i get IPL error: bad LIF magic.

I didnt get any errors when i made the tape. I checked the tape_boot.lif and i had entries there of ISL etc. So, why am i gettng errors. When i tar from the tape i get the response from it. Then what can it be, thanks.

Re: RECOVERY ERROR

Jannik — Thu, 16 Mar 2006 16:45:30 GMT

did you use this command:
make_tape_recovery -x inc_entire=vg00 -a /dev/rmt/0mn
If the LIF is not there it could be lag of space in /var/tmp.
Are you running VxVM or LVM?
Could you send the output from the above command?

Re: RECOVERY ERROR

Mark Greene_1 — Thu, 16 Mar 2006 17:04:18 GMT

Boot the system from disk. There will be a log file from the make_tape_recovery somewhere in the directory path /var/opt/ignite. If there where errors during the save, they will be in the log file.

mark

Re: RECOVERY ERROR

Patrick Wallek — Thu, 16 Mar 2006 17:10:02 GMT

It almost sounds as if P3 and P4 are not your tape drive.

Verify with ioscan the SCSI path of your tape drive. Then when you do the 'SEA IPL' check the path you get there against what you found with ioscan.

Also, your tape drive will show up as a 'Sequential Access Device' and NOT a 'Random Access Device'.

Re: RECOVERY ERROR

khilari — Fri, 17 Mar 2006 10:44:32 GMT

Well, i am using LVM. I am attaching the output i got# lifls -l /var/tmp/tape_boot.lif
volume ISL10 data size 1017176 directory size 3 06/03/15 11:55:31
filename type start size implement created
===============================================================
ISL -12800 16 242 0 06/03/15 11:55:31
AUTO -12289 264 1 0 06/03/15 11:55:31
INDEX BIN 272 1 0 06/03/15 11:55:31
CONFIG BIN 280 42 0 06/03/15 11:55:31
HPUX -12928 328 1024 0 06/03/15 11:55:31
FWWKAR6 BIN 1352 1 0 06/03/15 11:55:31
FWWKAR7 BIN 1360 1 0 06/03/15 11:55:31
FWWKAR8 BIN 1368 1 0 06/03/15 11:55:31
INSTALL -12290 1376 68148 0 06/03/15 11:55:32
INSTALLFS -12290 69528 49152 0 06/03/15 11:55:34
VINSTALLFS -12290 69528 49152 0 06/03/15 11:55:34
WINSTALLFS -12290 69528 49152 0 06/03/15 11:55:34
VINSTALL -12290 118680 73768 0 06/03/15 11:55:37
WINSTALL -12290 192448 83853 0 06/03/15 11:55:39
INSTCMDS BIN 276304 30019 0 06/03/15 11:55:40
RECCMDS BIN 306328 988 0 06/03/15 11:55:40
SYSCMDS BIN 307320 77845 0 06/03/15 11:55:43
SCRIPTS BIN 385168 43 0 06/03/15 11:55:43
VERSION BIN 385216 1 0 06/03/15 11:55:43
PAD BIN 385224 256 0 06/03/15 11:55:44

well, by getting this output. It shows that the boot header was made, and these are the entries.
As far as booting for p3 or p4 are concerned they are the only options other than the random access memory one. One gives lif message and the other just doesnt work.