topic Re: drd clone fails - making clone image bootable fails in Operating System - HP-UX

drd clone fails - making clone image bootable fails

VUT — Tue, 06 Nov 2012 14:03:17 GMT

doing a DRD clone on a 11.31 VM

keeps failing at the making clone image bootable

the following error appears

unable to stat " /var/opt/drd/mnts/sysimage_001/dev/vg00/lvswap1"

lvswap1 no longer exsists as has been removed - cannot see where this is being picked up from by the clone process !

We have just downloaded and used the latest DRD software same error

Any ideas would be good as spent too long looking at his and am now going round in circles

Re: drd clone fails - making clone image bootable fails

Patrick Wallek — Tue, 06 Nov 2012 14:30:54 GMT

You can enable additional logging / debugging messages to try to figure out what's happening:

Remove all files under /var/opt/drd/tmp, then run your DRD clone as below:

# export SMDDEBUG_SMDinit=9
#export INST_DEBUG=5
#drd clone -t /dev/disk/diskXXX -x overwrite=true -x verbosity=5

Once it has finished, or has failed, check the log files in /var/opt/drd/tmp.

Re: drd clone fails - making clone image bootable fails

VUT — Tue, 06 Nov 2012 16:02:25 GMT

thanks for the info

Found a reference to lvswap1 in one of the files but still dont know where it comes from

looks like some reference to the kernel as has /kconfig/Modules in the file

but the one containing the lvswap1 reference has a section starting

/pri_swap_node (0x1)

under this is

ps_path KR_VTYPE_STRING "/dev/vg00/lvswap1" (0x1)

so again where is DRD getting this info as lvlnboot shows swap as lvol2 - is there a way to change it in kernel to be lvol2 if that is where it is getting this info !!

Re: drd clone fails - making clone image bootable fails

Patrick Wallek — Tue, 06 Nov 2012 16:44:05 GMT

The lvlnboot output will only show your PRIMARY swap, which is usually lvol2.

However, you may have other swap logical volumes configured in VG00. You can look to see what swap you have configured via the 'swapinfo -tam' command. You should also look in /etc/fstab to see what swap areas are to be activated on system boot.

If the output of 'swapinfo' and the volumes listed in /etc/fstab do not match then that may be a problem. Since LVOL2 is the primary swap space, it will NOT be listed in /etc/fstab.

Re: drd clone fails - making clone image bootable fails

VUT — Tue, 06 Nov 2012 16:57:30 GMT

lvswap1 not showing in swapinfo or in fstab not showing as a lv under vg00 - argghh

Re: drd clone fails - making clone image bootable fails

Steven E. Protter — Tue, 06 Nov 2012 18:06:48 GMT

Shalom,

I have some experience with this issue. Normally this happens when the target disk has issues. The disk may be beginning to fail.

I've also seen it less often as a result of a software defect.

swlist -l bundle DynRootDisk

Please post and consider using the most current version.

SEP

Re: drd clone fails - making clone image bootable fails

VUT — Thu, 08 Nov 2012 13:34:33 GMT

Hi SEP

disk is a lun on SAN so not a physical disk in server

We are using the latest version of drd - B11.31.A.3.11.328 clone was also failing with previous version which is why we updated just in case !!

Re: drd clone fails - making clone image bootable fails

VUT — Mon, 12 Nov 2012 10:39:27 GMT

Ok gave in a raised a support case

They believed some reference to lvswap1 was hanging about or removed incorrectly

So we just did an lvcreate / lvremove of lvswap1 - this appears to have cleared the issue and the clone now completes ok