xTyD23x

Q: BOOTCAMP partition boot problems

Hi, I have seen a few posts that are very similar to mine, but I cannot seem to get to the bottom of this issue. Here is the background on what happened:

 

I was running El Capitan on a single OS X partition and decided to run Boot Camp Assistant and install Windows 10 on a new partition. This worked perfectly and I was using Windows and booting back and forth. I then decided that I would like to create a new partition to easily share files between the 2 OS's using a Fat-32 file system so that both OS's could have read/write access. I did this with Disk Utility on the Mac side and everything seemed to go smoothly. Also, I did not touch my BOOTCAMP partition, but took all the space for the new partition from the Mac side. Everything seemed fine.....until I tried to boot back into BOOTCAMP. Now this partition is not recognized as bootable, though it is accessible from within the Mac side and everything seems in tact.

 

I ran the diskutil list command and here is the output:

 

/dev/disk0 (internal, physical):

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      GUID_partition_scheme                        *500.3 GB   disk0

   1:                        EFI EFI                     209.7 MB   disk0s1

   2:                  Apple_HFS Macintosh HD            361.5 GB   disk0s2

   3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3

   4:                  Apple_HFS SHARED                  22.7 GB    disk0s4

   5:       Microsoft Basic Data BOOTCAMP                115.0 GB   disk0s5

Tylers-MacBook-Pro-3:~ tylerdouglas$ diskutil info disk0s5

   Device Identifier:        disk0s5

   Device Node:              /dev/disk0s5

   Whole:                    No

   Part of Whole:            disk0

   Device / Media Name:      BOOTCAMP

 

   Volume Name:              BOOTCAMP

 

   Mounted:                  Yes

   Mount Point:              /Volumes/BOOTCAMP

 

   File System Personality:  NTFS

   Type (Bundle):            ntfs

   Name (User Visible):      Windows NT File System (NTFS)

 

   Partition Type:           Microsoft Basic Data

   OS Can Be Installed:      No

   Media Type:               Generic

   Protocol:                 SATA

   SMART Status:             Verified

   Volume UUID:              1EF1A5FC-BEBE-4528-A0A2-6755D96E1AB0

   Disk / Partition UUID:    0F83EFE3-3E4B-4EAA-8C08-0590F3C60EAA

 

   Total Size:               115.0 GB (114999427072 Bytes) (exactly 224608256 512-Byte-Units)

   Volume Free Space:        72.5 GB (72523272192 Bytes) (exactly 141647016 512-Byte-Units)

   Device Block Size:        512 Bytes

   Allocation Block Size:    4096 Bytes

 

   Read-Only Media:          No

   Read-Only Volume:         Yes

 

   Device Location:          Internal

   Removable Media:          No

 

   Solid State:              Yes



My theory was that because the BOOTCAMP partition moved from 4 to 5, this somehow confused things. I decided that I didn't care any more about having the shared partition, so I erased it. I then tried to delete this partition, but I am unable to do this using Disk Utility in regular or recovery mode. I have tried unmounting and then deleting in both modes. I have scoured the the internet looking for a solution and I am completely stuck. This seems like it should be a super simple fix, but it's frustrating that I can't figure it out. I don't think I have damaged or corrupted anything and I just need to be able to boot into Bootcamp.


PLEASE HELP!!!


Thanks in advance!

MacBook Pro (Retina, Mid 2012), OS X El Capitan (10.11.3)

Posted on Mar 15, 2016 9:26 PM

Close

Q: BOOTCAMP partition boot problems

  • All replies
  • Helpful answers

first Previous Page 6 of 6
  • by xTyD23x,

    xTyD23x xTyD23x Apr 22, 2016 12:15 AM in response to Loner T
    Level 1 (4 points)
    Apr 22, 2016 12:15 AM in response to Loner T

    So I decided to give up and try to do this right. I backed up the data that I needed from my BC drive (accessible through osx) and I re-ran BC Assistant to install a fresh copy of Windows 10. Everything worked great. I ran the driver setup and everything is working perfectly. I went to boot back into Mac and I ran into the same issue as I had before (I think you called it a kernel panic??? - too lazy to go back in this thread to find it, but I think you know what I'm talking about ). I reinstalled OSX using my flash drive OS's recovery partition and it worked perfectly. Booted into Mac and everything was back to normal. Booted back into Windows to make sure all was well. All good. Booted back to Mac, same issue!!! I don't know what to do. I am down to just my original setup that was working before I tried to create an extra partition (Mac partition + recovery and my BootCamp partition). I have wasted a ton of time at this point and all to just get things back to the way they were. I was hoping to learn some stuff in the process, but mostly what I've learned is don't mess with partitions! Any idea why I would get this every time I boot into BC and then back into Mac???

  • by Loner T,

    Loner T Loner T Apr 22, 2016 6:02 AM in response to xTyD23x
    Level 7 (24,202 points)
    Safari
    Apr 22, 2016 6:02 AM in response to xTyD23x

    The issue is not your OS X. The GPU/CPU panic is related to incorrect drivers being installed by W10. Can you re-install W10 and disable Windows Automatic Updates and Driver updates and monitor the stability of the system? Also, consider W8.1 as an option.

first Previous Page 6 of 6