VMware vSphere

 View Only
Back to discussions
Expand all | Collapse all

VMware Converter error: 'File-level volume clone error failed with sourcevolume id \WindowsBitmapDriverVolumeId Error code: 112'

  • 1.  VMware Converter error: 'File-level volume clone error failed with sourcevolume id \WindowsBitmapDriverVolumeId Error code: 112'

    Posted Oct 25, 2024 02:16 PM

    I have seen a couple of posts relating to this error with VMware converter.

    In my case, this is version 6.6

    Trying to P2V a  Windows Server 2008R2 physical server to ESXi 8.0x directly with a 62TB datastore.

    The volume ID being identified in the error is in drive D. Drive D is 2TB.

    Already tried expanding the destination volume to 10 TB and it still fails at 87%

    The error is:

    FAILED: An error occurred during the conversion: 'File-level volume clone error failed with sourcevolume id \WindowsBitmapDriverVolumeId=[9B-6C-11-0D-00-00-10-00-00-00-00-00] and target volume id ;)<611=00000010000000000. Error code:
    112'

    I have browsed nearly all threads I have found here except for this one which is restricted: https://communities.vmware.com/thread/342166

    Any chance someone with access can view it and share?

    Or maybe share a recent solution that worked to fix this problem.

    Thanks.



  • 2.  RE: VMware Converter error: 'File-level volume clone error failed with sourcevolume id \WindowsBitmapDriverVolumeId Error code: 112'

    Posted Oct 26, 2024 03:36 AM

    Hi,

    I encountered a similar issue and found success using StarWind P2V Migrator instead. It worked well for me.

    Best regards,
    Sondre H.



    ------------------------------
    Sondre H.
    ------------------------------

    Original Message


  • 3.  RE: VMware Converter error: 'File-level volume clone error failed with sourcevolume id \WindowsBitmapDriverVolumeId Error code: 112'

    Broadcom Employee
    Posted Oct 29, 2024 04:30 AM
    Hello,

    Error 112 means "There is not enough space on the disk.". I see you have mentioned the source volume is 2 TB and you tried to expand the destination size to 10 TB, but still getting the same result. I looked at the code, but it is not obvious how we ended up there as the error code returned is as a result of a Windows API call. 
    There is one more interesting part though. By default for Windows physical conversions block-level cloning should be used, as it is faster and more robust. File-level cloning is triggered in general when the volume is resized - then the new volume is formatted and the data is copied file by file. There is also one detail here - if the source volume is formatted with NTFS and the size on the destination is increased - then still block-level clone is triggered, and after the data is transferred on block level - the FS on the destination is expanded "in-place" to accomodate the newly requested size (as NTFS allows this operation).
    In your case however it is clear that file-level cloning is triggered and it is not obvious why. Is it possible to share the log bundle for further investigation? You can send them privately if you prefer.

    Original Message