System Administration
cancel
Showing results for 
Search instead for 
Did you mean: 

DRD clone errors (lvlnboot: logical volume must be contiguous)

Will L
Occasional Visitor

DRD clone errors (lvlnboot: logical volume must be contiguous)

Hi,

I wonder if anybody has encountered this problem.

I'm trying to clone the vg00 volume group and am getting this error related to contiguous logical volume. You would think since the target is 146GB and the source is 72GB, this would not be a problem. Here's the output:

birch:/# drd clone -x overwrite=true -x ignore_unmounted_fs=true -v -t /dev/dsk/c1t2d0

======= 10/02/10 22:00:49 GMT BEGIN Clone System Image (user=root) (jobid=birch)

* Reading Current System Information


* Unmounted root volume group file systems will be ignored.
* Selecting System Image To Clone
* Selecting Target Disk
NOTE: There may be LVM 2 volumes configured that will not be recognized.
WARNING: Could not find "/dev/dsk/c10t0d3" in inventory
WARNING: Could not find "/dev/dsk/c13t0d3" in inventory
WARNING: Could not find "/dev/dsk/c10t0d0" in inventory
WARNING: Could not find "/dev/dsk/c13t0d1" in inventory
WARNING: Could not find "/dev/dsk/c10t0d3" in inventory
WARNING: Could not find "/dev/dsk/c13t0d3" in inventory
WARNING: Could not find "/dev/dsk/c10t0d0" in inventory
WARNING: Could not find "/dev/dsk/c13t0d1" in inventory
* The disk "/dev/dsk/c1t2d0" contains data which will be overwritten.
* Selecting Volume Manager For New System Image
* Analyzing For System Image Cloning
* Creating New File Systems
ERROR: Clone file system creation fails.
- Creating the target file systems fails.
- Command "/opt/drd/lbin/drdconfigure" fails with the return code 255. The errors written by
the command are displayed below:
- Start of errors written by /opt/drd/lbin/drdconfigure:
- * Using LVM for disk 0/4/1/0.0.0.2.0 (c1t2d0s2), group: drd00
* Creating LVM physical volume "/dev/rdsk/c1t2d0s2" (0/4/1/0.0.0.2.0).
* Creating volume group "drd00".
* Creating logical volume "drd00/lvol1" (/stand).
* Creating logical volume "drd00/lvol2" (swap_dump).
* Creating logical volume "drd00/lvol3" (/).
* Creating logical volume "drd00/lvol4" (/tmp).
* Creating logical volume "drd00/lvol5" (/u01).
* Creating logical volume "drd00/lvol6" (unused).
* Creating logical volume "drd00/lvol7" (/opt).
* Creating logical volume "drd00/lvol8" (/usr).
* Creating logical volume "drd00/lvol9" (/var).
* Creating logical volume "drd00/lvol200" (unused).
* Creating logical volume "drd00/lvol1bkp" (unused).
* Extending logical volume "drd00/lvol1" (/stand).
* Extending logical volume "drd00/lvol2" (swap_dump).
* Extending logical volume "drd00/lvol3" (/).
* Extending logical volume "drd00/lvol1bkp" (unused).
* Extending logical volume "drd00/lvol4" (/tmp).
* Extending logical volume "drd00/lvol5" (/u01).
* Extending logical volume "drd00/lvol6" (unused).
* Extending logical volume "drd00/lvol7" (/opt).
* Extending logical volume "drd00/lvol8" (/usr).
* Extending logical volume "drd00/lvol9" (/var).
* Extending logical volume "drd00/lvol200" (unused).
* Making VxFS filesystem for "/stand", (/dev/drd00/rlvol1).
* Making VxFS filesystem for "/", (/dev/drd00/rlvol3).
* Making VxFS filesystem for "/tmp", (/dev/drd00/rlvol4).
* Making VxFS filesystem for "/u01", (/dev/drd00/rlvol5).
* Making VxFS filesystem for "/opt", (/dev/drd00/rlvol7).
* Making VxFS filesystem for "/usr", (/dev/drd00/rlvol8).
* Making VxFS filesystem for "/var", (/dev/drd00/rlvol9).
* Installing boot area on disk.
ERROR: Command "/sbin/lvlnboot -A n -b /dev/drd00/lvol1" failed.

