VMware Communities
CWasko
Contributor
Contributor

Boot Camp not recognized

I've got a Mac Mini with three partitions. Two Mac partitions and one windows partition. Fusion does not recognize that there is a windows partition. Apple's Startup Disk control panel sees it just fine, and I can boot to it no problems. Also, Parallels sees the windows partition and can utilize it as well.

What do I need to do to get Fusion to recognize it?

Reply
0 Kudos
37 Replies
bgertzfield
Commander
Commander

Hi CWasko,

Can you open a Terminal (from the /Applications/Utilities folder) and run:

sudo fdisk /dev/rdisk0

then type your password, and copy-and-paste the output here?

Thanks!

Reply
0 Kudos
aliasme
Enthusiast
Enthusiast

Edit: sorry, my config is separate disks not partitions, but hopefully this will help.

I have 4 physical disks in my machine. Boot camp is installed on one of them. It boots fine. Parallels can also boot from it.

server01:~ me$ sudo fdisk /dev/rdisk0

Disk: /dev/rdisk0 geometry: 9039/255/63 \[145226112 sectors]

Signature: 0xAA55

Starting Ending

#: id cyl hd sec - cyl hd sec \[ start - size]

\----


1: EE 0 0 2 - 25 127 14 \[ 1 - 409639] on /.vol

/dev/disk2s2 on /Volumes/Biggie (local, journaled)

/dev/disk3s2 on /Volumes/Shared (local)

automount -nsl \[217] on /Network (automounted)

automount -fstab \[243] on /automount/Servers (automounted)

automount -static \[243] on /automount/static (automounted)

/dev/disk0s2 on /Volumes/Parallels (local, read-only)

Parallels is the name of the BootCamp disk. I hope soon to rename VMWare.

Notes: The disk0s2 is sometimes changed by OS X when booting. Every 3-4th time I boot I have to edit the Parallels config file to address the new location at disk1s2 or something similar. Parallels unmounts this disk when launching from the partition.

Reply
0 Kudos
bgertzfield
Commander
Commander

Hi jamesca,

