BootCamp disk giving "partition changed" error after reboot - El Capitan, Fusion 8.0.1 - any fixes?

[haralds]

I have two BootCamp drives that are Mac GUID partition but boot using BIOS mode with MBR emulation. The full disk is used for Windows 7 and Windows 10.

They work fine the first time they are configured under VMware. But when I reboot OSX, often one oft the drives (Windows 7) ends up with a different /dev switching between /dev/disk3 and /dev/disk4. This trips up VMware, which thinks the partitions have been reconfigured.

I remember this being a problem with Fusion years ago. Is there a way to fix it instead of reconfiguring or having multiple Guest configurations? How about identifying the partition by label or UUID?

This does not seem to be an issue with Yosemite and Fusion 7.

-- Harald

[nancyz]

Hi heralds,

Welcome to Fusion forum.

The full disk is used for Windows 7 and Windows 10.

What do you mean by that? You installed two OSes or you upgrade windows7 to windows 10?

[tliugogo]

Hi,

Can you provide your disk partition's detail if you get chance? Maybe I can have a try on my side.

1. diskutil list

2. Which Mac type do you use?

-- Tim

[Mikero]

An easier option is just to run the support script from Help > Collect Support Information and post that... it has logs as well as the partition map and mac system profile.

[haralds]

Sorry about the delay in answering. Here is more detail:

I have upgraded to Fusion 8.0.2. It is running on 10.11.1. Prior to the upgrade I was running Fusion 7 under 10.10.

I have two BootCamp drives with Windows 7 and Windows 10. These were set up by BootCamp assistant. They are GUID drives with a single NTFS partition each, but run under MBR emulation - Windows does not use EFI boot.

Prior to the upgrade, I never had an issue. After the upgrade, the disk /dev/ designation seems to jump around and give problems with the configured VMware drivers. One boot it might be /dev/disk2 (Windows 7) and /dev/disk3 (Windows 10), another /dev/disk4 and /dev/disk2 etc.

I have created multiple configurations for each of the possibilities that I see by editing the VMDK files in the bundles in the virtual machines in ~/Library/Application Support/VMware/Virtual Machines/Boot Camp. After a reboot, I run a 'mount' under terminal and then copy the appropriate files. It works, but is a real PITA.

Would it not be possible to find the correct drives by their UUID to avoid this issue? And why has this changed since the last system and product update?

Thanks.

[haralds]

The full designations for the partition is on slice 2 - s2. For example /dev/disk3s2 and /dev/disk1/s2

The system report is 50MB, so I am not uploading here unless requested.

[haralds]

Here are the details. As I pointed out, the /dev/diskns2 assignments keep changing and that is the root of the problem. Right now, Windows 7 is on /dev/disk0s2 and Windows 10 on /dev/disk3s2...

/dev/disk0 (external, physical):

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      GUID_partition_scheme                        *512.1 GB   disk0

   1:                        EFI EFI                     209.7 MB   disk0s1

   2:       Microsoft Basic Data Windows 7               511.9 GB   disk0s2

/dev/disk1 (external, physical):

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      GUID_partition_scheme                        *512.1 GB   disk1

   1:                        EFI EFI                     209.7 MB   disk1s1

   2:                  Apple_HFS Virtual Machines        511.8 GB   disk1s2

/dev/disk2 (external, physical):

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      GUID_partition_scheme                        *1.0 TB     disk2

   1:                        EFI EFI                     209.7 MB   disk2s1

   2:          Apple_CoreStorage Yosemite                999.2 GB   disk2s2

   3:                 Apple_Boot Recovery HD             784.2 MB   disk2s3

/dev/disk3 (external, physical):

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      GUID_partition_scheme                        *960.2 GB   disk3

   1:                        EFI EFI                     209.7 MB   disk3s1

   2:       Microsoft Basic Data Windows 10              960.0 GB   disk3s2

/dev/disk4 (internal, physical):

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      GUID_partition_scheme                        *4.0 TB     disk4

   1:                        EFI EFI                     209.7 MB   disk4s1

   2:                  Apple_HFS Media                   4.0 TB     disk4s2

/dev/disk5 (internal, physical):

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      GUID_partition_scheme                        *4.0 TB     disk5

   1:                        EFI EFI                     209.7 MB   disk5s1

   2:                  Apple_HFS Media iTunes            4.0 TB     disk5s2

/dev/disk6 (internal, physical):

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      GUID_partition_scheme                        *4.0 TB     disk6

   1:                        EFI EFI                     209.7 MB   disk6s1

   2:                  Apple_HFS Storage                 3.9 TB     disk6s2

   3:                  Apple_HFS Lion                    127.7 GB   disk6s3

/dev/disk7 (internal, physical):

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      GUID_partition_scheme                        *4.0 TB     disk7

   1:                        EFI EFI                     209.7 MB   disk7s1

   2:          Apple_CoreStorage Neptune                 4.0 TB     disk7s2

   3:                 Apple_Boot Recovery HD             650.0 MB   disk7s3

/dev/disk8 (external, virtual):

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:                  Apple_HFS Neptune                +998.8 GB   disk8

                                 Logical Volume on disk2s2

                                 FC0F2EAB-8D93-4A0D-834A-DBF21423F0CB

                                 Unlocked Encrypted

/dev/disk9 (external, physical):

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      GUID_partition_scheme                        *5.0 TB     disk9

   1:                        EFI EFI                     314.6 MB   disk9s1

   2:          Apple_CoreStorage Neptune_CCC             5.0 TB     disk9s2

   3:                 Apple_Boot Recovery HD             784.2 MB   disk9s3

/dev/disk10 (internal, virtual):

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:                  Apple_HFS Yosemite               +4.0 TB     disk10

                                 Logical Volume on disk7s2

                                 907B05A4-1362-4D17-BEB2-FC6D28354A88

                                 Unlocked Encrypted

/dev/disk11 (external, virtual):

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:                  Apple_HFS Neptune_CCC            +5.0 TB     disk11

                                 Logical Volume on disk9s2

                                 65DCCD16-8ADA-41B8-A193-B9AC221E9DA5

                                 Unlocked Encrypted

[Mikero]

Does the issue persist with Fusion 8.0.2? We had some bootcamp-specific fixes in there.

[admin]

If the problem still persists please try to recreate the BootCamp Virtual Machine. Refer : VMware KB: Launching your Boot Camp partition in VMware Fusion

This should help !!