Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Mavericks Damaged Bootcamp

murphychris said:
That's probably expected because I don't think that header is erased. Are you sure the resize grow of the NTFS volume was successful? It was originally what size and was grown to what size?
Click to expand...

It was originally around 100gb-150gb, I think, and has grown to about 220gb.
 
ihuman:D said:
It was originally around 100gb-150gb, I think, and has grown to about 220gb.
Click to expand...

OK interesting, because your GPT partition 3 size is 432312320 sectors, which by my calculation is 206GiB or 221GB.

This giant pile of free space is listed as 251270504 sectors. Combining the free space and GPT 3 is 325GiB, by my calculation. Feel free to double check that math, but it sounds like to me either the GPT is currently already correct and you have a mysterious pile of free space; or you're mistaken about how big this partition is supposed to be.

In testdisk you're able to navigate (get file and folder listing) the partition listed as [BOOTCAMP]? I think I see a screen shot of such files anyway...

----------

Nevermind, I guess that's one of the small MS Data options listing a few system files.

----------

I just looked at these numbers again and based on what you've said, I'm sufficiently confused that I don't have a good answer for you. Either the NTFS volume is what's listed as GPT 3, is 206GiB, and you have a pile of totally unused reason, free space for unknown reasons; or it's ~325GiB yet the proper header can't be found by either dd or testdisk, in which case it's more difficult to figure this out than a needle in 500 haystacks the size of Grand Central Terminal.
 
Thought this image from Disk Utility might be interesting.

attachment.php


Macintosh HD = 650GB
BOOTCAMP = 221.34GB
DISK0S4 = 128.65GB
Free Space = 221.21GB

I know Disk Utility can't always be trusted but it shows free space at the bottom and a blank space after Macintosh HD that is selected when Macintosh HD is. I have no idea where both came from.
I thought my OS X partition was 750GB.

So that would be: (Guessing)
OS X = 750GB
Win = 220GB
Which would add to 970GB with room to spare for Recovery HD (?) .
 

Attachments

  • Untitled.png
    Untitled.png
    15.7 KB · Views: 808
