Clone disk to disk on HP-UX

[nocandcan]

Currently, I want ghost from current HDD to new HDD to backup later.

I have ghost current HDD to new HDD by 'dd' command,

after I run 'dd' command complete, I turnoff temporary current HDD to boot with new HDD,

 but can not boot with new HDD.

I also adjust PRI BO with new H/W (new HDD) but can not be also boot with new HDD.

Can I have adjust more option to boot after using 'dd' command ?.

Please advise to me for this problem.

Thank you so much.

[Patrick Wallek]

You don't say what version of HP-UX you are running, but if you are running HP-UX 11.23/11iv2 or 11.31/11iv3 then Dynamic Root Disk is the best option to do something like this.

DRD is a FREE download and is available here:  http://www.hp.com/go/drd

To clone a disk with drd you use the following syntax:

# drd clone -x overwrite=true -t /dev/disk/disk3

(The above assumes an 11.31 system and uses the new disk names.  If you are using 11.23 you use the same syntax, but the regular /dev/dsk/c1t2d0 disk names.  Substitute the DESTINATION disk appropriate for your system after the '-t' option above.)

To activate the DRD disk so the system will boot from it:

# drd activate

Or you can simply use 'setboot' to set the primary boot path of your clone disk.

*****

I have used 'dd' in the past and have successfully booted a server.  The main issue is that you should really remove your original disk and place the 'dd' clone disk in the slot the original one was in.  The reason for this is that your 'dd' clone has all of the configuration from your original including files that reference the SCSI ID of the disk or specific device files for that disk.

In order to really diagnose your issue we need much more information:

1) What version of HP-UX?

2) What model server?

3) What errors do you see when you try to boot from the 'dd' clone disk?

[nocandcan]

I am sorry for my late reply.

About your information ask:

1) Version: OS_REV B.10.20

2) Model: 9000/778/B180L (ARCH 700, SW_ID 2013414539)

3) About error, please see file below:

(With this error, server auto restarted).

Thanks.

[Bill Hassell]

As Patrick said, you cannot boot the copy. The copy must boot with the same SCSI address and hardware slot as the original. Since you are on a workstation with the disks buried inside the box, you'll have to shutdown and power off the system, then with tools in hand, take apart the box, remove the primary disk and put the copied disk in its place. The system should now boot up correctly.

[Patrick Wallek]

OK, since it is HP-UX 10.20 DRD is not an option.

I agree with Bill 100%.  It can't configure VG00 because your clone disk is at a different SCSI address than the original.

If you move the clone disk to the slot the original disk is currently occupying you should be OK.

[nocandcan]

Thanks Bill and Patrick.

As the following your informations.

After I use 'dd' command complete, I have to shutdown and power off the system,

 I have to remove primary disk, then I installed copied disk into the same location

 of primary disk. Is this boot, ok?.

Thanks.

[Patrick Wallek]

Correct.  That should boot OK.

[nocandcan]

Hi, all

I have already started my server after I used 'dd' command and set jump for new disk same with current disk (server 2).

But when I login on as user and launch program, the server 1 reported 'Dump..'

I login on as root, that is Ok.

== I have got 3 servers with the same model '9000/778/B180L', OS HP-UX 10.20.

Server 1 is error disk, so It can not started.

I found the way to ghost from server 2 to new disk by 'dd' command,

       then install this new disk to server 1 to use.

Has the firmware of this two servers be different ?. so the server 1 reported 'Dump...'

(Firmware of server 2 (6.1) is newer than firmware of server 1 (5.6)).

Thank you so much.

[Bill Hassell]

>> But when I login on as user and launch program, the server 1 reported 'Dump..'

I login on as root, that is Ok

This is not very useful. You launch what program? What is the actual error message? Is it a core dump? Is there a core file left behind. If the system boots OK, it is unlikely the firmware is an issue, especially when it works OK as root. That sounds like a permission issue but there just aren't enough details to help.

