cranberry667
Level 1 (0 points)

Q: Created partition after bootcamp windows install - 'No Disk'

Had Windows 7 installed via bootcamp for some time and decided to go back into the mac OS and create another NTFS partition for extra storage and here I am 10 minutes later finding out this destroys the bootcamp partition.

 

Found this thread https://discussions.apple.com/thread/4144252?start=630&tstart=0

 

Setup:

 

Single 500GB drive

2 Partitions - 1 Mac OS, other Windows NTFS

 

 

sudo gpt -r -vv show disk0

 

 

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

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

  164017496  323990184        

  488007680  488765440      4  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

  976773120         15        

  976773135         32         Sec GPT table

  976773167          1         Sec GPT header

 

 

 

 

sudo fdisk /dev/disk0

 

 

Disk: /dev/disk0geometry: 60801/255/63 [976773168 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 -  162338320] HFS+       

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

4: 0C 1023 254  63 - 1023 254  63 [ 488007680 -  488765440] Win95 FAT32L

 

iMac, Mac OS X (10.7.5)

Posted on Jul 24, 2013 1:55 AM

by Christopher Murphy,Solvedanswer
Christopher Murphy Christopher Murphy
Level 3 (555 points)
A:

I can't answer your question, all I can tell you is I've filed two bugs: one for documentation to be more clear about what proscriptions there are related to Boot Camping a drive, and for Disk Utility to warn or disallow changes (short of blowing away the whole disk which it should still allow).

 

As for the 2-5GB that you can't use, it really isn't that difficult to move the Recovery HD partition to the end of that 2-5GB of free space, thereby making 2-5GB right after the OS X JHFS+ partition. Then diskutil resizevolume should allow the volume to be expanded into this free space. It also doesn't hurt to just leave it be. If you get to a situation where you need those 2-5GB, you're probably ready for a bigger drive anyway.

Posted on Jul 27, 2013 1:12 PM

Close
cranberry667

Q: Created partition after bootcamp windows install - 'No Disk'

  • All replies
  • Helpful answers