Last edited:
sudo gdisk -l /dev/rdisk0
Code: 
Found valid GPT with hybrid MBR; using GPT.
Disk /dev/rdisk0: 1953525168 sectors, 931.5 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): E75F28D6-93B0-42FD-9CE6-1408AC92ADE1
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 1953525134
Partitions will be aligned on 8-sector boundaries
Total free space is 1429 sectors (714.5 KiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1              40          409639   200.0 MiB   EF00  EFI System Partition
   2          409640      1269940887   605.4 GiB   AF00  Customer
   3      1521211392      1953523711   206.1 GiB   0700  BOOTCAMP
   4      1269940888      1521211391   119.8 GiB   0700  whoknows

sudo gpt -r -v show /dev/rdisk0
Code: 
gpt show: /dev/rdisk0: mediasize=1000204886016; sectorsize=512; blocks=1953525168
gpt show: /dev/rdisk0: 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  1269531248      2  GPT part - 48465300-0000-11AA-AA11-00306543ECAC
  1269940888   251270504      4  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
  1521211392   432312320      3  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
  1953523712        1423         
  1953525135          32         Sec GPT table
  1953525167           1         Sec GPT header
 
Disk Utility seems confused. Maybe it's trying to rectify the difference between the MBR and the GPT and just not doing a great job of it. It doesn't really matter in terms of fixing your problem, but if you use gdisk's main menu ? to find the option to restort the list, it'll put the entries in order of sector use. Your 4th partition is in fact between partitions 2 and 3 in terms of sectors, but it's the 4th entry in the partition table. The spec allows this so there's nothing wrong with it. At the same time you can use the expert menu to find the create new protective mbr command. And then write out the new partition maps. Reboot, then check it with Disk Utility and things should be more sane.

You definitely don't have 221GB of free space, if free space means unpartitioned space. All space on your disk in the GPT is currently partitioned except for 714.5KiB.
 
Thanks for your help. If there's no other way to get the Bootcamp data back then I think I'll just give up.
 
ihuman:D said:
Thanks for your help. If there's no other way to get the Bootcamp data back then I think I'll just give up.
Click to expand...

If you haven't already done it, I'd create a new hybrid MBR based on the current GPT, and run Windows Startup Repair. If that doesn't work, if it can't even find a legitimate Windows volume, then there's nothing to be done. But depending on the boot error, there are a number of repairs that can be done to fix this so long as the file system isn't trashed. Those are located on this page:

http://support.microsoft.com/kb/927392

Make sure to click on the + for Bootrec.exe options, which is where the meat and potatoes of this article are.
 
ihuman:D said:
Sorry for the late reply, thanks for helping me. What GPT partition numbers should I use when creating the new Hybrid MBR?
Click to expand...

Just to avoid confusion, since your 4th partition is added between partition 2 and 3, in the gdisk main menu, use the sort command, then make the hybrid MBR adding partitions 2 3 4 and making 4 bootable. From the recovery menu after you'd made the hybrid MBR, you can use the o and p command to display the hybrid MBR, and the GPT, and this should be the fourth partition instead of the 3rd:

3 1521211392 1953523711 206.1 GiB 0700 BOOTCAMP
 
Does anyone know what to do with this message?
You may need to edit /etc/fstab and/or your boot loader configuration!

I apologise if I'm being a hassle.
 
murphychris said:
Just to avoid confusion, since your 4th partition is added between partition 2 and 3, in the gdisk main menu, use the sort command, then make the hybrid MBR adding partitions 2 3 4 and making 4 bootable. From the recovery menu after you'd made the hybrid MBR, you can use the o and p command to display the hybrid MBR, and the GPT, and this should be the fourth partition instead of the 3rd:

3 1521211392 1953523711 206.1 GiB 0700 BOOTCAMP
Click to expand...

Or could I do 2 4 3 and make 3 bootable without using the sort command?
 
I tried Bootrec.exe using the following commands:

X:\ bootrec.exe /FixMbr
X:\ bootrec.exe /FixBoot
X:\ bootrec.exe /ScanOS

Nothing worked, they didn't detect anything. I also tried Automatic Repair which didn't find anything either.
 
Did you try creating a new hybrid MBR adding the EFI partition and then partitions 2 3 and 4 making partition 3 (or at least the one that defaults to type 07) as bootable?
That would be my first thought.
 
Code: 
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 - 1269531248] HFS+        
*3: 0C 1023 254  63 - 1023 254  63 [1521211392 -  432312320] Win95 FAT32L
 4: 00    0   0   0 -    0   0   0 [         0 -          0] unused
 
Not looking good then I'm afraid.
It's not encouraging that scanos finds no Windows installation either.
I think it may be time to consider starting afresh.

One last desperate attempt at regaining something could be to run a Linux Live system like Ubuntu and see whether any Windows type partition shows in its file system. If it does you may be able to recover something, though if testdisk didn't show much I doubt that.
It is a long shot that it will show up though.
Sorry :confused:
 
I tried an Ubuntu 12.04 live-cd and Bootcamp showed up in the file explorer but when I clicked it I received this error message:

Error mounting: mount exited with exit code 13: ntfs_mst_post_read_fixup_warn: magic: 0xd8cbad79 size: 1024 usa_ofs: 53960 usa_count: 23428: Invalid argument
Record 6 has no FILE magic (0xd8cbad79)
Failed to open inode FILE_Bitmap: Input/output error
Failed to mount '/dev/sda3': Input/output error
NTFS is either inconsistent, or there is a hardware fault, or it's a
SoftRAID/FakeRAID hardware. In the first case run chkdsk /f on Windows
then reboot into Windows twice. The usage of the /f parameter is very
important! If the device is a SoftRAID/FakeRAID then first activate
it and mount a different device under the /dev/mapper/ directory, (e.g.
/dev/mapper/nvidia_eahaabcc1). Please see the 'dmraid' documentation
for more details.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back