[Torsten.]

Not sure what exactly you did, but maybe you have a problem with SCSI IDs.

Never use the same ID for 2 disks!

For cloning, set disk1 to 6 for example (original setting), second disk to 5.

Then run "dd", remove the disk with ID 6, change the ID of the "new" disk from 5 to 6 and start the system.

The new disk will not boot with still ID 5 instead of 6, but with both disks on 6 the system cannot work either.

[nocandcan]

I sorry for my late reply.

---> About: the server 1 reported 'Dump..'

+ Software information of Server 2:

SOFTWARE B3782EA_ABJ B.10.20 "HP-UX Media Kit (Reference Only. See Description) "

SOFTWARE B6193CA B.10.20.ACE.2 "Workstation ACE for HP-UX 10.20 (June 1998) "

SOFTWARE HPUXJpnRT700 B.10.20 "Japanese HP-UX Runtime VUE Environment with JSE "

SOFTWARE Ignite-UX-10-20 A.1.59.1 "HP-UX Installation Utilities for Installing 10.20 Systems "

+ Dump error:

Please help me about this error, Has it related to firmware ?.

Thank you so much.

[Dennis Handly]

>Has it related to firmware?

A HPMC is more likely related to a CPU hardware failure.

[nocandcan]

> A HPMC is more likely related to a CPU hardware failure.

Has any way to solve this error ?.

[Dennis Handly]

>Has any way to solve this error?

Replacing hardware.

[nocandcan]

> Replacing hardware.

I need only replace CPU with another CPU ?.

[Dennis Handly]

>I need only replace CPU with another CPU?

If you are lucky and have one.  Or the cache or a board may have a problem.

If you replace the CPU, you may have problems if your software depended on the machine ID given by uname(1).

[Torsten.]

>> If you replace the CPU, you may have problems if your software depended on the machine ID given by uname(1).

[edit]

Right, the CPU is fixed to the board.

First I would try to start with minimum RAM, without the HDD tray and without additional I/O cards in order to get the boot menu .

[nocandcan]

> Currently:

+ Server 1: firmware 5.6

+ Server 2: firmware 6.1

Could I fix this problem (Dumps error) by upgrade firmware ?

[nocandcan]

If server run program in user mode reported dump error, could I run program in root user to test ?.

[Dennis Handly]

>Could I fix this problem (Dumps error) by upgrade firmware?

Possibly if the firmware documents this particular HPMC fix.

>If server run program in user mode reported dump error, could I run program in root user to test?

Most likely not.  A HPMC doesn't care who you are.  A root user isn't running in privilege level 0.

[nocandcan]

> Possibly if the firmware documents this particular HPMC fix.

Have you got the firmware document this particular HPMC ?.

[Torsten.]

Latest firmware is version 6.1 from year 1999.

Fixes between 5.6 and 6.1:

PF_CB1X0060:

- fixes LAN timeout problem when the BCH lan search command is used

- the BCH search LAN command now allows the number of retries to be
set to specific values. Two different types can be controlled: the
number of retries while searching for a server and the number of
retries during an IO transfer. These values are set by specifying a
LAN IP (all zeros means search for any available server) followed by
the search retry number and the IO retry number.

Example: sea lan.0.0.0.0.5.100 specifies a search for any
available server retrying search packets 5 times and IO packets
100 times.

- a "-5 returned by LAN entry init" is now only displayed if
a specific "search lan" is used vs a general "search". A message
suggesting that a LAN cable may be missing or not connected
will be displayed also.

PF_CB1X0058:

- supports latest version of LAN controller chipset

[nocandcan]

About upgrading new firmware, has that been solved the problem 'crash dump' ?

[Dennis Handly]

>has that been solved the problem 'crash dump'?

From Torsten's document, it doesn't look like it, HPMC isn't mentioned.  But you might as well upgrade, you don't have anything to lose.