Operating System - HP-UX
1753303 Members
6481 Online
108792 Solutions
New Discussion юеВ

Ignite Recovery Clone of rx6600 Hanging

 
Shayne Ludlow
Occasional Advisor

Ignite Recovery Clone of rx6600 Hanging

Hi,

I am attempting to clone an ignite archive of an rx6600 to another rx6600 using the network, albeit on different subnets. Unfortunatly the install is hanging on "loading configuration utility...."

I have completed these steps on the ignite server:-
1. Create a directory in the /var/opt/ignite/clients directory of the MAC addresss and link it to the the target host name,change owner to bin:bin.
2. Copy CINDEX and the recovery directory from the source directory into the newly created directory.
3. Made an entry for the new host in the /etc/exports file.

On the target server.
1. Boot from DVD.
2. Select to Install using an ignite server and then set the new install off from the ignite server changing the network parameters to that of the target server.

I would be grateful for any ideas you might have on how I can resolve the hanging issue?

Many Thanks

Regards

Colin

Details.
Ignite Server version C.7.4.157
Ignite Server OS PA-RISC HPUX 11.11
Source OS 11.31 (March 2008)

Install log is pasted below!

======= 06/23/08 12:08:44 EDT HP-UX Installation Initialization. (Mon Jun 23
12:08:44 EDT 2008)
@(#)Ignite-UX Revision C.7.0.212
@(#)ignite/launch (opt) $Revision: 10.590.1.2 $ $Date: 2006/12/18
20:51:11 $

* Configuring RAM filesystems...
* SAS (Serial Attached SCSI) disk devices (LUNs) found = 2.
* Reorder SAS disks/LUNs to physical order, swap:
0/4/1/0.0.0.1.0 (SAS:ENC1:BAY07 0x5000c5000a318239.0x0) <=>
0/4/1/0.0.0.0.0 (SAS:ENC1:BAY08 0x5000c5000a311335.0x0)
* Current SAS disk/LUN status:
* 0/4/1/0.0.0.0.0 0x5000c5000a318239.0x0 SAS:ENC1:BAY07
0x5000c5000a318239 "HP DH072BB978 "
* 0/4/1/0.0.0.1.0 0x5000c5000a311335.0x0 SAS:ENC1:BAY08
0x5000c5000a311335 "HP DH072BB978 "
* Scanning system for IO devices...
* Setting keyboard language.

The dimensions your terminal window is reporting (80x23) is insufficient to run the installation application. It must be at least 80x24 characters large. If you are using a resizeable (X11) terminal window, then you should resize it now.
Would you like recheck the dimensions now? ([y]/n): *
Response was: y

* Could not get DHCP information. No host specific network defaults
will be supplied. (dhcpclient returned: 9)
* Bringing up Network (lan2)
add net default: gateway 10.55.178.254
* NFS mounting clients directory.
* Using client directory: /var/opt/ignite/clients/0x001A4B0854C1
NOTE: Ignite-UX is ready to install the client. Start the installation from
the "ignite" user interface using the menu: "Action" -> "Install
client" -> "New Install"
* Checking configuration for consistency...
NOTE: The disk at HW path: 0/4/1/0.0x5000c5000a315b95.0x0 does not exist on
the system and is being substituted by the disk at:
0/4/1/0.0x5000c5000a311335.0x0 (HP_DH072BB978)
NOTE: Free space (7703712KB) in "/var" where /var/adm/crash is located is
less than system memory (8357276KB). This should be enough space to
capture at least a single dump (and likely more than that if the dump
is selective and/or compressed) in the event of a system crash.
Additional space may be required to uncompress the dump in order to
analyze it and to save multiple dumps. You can increase the size of
the "/var" volume on the "File System" tab when using the advanced
user interface.
WARNING: The disk at: 0/4/1/0:SAS:ENC1:BAY08 (HP_DH072BB978) appears to contain
a file system and boot area. Continuing the installation will destroy
any existing data on this disk.
WARNING: The disk at: 0/4/1/0:SAS:ENC1:BAY07 (HP_DH072BB978) appears to contain
a file system and boot area. Continuing the installation will destroy
any existing data on this disk.

6 REPLIES 6
Ivan Krastev
Honored Contributor

Re: Ignite Recovery Clone of rx6600 Hanging

Hi Shayne,

Please post the latest records from the log file.

Until now everything looks ok.


regards,
ivan
Steven E. Protter
Exalted Contributor

Re: Ignite Recovery Clone of rx6600 Hanging

Shalom,

Boot from the DVD and then use an Ignite server?

Normally to install off an Ignite server you boot off it, using a boot helper to bridge the gap if needed.

* Could not get DHCP information. No host specific network defaults
will be supplied. (dhcpclient returned: 9)
* Bringing up Network (lan2)
add net default: gateway 10.55.178.254

I think your server is having trouble as well getting DHCP network information.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Torsten.
Acclaimed Contributor

Re: Ignite Recovery Clone of rx6600 Hanging

I agree to Ivan, the last message is a warning about an existing file system on the disk - no problem until now.

Is there a question like "continue y/n" or something similar?

Or is the system already restoring the image?

During the restore you won't see so much ...

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Scot Bean
Honored Contributor

Re: Ignite Recovery Clone of rx6600 Hanging

I do not expect a subnet issue, booting from DVD first gets around that just fine.

You have shown us the server log output, but what about the target's console? Right after this point in the log is where the console interface is active and may be requesing your input / action.

So check the target console, see what is going on there.
Shayne Ludlow
Occasional Advisor

Re: Ignite Recovery Clone of rx6600 Hanging

All,

Thanks for your responses, it turns out that I was being in-patient (seems to be taking a long time, but I guess the ignite server is remote on a 100meg link). However it managed to load the mini system and then bombed out trying to nfs mount the archive. So I have removed the access=hostname from the /etc/exports file re-exported and restarted the install.

Thanks

Regards

Colin

PS Will advise once complete and assign points

Previous install log is below:-

======= 06/23/08 12:08:44 EDT HP-UX Installation Initialization. (Mon Jun 23
12:08:44 EDT 2008)
@(#)Ignite-UX Revision C.7.0.212
@(#)ignite/launch (opt) $Revision: 10.590.1.2 $ $Date: 2006/12/18
20:51:11 $

* Configuring RAM filesystems...
* SAS (Serial Attached SCSI) disk devices (LUNs) found = 2.
* Reorder SAS disks/LUNs to physical order, swap:
0/4/1/0.0.0.1.0 (SAS:ENC1:BAY07 0x5000c5000a318239.0x0) <=>
0/4/1/0.0.0.0.0 (SAS:ENC1:BAY08 0x5000c5000a311335.0x0)
* Current SAS disk/LUN status:
* 0/4/1/0.0.0.0.0 0x5000c5000a318239.0x0 SAS:ENC1:BAY07
0x5000c5000a318239 "HP DH072BB978 "
* 0/4/1/0.0.0.1.0 0x5000c5000a311335.0x0 SAS:ENC1:BAY08
0x5000c5000a311335 "HP DH072BB978 "
* Scanning system for IO devices...
* Setting keyboard language.

The dimensions your terminal window is reporting (80x23) is insufficient to run the installation application. It must be at least 80x24 characters large. If you are using a resizeable (X11) terminal window, then you should resize it now.
Would you like recheck the dimensions now? ([y]/n): *
Response was: y

* Could not get DHCP information. No host specific network defaults
will be supplied. (dhcpclient returned: 9)
* Bringing up Network (lan2)
add net default: gateway 10.55.178.254
* NFS mounting clients directory.
* Using client directory: /var/opt/ignite/clients/0x001A4B0854C1
NOTE: Ignite-UX is ready to install the client. Start the installation from
the "ignite" user interface using the menu: "Action" -> "Install
client" -> "New Install"
* Checking configuration for consistency...
NOTE: The disk at HW path: 0/4/1/0.0x5000c5000a315b95.0x0 does not exist on
the system and is being substituted by the disk at:
0/4/1/0.0x5000c5000a311335.0x0 (HP_DH072BB978)
NOTE: Free space (7703712KB) in "/var" where /var/adm/crash is located is
less than system memory (8357276KB). This should be enough space to
capture at least a single dump (and likely more than that if the dump
is selective and/or compressed) in the event of a system crash.
Additional space may be required to uncompress the dump in order to
analyze it and to save multiple dumps. You can increase the size of
the "/var" volume on the "File System" tab when using the advanced
user interface.
WARNING: The disk at: 0/4/1/0:SAS:ENC1:BAY08 (HP_DH072BB978) appears to contain
a file system and boot area. Continuing the installation will destroy
any existing data on this disk.
WARNING: The disk at: 0/4/1/0:SAS:ENC1:BAY07 (HP_DH072BB978) appears to contain
a file system and boot area. Continuing the installation will destroy
any existing data on this disk.
* Beginning installation from source: 10.59.4.63

======= 06/23/08 15:32:10 EDT Starting system configuration...



* Configure_Disks: Begin

NOTE: The disk at HW path: 0/4/1/0.0x5000c5000a315b95.0x0 does not exist on
the system and is being substituted by the disk at:
0/4/1/0.0x5000c5000a311335.0x0 (HP_DH072BB978)
* Mapping LUN Instance Data
NOTE: The disk at HW path: 0/4/1/0.0x5000c5000a315b95.0x0 does not exist on
the system and is being substituted by the disk at:
0/4/1/0.0x5000c5000a311335.0x0 (HP_DH072BB978)
* Will install B.11.31 onto this system.
WARNING: failed to remove(/sbin/insf): Text file busy (errno = 26)
* Creating LVM physical volume "/dev/rdisk/disk5"
(0/4/1/0.0x5000c5000a311335.0x0).
* Creating LVM physical volume "/dev/rdisk/disk4_p2"
(0/4/1/0.0x5000c5000a318239.0x0).
* Creating volume group "vg00".
* Creating logical volume "vg00/lvol1" (/stand).
* Creating logical volume "vg00/lvol2" (swap).
* Creating logical volume "vg00/lvol3" (dump).
* Creating logical volume "vg00/lvol4" (/).
* Creating logical volume "vg00/lvol5" (/tmp).
* Creating logical volume "vg00/lvol6" (/home).
* Creating logical volume "vg00/lvol7" (/opt).
* Creating logical volume "vg00/lvol8" (/usr).
* Creating logical volume "vg00/lvol9" (/var).
* Extending logical volume "vg00/lvol1" (/stand).
* Extending logical volume "vg00/lvol2" (swap).
* Extending logical volume "vg00/lvol3" (dump).
* Extending logical volume "vg00/lvol4" (/).
* Extending logical volume "vg00/lvol5" (/tmp).
* Extending logical volume "vg00/lvol6" (/home).
* Extending logical volume "vg00/lvol7" (/opt).
* Extending logical volume "vg00/lvol8" (/usr).
* Extending logical volume "vg00/lvol9" (/var).
* Making VxFS filesystem for "/stand", (/dev/vg00/rlvol1).
* Making VxFS filesystem for "/", (/dev/vg00/rlvol4).
* Making VxFS filesystem for "/tmp", (/dev/vg00/rlvol5).
* Making VxFS filesystem for "/home", (/dev/vg00/rlvol6).
* Making VxFS filesystem for "/opt", (/dev/vg00/rlvol7).
* Making VxFS filesystem for "/usr", (/dev/vg00/rlvol8).
* Making VxFS filesystem for "/var", (/dev/vg00/rlvol9).


* Configure_Disks: Warning



* Download_mini-system: Begin

LINES CUT TO REDUCE OUPUT ----

* Download_mini-system: Complete



* Loading_software: Begin

* Installing boot area on disk.
* Formatting HP Service Partition.
* Enabling swap areas.
* Backing up LVM configuration for "vg00".
* Processing the archive source (Archive_of_bgwdwms2).
nfs mount: 10.59.4.63:/var/opt/ignite/recovery/archives/bgwdwms2: Permission denied
NOTE: Retrying: "/sbin/fs/nfs/mount -oro
10.59.4.63:/var/opt/ignite/recovery/archives/bgwdwms2
/tmp/ign_configure/archive_nfs"
nfs mount: 10.59.4.63:/var/opt/ignite/recovery/archives/bgwdwms2: Permission denied
NOTE: Retrying: "/sbin/fs/nfs/mount -oro
10.59.4.63:/var/opt/ignite/recovery/archives/bgwdwms2
/tmp/ign_configure/archive_nfs"
nfs mount: 10.59.4.63:/var/opt/ignite/recovery/archives/bgwdwms2: Permission denied
NOTE: Retrying: "/sbin/fs/nfs/mount -oro
10.59.4.63:/var/opt/ignite/recovery/archives/bgwdwms2
/tmp/ign_configure/archive_nfs"
nfs mount: 10.59.4.63:/var/opt/ignite/recovery/archives/bgwdwms2: Permission denied
NOTE: Retrying: "/sbin/fs/nfs/mount -oro
10.59.4.63:/var/opt/ignite/recovery/archives/bgwdwms2
/tmp/ign_configure/archive_nfs"
nfs mount: 10.59.4.63:/var/opt/ignite/recovery/archives/bgwdwms2: Permission denied
NOTE: NFS mount (/sbin/fs/nfs/mount -oro
10.59.4.63:/var/opt/ignite/recovery/archives/bgwdwms2
/tmp/ign_configure/archive_nfs) failed, see messages above.
ERROR: Command "/sbin/fs/nfs/mount -oro
10.59.4.63:/var/opt/ignite/recovery/archives/bgwdwms2
/tmp/ign_configure/archive_nfs" failed. Ensure that
"/var/opt/ignite/recovery/archives/bgwdwms2" is properly exported on
10.59.4.63.
ERROR: Cannot load OS archive(s) (Archive_of_bgwdwms2)

The configuration process has incurred an error, would you like
to push a shell for debugging purposes? (y/[n]): *
Response was: n



* Loading_software: Error


======= 06/24/08 04:06:02 EDT Installation complete: Failure

NOTE: Search for the word "ERROR" in the log file for details:
on a server: /var/opt/ignite/clients/0x001A4B0854C1/install.log
on a client: /var/opt/ignite/local/install.log
NOTE: Rebooting system.

Shayne Ludlow
Occasional Advisor

Re: Ignite Recovery Clone of rx6600 Hanging

Hi,

Seems the slow network was just one of my issues. I have now switched too a faster network which means I now get to the real issue a lot faster.

The ignite recovery completes almost all of the steps but fails to reboot the server on the "boot from the client disk" step. When I switched to the client console the first time it was hanging on "insf: installing special files esdisk instance 4 etc ...".

The archive source rx6600 is indetical to the target and both have the same firmware!

MP FW F.02.17
BMC FW 05.21
EFI FW ROM A 06.20 ROM B 06.20
Systen FW ROM A 03.01, ROM B 03.01 Boot ROM B
PDH FW 50.07
DHPC Fw 01.23
UCIO FW 03.0b
PRS FW 00.08 UpSeqRev 0c, DownSeq 08
HFC FW 00.04 SetRev 00

I power cycled the server and now it is in a loop of crashing and rebooting!

Any thoughts on what might be causing this would be great!

Thanks

Regards

Colin