can't boot from tape:"Exec failed: Exec format error"

[Rambo_1]

Hi,
I wanted to recovery the OS(11.11) by the make_recovery tape.
First,I used #make_recovery -Av to make a tape ,and the result was "completed successfully". But when I begin booting from the tape ,I met these error and can't go on.

boot :
tape(0/0/1/0/3/0/0/0/0/0;0)WINSTALL
Exec failed: Exec format error
ISL>
If I enter HPUX under ISL>,the messages displayed:
ISL>HPUX
tape(0/0/1/0/3/0/0/0/0/0;0)/stand/vmunix can not open or executable
I deleted the Ignite-UX(B.3.5.68)and Install a new version Ignite-UX(C.6.7.79)depot and a patch named PHCO_32438 into OS, then used make_tape_recovery -Av to make a new tape ,I used the new tape to recovery ,but still meet the error as before:
boot :
tape(0/0/1/0/3/0/0/0/0/0;0)WINSTALL
Exec failed: Exec format error
ISL>
should I need more patches ? I don't know, can anyone help?

[Victor Fridyev]

Hi,

Are you sure that the tape was rewinded before installation ?
Take into account that ignite procedure uses /dev/rmt/0mn file (no-rewind), so after the tape creation it stands not in the beginning. I had such a problem and after
#> mt -f /dev/rmt/XXXX rew

boot worked properly.
Additionally could you check this tape drive or at least clean it up.

HTH

[Sandman!]

First of all, if using a tape made from make_tape_recovery, the source and target system have to be the same type of architecture. And you haven't said from which system was the tape made and which system is being recovered?

For example a make_tape_recovery made on a K-class system cannot be used to boot and recover an N-class machine. Verify that this is not the case or make sure that the make_tape_recovery is made on a machine that is the same as the one that has to be booted off like two N-class machines.

This is because there are currently 3 different Ignite-UX INSTALL kernels that
are used. The model of the system does not, necessarily, have to be the same, but the architecture does or the tape won't boot and the kernels are:

WINSTALL - used for all systems that are 64bit ONLY (N,L,A...etc).
VINSTALL - used for V class systems.
INSTALL - used for systems that can run BOTH 32 and 64bit (K,D,R...etc).

~hope it helps

[Rambo_1]

The source and target system are the same type of architecture ,I made the tape from L class and recovery to this L class.
the OS of this L class was 11.00 before .and had been upgraded to 11.11 now .

[A. Clay Stephenson]

First there are L-boxes and there are L-boxes so that you may not have all the drivers you need to boot this other box --- especially if the disks are different (ie LVD vs HVD SCSI cards/disks). The second thing to check is that the firmware may not be compatible with the OS level.

[Sandman!]

So the source and target systems are L-class machines (source running 11i). You can try booting off the kernel (with debugging on) at the ISL prompt i.e.

ISL>hpux -i3 (;0):INSTALL

[Sandman!]

Please let us know whether it worked or not?

~thanks

[John P. Kole]

It looks as though whatever is on the tape (where the kernel should be) is not a valid kernel.

Could you perform this command on the machine where the tape was made:

$ cd /opt/ignite/boot ; file Rel_B.11.*/*INSTALL

The output should be something like:
Rel_B.11.00/INSTALL: PA-RISC1.1 executable -not stripped
Rel_B.11.00/VINSTALL: ELF-64 executable object file - PA-RISC 2.0 (LP64)
Rel_B.11.00/WINSTALL: ELF-64 executable object file - PA-RISC 2.0 (LP64)
Rel_B.11.11/INSTALL: PA-RISC1.1 executable -not stripped
Rel_B.11.11/VINSTALL: ELF-64 executable object file - PA-RISC 2.0 (LP64)
Rel_B.11.11/WINSTALL: ELF-64 executable object file - PA-RISC 2.0 (LP64)
Rel_B.11.23/IINSTALL: ELF-64 executable object file - IA64
Rel_B.11.23/WINSTALL: ELF-64 executable object file - PA-RISC 2.0 (LP64)

[Rambo_1]

Hi Sandman:
I can't do this recover immedietely. sinc there is only one L class ,I must choose a time to stop all application and database .
In addtion,In anoter L class located in another city ï¼ 11.11ï¼ ,under /opt/ignite/boot/ ,there aren't the Rel_B.11 direcory ,just those files as John P. Kole said ,
Rel_B.11.00/INSTALL: PA-RISC1.1 executable -not stripped
Rel_B.11.00/VINSTALL: ELF-64 executable object file - PA-RISC 2.0 (LP64)
Rel_B.11.00/WINSTALL: ELF-64 executable object file - PA-RISC 2.0 (LP64)
Rel_B.11.11/INSTALL: PA-RISC1.1 executable -not stripped
Rel_B.11.11/VINSTALL: ELF-64 executable object file - PA-RISC 2.0 (LP64)
Rel_B.11.11/WINSTALL: ELF-64 executable object file - PA-RISC 2.0 (LP64)
Rel_B.11.23/IINSTALL: ELF-64 executable object file - IA64
Rel_B.11.23/WINSTALL: ELF-64 executable object file - PA-RISC 2.0 (LP64
why these different bewteen both L class ?
one has the Rel_B.11.11 Directory ,and another hasn't .

[Sandman!]

swverify the Ignite-UX installation on the L-class server missing the Rel_B.11.11 directory. It's possible that swinstall of Ignite-UX was unsuccessful and some of the filesets were not installed owing to that.

# swverify Ignite-UX

~cheers