FAILED: Unable to create a VSS snapshot of the source volume(s). Error code: 2147754766 (0x8004230E).

[azlans27]

Hi All,

I got error when trying converting physical server to VM. Here is the summary of my site:

Physical server OS               : Windows Server 2008 R2 SP1

vCenter converter version     : 6.2.0 build-7348398

vCenter Dest version             : Windows vCenter 6.5

Just few minutes after submitting jobs, I got this error:

FAILED: Unable to create a VSS snapshot of the source volume(s). Error code: 2147754766 (0x8004230E).

After searching, I know this error is related to Volume Shadow Copy Service that can not convert FAT32.

Yes, There is FAT32 system in physical server as below:

VMware KB ( VMware Knowledge Base​  ) says to uncheck FAT volume or convert to NTFS.

option 1:

When try to uncheck this FAT32 volume, the conversion progress will fail at 96 or 98 %, with error Warning: Unable to update BCD on the destination machine's system volume.

We know this FAT32 volume is system volume, we try to overcome this issue but still no luck till now, after some days troubleshooting.

Question: Does anyone know to overcome this issue?

Option 2:

Convert FAT32 volume to NTFS. Honestly we still do not try this option yet since the physical server is in prod and still running. We worry if this action can cause error to current server.

Question: does anyone know the safe way to convert FAT32 to NTFS?

Overall, anybody knows to solve issue in my site? Here I also attach the logs to analyze.

Best Regards,

Azlan  Syah

[Rosen Tomov]

Error VSS_E_VOLUME_NOT_SUPPORTED_BY_PROVIDER ((HRESULT)0x8004230EL) is "The given shadow copy provider does not support shadow copying the specified volume."

Check your VSS providers with "vssadmin list providers" command and eventually suppress other that Microsoft's providers.

O1: Looks strange that there is no active (bootable) volume, which is important for Converter, try to make the FAT32 volume as active and then convert. (be careful not to brick your machine)

O2: Not an option for you. There is "convert" command, but it's bad idea to convert boot volume - the system probably will become unbootable.

HTH

P.S.

Upgrade your Converter to the latest one 6.2.0.1

It's preferred to convert "This local machine" instead of "Remote machine", moreover you installed full Converter on machine.

[azlans27]

Hi POCEH,

Option1

Do you mean to activate FAT32 volume on prod server? what do you mean with active?

Option2

After searching out there, I find 2 article about how to solve this issue;

1. Server 2008 R2 P2V issues - FAT32

From the  link, i read we have to convert FAT32 volume to NTFS on physial server first before converting.

Question again; I'm not so confidence to do this way, since the physical server is prod server. Is it safe to do, without making server crash or data loss?

2. Convert FAT to NTFS without Data Loss in an Easy Way - EaseUS

Here is the screen shoot of the physical server disk management:

Is it safe to do, guys?

Best Regard,

Azlan Syah

[Rosen Tomov]

As a very first option - try to convert with 6.2.0.1

As a second option - mark your FAT32 volume as active (i.e. bootable) could be done with diskmgmt tool just right click on partition.

As last option - you can convert FAT32 to NTFS but this is not safe and could brick your machine!

HTH

[azlans27]

Hi POCEH,

Finally, we have solved our issue.

We go with option 1,, After conversion failed at 98 %, here is what we do:

1. Extend VMDK size around 1 GB, to create efi partition.

2. Attach windows installation to VM, then boot VM from CD Room.

3. Go repair option, choose Command prompt.

4. Following guide below;

for more detail, please check on this link: http://triplescomputers.com/blog/casestudies/repair-a-corrupted-efiuefi-boot-sector-and-bcd/

5. Then, if that is unsuccessful, please follow instruction on this link: Repair Corrupt BCD UEFI Windows Server | ecognosci

6. The last one we can do is following these guides:

for more detail, please check on this link: Windows Server 2008 Repair Steps for No Boot Issues - TechNet Articles - United States (English) - TechNet Wiki

Those all, I hope all links and info here will be useful for other people that have the same case with me.

Best Regard,

Azlan Syah

[bear410hk1]

Thanks  .

I fixed the Win10 p2v by following your step.

Thanks a lot