VMware Cloud Community
autigers1970
Contributor
Contributor

A general system error has occurred: unknown internal error.

I am having some problems with my Windows 10 VM.  I'm trying to expand the size of the VM but can't because of a weird partition from the Boot Camp conversion I had on my Mac.  For more details on that, you can see this post in the Fusion forum:

Virtual disk size incorrect

They suggested using VMWare VCenter Converter Standalone and deselect that partition when doing so.  Everything seems to work fine until the end when I get this error:

A general system error has occurred: unknown internal error.

I've attached a screenshot showing the partitions I can choose to convert as well as some diagnostic logs.  Can anyone help me figure out how to get this working?

0 Kudos
5 Replies
patanassov
VMware Employee
VMware Employee

Hello,

the screenshot shows 2 unrecognized partitions of which one remains selected. Have you tried to deselect both?

0 Kudos
autigers1970
Contributor
Contributor

Yes, I have unchecked them both.  I get the same error either way.

0 Kudos
patanassov
VMware Employee
VMware Employee

Looking at the logs I think the relevant part is this:

2016-08-10T05:33:58.496-05:00 warning vmware-converter-worker[04964] [Originator@6876 sub=Default] Disk number 1 has been skipped because of errors while reading partition table

2016-08-10T05:33:58.496-05:00 warning vmware-converter-worker[04964] [Originator@6876 sub=Default] Disk number 1 has been skipped because of errors while reading dynamic disks header or LDM database is corrupted

2016-08-10T05:33:58.496-05:00 warning vmware-converter-worker[04964] [Originator@6876 sub=Default] [MoveActiveDiskIfNeeded] GetFirstBootDisk failed, mntapi error: 176

2016-08-10T05:33:58.496-05:00 warning vmware-converter-worker[04964] [Originator@6876 sub=Default] Partition:Invalid sector magic number.

2016-08-10T05:33:58.496-05:00 warning vmware-converter-worker[04964] [Originator@6876 sub=Default] Partition:Invalid sector magic number.

2016-08-10T05:33:58.496-05:00 warning vmware-converter-worker[04964] [Originator@6876 sub=Default] [PopulateCapabilities] Volume-based cloning was disabled due to: <no volumes are recognized>

2016-08-10T05:33:58.496-05:00 info vmware-converter-worker[04964] [Originator@6876 sub=Default] [LogMessagesForQA] System volume is not detected.

2016-08-10T05:33:58.496-05:00 info vmware-converter-worker[04964] [Originator@6876 sub=Default] [BaseComputerImpl::Open] Config file: E:\Bryan-PC\Bryan-PC.vmx

2016-08-10T05:33:58.496-05:00 warning vmware-converter-worker[04964] [Originator@6876 sub=Default] Partition:Invalid sector magic number.

2016-08-10T05:33:58.590-05:00 info vmware-converter-worker[04964] [Originator@6876 sub=Default] Cannot mix MBR and GPT partitions, partition 0 is GPT!

2016-08-10T05:33:58.590-05:00 info vmware-converter-worker[04964] [Originator@6876 sub=Default] Failed to create the partition Tables error:-1

2016-08-10T05:33:58.590-05:00 error vmware-converter-worker[04964] [Originator@6876 sub=Default] [BaseDiskSetComputer::PartitionDisk] Failed to partition disk disk-5, mntapi error: 400

2016-08-10T05:33:58.590-05:00 error vmware-converter-worker[04964] [Originator@6876 sub=Default] [BaseDiskSetComputer::AnalyzeErrorAndThrow] Error occurred when opening disk set, MNTAPI_ERROR = 400 MNTAPI errorType = 0, errorCode = 25

2016-08-10T05:33:58.637-05:00 error vmware-converter-worker[04964] [Originator@6876 sub=Default] TargetVmManagerImpl::CreateVM: Failed to retrieve the storage mapping with error Partitioning disk error.

I've bolded those that seem most interesting.

According to the other thread you mention:

When a user wants to grow his virtual disk he bumps problems due to strange partition layout.

Windows doesn't let him use the OS X partition part because bootcamp positions the Windows partition at the end of the disk.

Looks like Converter too "bumps problems due to strange partition layout".

As a (potential) workaround, I'd suggest you inspect your C: drive and move any additional data files (i.e. not part of the system neither installed apps) to the other volume. Temporary disabling the paging file may also help you get the coveted 3GB needed by Windows upgrader (I don't think Windows will eat all the 20GB, it is needed for temp files, so you can restore the paging file after the upgrade).

Regards,

Plamen

0 Kudos
autigers1970
Contributor
Contributor

I was able to delete enough files and use disk cleanup to get Windows 10 update to install.  Also had to do it via USB stick rather than in place but it worked.  But there's still this lingering issue with not being able to resize the disk and having that humongous 418GB volume sitting there.  My entire physical hard drive for this Mac is only 500GB and the native MacOS, files and applications take up 160GB, so I know that 418GB thing not possible.

I tried another method and it got further.  I copied the entire VM to an external hard drive and instead of converting the VM I was running, I attempted to convert a copy of it that was powered off.  It gets to 98% then fails with a message about a missing volume or something.  I'll have to try it again tonight if you need exact wording on the error.  Any thoughts on getting past that?

0 Kudos
autigers1970
Contributor
Contributor

Any other ideas on how to convert this VM so that I can resize it properly in the future?

0 Kudos