VMware Cloud Community
Gilbert2797
Contributor
Contributor

Converter fails when converting Red Hat Linux 4 OS

I'm using the latest version of the Standalone Converter and I've been able to successfully convert other Red Hat Linux physical machines, just not this particular machine.

It keeps failling at the /VAR partition.  I even tried to do a cold boot from CD but that fails as well.

I opened up a case with RedHat support so they can help me check the file system on VAR and it checked out ok.  I opened up a case with Vmware support and I don't think my assigned tech knows what to do either.  Here's what we tried:

Followed the command
made a dir :-  mkdir -p /tmp/p2v-src-root/var   (assuming you have enough space in /tmp for the contents of /var from the source)

Also followed the below command.
ssh root@<IP> "tar --one-file-system --sparse -C /var -cf - ." | tar -v -C /tmp/p2v-src-root/var -xf -

When the script ran took a duplicate session and observed the files were stuck and were not copied properly.

So suggested him to take a backup of the var partition and then delete the contents in log folder.

------------------------------------------------------------

I tried this but it didn't work.  (i.e. I removed all the log files but then I noticed it getting stuck in a different location)

0 Kudos
8 Replies
continuum
Immortal
Immortal

if I remember right the "var" problem has been solved before - did you search in this section for it ?

sorry - don't have a link - I gave up searching this forum long ago


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

0 Kudos
Gilbert2797
Contributor
Contributor

I tried searching for VAR but it didn't come up with anything.

0 Kudos
continuum
Immortal
Immortal

I would not waste my time with Hotclone-Converter - either do it manually with a Coldclone CD like described here
http://www.petri.co.il/physical-to-virtual-conversion-of-linux-servers-with-vmware-converter-bootcd....

or follow any of the other howtos  you find in google


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

0 Kudos
Gilbert2797
Contributor
Contributor

I tried that but it still fails.

0 Kudos
continuum
Immortal
Immortal

then use a Knoppix LiveCD and use dd - store the image in a USB disk

a dd image can be easily converted to a esx-ready vmdk


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

0 Kudos
Gilbert2797
Contributor
Contributor

I guess that would be a workaround but I'm not familar with the Knoppix Live CD.

it still bugs me that the Converter is not working like it should.

0 Kudos
continuum
Immortal
Immortal

Knoppix is just an example - any Linux liveCD will do

procedure in short:

boot machine into Knoppix with large USB-drive connected
launch gparted to find out the device-names
lets say the local system uses /dev/sda and the USB-disk appears as /dev/sdb
mount the USB-disk to lets say /mnt/usb

open root shell and run

dd if=/dev/sda of=/mnt/usb/linux-flat.vmdk

this will take some time - drink a coffee

when done go to your Windows admin machine and copy the linux-flat.vmdk to ESX

visit my site and read http://sanbarrow.com/vmdk-howtos.html#calcgeoexample
create linux.vmdk text file and upload it to ESX
create new VM with Viclient and attach linux.vmdk as existing disk

step 1 finished
continue with the patching as explained in the link be discussed before

don't worry about Converter - you are not the only one - most users complain that Linuxp2v does not work as advertised


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

0 Kudos
Gilbert2797
Contributor
Contributor

I figured it out:

FIX:

1.  ls -lh /var/log

2.  look at the LASTLOG file, it will show as 1.2T

3.  cd /var/log

4.  rm lastlog

5.  touch lastlog

http://communities.vmware.com/message/1722578

http://communities.vmware.com/message/1396631#1396631

0 Kudos