Jacobn617

Q: Bootcamp not showing in Devices & Can't transfer files between.

My computer can boot up BOOTCAMP but is not showing up in Finder. It is also not Mounting . I have tried to do system repair on windows 7 but had no problems.

I read multiple discussions about people having their MBR/GPT 's getting corrupt and instaled gdisk to fix it. Then found out that those solutions will not apply to me without messing up my hard drive.

 

I have Tuxera NTFS and Gdisk installed if thats any help.

 

I had the command: sudo gpt -r -vv show disk0 shown and this is what appeared.

 

gpt show: disk0: mediasize=500107862016; sectorsize=512; blocks=976773168

gpt show: disk0: Suspicious MBR at sector 0

gpt show: disk0: Pri GPT at sector 1

gpt show: disk0: Sec GPT at sector 976773167

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

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

  588019544        168        

  588019712  144130048      4 

  732149760  244623360      4  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

  976773120         15        

  976773135         32         Sec GPT table

  976773167          1         Sec GPT header

 

And have done the: sudo fdisk /dev/disk0 command.

 

Disk: /dev/disk0geometry: 60801/255/63 [976773168 sectors]

Signature: 0xAA55

         Starting       Ending

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

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

1: EE    0   0   2 -   25 127  14 [         1 -     409639] <Unknown ID>

2: AF   25 127  15 - 1023 254  63 [    409640 -  586340368] HFS+       

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

*4: 07 1023 254  63 - 1023 254  63 [ 588019712 -  388753408] HPFS/QNX/AUX

 

If that is any help. Please help, i've had this problem for ages and had to painstakingly wait about 10 min just to transfer files via USB.

 

EDIT: I also have had my partition resized when this occoured.

MacBook Pro (13-inch, Mid 2012), OS X Mountain Lion (10.8.2), Really Awesome

Posted on Mar 8, 2013 4:02 AM

Close

