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.

Level 1

0 points

Bootcamp not working after partition resizing

Hi,

Following Loner T's advice, I'm starting a new thread.

My problem:

I run OS X 10.9.2 with an SSD which is partitioned. I have OS X and Win 7 via bootcamp. I also use Parallels to run the bootcamp partition when I don't want to restart my computer.

One day I thought I could easily resize my partitions but once I did that, I got my bootcamp ruined and I no longer can boot windows from bootcamp or Parallels.

However I do access the files from OS X.

Marco-Correas-iMac-3:~ marcoac14$ sudo gpt -r -vv show disk0

Password:

gpt show: disk0: mediasize=256060514304; sectorsize=512; blocks=500118192

gpt show: disk0: Suspicious MBR at sector 0

gpt show: disk0: Pri GPT at sector 1

gpt show: disk0: Sec GPT at sector 500118191

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 312914240 2 GPT part - 48465300-0000-11AA-AA11-00306543ECAC

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

314593416 28882808

343476224 156641280 4 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

500117504 655

500118159 32 Sec GPT table

500118191 1 Sec GPT header

Marco-Correas-iMac-3:~ marcoac14$ sudo fdisk /dev/disk0

Disk: /dev/disk0 geometry: 31130/255/63 [500118192 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 - 312914240] HFS+

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

4: 0C 1023 254 63 - 1023 254 63 [ 343476224 - 156641280] Win95 FAT32L

What Loner T has asked me to try:

Please start a new thread, but it may be easily fixable.

Your GPT#4 and MBR#4 seem to be in sync.

1. Check if NTFS is intact (this should show you "R.NTFS" in the dump).

sudo dd if=/dev/rdisk0s4 count=1 2>/dev/null | hexdump -C

2. Using fdisk,

sudo fdisk -e /dev/disk0

setpid 4

07

flag 4

p

w

y

Reboot and test.

Dump:

Marco-Correas-iMac-3:~ marcoac14$ sudo dd if=/dev/rdisk0s4 count=1 2>/dev/null | hexdump -C

Password:

00000000 eb 52 90 4e 54 46 53 20 20 20 20 00 02 08 00 00 |.R.NTFS .....|

00000010 00 00 00 00 00 f8 00 00 3f 00 ff 00 00 08 79 14 |........?.....y.|

00000020 00 00 00 00 80 00 80 00 ff 27 56 09 00 00 00 00 |.........'V.....|

00000030 00 00 0c 00 00 00 00 00 02 00 00 00 00 00 00 00 |................|

00000040 f6 00 00 00 01 00 00 00 71 d1 53 7a e2 53 7a 42 |........q.Sz.SzB|

00000050 00 00 00 00 fa 33 c0 8e d0 bc 00 7c fb 68 c0 07 |.....3.....|.h..|

00000060 1f 1e 68 66 00 cb 88 16 0e 00 66 81 3e 03 00 4e |..hf......f.>..N|

00000070 54 46 53 75 15 b4 41 bb aa 55 cd 13 72 0c 81 fb |TFSu..A..U..r...|

00000080 55 aa 75 06 f7 c1 01 00 75 03 e9 dd 00 1e 83 ec |U.u.....u.......|

00000090 18 68 1a 00 b4 48 8a 16 0e 00 8b f4 16 1f cd 13 |.h...H..........|

000000a0 9f 83 c4 18 9e 58 1f 72 e1 3b 06 0b 00 75 db a3 |.....X.r.;...u..|

000000b0 0f 00 c1 2e 0f 00 04 1e 5a 33 db b9 00 20 2b c8 |........Z3... +.|

000000c0 66 ff 06 11 00 03 16 0f 00 8e c2 ff 06 16 00 e8 |f...............|

000000d0 4b 00 2b c8 77 ef b8 00 bb cd 1a 66 23 c0 75 2d |K.+.w......f#.u-|

000000e0 66 81 fb 54 43 50 41 75 24 81 f9 02 01 72 1e 16 |f..TCPAu$....r..|

000000f0 68 07 bb 16 68 70 0e 16 68 09 00 66 53 66 53 66 |h...hp..h..fSfSf|

00000100 55 16 16 16 68 b8 01 66 61 0e 07 cd 1a 33 c0 bf |U...h..fa....3..|

