Resized OSX partition using Disk Utility and now Windows 7 will not boot

Question

Resized OSX partition using Disk Utility and now Windows 7 will not boot

My windows 7 partition doesn't show up after I tried to make more room for it by shrinking my OSX partition in disk utility.

I had no problem doing this on a MBP a few weeks ago.

I tried to run a repair before coming here.

disk utility log:

2013-06-07 15:50:20 -0500: Disk Utility started.

2013-06-07 15:51:14 -0500: Preparing to partition disk: “Hitachi HDT721064SLA360 Media”

2013-06-07 15:51:14 -0500: Partition Scheme: GUID Partition Table

2013-06-07 15:51:14 -0500: 2 partitions will be created

2013-06-07 15:51:14 -0500:

2013-06-07 15:51:14 -0500: Partition 1

2013-06-07 15:51:14 -0500: Name : “Macintosh HD”

2013-06-07 15:51:14 -0500: Size : 90 GB

2013-06-07 15:51:14 -0500: Filesystem : Mac OS Extended (Journaled)

2013-06-07 15:51:14 -0500: Do not erase contents

2013-06-07 15:51:14 -0500:

2013-06-07 15:51:14 -0500: Partition 2

2013-06-07 15:51:14 -0500: Name : “DISK0S3”

2013-06-07 15:51:14 -0500: Size : 352.79 GB

2013-06-07 15:51:14 -0500: Filesystem : MS-DOS (FAT)

2013-06-07 15:51:14 -0500: Do not erase contents

2013-06-07 15:51:14 -0500:

2013-06-07 15:51:14 -0500: Beginning partition operations

2013-06-07 15:51:14 -0500: Verifying disk

2013-06-07 15:52:03 -0500: Shrinking disk

2013-06-07 15:52:23 -0500: Unmounting disk

2013-06-07 15:52:24 -0500: Finishing partition modifications

2013-06-07 15:52:24 -0500: Waiting for disks to reappear

2013-06-07 15:52:24 -0500: Partition complete.

2013-06-07 15:52:24 -0500:

**********

2013-06-07 15:57:18 -0500: Disk Utility started.

2013-06-07 15:57:58 -0500: Verifying volume “Macintosh HD”

2013-06-07 15:57:58 -0500: Starting verification tool:

2013-06-07 15:58:46 -0500: Performing live verification.

2013-06-07 15:58:46 -0500: Checking Journaled HFS Plus volume.

2013-06-07 15:58:46 -0500: Checking extents overflow file.

2013-06-07 15:58:46 -0500: Checking catalog file.

2013-06-07 15:58:46 -0500: Checking multi-linked files.

2013-06-07 15:58:47 -0500: Checking catalog hierarchy.

2013-06-07 15:58:47 -0500: Checking extended attributes file.

2013-06-07 15:58:47 -0500: Checking volume bitmap.

2013-06-07 15:58:47 -0500: Checking volume information.

2013-06-07 15:58:47 -0500: The volume Macintosh HD appears to be OK.

2013-06-07 15:58:47 -0500: Repair tool completed:

2013-06-07 15:58:47 -0500:

2013-06-07 15:58:47 -0500: Verifying volume “disk0s3”

2013-06-07 15:58:47 -0500: Starting verification tool:

2013-06-07 15:58:47 -0500: ** /dev/disk0s3

2013-06-07 15:58:47 -0500: Invalid BS_jmpBoot in boot block: 534552

2013-06-07 15:58:47 -0500: Error: This disk needs to be repaired. Click Repair Disk.2013-06-07 15:58:47 -0500:

2013-06-07 15:58:47 -0500: Disk Utility stopped verifying “disk0s3”: This disk needs to be repaired. Click Repair Disk.

2013-06-07 15:58:47 -0500:

2013-06-07 16:05:53 -0500: Verify and Repair volume “disk0s3”

2013-06-07 16:05:53 -0500: Starting repair tool:

2013-06-07 16:05:53 -0500: ** /dev/disk0s3

