Apple Event: May 7th at 7 am PT

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

MattP94 Author

Level 1

0 points

Inaccessible bootcamp partition for startup disk

Here are the results of the commands that Christopher asked for in thread: https://discussions.apple.com/thread/4144252

Matts-iMac:~ mattp$ sudo fdisk /dev/disk0

Disk: /dev/disk0 geometry: 121601/255/63 [1953525168 sectors]

Signature: 0xAA55

Starting Ending

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

------------------------------------------------------------------------

1: EE 1023 254 63 - 1023 254 63 [ 1 - 409639] <Unknown ID>

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

3: AB 1023 254 63 - 1023 254 63 [1660565928 - 1269536] Darwin Boot

*4: 07 1023 254 63 - 1023 254 63 [1661837312 - 291686400] HPFS/QNX/AUX

Matts-iMac:~ mattp$ sudo gpt -r -v show disk0

gpt show: disk0: mediasize=1000204886016; sectorsize=512; blocks=1953525168

gpt show: disk0: Suspicious MBR at sector 0

start size index contents

0 1 MBR

1 1 Pri GPT header

2 32 Pri GPT table

34 6

40 409600 1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B

409640 1660156288 2 GPT part - 48465300-0000-11AA-AA11-00306543ECAC

1660565928 1269536 3 GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC

1661835464 1848

1661837312 291686400 4 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

1953523712 1423

1953525135 32 Sec GPT table

1953525167 1 Sec GPT header

iMac (27-inch Mid 2011), OS X Mountain Lion (10.8.4)

Posted on Jul 16, 2013 6:37 PM

16 replies

Jul 17, 2013 12:07 PM in response to MattP94

/dev/disk0s4 on /Volumes/BOOTCAMP (fusefs_txantfs, local, synchronous)

The problem is the fs type in mount info is fusefs_txantfs instead of ntfs as it is when Apple's fs kext is being used. I'm curious how Paragon's results compare. Apple lists msdos, ntfs, and udf as valid options. Since fusefs_txantfs isn't on the list, it's not seen as a valid file system.

I don't know that it's possible for Tuxera to do anything about this because they do in fact implement NTFS via FUSE. Whereas Apple could list any *ntfs file system as bootable. But I suspect they'd just say "works as designed".

You could hack the prefpane in a hexeditor and find the two instances of ntfs and substitute fusefs_txantfs intead. And yeah I would consider it somewhat catestraphic because a.) it's a regression over default behavior and b.) it obviates setting Windows for default booting. The present behavior means you have to use option at boot every time you want to boot windows.

Inaccessible bootcamp partition for startup disk