Repairing Boot Camp after creating new partition

It does not matter if it's an SSD. Don't type exit, type reboot, or if that doesn't work for some reason 'shutdown -r now'.

Neither 'reboot' nor 'shutdown' are recognized as commands.

Before I run the

fsck_hfs -r /dev/rdisk0s2

when I get into the single user, it says

'Singleuser boot -- fsck not done

Root device is mounted read-only

If you want modifications to files:

/sbin/fsck -fy

/sbin/mount -uw /

If you wish to boot the system:

exit '

Seems I am running GNU bash version 3.2.48 if that helps

I don't know what to tell you. reboot and shutdown have been around on OS X since day 1, and on BSD well before then. So if you're getting unrecognized command messages with either of those in single user mode, something isn't right with the system.

Well. I for sure do not know.

I tried

Is there any other way to get at the free space?

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'.

@ 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?

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.

@ 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?

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?

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.

Clueless :S

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.

Oh boy.

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?

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.