2013-06-07 16:05:53 -0500: Invalid BS_jmpBoot in boot block: 534552

2013-06-07 16:05:53 -0500: Volume repair complete.2013-06-07 16:05:53 -0500: Updating boot support partitions for the volume as required.2013-06-07 16:05:53 -0500: Error: Disk Utility can’t repair this disk. Back up as many of your files as possible, reformat the disk, and restore your backed-up files.2013-06-07 16:05:53 -0500:

2013-06-07 16:05:53 -0500: Disk Utility stopped repairing “disk0s3”: Disk Utility can’t repair this disk. Back up as many of your files as possible, reformat the disk, and restore your backed-up files.

2013-06-07 16:05:53 -0500:

terminal output

Computer-IV:~ computerIII$ sudo fdisk /dev/disk0

Password:

Disk: /dev/disk0 geometry: 77825/255/63 [1250263728 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 - 175781256] HFS+

3: 0C 1023 254 63 - 1023 254 63 [ 561219584 - 689043456] Win95 FAT32L

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

Computer-IV:~ computerIII$

Computer-IV:~ computerIII$ sudo gpt -r -v show disk0

gpt show: disk0: mediasize=640135028736; sectorsize=512; blocks=1250263728

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

176190896 385028688

561219584 689043456 3 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

1250263040 655

1250263695 32 Sec GPT table

1250263727 1 Sec GPT header

iMac, Mac OS X (10.6.8)

Posted on Jun 7, 2013 4:05 PM

Reply

Answer 1

Jun 7, 2013 4:38 PM in response to Justin Randall

You need to provide a detailed step by step how the BOOTCAMP volume was created, and exactly how you tried to make more room for it. Can you confirm this is 10.6.8? The repair log clearly indicates the repair utility thinks disk0s3 is FAT32, not NTFS which is what it should be. When you installed Windows, did you format it NTFS first?

Reply

Answer 2

Jun 7, 2013 5:15 PM in response to Christopher Murphy

By bootcamp volume do you mean my windows partition? Its been so long I don't remember what I did when I created it.

I'm fairly sure the windows partition wasn't formatted for FAT32 when it was working properly.

Yes my mac os is 10.6.8.

I tried to make room for my windows partition by grabbing the slider in disk utility and dragging it smaller. I then set the partition size manually to 90 GB. I was then going to boot in windows and open up the control panel and resize that partition larger to allocate more space, but the option to boot in windows didn't show up with the option button held on startup.

Reply

Answer 3

Jun 7, 2013 5:18 PM in response to Justin Randall

You wanted to make the Windows volume bigger, so you used Disk Utility to make the OS X volume smaller first?

Reply

Answer 4

Jun 7, 2013 5:48 PM in response to Christopher Murphy

Yes. There was over 100GB of unused space on my OSX partition that I wanted to make available on my windows partition.

Reply

Answer 5

Jun 7, 2013 6:01 PM in response to Justin Randall

OK part of this I think is a bug, in that upon shrinking the OS X volume and changing the GPT, diskutil also changed the hybrid MBR but didn't correctly set the partition type ID or the active flag. It's possible Disk Utility sees the 0C type code, and incorrectly assumes the Windows volume is FAT32 and tries to repair it. In fact it's NTFS, so if it actually tried to modify the volume, it would almost certainly damage it. The likely solution is to change the MBR #3 partition type ID to 07, and set the boot flag. This is maybe easiest done with the built-in fdisk utility:

sudo fdisk -e /dev/disk0

You'll get some bogus error you can ignore, and will now find you're at an fdisk prompt indicating you're in interactive mode. Type these commands following each line with return

print

setpid 3

07

flag 3

print

At this point stay in interactive mode and copy everything, and then paste it somewhere like pastebin.com with a 1 week or more expiration. I'll double check the changes, and you'll then type: write <enter> to write out the modified mbr. Then reboot and see if you can get into Windows.

Reply

Answer 6

Jun 7, 2013 7:38 PM in response to Christopher Murphy

