Search This Blog

Friday, May 30, 2014

vxvmconvert Failed to Convert from LVM to VxVM


ISSUE:

During a convert from LVM for non-vg00 volume to VxVM with vxvmconvert, the analysis failed with the following error message:

" Device device_name has the following bad blocks: [1] bad block number (PE# n data block bnum) alternate number Cannot convert LVM Volume Group, vgXX "

SOLUTION:

Description:
Unlike LVM, VxVM does not support bad block revectoring at the physical volume level. If there appear to be any valid bad blocks in the bad block directory of any disk used in an LVM volume group, the group cannot be converted.

Action:
You have the following choices:
Place a hardware call to have the disk replaced or have the hardware engineer use the diagnostics (if applicable for this disk type) to re-vector the block. Then clear the BBDIR as described below.

If the errors were transient, or after the disk has been replaced, clear the BBDIR as follows:

Step 1. Back up all the data associated with the physical volume.

Step 2. Make a current backup of the LVM headers, for example:
# vgcfgbackup /dev/vg01

Step 3. Close all the logical volumes associated with the volume group and then deactivate the volume group.
# vgchange -a n /dev/vg01

Step 4. Create a dummy link to the raw device, for example:
# ln /dev/rdsk/c0t0d0 /dev/rdsk/temp

Step 5. Destroy the LVM headers using pvcreate -f on the dummy link, For example:
# pvcreate -f /dev/rdsk/temp

Step 6. Remove the dummy link to the raw device
# rm /dev/rdsk/temp

Step 7. Restore the headers from the lvmconf backup
# vgcfgrestore -n /dev/vg01 /dev/rdsk/c0t0d0

Step 8. Activate the volume group and integrity check the data or recover from backup.
# vgchange -a y /dev/vg01

Now, use vxvmconvert again to analyze the conversion from LVM to VxVM

No comments:

Post a Comment