Currently Being ModeratedMar 14, 2013 5:01 PM (in response to Christopher Murphy)
Well. I for sure do not know.
sudo gpt -r show disk0
gpt show: disk0: Suspicious MBR at sector 0
start size index contents
0 1 MBR
1 1 Pri GPT header
2 32 Pri GPT table
40 409600 1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
409640 269273912 2 GPT part - 48465300-0000-11AA-AA11-00306543ECAC
269945696 1269536 3 GPT part - 48465300-0000-11AA-AA11-00306543ECAC
300509184 189724672 4 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
490234719 32 Sec GPT table
490234751 1 Sec GPT header
Is there any other way to get at the free space?
Currently Being ModeratedMar 14, 2013 5:44 PM (in response to Christopher Murphy)
The odd thing is - I booted into the repair OS X partition and ran the Disk Utility, and asked it to repair the disk. It found 15.13 Gb of free sectors that it said would be left without modifications. But when I look at the disk after a normal boot, these sectors are 'invisible'.
Currently Being ModeratedMar 17, 2013 6:43 AM (in response to Christopher Murphy)
@ Christopher Morphy: I had the exact same problem as the original poster, and followed your instructions carefully (Additional Info: Before following your instructions, I updated the 03/15 Update from the App Store). It seemed to work, as I was able to boot up to Windows 7 again. But when I tried starting my machine ('10 Mac Mini) today, it wouldn't get past the white screen.
After nothing helped, I took the HDD out of my Mac and formatted it via USB case, put it back in and made everything ready for reinstall. But it doesn't get past the white screen yet again!!
I must have messed something up with your instruction, or it interfered with the new update. Did all this tweaking not happen on the HDD, but somewhere else on the hardware? How can I reset everything in order to get my Mini working again?
Currently Being ModeratedMar 17, 2013 10:13 AM (in response to zoidb_1221)
Hang that early in the boot process is probably firmware related. I'd guess that NVRAM is pointing to the old Windows volume for booting, but since you formatted the drive, it's no longer there. However, a reformat doesn't get rid of a small bit of Windows related boot code in the first 440 bytes of the first sector. So to get rid of that:
sudo dd if=/dev/zero of=/dev/diskX bs=440 count=1
X is the number of the drive, found with diskutil list. It's important to get count=1 before you hit return or it'll start zeroing your hard drive without question.
Another option is to zap the PRAM which clears entries in NVRAM, or you can selectively delete entries using the nvram command, man nvram for more info.
Currently Being ModeratedMar 17, 2013 10:50 AM (in response to Christopher Murphy)
@ Christopher Murphy: That sounds like a plan, but how exactly can I use commands, if the computer doesn't boot at all? Are you talking about putting the HDD into my USB case again, or is it also possible to access it via FW800 or Ethernet from another Mac while still in the Mini?
There has to be some way of accessing the Mini's hardware, because otherwise I would never be able to clean the NVRAM, would I?
Currently Being ModeratedMar 17, 2013 11:25 AM (in response to zoidb_1221)
Disconnect all devices other than what you need to boot the computer. That would be one drive, keyboard, mouse, and display. Nothing else. Zap the PRAM. On the 2nd chime hold down the option key. What happens?
Currently Being ModeratedMar 17, 2013 12:37 PM (in response to Christopher Murphy)
It seems i can't zap the NVRAM/PRAM. Tried many times with Bluetooth keyboard as well as with the USB one. Method: Cmd+Alt+P+R
There is an OSX disk in the slot, but I've also tried it earlier the day and it didn't work either.
Currently Being ModeratedMar 17, 2013 1:27 PM (in response to zoidb_1221)
This isn't a Boot Camp problem anymore, I think you need to post in the Mac Mini forum. You need to get the hardware to boot off chosen media. Holding either the eject button on the keyboard or the mouse button on a mouse should eject the disk in the drive. And short of a hardware issue I've never heard of a Mac that doesn't respond to zapping the PRAM.
Currently Being ModeratedMar 17, 2013 1:56 PM (in response to Christopher Murphy)
But as I said in my first post, the whole problem must have sth to do with your advice from page 1. Either I messed sth up, or the whole thing interfered with the March 15th software update (careful, people!). I don't expect you to know exactly what to do now, and this might not be the appropriate place, but:
Your advice tweaked data that is stored in PRAM as well as on the hard drive, right? Physically restoring both should solve all this?
Where is the problem likely to be located? EFI or GPU?
Currently Being ModeratedMar 17, 2013 2:11 PM (in response to zoidb_1221)
But as I said in my first post, the whole problem must have sth to do with your advice from page 1.
That advice wasn't for you. It was for one particular person with a particular problem. It doesn't inherently work for everyone who thinks their problem is exactly same, which often turns out it isn't exactly the same. If you had a disk with five partitions, and Windows was installed on the fifth partition, then that advice would work. But even if that's not true you'd still be able to zap PRAM, you'd still get a boot menu holding down the option key at startup, you'd still be able to boot OS X off an install DVD in the computer when holding either option or c. That you can'd do any of these things implicates your keyboard, or your USB hub, or your computer. Nothing on the disk or NVRAM has even been read at this point, it's as if your keyboard is being ignored.
Your advice tweaked data that is stored in PRAM as well as on the hard drive, right?
No. It changes nothing in NVRAM or the GPT. It only copies info from GPT entry 5, to MBR entry 2. It wouldn't prevent OS X from booting, let alone prevent PRAM from being zapped, let alone prevent booting from DVD.
Physically restoring both should solve all this?
Zapping the PRAM restores the NVRAM, and is a function of the firmware. It wouldn't matter how badly the drive or NVRAM are misconfigured, zapping PRAM should always work.
Where is the problem likely to be located? EFI or GPU?
I can't possibly answer these.
Currently Being ModeratedMar 18, 2013 1:46 AM (in response to Christopher Murphy)
I was just about to post in the Mac Mini forum, when I got the idea.
It wouldn't matter how badly the drive or NVRAM are misconfigured, zapping PRAM should always work.
So if I opened the Mini again and manually put the PRAM battery out and back in again, it should also do it.
Currently Being ModeratedMar 18, 2013 8:39 AM (in response to zoidb_1221)
I'd wonder if the battery just needs to be replaced with a new one if that works though. I know these CMOS batteries were needed at one time to make the memory boot information was stored in non-volatile. But I don't know if that's still true, or if this battery is just for the clock when the computer is powered off. *shrug*
Currently Being ModeratedMar 18, 2013 11:55 AM (in response to Christopher Murphy)
Well, it didn't work. Interestingly, the Mini sounded different when it started this time, but didn't get past the white yet again.
I started a thread in the Mini forum, so if anyone has a clue, I'm thankful for any help I can get.
Currently Being ModeratedMar 19, 2013 9:04 PM (in response to Christopher Murphy)
Christopher: I just wanted to say thanks for helping me out! Your advice saved me a lot of bother!! My remaining issues have nothing to do with Bootcamp or partitioning. Furthermore, they are not urgent - I can figure them out and deal with them when I have time and need to do it, for the moment my Macbook works just fine.
Currently Being ModeratedMar 26, 2013 6:41 AM (in response to Christopher Murphy)
Christopher Murphy wrote:
Yes. Obviously I wouldn't have seen it so if you're trying to get my attention it's worth posting a link in this **** thread with a 1-2 line summary and maybe I'd poke my head in. Too late now, you have a plan to follow.
Could you please have a look at this thread https://discussions.apple.com/thread/4919881 ?
I have the problem that i temporarily detached a disk in my system to install Win 8 (since it doesnt allow to be installed on the second disk in a system) and after reattaching Windows doesnt boot anymore.
I would very much apreciate any suggestions. Think it is somewhat different to the problem in this thread so i followed the suggestion to make a new one. Thanks.
More Like This
- Retrieving data ...
- This solved my question - 10 points
- This helped me - 5 points