Page 1 of 3 last Next

  • by BobTheFisherman,

    BobTheFisherman BobTheFisherman Jul 24, 2013 7:01 AM in response to cranberry667
    Level 6 (15,734 points)
    Jul 24, 2013 7:01 AM in response to cranberry667

    Do you have a question?

  • by cranberry667,

    cranberry667 cranberry667 Jul 24, 2013 7:38 AM in response to BobTheFisherman
    Level 1 (0 points)
    Jul 24, 2013 7:38 AM in response to BobTheFisherman

    Hi I made the post to show Christopher Murphy from the thread I linked, the required information for him to help me fix the issue of being unable to boot into a bootcamp partition and being presented with the 'No bootable device' error. I found the reason for this is repartitioning the main drive after creating a bootcamp partition.

     

    But if you too can help me then that would be great.

  • by BobTheFisherman,

    BobTheFisherman BobTheFisherman Jul 24, 2013 7:42 AM in response to cranberry667
    Level 6 (15,734 points)
    Jul 24, 2013 7:42 AM in response to cranberry667

    You should post the information in the thread where he is helping you. He may not find this (your) randomly placed post.

  • by cranberry667,

    cranberry667 cranberry667 Jul 24, 2013 7:53 AM in response to BobTheFisherman
    Level 1 (0 points)
    Jul 24, 2013 7:53 AM in response to BobTheFisherman

    He wasn't helping me. He'd said to others to create a post with the correct information and link to the thread in the main discussion so he can find it and reply here.

  • by BobTheFisherman,

    BobTheFisherman BobTheFisherman Jul 24, 2013 8:02 AM in response to cranberry667
    Level 6 (15,734 points)
    Jul 24, 2013 8:02 AM in response to cranberry667

    It is not clear what your question is by reading this thread. It appears you tried to create another partition after creating a Bootcamp partition. You can not do that. By doing so you have messed up your drive. You have to save off your data,  erase, and format your hard drive. Then reinstall OSx. Then run Bootcamp Assistant again. Do not try to resize, add, delete, or otherwise mess with a drive that contains a Bootcamp partition.

  • by cranberry667,

    cranberry667 cranberry667 Jul 24, 2013 8:21 AM in response to BobTheFisherman
    Level 1 (0 points)
    Jul 24, 2013 8:21 AM in response to BobTheFisherman

    Yer sorry I didn't think this would be found by anyone else apart from the person it was intended for.

     

    I thought I'd have to do that too but according to Christopher Murphy it can be fixed without starting from scratch.

     

     

    Christopher Murphy wrote:

     

    Yes I know how to fix this without starting over from scratch, but it requires committment to the command line and most people turn into wimps and bail out. So unless you commit to the process I'm not going to put in the investment. In the meantime you can provide the output from the following to comfirm/deny what I think is the likely problem and solution:

     

    sudo gpt -r -vv show disk0

    sudo fdisk /dev/disk0

     

    These are read only commands, no modification to the disk is made.

     

  • by Csound1,

    Csound1 Csound1 Jul 24, 2013 8:23 AM in response to cranberry667
    Level 9 (51,432 points)
    Desktops
    Jul 24, 2013 8:23 AM in response to cranberry667

    Then post in a thread where Chris is active, that way he will get a notification. Expecting him to search for unknown posts that may concern him is not sensible.

  • by cranberry667,

    cranberry667 cranberry667 Jul 24, 2013 8:42 AM in response to Csound1
    Level 1 (0 points)
    Jul 24, 2013 8:42 AM in response to Csound1

    The last post he made in the main thread:

     

     

    Christopher Murphy:

     

    OK you shouldn't "do the steps" that are meant for someone else's problem. Everyone has slightly different issues that are all related, but often take slightly different steps to fix the problem or you'll make it worse. So I suggest you start a new thread and briefly explain your setup, exactly what you've done, and include the results from:

    sudo fdisk /dev/disk0

    sudo gpt -r -v show disk0

     

    Then post the URL for the new thread here.

     

     

     

    I was trying to do the sensible thing...

  • by Csound1,

    Csound1 Csound1 Jul 24, 2013 8:45 AM in response to cranberry667
    Level 9 (51,432 points)
    Desktops
    Jul 24, 2013 8:45 AM in response to cranberry667

    By 'here' Chris means in the same thread.

  • by cranberry667,

    cranberry667 cranberry667 Jul 24, 2013 8:55 AM in response to Csound1
    Level 1 (0 points)
    Jul 24, 2013 8:55 AM in response to Csound1

    Yes by 'here' he means post the url of the new thread containing the information he asked for, in the same thread(main thread). Have i missed something here? It seems pretty easy to understand from the quote I just gave you.

     

    I mean i didn't even have to go back one page in the main thread to understand what he wanted people to do.

     

    A page back:

     

     

    Christopher Murphy:

     

    I suggest starting a new thread and posting the relevant information there, and then post the URL in this thread so I get a notification. This thread is too unweildy to keep track of multiple people's issues. Thanks.

    I did the sensible thing. I just didn't make myself clear in the OP.

  • by Csound1,

    Csound1 Csound1 Jul 24, 2013 8:59 AM in response to cranberry667
    Level 9 (51,432 points)
    Desktops
    Jul 24, 2013 8:59 AM in response to cranberry667

    cranberry667 wrote:

     

    Yes by 'here' he means post the url of the new thread containing the information he asked for, in the same thread(main thread). Have i missed something here? It seems pretty easy to understand from the quote I just gave you.

     

    I mean i didn't even have to go back one page in the main thread to understand what he wanted people to do.

     

    A page back:

     

     

    Christopher Murphy:

     

    I suggest starting a new thread and posting the relevant information there, and then post the URL in this thread so I get a notification. This thread is too unweildy to keep track of multiple people's issues. Thanks.

    I did the sensible thing. I just didn't make myself clear in the OP.

    You have yet to tell us whether or not you posted the link in the original thread, did you?

  • by cranberry667,

    cranberry667 cranberry667 Jul 24, 2013 9:06 AM in response to Csound1
    Level 1 (0 points)
    Jul 24, 2013 9:06 AM in response to Csound1

    Yes I posted it 7 hours ago in the thread I linked in the OP

  • by Csound1,Helpful

    Csound1 Csound1 Jul 24, 2013 9:08 AM in response to cranberry667
    Level 9 (51,432 points)
    Desktops
    Jul 24, 2013 9:08 AM in response to cranberry667

    Then you are now waiting for Chris.

  • by cranberry667,

    cranberry667 cranberry667 Jul 24, 2013 9:12 AM in response to Csound1
    Level 1 (0 points)
    Jul 24, 2013 9:12 AM in response to Csound1

    hahaha thanks for telling me what I knew before making this thread.

Page 1 of 3 last Next