restore from ignite backup hangs on ISL> after reboot.

[Durand_1]

Hi,
I have a system backup that I want to install to clone on a backup system.
Let's say A is original system and B is where it will be cloned.
Both configurations are identical (rp 2470 with same processor, memry disk and IO config.
A system includes a 2nd WAN adapter that is not available on B.

A was backed up with a make_tape_recovery -Av

I booted B with the cartridge in the DAT drive.
Every thing went OK up to a reboot which ended with :
"
Primary boot path: 0/0/1/1.15
Alternate boot path: 0/0/2/1.15
Console path: 0/0/4/1.643
Keyboard path: 0/0/4/0.0


Processor is booting from first available device.

To discontinue, press any key within 10 seconds.

10 seconds expired.
Proceeding...

Trying Primary Boot Path
------------------------
Booting...
Boot IO Dependent Code (IODC) revision 1


HARD Booted.

ISL Revision A.00.38 OCT 26, 1994

ISL booting hpux



ISL>

What next ?
What did I fopget ?
How can I boot HP-UX ?
Thanks for helping

[Patrick Wallek]

What happens if you just type 'hpux' at the ISL prompt?

ISL> hpux

[Robert-Jan Goossens]

ISL> sea

enter the option for the tape device.

Regards,
Robert-Jan

[Durand_1]

I already tried both SEA and HPUX

For SEA I can see that the primary boot device is the correct disk drive
P0 0/0/1/0.3 extscsia.3 Random access media 1
P1 0/0/1/0.1 extscsia.1 Sequential access media 1
P2 0/0/1/1.15 intscsia.15 Random access media 1
P3 0/0/2/1.15 intscsib.15 Random access media 1

and

For HPUX command I get back to the ISL> prompt without further notice
Philippe

[Stephen Keane]

ISL> bo p1

[Durand_1]

Stephen, why would I try to boot again on the tape ? I could see the system was successfully installed on the disks 0/0/X/1.15 (they are mirrored).
Are yu shure ?
Philippe

[Robert-Jan Goossens]

Sorry misunderstood your question :-)

is autoboot set ?

isl> autoboot on

isl> lsautofl

does it return something like hpux ?

if not.

isl> hpux set autofile

Regards,
Robert-Jan

[Durand_1]

Yes, Robert-Jan it returns :
ISL> lsautofl

Auto-execute file contains:
hpux

[Stephen Keane]

Sorry, phillipe, I misread your question. I thought you were still trying to recovery/install from the Ignite tape.

You could try

ISL > bo p2

after running the SEArch command. To boot from your primary disk.

[Patrick Wallek]

I'm not entirely convinced that the install actually completed successfully / correctly.

What happens if you do a 'bo pri' or 'bo alt' (assuming that the mirror is set as the alternate boot path)?

Also, did you mirror by hand or have some post install scripts do the mirroring for you? Ignite does NOT re-mirror drives by itself when you install.

[Durand_1]