Q: Bootcamp not showing in Devices & Can't transfer files between.

  • All replies
  • Helpful answers

  • by Jacobn617,

    Jacobn617 Jacobn617 Mar 8, 2013 2:27 PM in response to Jacobn617
    Level 1 (5 points)
    Mar 8, 2013 2:27 PM in response to Jacobn617

    Bump.

    If no one helps between 48 Hours ill just close this thread.

  • by Christopher Murphy,Solvedanswer

    Christopher Murphy Christopher Murphy Mar 8, 2013 3:29 PM in response to Jacobn617
    Level 3 (555 points)
    Mar 8, 2013 3:29 PM in response to Jacobn617

    What did you use to resize the NTFS volume?

     

    The problem is that the tool you used to resize the NTFS volume updated the MBR but didn't update the GPT. OS X only uses the GPT, and since the partition is invalid in the GPT, the NTFS volume doesn't mount. The MBR must have the correct entry, and that's why you can still boot.

     

    Only tools explicitly designed for resizing Bootcamp'd disks know to update both the MBR and the GPT. So you're kinda lucky this hasn't totally hosed both systems. I suggest backing up before you do anything else. Use Windows backup or even file copy to get the most important stuff off the Windows side, and also make sure you have a current OS X backup also. Then you can proceed.

     

    What you need to do is delete GPT entry #4, and use the information from the MBR entry #4 to create a new GPT #4 entry. You can do this with gdisk. The basic steps in gdisk:

     

    1. p to print the GPT partition table

    2. Confirm in the list that partition 4 starts at LBA 732149760, and if so delete this partition. That's d <enter> then enter the partition number to delete.

    3. n to create a new partition. The start sector is 588019712, the end sector is 976773119. The partition type code is 0700.

    4. r to get to the recovery/transform menu.

    5. h to create a new hybrid mbr

    6. 2 3 4 to add GPT partitions 2 3 4 to the MBR.

    7. y to put EFI GPT as the first MBR entry.

    8. For all prompts to enter an MBR hex code, just hit return, which will accept the default.

    9. For GPT partition 2 and 3, do NOT make them bootable.

    10. For GPT partition 4, DO make it bootable.

    11. type o <return> p <return> and post the results if you want and I'll proof read it before you commit. Just leave gdisk at that prompt don't close Terminal or quit gdisk. The changes are in memory.

     

    When you're ready to commit, you'll type w to write it out to disk. Then you need to reboot.

  • by Jacobn617,

    Jacobn617 Jacobn617 Mar 8, 2013 4:41 PM in response to Jacobn617
    Level 1 (5 points)
    Mar 8, 2013 4:41 PM in response to Jacobn617

    I shall try this tonight, im currently outside. Thank you

  • by Jacobn617,

    Jacobn617 Jacobn617 Mar 8, 2013 5:29 PM in response to Jacobn617
    Level 1 (5 points)
    Mar 8, 2013 5:29 PM in response to Jacobn617

    Ok before I commit:

     

    o <return> :

    Disk size is 976773168 sectors (465.8 GiB)

    MBR disk identifier: 0x39530D0A

    MBR partitions:

     

     

    Number  Boot  Start Sector   End Sector   Status      Code

       1                     1       409639   primary     0xEE

       2                409640    586750007   primary     0xAF

       3             586750008    588019543   primary     0xAB

       4      *      588019712    976773119   primary     0x07

     

    And p <return>:

    Disk /dev/disk0: 976773168 sectors, 465.8 GiB

    Logical sector size: 512 bytes

    Disk identifier (GUID): 4DC85F3A-EF63-471F-B5A1-FA4E30FF109C

    Partition table holds up to 128 entries

    First usable sector is 34, last usable sector is 976773134

    Partitions will be aligned on 8-sector boundaries

    Total free space is 189 sectors (94.5 KiB)

     

    Number  Start (sector)    End (sector)  Size       Code  Name

       1              40          409639   200.0 MiB   EF00  EFI System Partition

       2          409640       586750007   279.6 GiB   AF00  Customer

       3       586750008       588019543   619.9 MiB   AB00  Recovery HD

       4       588019712       976773119   185.4 GiB   0700  Microsoft basic data

     

    So permission to start?

  • by Christopher Murphy,Helpful

    Christopher Murphy Christopher Murphy Mar 8, 2013 5:54 PM in response to Jacobn617
    Level 3 (555 points)
    Mar 8, 2013 5:54 PM in response to Jacobn617

    Yes, write it out.

  • by Jacobn617,

    Jacobn617 Jacobn617 Mar 8, 2013 5:56 PM in response to Christopher Murphy
    Level 1 (5 points)
    Mar 8, 2013 5:56 PM in response to Christopher Murphy

    lol how so i write it out -_-

  • by Christopher Murphy,Helpful

    Christopher Murphy Christopher Murphy Mar 8, 2013 5:58 PM in response to Jacobn617
    Level 3 (555 points)
    Mar 8, 2013 5:58 PM in response to Jacobn617

    w

  • by Jacobn617,

    Jacobn617 Jacobn617 Mar 8, 2013 6:21 PM in response to Jacobn617
    Level 1 (5 points)
    Mar 8, 2013 6:21 PM in response to Jacobn617

    Success thank you so much

  • by Christopher Murphy,

    Christopher Murphy Christopher Murphy Mar 8, 2013 6:28 PM in response to Jacobn617
    Level 3 (555 points)
    Mar 8, 2013 6:28 PM in response to Jacobn617

    You can boot Windows, and see also see the Windows volume when booted in OS X?

     

    You somehow managed to escape a nasty case of data loss. Often what happens in these cases is the various parts overlap. And the NTFS resize is only noted in the MBR. Further the NTFS resize causes corruption of the backupt GPT at the end of the disk. When fixing the GPT corruption, it corrupts the NTFS volume, and also replaces the MBR, which contains the correct entry for the NTFS volume. Now, the correct values for the NTFS volume aren't available, and the NTFS file system is corrupt. So it's a huge mess.

     

    If you aren't doing regular backups of both environments, this really, really should scare you into doing it now.

  • by Jacobn617,

    Jacobn617 Jacobn617 Mar 8, 2013 6:45 PM in response to Jacobn617
    Level 1 (5 points)
    Mar 8, 2013 6:45 PM in response to Jacobn617

    Yep all fully functional

     

    Thanks so much