Quantcast
Channel: VMware Communities: Message List - Converter Standalone
Viewing all articles
Browse latest Browse all 8478

Re: Unable to convert Linux Physical Server

$
0
0

Hm, in the log there is the following line:

2014-12-22T18:01:18.434+01:00 [09488 info 'Default'] [Converter Agent SysinfoQuery] successfully exec'ed vmware-sysinfo; result: Error: Can't have a partition outside the disk!

This error seem to be reported by 'libparted'. Converter is using 'libparted' for getting information about the source disk configuration. In the specific case seems for some reason it does not like /dev/sda and does not report partition details for it (most likely because of this error):

-->   <disk type="msdos" controllerType="scsi" bus="0" deviceId="2" capacityInSectors="143110145">
-->    <device path="/dev/sda" major="8" minor="0"/>
-->    <hwGeometry cylinders="8908" heads="255" sectors="63"/>
-->    <biosGeometry cylinders="8908" heads="255" sectors="63"/>
-->   </disk>

There should be partitions list under the <disk> element, but as you can see - the list here is empty, that is 'parted' did not return any partitions for this disk. Looking at the disk geometry it says the disk has 8908 cylinders, but according to the output of fdisk -l you posted, the last partition ends on sector 8911, which is beyond the end of the disk, thus the error generated.

 

As a result the partition list for this disk returned by 'parted' is empty and Converter skipped the boot volume, because it could not find appropriate partition for it in the available partition list, which later lead to the error you observed.

 

As I google'd for the "Can't have a partition outside the disk!" error I came upon this page - GParted -- How-to Fix Invalid MSDOS Partition Tables. There is a step-by-step guide in it how to fix this problem, but the process described there looks too dangerous to me and especially if it is a production server I would take a full backup of it before trying to make any changes (especially when there is an LVM involved and this could lead to a corrupted / volume because of inconsistent LVM volume information).


Viewing all articles
Browse latest Browse all 8478

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>