Known Issue - Failed to attach virtual disk 0x06

Symptoms: 

Error message "Failed to attach virtual disk, error = 0x0x6" on Windows 2008R2 and Windows 2012 OS

Explanation: 

The image path to unsupported destination was specified.

Diagnostics: 

A) Figure out if it's a local network share.

 

  1.     Start cmd.exe with Administrator privileges, run the following command
  2.     net use
  3.     See the list of network attached shares returned by the command
  4.     See if drive specified in a image path corresponds to any of shares
  5.     Check if this share path points to local drive

B) Figure out what filesystem the path resides on, right click on drive you specified in Windows Explorer and see its properties.

C) Check whether the folder specified is compressed:
Start cmd.exe with Administrator privileges, run the following command

    compact <image folder path>
Possible causes: 

Cloudscraper doesn't support creation of VHD images on paths:

  1.     Local FAT32 filesystem
  2.     Compressed NTFS folders
  3.     Network shares residing on the same computer, e.g. \\localhost\ or \\127.0.0.1\ , or network drives mapped to such a share
Solution: 

1. Switch to RAW image format

Applies in any diagnostics result.

  1.     Locate .ini configuration file you specified in "Save Transfer Configuration" Window.
  2.     Open it via Notepad
  3.     Replace row
  image-type = VHD

        with

  image-type = RAW

    4. Restart Cloudscraper and pick Resume Existing Transfer option. Specify .ini file you just edited, enter your keys, press "Next", then "Start"

 

2. Use direct path for VHD image folder

Applies in case share based on the same computer is diagnosed.

  1.     Specify full path to local drive ommiting network path or mapped disk drives.

3, Use another path to store the images.

It should be located on the supported location: NTFS or network share on another computer.

4. Decompress the folder

Applies in case of compressed NTFS.

    compact /U /S <image folder path>
Notes: 

1) There are several important limitations for VHDs:

  1. VHDs can be mounted only on NTFS volumes (although you can still save a VHD file on FAT/FAT32 assuming the maximum file size limit is not violated). For example, if you have a differencing VHD chain, then every VHD along the chain must sit on an NTFS volume to make VHD attaching work.
  2. VHDs cannot be mounted within a compressed folder in Windows Server 2008 R2. This was possible in Hyper-V role in Windows Server 2008, but this capability was explicitly blocked in the Hyper-V role in Windows Server 2008 R2 since the compressed file size limit is relatively small. A dynamically expandable VHD can easily outgrow that limit and get corrupted.
  3. In addition to the maximum file size of NTFS, dynamic or difference VHDs cannot exceed 2040GB. The reason for the 2040G limit is the length of each Block Allocation Table entry is set to 4 Bytes and the maximum valid value is 0xFFFFFFFE (0xFFFFFFFF means an unused entry). If you multiply that value by 512B sector size and then subtract the overhead of on disk meta-data structures, 2040G will be the maximum size of dynamically or differencing VHDs.

See Microsoft Technet article: http://blogs.technet.com/b/ranjanajain/archive/2010/03/23/virtual-hard-d...