00000110 28 10 b9 d8 0f fc f3 aa e9 5f 01 90 90 66 60 1e |(........_...f`.|

00000120 06 66 a1 11 00 66 03 06 1c 00 1e 66 68 00 00 00 |.f...f.....fh...|

00000130 00 66 50 06 53 68 01 00 68 10 00 b4 42 8a 16 0e |.fP.Sh..h...B...|

00000140 00 16 1f 8b f4 cd 13 66 59 5b 5a 66 59 66 59 1f |.......fY[ZfYfY.|

00000150 0f 82 16 00 66 ff 06 11 00 03 16 0f 00 8e c2 ff |....f...........|

00000160 0e 16 00 75 bc 07 1f 66 61 c3 a0 f8 01 e8 09 00 |...u...fa.......|

00000170 a0 fb 01 e8 03 00 f4 eb fd b4 01 8b f0 ac 3c 00 |..............<.|

00000180 74 09 b4 0e bb 07 00 cd 10 eb f2 c3 0d 0a 41 20 |t.............A |

00000190 64 69 73 6b 20 72 65 61 64 20 65 72 72 6f 72 20 |disk read error |

000001a0 6f 63 63 75 72 72 65 64 00 0d 0a 42 4f 4f 54 4d |occurred...BOOTM|

000001b0 47 52 20 69 73 20 6d 69 73 73 69 6e 67 00 0d 0a |GR is missing...|

000001c0 42 4f 4f 54 4d 47 52 20 69 73 20 63 6f 6d 70 72 |BOOTMGR is compr|

000001d0 65 73 73 65 64 00 0d 0a 50 72 65 73 73 20 43 74 |essed...Press Ct|

000001e0 72 6c 2b 41 6c 74 2b 44 65 6c 20 74 6f 20 72 65 |rl+Alt+Del to re|

000001f0 73 74 61 72 74 0d 0a 00 8c a9 be d6 00 00 55 aa |start.........U.|

00000200

Marco-Correas-iMac-3:~ marcoac14$ sudo fdisk -e /dev/disk0

fdisk: could not open MBR file /usr/standalone/i386/boot0: No such file or directory

Unfortunately the file is missing but I hope this is still fixable.

Cheers

iMac, OS X Mavericks (10.9.2)

Posted on Sep 7, 2014 5:49 PM

Best reply

Loner T

Level 9

59,471 points

Posted on Sep 7, 2014 6:05 PM

Good to see the NTFS header intact.

Please ignore that error messages which is related to older i386 stuff and continue.

Resizing, using Disk Utility or any other tool, of a Bootcamp partition is not recommended. - Boot Camp 5.1: Frequently asked questions

You may lose this space. 314593416 28882808

View in context

39 replies

marcoac14 Author

Level 1

0 points

Oct 15, 2014 6:55 PM in response to Loner T

I tried that solution but it didn't work either.

The partition I'm taking about has nothing to do with bootcamp or windows installation.

I have two hard disks with two partitions each.

SSD: Macintosh HD (for OS X) and Bootcamp (it's blank right now since I can't install windows)

HDD: Macintosh HD Files (this one shows up in finder and I can access it) and Windows HD Files (this is the one that won't mount)

Thanks

Loner T

Level 9

59,471 points

Oct 15, 2014 7:24 PM in response to marcoac14

When you have more than one physical disk in the system, Bootcamp requires that all drives that are not needed for Bootcamp, should be removed from the system. The only exception is a Fusion drive. A Fusion drive with Bootcamp Assistant ends up with Windows on HDD only, BA will not use the SSD. This is a limitation of BA design.

Can you post the output of

diskutil list

sudo fdisk /dev/disk0

sudo fdisk /dev/disk1

marcoac14 Author

Level 1

0 points

Oct 16, 2014 7:22 PM in response to Loner T

Confused 😟

Just to clear things up, I don't have a Fusion drive. I installed the SSD by myself on a spare SATA port.

I always had Windows installed on a bootcamp SSD partition. I've run my mac like this for years.

There you go:

marcocoeasimac3:~ marcoac14$ diskutil list

/dev/disk0

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *256.1 GB disk0

1: EFI EFI 209.7 MB disk0s1

2: Apple_HFS Macintosh HD 153.2 GB disk0s2

3: Apple_Boot Recovery HD 650.0 MB disk0s3

4: Microsoft Basic Data BOOTCAMP 102.0 GB disk0s4

/dev/disk1

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *1.0 TB disk1

1: EFI EFI 209.7 MB disk1s1

2: Apple_HFS Macintosh HD Files 499.9 GB disk1s2

3: Microsoft Basic Data Windows HD Files 499.9 GB disk1s3

marcocoeasimac3:~ marcoac14$ sudo fdisk /dev/disk0

Password:

Disk: /dev/disk0 geometry: 31130/255/63 [500118192 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 - 299220224] HFS+

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

4: 0B 1023 254 63 - 1023 254 63 [ 300900352 - 199217152] Win95 FAT-32

marcocoeasimac3:~ marcoac14$ sudo fdisk /dev/disk1

Disk: /dev/disk1 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 - 976426672] HFS+

3: 07 1023 254 63 - 1023 254 63 [ 977098752 - 976424960] HPFS/QNX/AUX

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

Thanks!

Loner T

Level 9

59,471 points

Oct 16, 2014 7:44 PM in response to marcoac14

This makes much more sense now. All this while I was under the impression that you had a single disk, while you have two. Your OSes are the SSD and your data is on HDD.

Since you are restarting the Windows installation, the MBR (Fdisk from disk0) indicates it is ready for a Windows installation.

Do you get an error message when you try to mount "Windows HD Files"? Is it an NTFS partition or a FAT? The MBR suggests it is NTFS (type code 07). Since you no longer have Windows on the SSD, you cannot run chkdsk on the drive which is "Windows HD Files".

If you can get Windows up an running, the Windows HD files may need a chkdsk. If it was FAT, OS X could run a Verify/Repair, but not on an NTFS partition.

Do you have any third-party NTFS drivers installed on your OS X side (Tuxera, Paragon, NTFS-3g, etc.)?

You can look at this - http://i.vishalagarwal.com/post/30387627819/ntfs-write-on-lion-or-mountain-lion

marcoac14 Author

Level 1

0 points

Oct 16, 2014 7:49 PM in response to Loner T

It's an NTFS partition and I do get an error.

Mount failed: The disk "Windows HD Files" could not be mounted. Try running First Aid on the disk and then retry mounting.

I have Tuxera. It's weird that Macintosh HD Files is up and running, so I don't be believe I have a faulty disk.

I don't know what's happening but I just can't get Windows working. This is driving me crazy!

I have win xp installed on a VM but the data partition won't show up in windows.

Thanks

Loner T

Level 9

59,471 points

Oct 16, 2014 7:55 PM in response to marcoac14

Can I suggest that you remove Tuxera temporarily (and completely)?

Install Bootcamp so there is no conflict between Apple NTFS and Tuxera. One of your issues is such interference and it will cause problems with Bootcamp installation. Once complete, verify the ability to mount/unmount Windows HD Files. If all this works, now you can install Tuxera and retry your tests. I use the NTFS-3g (2010) version with the UI and I have stayed with it for almost 4+ years without any issues with Bootcamp. The UI specifically allows me to selectively disable NTFS-3g for volumes.

marcoac14 Author

Level 1

0 points

Oct 16, 2014 8:10 PM in response to Loner T

I like your suggestion. It's worth trying!

Do you know of any issues regarding the optical drive reading all dvds as blank?

Maybe it's time to clean up the laser lens. =/

Thanks

Loner T

Level 9

59,471 points

Oct 16, 2014 8:28 PM in response to marcoac14

In last couple of threads with Macs from around 2009-2011, many have mentioned Optical drive failures.

This is the latest - No bootable disk on bootcamp .

Nov 4, 2016 11:25 AM in response to marcoac14

It's actually very simple.

1- Turn off your MAC;

2 - Insert the Windows Bootable Flashdrive that Bootcamp created.

3 - Turn your MAC on AND BE READY;
4 - Once you listen the "chime", yet in the black screen, press and hold the OPTION key;

5 - When the boot menu opens, choose your Bootcamp partition (NOT THE USB DRIVE);

6 - You'll see a troubleshoot screen, choose your language, and go NEXT;

7 - At the bottom part of the window, choose the REPAIR option;

8 - A new menu will show up. Choose ADVANCED;

9 - Then choose to FIX STARTUP (or something like this... can't remember the exact words...)

DONE

Your Bootcamp is back! At least worked for me... Twice...

Bootcamp not working after partition resizing