Here is the end of the restore :
* Download_mini-system: Complete
* Loading_software: Begin
* Installing boot area on disk.
* Enabling swap areas.
* Backing up LVM configuration for "vg00".
* Processing the archive source (recovery).
* Thu Jan 06 08:24:26 EST 2005: Starting archive load of the source
(Recovery Archive).
* Positioning the tape (/dev/rmt/0mn).
* Archive extraction from tape is beginning. Please wait.
* Thu Jan 06 08:38:47 EST 2005: Completed archive load of the source
(Recovery Archive).
* Executing user specified script:
"/opt/ignite/data/scripts/os_arch_post_l".
* Running in recovery mode (os_arch_post_l).
* Running the ioinit command ("/sbin/ioinit -c")
* Creating device files via the insf command.
insf: Installing special files for sdisk instance 0 address 0/0/1/0.3.0
insf: Installing special files for sdisk instance 1 address 0/0/1/1.15.0
insf: Installing special files for sdisk instance 2 address 0/0/2/1.15.0
insf: Installing special files for stape instance 0 address 0/0/1/0.1.0
insf: Installing special files for btlan instance 0 address 0/0/0/0
insf: Installing special files for btlan instance 1 address 0/2/0/0/4/0
insf: Installing special files for btlan instance 2 address 0/2/0/0/5/0
insf: Installing special files for btlan instance 3 address 0/2/0/0/6/0
insf: Installing special files for btlan instance 4 address 0/2/0/0/7/0
insf: Installing special files for pseudo driver dlpi
insf: Installing special files for pseudo driver kepd
insf: Installing special files for pseudo driver framebuf
insf: Installing special files for pseudo driver sad
* Running "/opt/upgrade/bin/tlinstall -v" and correcting transition link
permissions.
* Constructing the bootconf file.
* Setting primary boot path to "0/0/1/1.15.0".
* Executing user specified commands.
NOTE: tlinstall is searching filesystem - please be patient
NOTE: Successfully completed
* Loading_software: Complete
* Build_Kernel: Begin
NOTE: Since the /stand/vmunix kernel is already in place, the kernel will
not be re-built. Note that no mod_kernel directives will be processed.
* Build_Kernel: Complete
* Boot_From_Client_Disk: Begin
* Rebooting machine as expected.
NOTE: Rebooting system.

I tried to break with Ctrl-B and RS from GSP and BO PRI It hangs on the ISL prompt.

[Durand_1]

The disk configuration gave:

* Loading configuration utility...
* Beginning installation from source: /dev/rmt/0m
======= 01/06/05 08:21:04 EST Starting system configuration...
* Configure_Disks: Begin
* Will install B.11.00 onto this system.
* Creating LVM physical volume "/dev/rdsk/c3t15d0" (0/0/2/1.15.0).
* Creating LVM physical volume "/dev/rdsk/c1t15d0" (0/0/1/1.15.0).
* Creating volume group "vg00".
* Creating logical volume "vg00/lvol1" (/stand).
* Creating logical volume "vg00/lvol2" (swap_dump).
* Creating logical volume "vg00/lvol3" (/).
* Creating logical volume "vg00/lvol4" (/tmp).
* Creating logical volume "vg00/lvol5" (/home).
* Creating logical volume "vg00/lvol6" (/opt).
* Creating logical volume "vg00/lvol7" (/usr).
* Creating logical volume "vg00/lvol8" (/var).
* Creating logical volume "vg00/VARTMP" (/var/tmp).
* Creating logical volume "vg00/applia" (/APPLI_A).
* Creating logical volume "vg00/lvolsoft" (/SOFT).
* Creating logical volume "vg00/lvoloutils" (/OUTILS).
* Extending logical volume "vg00/lvol1" (/stand).
* Extending logical volume "vg00/lvol2" (swap_dump).
* Extending logical volume "vg00/lvol3" (/).
* Extending logical volume "vg00/VARTMP" (/var/tmp).
* Extending logical volume "vg00/applia" (/APPLI_A).
* Extending logical volume "vg00/lvolsoft" (/SOFT).
* Extending logical volume "vg00/lvol4" (/tmp).
* Extending logical volume "vg00/lvol5" (/home).
* Extending logical volume "vg00/lvol6" (/opt).
* Extending logical volume "vg00/lvol7" (/usr).
* Extending logical volume "vg00/lvol8" (/var).
* Extending logical volume "vg00/lvoloutils" (/OUTILS).
* Making HFS filesystem for "/stand", (/dev/vg00/rlvol1).
* Making VxFS filesystem for "/", (/dev/vg00/rlvol3).
* Making VxFS filesystem for "/var/tmp", (/dev/vg00/rVARTMP).
* Making VxFS filesystem for "/APPLI_A", (/dev/vg00/rapplia).
* Making VxFS filesystem for "/SOFT", (/dev/vg00/rlvolsoft).
* Making VxFS filesystem for "/tmp", (/dev/vg00/rlvol4).
* Making VxFS filesystem for "/home", (/dev/vg00/rlvol5).
* Making VxFS filesystem for "/opt", (/dev/vg00/rlvol6).
* Making VxFS filesystem for "/usr", (/dev/vg00/rlvol7).
* Making VxFS filesystem for "/var", (/dev/vg00/rlvol8).
* Making VxFS filesystem for "/OUTILS", (/dev/vg00/rlvoloutils).
* Setting rotational delay to 0 for "/stand".
* Configure_Disks: Complete
* Download_mini-system: Begin
x ./sbin/fs/hfs/mkfs, 229376 bytes, 448 tape blocks
x ./sbin/fs/hfs/newfs, 147456 bytes, 288 tape blocks
x ./sbin/fs/vxfs/mkfs, 262144 bytes, 512 tape blocks