- End of errors written by /opt/drd/lbin/drdconfigure
- Command "/opt/drd/lbin/drdconfigure" fails with the return code 255. The entire output from
the command is given below:
- Start of output from /opt/drd/lbin/drdconfigure:
- Physical volume "/dev/rdsk/c1t2d0s2" has been successfully created.
Volume group "/dev/drd00" has been successfully created.
Logical volume "/dev/drd00/lvol1" has been successfully created with
character device "/dev/drd00/rlvol1".
Logical volume "/dev/drd00/lvol2" has been successfully created with
character device "/dev/drd00/rlvol2".
Logical volume "/dev/drd00/lvol3" has been successfully created with
character device "/dev/drd00/rlvol3".
Logical volume "/dev/drd00/lvol4" has been successfully created with
character device "/dev/drd00/rlvol4".
Logical volume "/dev/drd00/lvol5" has been successfully created with
character device "/dev/drd00/rlvol5".
Logical volume "/dev/drd00/lvol6" has been successfully created with
character device "/dev/drd00/rlvol6".
Logical volume "/dev/drd00/lvol7" has been successfully created with
character device "/dev/drd00/rlvol7".
Logical volume "/dev/drd00/lvol8" has been successfully created with
character device "/dev/drd00/rlvol8".
Logical volume "/dev/drd00/lvol9" has been successfully created with
character device "/dev/drd00/rlvol9".
Logical volume "/dev/drd00/IuXtMp10" has been successfully created with
character device "/dev/drd00/rIuXtMp10".
Logical volume "/dev/drd00/lvol200" has been successfully created with
character device "/dev/drd00/rlvol200".
Logical volume "/dev/drd00/lvol1bkp" has been successfully created with
character device "/dev/drd00/rlvol1bkp".
Logical volume "/dev/drd00/IuXtMp10" has been successfully removed.
Logical volume "/dev/drd00/lvol1" has been successfully extended.
Logical volume "/dev/drd00/lvol2" has been successfully extended.
Logical volume "/dev/drd00/lvol3" has been successfully extended.
Logical volume "/dev/drd00/lvol1bkp" has been successfully extended.
Logical volume "/dev/drd00/lvol4" has been successfully extended.
Logical volume "/dev/drd00/lvol5" has been successfully extended.
Logical volume "/dev/drd00/lvol6" has been successfully extended.
Logical volume "/dev/drd00/lvol7" has been successfully extended.
Logical volume "/dev/drd00/lvol8" has been successfully extended.
Logical volume "/dev/drd00/lvol9" has been successfully extended.
Logical volume "/dev/drd00/lvol200" has been successfully extended.
lvlnboot: Logical Volume "/dev/drd00/lvol1" must be contiguous.

- End of output from /opt/drd/lbin/drdconfigure
* Creating New File Systems failed with 1 error.
* Unmounting New System Image Clone
* System image: "sysimage_001" on disk "/dev/dsk/c1t2d0"
* Cleaning up after clone errors.

======= 10/02/10 22:01:48 GMT END Clone System Image failed with 1 error. (user=root) (jobid=birch)

6 REPLIES
Shibin_2
Honored Contributor

Re: DRD clone errors (lvlnboot: logical volume must be contiguous)

Have you searched this forum for similar issue.

I found this and hope it may help ( similar error ).

http://forums13.itrc.hp.com/service/forums/questionanswer.do?admit=109447627+1288751477736+28353475&threadId=1374506
Regards
Shibin
Will L
Occasional Visitor

Re: DRD clone errors (lvlnboot: logical volume must be contiguous)

Yes, I have searched itrc prior to my post. Unfortunately, I read that same discussion already. That person's problem was related to major/minor numbers, while mine is related to lvol1 which is not in contiguous state. Still hoping someone knows a workaround. Thanks.
Bill Hassell
Honored Contributor

Re: DRD clone errors (lvlnboot: logical volume must be contiguous)

> lvlnboot: Logical Volume "/dev/drd00/lvol1" must be contiguous.

This is not a DRD problem, this is a system problem. Somehow the mandatory contiguous design of lvol1 has been modified. Possibly someone (a root user) has used the pvmove command. If lvol1 is not contiguous, you will have problems booting this system. lvol1 needs to be repaired -- DRD is just letting you know.


Bill Hassell, sysadmin
Will L
Occasional Visitor

Re: DRD clone errors (lvlnboot: logical volume must be contiguous)

There are no problems when the server is rebooted. Yes, lvol1 has been changed from contiguous to non-contiguous. I guess it seems DRD can't be told to make the lvol contiguous when it is copying it?
Patrick Wallek
Honored Contributor

Re: DRD clone errors (lvlnboot: logical volume must be contiguous)

>>Yes, lvol1 has been changed from contiguous to non-contiguous.

Why would you do that? That can have very severe consequences. Your system may not boot correctly at some point in the future with this configuration.
Torsten.
Acclaimed Contributor

Re: DRD clone errors (lvlnboot: logical volume must be contiguous)

>> Yes, lvol1 has been changed from contiguous to non-contiguous


Never do this.

The system may or may not boot in normal mode; but it will probably never be able to boot into maintenance mode in case of emergency.


Create and restore an ignite backup in order to have a supported and healthy system again!

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!