centos convert fails using vsphere converter.

Hi, I have read tons of articles here regarding on How to convert a CentOS from physical to virtual (P2V), but I want to know why  is failing the converter in our environment?

Attached you can find logs from converter. Also, you will see other information about the vcenter converter wizard.

Finally I have attached the fdisk's output  from our Centos server.

In case, our case will not be supported by the converter, which free solutions you experts think we should analyze to P2V our server.

If uou need other information, just let me know.

Thanks.
fdisk.txt
vmware-converter-server-2.log
vmware-converter-worker-2.log
LVL 2
CSIA ANAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
asavenerConnect With a Mentor Commented:
You can see in your screenshot that it's trying to use LVG for the disk with /.  (The little icon next to VitualDisk has LVG on it.)
0
 
asavenerCommented:
Well, this seems to be your problem:  
Disk id fake-disk-from-vg(vg_SRV2) does not identify an existing disk

Somewhere, you system references that disk, whether it's an extent in a logical volume, or an entry in FSTab, or something.  Find that reference, remove it, and probably reboot.
0
 
CSIA ANAuthor Commented:
Hi,
That's what I have on fstab

[root@SRV2 ~]# cat /etc/fstab

#
/dev/mapper/vg_SRV2-lv_root /                       ext4    defaults        1 1
UUID=428398a9-e2ca-49a2-9ebf-cafd06d45e67 /boot     ext4    defaults        1 2
/dev/mapper/vg_SRV2-lv_home /home                   ext4    defaults        1 2
/dev/mapper/vg_SRV2-lv_swap swap                    swap    defaults        0 0
tmpfs                   /dev/shm                tmpfs   defaults        0 0
devpts                  /dev/pts                devpts  gid=5,mode=620  0 0
sysfs                   /sys                    sysfs   defaults        0 0
proc                    /proc                   proc    defaults        0 0


[root@SRV2 ~]# vgdisplay
  --- Volume group ---
  VG Name               vg_SRV2
  System ID
  Format                lvm2
  Metadata Areas        1
  Metadata Sequence No  4
  VG Access             read/write
  VG Status             resizable
  MAX LV                0
  Cur LV                3
  Open LV               3
  Max PV                0
  Cur PV                1
  Act PV                1
  VG Size               67.28 GiB
  PE Size               4.00 MiB
  Total PE              17224
  Alloc PE / Size       17224 / 67.28 GiB
  Free  PE / Size       0 / 0
  VG UUID               FEyw3I-t3bO-LEkC-xwzu-TvVH-2E5s-0sSKGU

[root@SRV2 ~]# pvdisplay
  --- Physical volume ---
  PV Name               /dev/mapper/asr_Raid1p2
  VG Name               vg_SRV2
  PV Size               67.28 GiB / not usable 3.00 MiB
  Allocatable           yes (but full)
  PE Size               4.00 MiB
  Total PE              17224
  Free PE               0
  Allocated PE          17224
  PV UUID               KLSgzK-7AvY-1akC-xDZp-rLuD-LcA8-pGqdCj

[root@SRV2 ~]# lvdisplay
  --- Logical volume ---
  LV Path                /dev/vg_SRV2/lv_root
  LV Name                lv_root
  VG Name                vg_SRV2
  LV UUID                bjqnrT-08z5-wSvn-n7t0-Mz7O-u2zN-Mdpp18
  LV Write Access        read/write
  LV Creation host, time SRV2.domain.net, 2012-07-27 17:48:22 +0200
  LV Status              available
  # open                 1
  LV Size                50.00 GiB
  Current LE             12800
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:3

  --- Logical volume ---
  LV Path                /dev/vg_SRV2/lv_home
  LV Name                lv_home
  VG Name                vg_SRV2
  LV UUID                trnHVG-ERj9-EQoF-ipW1-Qng4-UOqk-0OcYA5
  LV Write Access        read/write
  LV Creation host, time SRV2.domain.net, 2012-07-27 17:48:37 +0200
  LV Status              available
  # open                 1
  LV Size                13.31 GiB
  Current LE             3408
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:5

  --- Logical volume ---
  LV Path                /dev/vg_SRV2/lv_swap
  LV Name                lv_swap
  VG Name                vg_SRV2
  LV UUID                eGpPhD-8mMb-elEY-ucCE-19R9-dJKz-7bJQ19
  LV Write Access        read/write
  LV Creation host, time SRV2.domain.net, 2012-07-27 17:48:46 +0200
  LV Status              available
  # open                 1
  LV Size                3.97 GiB
  Current LE             1016
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:4

Open in new window


It seems to be OK. Dont you think?
0
The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

 
asavenerCommented:
Yes, but since it references logical volumes created from the logical volume group vg_SRV2, I'd suggest looking at the extents used to create your logical volume group(s).

Run the "vgdisplay" command.
0
 
CSIA ANAuthor Commented:
vgdisplay output:

[root@SRV2 ~]# vgdisplay
  --- Volume group ---
  VG Name               vg_SRV2
  System ID
  Format                lvm2
  Metadata Areas        1
  Metadata Sequence No  4
  VG Access             read/write
  VG Status             resizable
  MAX LV                0
  Cur LV                3
  Open LV               3
  Max PV                0
  Cur PV                1
  Act PV                1
  VG Size               67.28 GiB
  PE Size               4.00 MiB
  Total PE              17224
  Alloc PE / Size       17224 / 67.28 GiB
  Free  PE / Size       0 / 0
  VG UUID               FEyw3I-t3bO-LEkC-xwzu-TvVH-2E5s-0sSKGU

Open in new window


See something?
0
 
asavenerCommented:
Oops, I'm sorry.  

We need the output from the physical volumes...

Please provide the output of pvdisplay and pvscan.
0
 
CSIA ANAuthor Commented:
Here's

[root@SRV2 ~]# pvdisplay
  --- Physical volume ---
  PV Name               /dev/mapper/asr_Raid1p2
  VG Name               vg_SRV2
  PV Size               67.28 GiB / not usable 3.00 MiB
  Allocatable           yes (but full)
  PE Size               4.00 MiB
  Total PE              17224
  Free PE               0
  Allocated PE          17224
  PV UUID               KLSgzK-7AvY-1akC-xDZp-rLuD-LcA8-pGqdCj

[root@SRV2 ~]# pvscan
  PV /dev/mapper/asr_Raid1p2   VG vg_SRV2   lvm2 [67.28 GiB / 0    free]
  Total: 1 [67.28 GiB] / in use: 1 [67.28 GiB] / in no VG: 0 [0   ]

Open in new window

0
 
asavenerCommented:
Well, that's obviously not it....

How about lvdisplay?
0
 
CSIA ANAuthor Commented:
lvdisplay output is in the thread... take a look above...;)
0
 
asavenerCommented:
Ah.  Didn't see that that the text window had additional data.

Well, that's a bust....

When you run the conversion, can you select the advanced disk options see whether that volume is listed as needing to be converted?  Maybe we can just unselect it from the conversion.
0
 
CSIA ANAuthor Commented:
Hi,

Advanced options are attached... dont really know what is happening...'-(
advanced.png
0
 
CSIA ANAuthor Commented:
It seems it's not possible to solve my problem...
0
 
asavenerCommented:
I would suggest the next step is to search all files on your system for the text "fake-disk-from-vg".

 grep -rnw '/' -e "fake-disk-from-vg"
0
 
CSIA ANAuthor Commented:
mmmm.... read this pls...

http://www.no-x.org/?p=910
0
 
asavenerCommented:
Yup, seems to accurately describe your issue.
0
 
CSIA ANAuthor Commented:
But, it's strange... I have searched on Knowledge Base inside vmware and it didn't returned any information.  What do you think it's? A bug to vmware converter?
0
 
asavenerCommented:
Are you running the latest version of the VMware converter?  (5.5.3)

From the release notes on 5.5.2:

P2V conversions of SLES 9 sources cannot complete, if the root directory is located on an LVM disk
When you select to convert a physical SLES 9 source, Converter Standalone cannot complete the conversion if the root directory is located on an LVM disk. After the conversion job is 99% complete, the job status changes to Failed and the following entry is added to the log:
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: * Unpacking initrd image /mnt/p2v-src-root//boot/initrd cpio: unsupported cpio format, use newc or crc ERROR: Unable to unpack initrd image /mnt/p2v-src-root//boot/initrd '

Workaround: Convert the LVM disk to a basic disk.

    On the Options page of the Conversion wizard, click Data to copy in the options list.
    Click Advanced and select the Destination layout tab.
    Select the volume that contains the root directory and click To basic.

0
 
CSIA ANAuthor Commented:
Yes.. version is 5.5.3 (latest)...

regarding this:
Workaround: Convert the LVM disk to a basic disk.

basic option is disabled (gray), so I cannot check it.  See image attached above advanced.png

;(
0
 
asavenerCommented:
Try hitting the "add a disk" button, and moving each mount point to its own disk.
0
 
CSIA ANAuthor Commented:
SOrry the delay.. I've been out of office.

@asavener, what do you mean by " moving each mount point to its own disk. "?
0
 
asavenerCommented:
In VMware converter, you can select the advanced view, and then create multiple virtual disks.  Then you highlight the mount point and use the up/down arrows to move it to the correct virtual disk.  Once you have each mount point on a dedicated virtual disk, try the conversion again.
0
 
CSIA ANAuthor Commented:
Hi,

I have tried but no success. I created 2 more virtualdisk and move filesystems to them. See image attached.
converter-3virtualdisk.png
0
 
asavenerCommented:
Hmm....

Just tried this on a Red Hat server, and the "to basic" button is enabled, once I add disks for the other partitions.

But it doesn't allow it for the /boot partition.  In fact, it automatically created a separate virtual disk for the /boot partition, and then  another virtual disk using logical volumes for the other partitions

Playing around with it a little more, / and /boot are pinned to their original virtual disks.  I can move /opt and swap around wherever I wish, though.


What version of CentOS are you running on this box?  I've seen several articles mention special difficulties with CentOS 5.5.  (Try running cat /etc/redhat-release)
0
All Courses

From novice to tech pro — start learning today.