topic Re: cloned system doesn't boot. in Operating System - HP-UX

cloned system doesn't boot.

SILO Storagetek — Thu, 08 Apr 2004 03:45:53 GMT

Hi everybody,
I made a make_recovery of an 11.0 v-class, and now I'm trying to install an n-class.
The problem appears at first reboot after installation: the new system doesn't boot. this is the console log:

Tryng Primary Boot Path
---
Booting...
Boot IO Dependent Code (IODC) revision 1
HARD Booted
ISL Revision A.00.36 OCT 26, 1994
ISL booting hpux

then, exits at:

ISL>

any suggest?

Re: cloned system doesn't boot.

Hoefnix — Thu, 08 Apr 2004 03:50:49 GMT

Hi,

I am not experienced on the V-class, but check if hardware archtecture is the same. Also see if the V-class uses the same number of disks.
Otherwise try to boot from ISL using: hpux -lq

HTH,
Peter

Re: cloned system doesn't boot.

Sanjay Kumar Suri — Thu, 08 Apr 2004 03:53:10 GMT

My understanding is as under:

make_recovery tape should generally be restored on a system on which it was created.

If you are trying to "clone" systems, consider using the make_sys_image.

sks

Re: cloned system doesn't boot.

Michael Tully — Thu, 08 Apr 2004 03:55:11 GMT

What version of ignite did you use to create the tape from the V class?
Only the very latest ignite version will create a system on a different class server.(although I wouldn't) Because of the different hardware involved, I would be more inclined to doa fresh install/patch and then import disks and the like.

Re: cloned system doesn't boot.

SILO Storagetek — Thu, 08 Apr 2004 04:01:55 GMT

I've already tryed "hpux -lq", with the same result.
I can try something else before to use make_sys_image?

thanks.
p.

Re: cloned system doesn't boot.

SILO Storagetek — Thu, 08 Apr 2004 04:04:22 GMT

sorry, I forget this:

B5725AA B.5.1.33 HP-UX Installation Utilities (Ignite-UX)

from Dec 2003 App. CD

p.

Re: cloned system doesn't boot.

Fabio Ettore — Thu, 08 Apr 2004 04:05:18 GMT

Ciao,

KBRC00007035 - Ignite-UX and Cloning guidelines.

In summary, the cloning guidelines are:

1) The source and target system must use the same install kernel if using a
make_recovery or make_tape_recovery tape. If not, use make_sys_image and
make_media_lif.

2) The source system must have the required Hardware Enablement patches needed
to generate a bootable kernel on the target.

HTH.

Best regards,
Ettore

Re: cloned system doesn't boot.

SILO Storagetek — Thu, 08 Apr 2004 04:19:08 GMT

I've just tryed to runa recovery shell.. and at the chroot_lvmdisk...

BAD SUPER BLOCK: MAGIC NUMBER WRONG
USE -b OPTION TO FSCK TO SPECIFY LOCATION OF AN ALTERNATE
SUPER-BLOCK TO SUPPLY NEEDED INFORMATION; SEE fsck(1M).
/sbin/fs/hfs/fsck -y /dev/rdsk/c1t6d0s2lvm Failed!

maybe doesn't find the boot area on disk?

Re: cloned system doesn't boot.

PVR — Thu, 08 Apr 2004 04:19:27 GMT

You made the recovery tape from V class and trying to restore it in N class. I don't think this will work.

The recommended thing is to restore the tape in the same system. I checked with other servers of same type. this will work. (I mean same class systems)

Re: cloned system doesn't boot.

SILO Storagetek — Thu, 08 Apr 2004 04:39:34 GMT

I'm tryng to make a new tape.. See you in a few hours...

p.