Skip navigation

Repairing Boot Camp after creating new partition

176802 Views 1,252 Replies Latest reply: Apr 5, 2014 6:57 AM by BobTheFisherman RSS
  • Berend de Meyer Calculating status...
    Currently Being Moderated
    Jan 27, 2013 6:45 AM (in response to autnagrag)

    Hey,

     

    Thanks for your contribution to this thread and good luck and happy BootCamping yourself! :-D

     

    Cheers!

  • Christopher Murphy Level 2 Level 2 (470 points)

    Ok anytime you have to use the power switch to force off power, you've going to have some level of JHFS+ corruption. The journaling doesn't make it any safer, it just makes repairs go faster. So I suggest you reboot in single user mode (with command s) and

    fsck -fy

    <wait>

    then do

    fsck_hfs -r /dev/rdisk0s2

    <wait>

    fsck_hfs -Ra /dev/rdisk0s2

    fsck_hfs -Re /dev/rdisk0s2

     

    -r will definitely find things to repair that regular fsck will not. The other two rarely fix things in my experience, but best to rebuild those btrees too. Then reboot. And it's not a guarantee that it's healthy and problem free, but most likely healthier.

  • Christopher Murphy Level 2 Level 2 (470 points)

    And thanks, but I don't actualy use Bootcamp myself. I consider it too risky. So, go figure - the guy who can fix this stuff himself very easily most of the time still thinks it's too risky to use.

  • Berend de Meyer Level 1 Level 1 (5 points)

    Hi Christopher,

     

    Working on that right now but my root device seems to be read only.

    In the startup it mentioned /sbin/fsck -fy can be used to modify files!

     

    Cheers

  • Christopher Murphy Level 2 Level 2 (470 points)

    It needs to be read only to properly do the repair. fsck can only do a verify on a read/write volume.

  • Berend de Meyer Level 1 Level 1 (5 points)

    OK! I'm set to go then..... keep you posted on the outcome!

     

    Cheers

  • Berend de Meyer Level 1 Level 1 (5 points)

    /var/log fsck_hfs.log

     

    /dev/rdisk0s2: fsck_hfs run at Sun Jan 27 18:29:14 2013

    ** /dev/rdisk0s2

    ** Root file system

       Executing fsck_hfs (version diskdev_cmds-557~393).

    ** Checking Journaled HFS Plus volume.

       The volume name is MAC_OSX_ML

    ** Checking extents overflow file.

    ** Checking catalog file.

    ** Rebuilding extents overflow B-tree.

    ** Rechecking volume.

    ** Checking Journaled HFS Plus volume.

       The volume name is MAC_OSX_ML

    ** Checking extents overflow file.

    ** Checking catalog file.

    ** Checking multi-linked files.

    ** Checking catalog hierarchy.

    ** Checking extended attributes file.

    ** Checking volume bitmap.

    ** Checking volume information.

    ** The volume MAC_OSX_ML was repaired successfully.

    *****The volume was modified *****

     

    Hi Christopher,

     

    THANKS a bunch, above is the only log I could find. During the operation of the commands I wrote down some listings:

     

    fsck -fy

     

    ** MAC_OSX_ML Appears to be ok

     

    fsck_hfs -r /dev/rdisk0s2

     

    ** Rebuilding B-tree

    ** Recheck

    ** Repairing

         Invalid file count

         Invalid directory count

         Invalid free block

    ** Recheck

     

    fsck_hfs -Ra /dev/rdisk0s2


    ** Rebuilding extended attributes

    ** The volume MAC_OSX_ML was repaired successfully.

    *****The volume was modified *****

     

    fsck_hfs -Ra /dev/rdisk0s2


    ** The volume MAC_OSX_ML was repaired successfully.

    ***** The volume was modified *****

     

    The last modification I did was using Paragon NTFS for MAC to set my Windows 8 as Start-up Drive so my new boot-sequence WITHOUT having te use the [power-button] Tried it 5 times now!!!! ;-)

     

    Power-on will primairy boot Windows

    Power-up/Reboot holding [option-key] switch to MAC OSX X disk and boot without the known issues uptill now!

     

    Perhaps in the near future I'll be able to use MAC's Start-Up Disk and BootCamp Application in Windows to switch but for now I'm very happy with the results. Indeed it is much HEALTHIER not to have to use the hard reset everytime now!

     

    Thanks again for your time and help and teaching me even more about the OS X terminal commands which I still will call: "Rocket-Sience!!! ;-)

     

    CHEERS

     




     


    Mac Pro (Early 2008), OS X Mountain Lion (10.8.2), 2.8 GHz | Apple RAID5 | 14GB RAM
  • MacDouglas Calculating status...

    Thanks for this solution and for the tutorial on hybrid MBRs. Your instructions were great, and you've convinced me to use VMs the next time I rebuild my disk.

     

    My question: if I ever need to do a reinstall (repair install) of MacOS from the recovery partition, is it going to muck up this setup?

  • Christopher Murphy Level 2 Level 2 (470 points)
    Currently Being Moderated
    Feb 4, 2013 12:20 PM (in response to MacDouglas)

    I'll use the "s word" followed by the "b word"...  No it shouldn't, but it depends on the setup. If it's a conventional Apple four partition GPT and MBR that are in sync, I've yet to see a problem.

     

    But if the GPT and MBR aren't in sync, because you have a fifth partition, for example;  it seems something tries to make them sync up again, which would cause a problem. I see this in the case where an OS X partition is reformatted (erased), which tends to cause an update to the GPT and MBR in such a way that it renders Windows unbootable until the hybrid MBR is repaired. In a handful of cases the Windows volume is corrupted beyond repair but I haven't been able to establish a reproducing cause for this, so I don't know what sequence is required to make it happen and therefore I don't know how to avoid it.

  • MacDouglas Level 1 Level 1 (0 points)

    Thanks. This is my current setup FYI.

     

    gpt show: disk0: mediasize=512110190592; sectorsize=512; blocks=1000215216

     

    gpt show: disk0: Suspicious MBR at sector 0

    gpt show: disk0: Pri GPT at sector 1

    gpt show: disk0: Sec GPT at sector 1000215215

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

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

       591671512   249589544      4  GPT part - 48465300-0000-11AA-AA11-00306543ECAC

       841261056      262144        

       841523200   158691328      5  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

      1000214528         655        

      1000215183          32         Sec GPT table

      1000215215           1         Sec GPT header

     

    The original motivation for creating a bootcamp partition was (perceived) better performance from parallels. I only ever run the partition in parallels, because of Windows activation issues. Given that I'm running an SSD, I think this original idea is red herring. I'll definitely keep it simpler next time. Parallels has an import from bootcamp to create a vdisk. I should have headed in that route.

    MacBook Pro, Mac OS X (10.7.3)
  • Christopher Murphy Level 2 Level 2 (470 points)
    Currently Being Moderated
    Feb 4, 2013 12:36 PM (in response to MacDouglas)

    Your GPT has five partitions. MBR can only have four primary partitions. Therefore they can't be sync'd. Don't let Disk Utility format any partition on this disk, or add any more partitions to this disk. And maintain good backups, especially right before doing an OS upgrade.

  • MacDouglas Level 1 Level 1 (0 points)

    Thanks. Yes, I'm staying away from Disk Utility already and will do so on a reinstall. Disk Utility is what lead me to this thread in the first place.

  • maghikal Calculating status...

    Hello again i forgot to update this once i fixed my issue.

     

    It turns out Windows 8 wants to boot of the primary internal drive no matter what.

    I put the Windows drive in the palmrest bay and the OS X drive in the optibay.

    Everything just worked after that. i'm using 7200 RPM drives so i'm not suffering from the decreased bandwidth in the optibay but i would rethink my set up had i used an SSD.

  • Christopher Murphy Level 2 Level 2 (470 points)

    The OS X (bootable) volume? Or the data volume?

     

    An OS X bootable system volume can't be encrypted without a Recovery HD partition to be used as the boot volume. You can encrypt the OS X data volume as you suggest.

     

    Further, modification of the Recovery HD volume is necessary, as well as NVRAM, to make the computer aware that the actual boot volume is Recovery HD, decrypt the OS X volume, and complete the system startup sequence from the encrypted volume. I'm unfamiliar with how to do this outside of FileVault 2. I'm not even sure that diskutil cs convert <device> -stdinpassphrase automatically makes these adjustments.

1 ... 30 31 32 33 34 ... 84 Previous Next

Actions

More Like This

  • Retrieving data ...

Bookmarked By (21)

Legend

  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.