error 209 (type 1 code 13)

[mdterp]

My server gets to about 94% and fails with error 209 (type 1 code 13) .  Much of my research says that it is a bad block on my disk array.  I ran chkdsk and it didn't come back with any problems.

The server is a 500 GB C: running Windows 2003 server.  I am trying to P2V to a C:\p2v folder on the same server.  Will that even work?

[Rosen Tomov]

Nope, this is not possible, use USB stick or SMB/network drive.

[mdterp]

I am going to try Disk2VHD.  Reading really quickly it sounds as if that one will work.  Then I can v2v to Vmware.

[JagadeeshDev]

Did you run the disk defrag and chkdsk /r/f /x /b

[mdterp]

I did run chkdsk but it didn't discover any errors.  I think my problem is either that I am running out of disk space or the fact that I am trying to do the P2V to the same local C: drive as the server.

[Ivan Ivanov]

When performing P2V conversions Converter creates a VSS snapshot on the source server. By default the amount of space used for VSS snapshots is set to a small percent of the disk free space. When you perform conversion to the same snapshotted drive you actually want to write another copy of all your data to the same drive. This will cause the VSS snapshot to expand to a value that is equal to the data you have on your disk and this most likely is above the VSS limit set by the system, which can cause errors in read/write operations later.

[mdterp]

So it is possible to P2V a live and running server to a local drive(provided there is enough space)?  For example ServerX.domain.local with a C: of 500GB can be P2Ved into a c:\myServerX\

If so is it about a 1:1 ratio?

[mdterp]

I was successful in P2V using disk2vhd.  It took a long time, but it worked with no errors.  I think my problem with the vmware converter was the disk space issue.  I was able to clean up some space.  I will try again with the vmware converter