P2V failed after 98% when converting physical RHEL 6.2 system

[ajoys]

Hi all,

We are getting the following error when converting physical system of RHEL 6.2 to virtual system using Vmware vCenter standalone converter 5.1 :

Status : FAILED: An error occurred during the conversion: 'Failed to restore original lvm in initrd image: /usr/lib/vmware-converter/restoreLvmInInitrd.sh failed with return code: 1, and message: * /mnt/p2v-src-root/dev has 3 files * user script returning code 0 * unmounting /mnt/p2v-src-root/dev /mnt/p2v-src-root/proc and /mnt/p2v-src-root/sys * Files to copy: /lib64/libudev.so.0 /lib64/libdl.so.2 /lib64/libdevmapper-event.so.1.02 /lib64/libdevmapper.so.1.02 /lib64/libreadline.so.6 /lib64/libc.so.6 /lib64/libselinux.so.1 /lib64/libsepol.so.1 /lib64/libtinfo.so.5 * Unpacking initrd image /mnt/p2v-src-root//boot/initramfs-2.6.32-220.el6.x86_64.img cpio: write error: No space left on device ERROR:

Unable to unpack initrd image /mnt/p2v-src-root//boot/initramfs-2.6.32-220.el6.x86_64.img '

Also in the log highlight is showing "Error: Unable to reconfigure the destination virtual machine."

The source file systems are:

$ uname -a

Linux idestest 2.6.32-220.el6.x86_64 #1 SMP Wed Nov 9 08:03:13 EST 2011 x86_64 x86_64 x86_64 GNU/Linux

$

$ df

Filesystem           1K-blocks      Used Available Use% Mounted on

/dev/sda7             10321208    522560   9274360   6% /

tmpfs                 16434556       300  16434256   1% /dev/shm

/dev/sda1               198337     59726    128371  32% /boot

/dev/sda3             15481840    598664  14096744   5% /opt

/dev/sda8             10321208    252696   9544224   3% /tmp

/dev/sda5             15481840   7667632   7027776  53% /usr

/dev/sda6             15481840    496016  14199392   4% /var

/dev/mapper/VG00-usr_sap

                     129015460  23310488  99151372  20% /usr/sap

/dev/mapper/VG00-oracle

                     433491744 346499652  64971996  85% /oracle

/dev/mapper/VG00-sapmnt

                      42317056   8990728  31176748  23% /sapmnt

$

Is there any solution for this type of error.  Please guide.

Regards

Ajoy Sonowal.

[patanassov]

Hi

let me give a little background first. mkinitrd script may call lvm. Sometimes this call fails when the lvm version in the distro converted is different from the one in helper VM. To work around this issue we patch the initrd image by injecting the lvm (and its libraries) from the helper, run mkinitrd, and then restore the original binaries in the image. All this requires additional disk space and time unfortunately.

This stuff happens in the /boot directory which is being created in a separate partition at the destination (even if it is not at the source). If you increase the boot partition size before starting the conversion, this should work around the issue. As an approximation, I suppose having it 3 times the size of the initrd image should suffice. In your case you have 32% usage, which is in the expected size. I think it hasn't been enough by just a small amount. But if you want to be on the safe side, double the partition size.

HTH

Plamen

[ajoys]

Hello Plamen,

Though we have converted the system successfully, We are not able to boot the system and we are getting the following error:

"Waiting for required block device discover..

"Waiting for two sda-like devices(s)..

We have tried by increasing the size of /boot by 4GB but still it fails. As you suggested by "patch the initrd image by injecting the lvm (and its libraries) from the helper, run mkinitrd, and then restore the original binaries in the image".  How we will inject lvm (and its libraries) from the helper?

Regards

Ajoy Sonowal.

[patanassov]

What you have done has been successful.The good news is the conversion has succeeded. the bad news is that you have hit a different issue. Unfortunately I don't know what is wring this time.

The loading messages mention kvm, but you said it is a physical machine (btw converter doesn't convert KVM machines). Is it a KVM server by chance? Can you pls give more info on peculiarities of the source machine. Also upload the log bundle, it might be useful.

[ajoys]

Hello ,

If we don't consider the LVMs, the converter converted P2V successfully. Though it is completed successfully but it is giving problem while booting the system which is mentioned above.

But if we consider LVMs for conversion, it fails after 98%.

So, what should we do both both the scenarios.

Regards

Ajoy Sonowal.

[patanassov]

I don't understand. What do you mean by "if we don't consider the LVMs"? Does it mean you have set the volumes to basic before conversion? If yes, does it also mean that if you don't set them to basic *and* increase the /boot volume size, it still fails with the same "no space left" error?