http://pastebin.com/ZTPMxzBa

Reply

Answer 7

Jun 7, 2013 7:40 PM in response to Justin Randall

Ok good. Now type:

write

And reboot, see if it works.

Reply

Answer 8

Jun 7, 2013 8:08 PM in response to Christopher Murphy

It gave me a confirmation dialogue and I pressed "y" then quit and restart. The windows option shows up when I hold down "alt"" at start up. I selected it and wait then a message saying "missing operating system" or something like that. I have to restart to exit.

Thanks for getting me this far, haven't tried anything else yet.

Any other ideas?

Reply

Answer 9

Jun 7, 2013 8:16 PM in response to Justin Randall

Disk Utility thinks its FAT32 when I click on the partition.

here are the same sudo commands from the begining performed now.

http://pastebin.com/gRjP2av9

Reply

Answer 10

Jun 7, 2013 8:20 PM in response to Justin Randall

The partition information is now correct. Remaining problems can be with the MBR boot strap code, the volume boot record code, or winload, or the file system itself. Ideally you'd make a backup using something like dd, which can make a sector copy of a partition and save it as a file. That way if repair attempts make things worse, there's a way to regress.

Next, boot from the Windows installation disk, and run Windows Startup Repairand let it chug away.

Reply

Answer 11

Jun 7, 2013 8:25 PM in response to Justin Randall

OK hold working on the previous advice. We need to find out if this partition is NTFS or FAT32, if it's FAT32 it's been reformatted somehow and if that's the case you're in testdisk catagory if you don't have a backup. Copy paste this command to terminal and put the output in pastebin and report the url.

sudo dd if=/dev/disk0s3 count=8 2>/dev/null | hexdump -C

That's a single line command.

Reply

Answer 12

Jun 7, 2013 9:03 PM in response to Christopher Murphy

I didn't see your 2nd comment before I tried to have the windows system disk attempt a repir. It wasn't able to and I dont have a image or backup to restore to.

here is the result of the above command

http://pastebin.com/nJfzxWzM

Reply

Answer 13

Jun 8, 2013 4:39 AM in response to Justin Randall

OK that doesn't look like it's either FAT32 or NTFS, so now you're in testdisk territory.

For future reference, the approach you were trying to use couldn't have worked. Apple's tools always unset the boot flag and change the partition type code in the MBR, incorrectly, when altering the MBR/GPT after a resize. Even if you fix that, and then get to Windows to do a resize, this won't work for two reasons: 1.) live resizes happen from the end of the volume. It won't resize from the beginning but the free space you had was at the beginning. So it takesa different utility that can first relocate the volume to a new starting point, and then resizing from the end. 2.) The Windows resize utility doesn't know about hybrid MBR/GPTs, so it will only update the MBR information, leaving the GPT with incorrect information. Windows will boot, but OS X will no longer see the NTFS volume.

The point is, you have to use a resizing utility that expressly understands the unique (non-standard) partition layout being used to make Boot Camp work.

Reply

Answer 14

LowLuster

Level 6

12,105 points

Jun 8, 2013 5:49 AM in response to Justin Randall

Once you create a windows partition you can not fool with any partitions on your system. Neither on the mac side or the windows side as if you do, as you have found out, windows won't boot. And sometimes not even os x will boot.

You'll have to redo all of your partitions. One for os x and then one for windows using the boot camp assistant program and then leave them alone. Do not try to modify either os x or windows partitions in any way.

Reply

Answer 15

Jun 8, 2013 2:09 PM in response to LowLuster

That's not really true. The are 3rd party applications that will do this correctly, like CampTune, WinClone or iPartition. It's also possible to do this manually with free utilities: diskutil to resize HFS+, GParted on Linux to move and resize the NTFS volume, then fdisk or gdisk to recreate the hybrid MBR and set the boot flag on the Windows partition.

What is true is that Apple doesn't provide the means to do this, and Disk Utility is unsafe, at most any speed, to use on a Bootcamp'd disk.

Reply