VMware Cloud Community
ybalin
Contributor
Contributor

Error 23

\[2007-03-16 14:17:28.970 'App' 1428 verbose] \[imageProcessingTaskStep,307] VmiImportTask::task\{36} step "Clone VM" 12% completed

\[2007-03-16 14:17:28.970 'App' 1428 verbose] \[imageProcessingTaskWrapper,749] Got an update from BlockLevelVolumeCloning::task\{38}

\[#10] \[2007-03-16 14:17:28.970 'App' 2228 verbose] \[imageProcessingTaskWrapper,437] Waiting for updates from CloneTask::task\{37}

\[#10] \[2007-03-16 14:17:28.970 'App' 2244 verbose] \[imageProcessingTaskWrapper,437] Waiting for updates from BlockLevelVolumeCloning::task\{38}

\[#10] \[2007-03-16 14:17:28.970 'App' 2228 verbose] \[imageProcessingTaskWrapper,668] (Re)Start waiting for property updates from CloneTask::task\{37}

\[#10] \[2007-03-16 14:17:28.970 'App' 2244 verbose] \[imageProcessingTaskWrapper,668] (Re)Start waiting for property updates from BlockLevelVolumeCloning::task\{38}

\[2007-03-16 14:17:28.970 'App' 1428 verbose] \[imageProcessingTaskWrapper,749] Got an update from CloneTask::task\{37}

\[#10] \[2007-03-16 14:17:28.970 'App' 2228 verbose] \[imageProcessingTaskWrapper,437] Waiting for updates from CloneTask::task\{37}

\[#10] \[2007-03-16 14:17:28.970 'App' 2228 verbose] \[imageProcessingTaskWrapper,668] (Re)Start waiting for property updates from CloneTask::task\{37}

\[#10] \[2007-03-16 14:18:06.938 'App' 2224 error] \[blockLevelVolumeCloningTaskImpl,353] Error 23 reading 65536 bytes starting from 374832640 from the source volume

\[#10] \[2007-03-16 14:18:07.282 'App' 2224 error] \[imageProcessingTaskImpl,536] BlockLevelVolumeCloning::task\{38}: Image processing task has

Hi guys;

I get the error above while I am trying Vmware converter on Windows 2000 server (regular not advanced). I am importing the machine to itself (its own harddisk). I also tried to another harddisks but still give the same error. Starts with 1% , 3%, 7% and 97% and it fails...

Anybody seen error 23 before?

Thanks.

Reply
0 Kudos
3 Replies
esiebert7625
Immortal
Immortal

Sounds like a disk error, try running Chkdsk /f on your drive to check for any disk errors. If you still have problems you might try re-sizing the drive when you are setting up the convert. Doing this will trigger a file by file copy of the source server instead of a block by block copy. You will also not being copying the entire disk regardless of any un-used space on it. Even if you re-size it slightly smaller, say 1MB smaller, it will trigger the alternate copy method, create a new vmdk file but only copy the actual data on the source hard drive.

Reply
0 Kudos
ybalin
Contributor
Contributor

Thanks for the reply buddy...

I will take a look at it.

Reply
0 Kudos
ybalin
Contributor
Contributor

It did work. I copyied the minimum amount possible. Thanks for the information.

Yigit

Reply
0 Kudos