Just curious, but how do you have four physical disks in a Mac mini? Is this an external USB or FireWire drive? (I was under the impression that Boot Camp didn't allow users to install on an external drive.)

Reply
0 Kudos
aliasme
Enthusiast
Enthusiast

Gosh, my apologies I didn't catch that in his original post either.

This is a Mac Pro. Boot Camp is installed on one of the SATA disks.

Sorry for the confusion.

Reply
0 Kudos
bgertzfield
Commander
Commander

OK. Looks like you have Boot Camp on your first disk, and Mac OS on your second disk. I don't think we tested this scenario, but I'll file a bug internally to see if we can reproduce it.

Reply
0 Kudos
aliasme
Enthusiast
Enthusiast

Oh, very interesting. Mac OS X can address the disks correctly if moved around in the bays 1-4. From what you just said, it sounds like Fusion might recognize the disks if I switch their physical order to Mac first, Boot Camp second. While this might be something you should address anyway, I'll move them around in my machine today to see if I can at least get this working.

Thanks for the insight.

Update: Switching the physical disk order in the bays doesn't work. The disk IDs in OS X don't change. The system and Boot Camp still work fine.

Reply
0 Kudos
bgertzfield
Commander
Commander

Hi jamesca,

I've read through the code that detects if a Boot Camp partition is present. It looks like we currently only detect Boot Camp partitions on a disk that also has a Mac (HFS+) partition before the Boot Camp partition.

We'll reproduce and fix this internally. Thanks for the report!

Reply
0 Kudos
KarlKFI
Contributor
Contributor

I am also on a Mac Pro and have Boot Camp installed on my primary drive and two Windows formatted drives (NTSF, formatted by the Vista installer) in the 2nd and 3rd HD slots. My third drive has Windows Vista Enterprise installed and Boot Camp works fine. I have the drives read/write accessible on the Mac side using MacFuse and a ntfs-3g login script ( http://shadowofged.blogspot.com/2007/03/ntfs-3g-for-mac-os-x.html ) but I dont' think that should affect their being detected.

As with the previous posters VMWare Fusion doesn't detect the Windows drive. So I figured you might be able to use my drive fdisks as follows. As you can see, fdisk doesn't recognize that my Vista disk has anything other than the first partition, which I assume is the Boot Camp partition, since it's on the rdisk0 as well, my Mac OS 10.4.9 boot disk. I'm a little confused as to why it thinks rdisk1 is HPFS tho.

Quad-Turbo:/ me$ sudo fdisk /dev/rdisk0

Disk: /dev/rdisk0 geometry: 19457/255/63 \[312581808 sectors]

Signature: 0xAA55

Starting Ending

#: id cyl hd sec - cyl hd sec \[ start - size]

\----


1: EE 1023 254 63 - 1023 254 63 \[ 1 - 409639]

2: 07 1023 254 63 - 1023 254 63 \[ 409640 - 312172128] HPFS/QNX/AUX

3: 00 0 0 0 - 0 0 0 \[ 0 - 0] unused

4: 00 0 0 0 - 0 0 0 \[ 0 - 0] unused

Quad-Turbo:/ me$ sudo fdisk /dev/rdisk1

Disk: /dev/rdisk1 geometry: 24321/255/63 \[390721968 sectors]

Signature: 0xAA55

Starting Ending

#: id cyl hd sec - cyl hd sec \[ start - size]

\----


*1: 07 0 32 33 - 1023 254 63 \[ 2048 - 390717440] HPFS/QNX/AUX

2: 00 0 0 0 - 0 0 0 \[ 0 - 0] unused

3: 00 0 0 0 - 0 0 0 \[ 0 - 0] unused

4: 00 0 0 0 - 0 0 0 \[ 0 - 0] unused

Quad-Turbo:/ me$ sudo fdisk /dev/rdisk2

Disk: /dev/rdisk2 geometry: 30401/255/63 \[488397168 sectors]

Signature: 0xAA55

Starting Ending

#: id cyl hd sec - cyl hd sec \[ start - size]

\----


1: EE 1023 254 63 - 1023 254 63 \[ 1 - 488397160]

2: 00 0 0 0 - 0 0 0 \[ 0 - 0] unused

3: 00 0 0 0 - 0 0 0 \[ 0 - 0] unused

4: 00 0 0 0 - 0 0 0 \[ 0 - 0] unused

Hope that helps.

Message was edited by:

KarlKFI

Reply
0 Kudos
trodemaster
Hot Shot
Hot Shot

Excellent! I also have a mac pro with a dedicated windows disk.

Currently fusion does not see it at all.

Blake-

Reply
0 Kudos
bgertzfield
Commander
Commander

Thanks for your reports, folks!

We'll definitely make the Boot Camp partition detection algorithm a little more flexible for the next release.

Right now, it's very conservative (only detects if there's a Mac and a Boot Camp partition on the same drive), since that's the only configuration we encountered in testing.

Reply
0 Kudos
aliasme
Enthusiast
Enthusiast

I know you can't comment on upcoming release dates, but lets say I need to use the Boot Camp disk on a daily basis every day this month. Would it be a waste of my time to reinstall a Boot Camp partition under my Mac partition considering I need this daily from now until your next release date? Hopefully this is both vague enough and clear enough for you to answer. Smiley Happy

Reply
0 Kudos
latke
Contributor
Contributor

I also have this problem with bootcamp not being recognized, I have a single hard disk in a macbook (core2) with 4 partitions (the 4th being windows XP, NTFS formatted).

Running fusion beta 3, build 43733

\# fdisk /dev/rdisk0

Disk: /dev/rdisk0 geometry: 14593/255/63 \[234441648 sectors]

Signature: 0xAA55

Starting Ending

#: id cyl hd sec - cyl hd sec \[ start - size]

\----


1: EE 0 0 2 - 25 127 14 \[ 1 - 409639]

2: AF 25 127 15 - 1023 159 14 \[ 409640 - 132120576] HFS+

3: AF 1023 240 16 - 1023 116 48 \[ 132792360 - 41680896] HFS+

*4: 07 1023 197 50 - 1023 80 23 \[ 174735400 - 59706208] HPFS/QNX/AUX

The fourth partition is actually Partition Type : Microsoft Basic Data

Partition table is hybrid GPT/MBR

Reply
0 Kudos
roundguy
Contributor
Contributor

Boot Camp is also not recognized on my system.

Disk: /dev/rdisk0 geometry: 12161/255/63 \[195371568 sectors]

Signature: 0xAA55

Starting Ending

#: id cyl hd sec - cyl hd sec \[ start - size]

\----


1: AF 0 1 1 - 1023 254 63 \[ 63 - 41929587] HFS+

2: AF 1023 254 63 - 1023 254 63 \[ 41943132 - 111485488] HFS+

*3: 07 1023 254 63 - 1023 254 63 \[ 153428625 - 41942943] HPFS/QNX/AUX

4: 00 0 0 0 - 0 0 0 \[ 0 - 0] unused

Reply
0 Kudos
bgertzfield
Commander
Commander

I know you can't comment on upcoming release dates,

but lets say I need to use the Boot Camp disk on a

daily basis every day this month. Would it be a

waste of my time to reinstall a Boot Camp partition

under my Mac partition considering I need this daily

from now until your next release date?

That would not be a waste of your time.

Reply
0 Kudos
Panache
Contributor
Contributor

I also have this problem on a Mac Pro. I have two disks, one for Mac OSX, one for Windows. Strangely, regardless of the order the disks are inserted in Bay 1 and Bay 2, the disk with the Windows volume always shows as disk0 and the disk with the Mac OS X volumes always shows as disk1. Either way, Fusion doesn't recognize the Windows volume.

diskutil list

/dev/disk0

#: type name size identifier

0: GUID_partition_scheme *232.9 GB disk0

1: EFI 200.0 MB disk0s1

2: Microsoft Basic Data win32 232.7 GB disk0s2

/dev/disk1

#: type name size identifier

0: GUID_partition_scheme *465.8 GB disk1

1: EFI 200.0 MB disk1s1

2: Apple_HFS osx 232.8 GB disk1s2

Reply
0 Kudos
mail64565465
Contributor
Contributor

no bootcamp detection here either.... fully loaded mac pro.

diskutil list

/dev/disk0

#: type name size identifier

0: GUID_partition_scheme *298.1 GB disk0

1: EFI 200.0 MB disk0s1

2: Apple_HFS Scratch_200 197.0 GB disk0s2

3: Microsoft Basic Data BootCamp 100.8 GB disk0s3

/dev/disk1

#: type name size identifier

0: GUID_partition_scheme *465.8 GB disk1

1: EFI 200.0 MB disk1s1

2: Apple_HFS OSX 150.6 GB disk1s2

3: Apple_HFS MP3 200.6 GB disk1s3

4: Apple_HFS Scratch_115 114.0 GB disk1s4

/dev/disk2

#: type name size identifier

0: GUID_partition_scheme *298.1 GB disk2

1: EFI 200.0 MB disk2s1

2: Apple_HFS AppleTV 50.0 GB disk2s2

3: Apple_HFS Video 247.6 GB disk2s3

/dev/disk3

#: type name size identifier

0: GUID_partition_scheme *372.6 GB disk3

1: EFI 200.0 MB disk3s1

2: Apple_HFS OSX_Backup 150.0 GB disk3s2

3: Apple_HFS Downloads 200.0 GB disk3s3

4: Apple_HFS OSX_Setup 22.0 GB disk3s4

Reply
0 Kudos
iyusaf
Contributor
Contributor

Right now, it's very conservative (only detects if

there's a Mac and a Boot Camp partition on the same

drive), since that's the only configuration we

