I am trying to convert a Windows 2003 Server to vSphere 4.0. I have tried using both the Cold and Hot method and each time I am only able to view the System drive to convert. I do not have an issue with a similar server, (Same model and partition configuration, OS etc)
The Server is a HP DL380G4 with 2 x 144GB HDD setup with RAID 1. Within this one Array is 2 Logical Drives.
C: is the System Partion (12GB)
D: is a data and application install partition (124GB) - This is the partition that will not convert.
When i examine the log i see a couple of errors, but have not been able to find a solution yet. Failed to get Volume's partition info:
Incorrect function and Cannot get volume's active flag info are the errors but i cannot find any cross referenced information as to what would cause this. Anyone with more information or idea's on how to fix this issue?
Thanks
vConverter 4.0.1 Error Log file
-
[2009-10-02
14:56:16.742 'App' 5740 info]
VmiQuerySourceInfoTask initialized
QueryDosDevice: ret=6779 size=16384 err=0
Disk:
.\PhysicalDrive0 has adapter type: 1
: error Read
.\PhysicalDrive1 disk layout: Incorrect
function (1) for disk #1
Found
volume with name "
?\Volume{dd86434d-464b-11da-b332-806e6f6e6963}\"
Found
volume with name "
?\Volume{7ead8bfe-84ab-4146-9553-202dc471644f}\"
Found
volume with name "
?\Volume{dd86434b-464b-11da-b332-806e6f6e6963}\"
Found
volume with name "
?\Volume{dd86434a-464b-11da-b332-806e6f6e6963}\"
volume
?\Volume{dd86434d-464b-11da-b332-806e6f6e6963}\ corresponds to \Device\HarddiskVolume1
device name.
Successfully retrieved media type for
?\Volume{dd86434d-464b-11da-b332-806e6f6e6963}\
GetDriveLetterOrMountPoint: Mount point for volume
?\Volume{dd86434d-464b-11da-b332-806e6f6e6963}\ is C:
Successfully retrieved
?\Volume{dd86434d-464b-11da-b332-806e6f6e6963}\
volume's active flag info.
The partition number is 1
finished.
Mapping a
recognized format volume
?\Volume{dd86434d-464b-11da-b332-806e6f6e6963}\ with
ID
?\Volume{dd86434d-464b-11da-b332-806e6f6e6963}\
volume
?\Volume{7ead8bfe-84ab-4146-9553-202dc471644f}\ corresponds to
\Device\HarddiskVolume3 device name.
Successfully retrieved media type for
?\Volume{7ead8bfe-84ab-4146-9553-202dc471644f}\
GetDriveLetterOrMountPoint: Mount point for volume
?\Volume{7ead8bfe-84ab-4146-9553-202dc471644f}\
is D:
error
Failed to get
.\Volume{7ead8bfe-84ab-4146-9553-202dc471644f} Volume's partition info:
Incorrect function (1)
Cannot get
?\Volume{7ead8bfe-84ab-4146-9553-202dc471644f}\
volume's active flag info.
finished.
Volume
?\Volume{7ead8bfe-84ab-4146-9553-202dc471644f}\ is assosiated with a disk
that had been filtered out; filter out the volume as well.
volume
?\Volume{dd86434b-464b-11da-b332-806e6f6e6963}\ corresponds to \Device\CdRom0
device name.
Successfully retrieved media type for
?\Volume{dd86434b-464b-11da-b332-806e6f6e6963}\
Filtered
the device with name
?\Volume{dd86434b-464b-11da-b332-806e6f6e6963}\
[2009-10-02
14:56:16.804 'App' 5740 verbose]
volume
?\Volume{dd86434a-464b-11da-b332-806e6f6e6963}\ corresponds to
\Device\Floppy0 device name.
Successfully retrieved media type for
?\Volume{dd86434a-464b-11da-b332-806e6f6e6963}\
?\Volume{dd86434a-464b-11da-b332-806e6f6e6963}\ volume has media of type 5
?\Volume{dd86434a-464b-11da-b332-806e6f6e6963}\ volume has media of type 2
Filtered
the device with name
?\Volume{dd86434a-464b-11da-b332-806e6f6e6963}\
HostDeviceInfo: Failed to
enumerate host parallel ports via the registry. Could not open device map
parallel port registry key.
Detected RAM size
is 3757539328, in megabytes: 3583 MB , rounded: 3584 MB
Microsoft Windows Version 5.2 Build 3790
Connected to ROOT\CIMV2 WMI namespace
created Net Configuration instance