... and so on for the mini-system install

[Robert-Jan Goossens]

Could it be the disk is not bootable (not being created with mkboot -a)?

isl> hpux /stand/vmunix

Regards,
Robert-Jan

[Durand_1]

Good Idea Robert,
but the result is
ISL> hpux/stand/vmunix
Isl command or utility name exceeds 10 characters.

What next ? Is it possible to modify the autolf ? Does it make sense ?

[Robert-Jan Goossens]

did you put a space between hpux and /stand/vmunix ?

[Stephen Keane]

Thats hpux /stand/vmunix
by the way

Or you could try

ISL> ls

[Durand_1]

with a space and ls :
ISL> hpux /stand/vmunix

ISL> ls
Utilities on this system are:

filename type start size created
====================================================
HPUX -12928 832 800 97/11/06 02:10:13

ISL>

[Helen French]

Just wondering why did you use '-Av' option with make_tape_recovery? The -A option has been used in the old make_recovery version to include the entire root volume group, but does a different function when used with make_tape_recovery. Are you using an include/exclude file option?

Did you ever try creating the Ignite tape with -x option? That will backup the entire vg00 normally:

# make_tape_recovery -I -v -x inc_entire=vg00 -a /dev/rmt/0mn

[Durand_1]

The make_recovery gave me the following output :
root@servoz:/# make_recovery -Av
NOTE: make_recovery(103): The make_recovery command will be replaced by
make_tape_recovery. Both commands are supported in this
release (Ignite-UX Revision 3.2). Please read the man page
make_tape_recovery(1M) for usage of the new command. In a
future release, make_recovery will be replaced by a script
that calls make_tape_recovery.
Option -A specified. Entire Core Volume Group/disk will be backed up.

It seems to be correct.
Nevertheless, I'm restarting the whole process with a new cartridge build with
make_tape_recovery -I -v -x inc_entire=vg00 -a /dev/rmt/0mn

In a few moment I'll see the result

[Durand_1]

I just tried to restore a tape produced by make_tape_recovery -I -v -x inc_entire=vg00 -a /dev/rmt/0mn
Same result : hanging at the "ISL>" prompt

[Stephen Keane]

What does

ISL> hpux ll /stand

give you?

That version of HPUX you've got there looks old, 1997?

[Durand_1]

No reaction --> back to the ISL> prompt

[Stephen Keane]

Probably not going to work... but

ISL> hpux -v

It looks like your secondary system loader is not a happy bunny.

Can you put the recovery tape on another machine, rewind it, run

dd if=/dev/rmt/?? of=/whatever bs=2k

then lifls -l /whatever

(substitute your own values for ?? and /whatever - you'll need some decent space in /whatever)

Is the HPUX on that listing the same as the one you posted earlier?

[Angus Crome]

Ignite version 3.2 is pretty old. It is entirely possible, that your firmware versions are not the same between those two machines, and ignite is not happy about it. I would suggest the firmware be brought up to current supported levels (equivalently), and the Ignite version be updated to current levels. There were lots of issues with older Ignite versions during system transitions (new hardware).

[Durand_1]

I will install Ignite C6 release on source system and try again.
I'm quite sure it's the solution.
Thanks everybody.

I'll post the result on monday or tuesday.
I will not upgrade a production server on Friday.

R. Crusoe was very happy : he allways got the job done by Friday ! ;-)))