encountered in testing.

My Bootcamp v1.2 partition is not auto detected. I have a MacBook Pro with the following partition scheme:

/dev/disk0

#: type name size identifier

0: GUID_partition_scheme *149.1 GB disk0

1: EFI 200.0 MB disk0s1

2: Apple_HFS Macintosh HD 87.8 GB disk0s2

3: Microsoft Basic Data Windows XP 61.0 GB disk0s3

The Windows partition is NTFS. I also use Windows NT Filesystem 3G.

Reply
0 Kudos
sung329
Contributor
Contributor

My macbook also not recognizing Bootcamp 1.2 Paritition.

It was partitioned by the terminal.

Disk: /dev/rdisk0 geometry: 7296/255/63 \[117210240 sectors]

Signature: 0xAA55

Starting Ending

#: id cyl hd sec - cyl hd sec \[ start - size]

\----


1: EE 0 0 2 - 25 127 14 \[ 1 - 409639]

2: AF 25 127 15 - 1023 57 63 \[ 409640 - 85091944] HFS+

3: AF 1023 139 2 - 1023 238 40 \[ 85763728 - 10223616] HFS+

*4: 0C 1023 64 42 - 1023 254 23 \[ 96249488 - 20960712] Win95 FAT32L

Reply
0 Kudos
mpontes
Contributor
Contributor

Sorry for the bump, but VMware Fusion beta 3 doesn't recognize my Boot Camp partition on my MacBook Pro either. I installed Boot Camp as normal first. Later, I split my HFS+ partition into two to be able to accommodate a Linux installation. I'm currently using rEFIt as my bootloader, Linux is using grub.

Parallels doesn't detect it at first either, but it works if I force it to use Boot Camp;disk0s4 as the disk image.

Disk: /dev/rdisk0 geometry: 14593/255/63 \[234441648 sectors]

Signature: 0xAA55

Starting Ending

#: id cyl hd sec - cyl hd sec \[ start - size]

\----


1: EE 1023 254 63 - 1023 254 63 \[ 1 - 409639]

2: AF 1023 254 63 - 1023 254 63 \[ 409640 - 180355072] HFS+

3: 83 1023 254 63 - 1023 254 63 \[ 180764712 - 21233664] Linux files*

*4: 07 1023 254 63 - 1023 254 63 \[ 201998376 - 32443232] HPFS/QNX/AUX

Reply
0 Kudos