Hello:
I am converting physical machines to VM sot hat we can consolidate our environment. The converter V5.1.0 Build1087880 fails at 71%, with a Warning:
so far, I have good progress on other physical machines except for this stubborn XP -X64 machine. We need to keep it for legacy reasons until there are replacement apps for all sw running on it (; This machine has SSD drive and no spinning HD
each time the conversion is able to start and complete the first on two drives. The GUI states its fine , but the log shows
2013-08-11T09:00:00.782-04:00 [02748 warning 'Default'] Disk number 1 has been skipped because of errors while reading partition table
2013-08-11T09:00:00.782-04:00 [02748 warning 'Default'] Disk number 1 has been skipped because of errors while reading dynamic disks header or LDM database is corrupted
When it gets to the second drive, I stops as it cant read some sector block.
2013-08-11T09:00:00.782-04:00 [02748 warning 'Default'] Disk number 2 has been skipped because of errors while reading partition table
2013-08-11T09:00:00.782-04:00 [02748 warning 'Default'] Disk number 2 has been skipped because of errors while reading dynamic disks header or LDM database is corrupted
2013-08-11T10:16:13.706-04:00 [04324 error 'task-2'] BlockLevelVolumeCloneMgr::ReadAndSkipBadBlocks():
Error (type: 2, code: 27) reading 223232 bytes starting at 0x000000069377f000 from the source volume D:
2013-08-11T10:16:53.800-04:00 [04324 error 'task-2'] BlockLevelVolumeCloneMgr::ReadAndSkipBadBlocks():
Error (type 2, code: 27), detected bad sector at offset 0x0000000693796000 on the source volume D:
I have run several apps to check and fix the D drive, but none find any issues. the XP-X64 machine has been restated after each test and re run. no issues are found on either drive
I have tried to run the converter without the D drive. It wont let me do so as it states that the D drive Is critical to the conversion and wont proceed without it
I have attached GUI screen shots and two logs files
Can anyone please help?
Is there is a way to find the root problem or proceed?
if windows cant find an issue with the D Drive why does the converter?
