drd clone fails whilst trying to make clone bootable

[Mr Phil Rigby]

Hi,

I have an RX8640 with HP-UX 11i v3, September 2008 running on it. I am trying to make a clone of the root disk to another internal disk on the server. The command I issue is:-

/opt/drd/bin/drd clone -t /dev/disk/disk18 -x overwrite=true -x verbosity=5

The log from this suggests it copies the filesystem contents ok but fails to make the clone bootable. Here is the log:-

======= 04/21/09 12:15:09 BST BEGIN Clone System Image (user=root) (jobid=ukcsbpd1)

* Reading Current System Information
* Selecting System Image To Clone
* Selecting Target Disk
* The disk "/dev/disk/disk18" contains data which will be overwritten.
* Selecting Volume Manager For New System Image
* Analyzing For System Image Cloning
* Creating New File Systems
* Copying File Systems To New System Image
* Making New System Image Bootable
ERROR: Making the file system bootable on clone fails.
- Mounting the file system fails.
- Mounting the inactive system image fails.
- An inactive system image could not be identified for "mount".
* Making New System Image Bootable failed with 1 error.
* Preparing To Unmount New System Image Clone
ERROR: No system image is available to "unmount.".
* Cleaning up after clone errors.

======= 04/21/09 12:36:13 BST END Clone System Image failed with 2 errors. (user=root) (jobid=ukcsbpd1)

Anyone know what I should do?

A secondary question is that, even though specifying -x verbosity=5 on the drd clone command, no extra info was written to the output log. Is this normal behaviour?


Thanks,
Phil.

[Bart Paulusse]

Hi Phil,

I'n running 11iv2 but on my systems creating a clone only succeeded recently after downloading the latest version of DRD.

What kind of disk is your target disk?

Regards,
Bart

[Mr Phil Rigby]

As I said, I am attempting to clone to another internal disk shipped with the RX8640 server. Both the source and target disks were factory-installed hardware with the server.

[Torsten.]

You said in your other thread disk 18 is an active boot disk - is it still?

http://forums.itrc.hp.com/service/forums/questionanswer.do?threadId=1333068

[Andrew Rutter]

hi,

It may be worth checking the version of DRD installed.

It could be that your new system is using VG version 2.0.

you can check this with vgdisplay

up until the latest version i think it was, that it would fail while making the boot part using the lvlnboot files with 2.0

migth be worth checking the release notes of DRD on docs.hp.com

Andy

[Mr Phil Rigby]

I got the cloning working in the end by doing a pvremove on the target disk, disk18. Yes Torsten this was left over from the old incorrect way I had tried to mirrored at nPars level.

Out of interest Andy, vgdisplay shows vg v1.0.

So, the only unanswered bit here now is the verbosity setting in the drd clone command not appearing to make any difference to the amount of stuff that is written to the log.

Incidentally, my drd version is:

# swlist -l product|grep -i drd
DRD B.1131.A.3.2.1959 Dynamic Root Disk

[Torsten.]

For your information - this site lists versions, release notes, patches, etc...

http://docs.hp.com/en/DRD/infolib.html

There is already a newer version with new features, fixes ... (need add. patches).

[Marlou Everson]

Phil,

I had the same experience with the verbosity setting when I was having problems with DRD. No matter what it was set at, there was nothing else logged. Sort of falls into the bucket with the contact your System Administrator messages. :)

Marlou

[Judy Wathen]

Hello Phil,

Can you check whether the /stand/bootconf file on the booted disk contains the device file of the clone target? If so, you need to remove it.

The /stand/bootconf file on the booted system should contain device files for just the booted disk and any of its mirrors not the clone target.

The /stand/bootconf file that is created on the clone target WILL contain the device file of the target itself (or, on an IPF system, the device file of the HP-UX partition of the target).

Certainly nothing in the error messages displayed makes this action obvious. Starting with Release A.3.2 of DRD, the check on /stand/bootconf was moved much earlier in the clone and the message improved. We have also decreased our dependence on the bootconf file, but you still need to remove the clone target from it.

It is true that, while DRD has the ability to issue â very verboseâ messages, there are very few such messages in the product. â This is an area for improvement.

Thanks,
Judy