Issue in creating DRD with a disk

[Jayaprakash Subramanian]

Hello All,

I have an EVA and rx machine and I have created a new vdisk on the EVA and try to clone the existing disk to the new disk using DRD.

root@apln01# /usr/sbin/ioscan -fNnkC disk
Class I H/W Path Driver S/W State H/W Type Description
===================================================================
disk 33 64000/0xfa00/0x1d esdisk CLAIMED DEVICE HP HSV200
/dev/disk/disk33 /dev/rdisk/disk33
/dev/disk/disk33_p1 /dev/rdisk/disk33_p1
/dev/disk/disk33_p2 /dev/rdisk/disk33_p2
/dev/disk/disk33_p3 /dev/rdisk/disk33_p3
disk 34 64000/0xfa00/0x21 esdisk CLAIMED DEVICE HP HSV200
/dev/disk/disk34 /dev/rdisk/disk34

Here /dev/rdisk/disk33 is the original disk and /dev/rdisk/disk34 is the newly created disk.

I gave the following command to put DRD to copy the disk to the new vdisk

root@apln01# /opt/drd/bin/drd clone -v -x overwrite=true -t /dev/disk/disk34

It throws the following error -
======= 04/06/09 02:03:56 PDT BEGIN Clone System Image (user=root) (jobid=ap03)

* Reading Current System Information
* Selecting System Image To Clone
* Selecting Target Disk
ERROR: Selection of the target disk fails.
- Selecting the target disk fails.
- Validation of the disk "/dev/disk/disk34" fails with the following error(s):
- The device special file "/dev/disk/disk19" cannot be identified in the system configuration information.
* Selecting Target Disk failed with 1 error.

======= 04/06/09 02:04:01 PDT END Clone System Image failed with 1 error. (user=root) (jobid=ap03)

I didn't get any disk named "/dev/disk/disk19" during ioscan. What is that device special file?

Did I need to do something else to perform this task?

Please Advise.

Thanks,
Jayaprakash S

[Ivan Krastev]

Remove DRD registry file - see the latest post here - http://forums.itrc.hp.com/service/forums/questionanswer.do?admit=109447627+1239012081359+28353475&threadId=1289262

regards,
ivan

[Matti_Kurkela · Accepted solution]

Check /stand/bootconf. Maybe "/dev/disk/disk19" is old information and /stand/bootconf was not updated in some previous change?

For more information on /stand/bootconf, use "man bootconf".
http://docs.hp.com/en/B2355-60130/bootconf.4.html

Although updating /stand/bootconf whenever boot disk configuration is changed has been a recommended procedure for a long time, some people have omitted that because leaving it out has no immediate harmful effect. But DRD requires that /stand/bootconf is correct.

(A correct /stand/bootconf also ensures that swinstall can install any bootloader patches to all configured boot disks, so maintaining it is important even if DRD is not used.)

MK

[Jayaprakash Subramanian]

Hi Matti Kurkela,

Thanks for your info, This problem is resolved.

I have another question. After cloning the disk, I need to boot a disk in the vpar (either the original or the cloned one. But only one disk is connected at a time.). Shall I use primary and secondary boot paths? If primary disk is found, then it boots on that path and if the primary disk is not there, then it boots on the alternate path. Is this approach is correct or is there any alternate ways are there.

What shall I do for archiving this?

Thanks,
Jayaprakash S