Mac mini won't boot up on OSX even after all keyboard commands and shortcuts.

Hi. I installed windows 7 using bootcamp on my mac. Windows installed successfully but I had to reformat its designated partition to NTFS (20GB which I allocated). But now I can't seem to run OSX even after doing Cmd.   R, Option, C, etc. still Windows boot everytime. Anyone know how I can fix this problem before I submit the computer for professional service? Thanks.

Usually means you may have also formatted your OS X partition or RDB with the Windows formatter. You might try this:
Repair the Hard Drive and Permissions
Boot from your Snow Leopard Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list.  In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive.  If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer.
If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
If the above doesn't help any then you are looking at having to reformat your OS X partition.

Similar Messages

  • Mac mini won't boot anymore

    My Mac mini won't boot anymore. It's been running fine for months.
    It's running Leopard Server 10.5.2 Build 9C31
    It starts to boot, I get the first spinning gear with the gray screen, then the blue desktop blinks, then a second spinning gear on a gray screen and it appears to hang (the gear stops spinning).
    I booted off the install DVD, ran disk utility, repaired the HD, repaired the permissions: the behavior is the same.
    Safe mode doesn't work (same hang as above).
    Single user mode does work.
    I can connect to it via Server Admin while it appears hung.
    The last few lines of the system log are:
    May 15 18:38:58 server emond[67]: SetUpLogs: uid = 0 gid = 0
    May 15 18:38:58 server emond[67]: SetUpLogs: opening /Library/Logs/EventMonitor/EventMonitor.error.log
    May 15 18:38:59 server kextd[23]: writing kernel link data to /var/run/mach.sym
    May 15 18:39:09 server KernelEventAgent[59]: tid 00000000 received unknown event (12)
    May 15 18:39:20 server kernel[0]: display: Not usable
    May 15 18:39:20 server com.apple.KerberosAutoConfig[126]: Kerberos configuration is up to date
    May 15 18:39:20 server com.apple.ATSServer[125]: FODBCheck: New annex file created
    May 15 18:39:21 server ARDAgent [130]: ******ARDAgent Launched******
    May 15 18:39:21 server com.apple.KerberosAutoConfig[132]: Kerberos configuration is up to date
    May 15 18:39:22 server ARDAgent [130]: call logout from LoginLogoutProxyCallBackFunction
    May 15 18:39:22 server com.apple.launchd[1] (com.apple.RemoteDesktop.agent): Throttling respawn: Will start in 9 seconds
    May 15 18:39:24 server loginwindow[58]: Login Window Started Security Agent
    May 15 18:39:29 server servermgrd[53]: servermgr_calendar: created default calendar virtual host
    May 15 18:39:31 server ARDAgent [146]: ******ARDAgent Launched******
    May 15 18:39:32 server ARDAgent [146]: ******ARDAgent Ready******
    May 15 18:39:33 server mdworker[109]: (Error) SyncInfo: Boot-cache avoidance timed out!
    May 15 18:39:54 server Python[47]: CGImageSourceCreateWithData data parameter is nil
    May 15 18:39:54 server com.apple.wikid[47]: Thu May 15 18:39:54 server.jeff.carpenter.name Python[47] <Error>: CGImageSourceCreateWithData data parameter is nil\n
    May 15 18:39:56 server kernel[0]: AppleYukon2 - bad packet received. length: 1440, packet status bits: MII error
    May 15 18:39:56 server kernel[0]: AppleYukon2: 00000000,00000001 sk98osx sky2 - - sk98osx_sky2::replaceOrCopyPacket tried N times
    May 15 18:49:54 server kernel[0]: serialnumberd 194 FSWRITEDATA SBF /dev/dtracehelper 13 (seatbelt)
    May 15 18:49:54 server kernel[0]: serialnumberd 194 FSREADDATA SBF /dev/autofs_nowait 13 (seatbelt)
    May 15 18:49:54 server kernel[0]: serialnumberd 194 FSREADDATA SBF /usr/sbin 13 (seatbelt)
    May 15 18:55:12 server kernel[0]: AppleYukon2 - bad packet received. length: 23, packet status bits: MII error
    Any ideas?

    Yes, it's been running Server since I purchased it.
    I doubt the serial number is in use elsewhere: I purchased the 10-user version at a retail store in a sealed package and I've only installed it once.

  • Mac Mini won't boot up.

    Mac Mini won't boot up! Just getting blank white screen, any ideas why? No apple, just a blank screen. It worked fine last night.

    Have you tried booting into the Recovery HD by pressing/holding COMMAND+R at system start or the Option/Alt key and choosing Recovery HD to boot into?
    If you can get into the Recovery HD, open Disk Utilities and Verify Disk. Repair if necessary.

  • Mac Mini won't boot after failed XP installation

    Recently upgrade HD to 320GB 7200 rpm and 3GB ram. Running 10.5.8 fine.
    I tried to install Windows XP through Boot Camp, but wasn't successful, I terminated the installation. Then Mac Mini won't boot up. When powered on, you heard the chime, then grey screen showed and stayed. Tried starting with "C" (boot from CD), "OPT" (boot option), "T" (target), and reset PRAM. None of them worked.
    What should I try next?
    Thanks
    Message was edited by: Yijian Cao

    If you install XP on Bootcamp, your startup disc will be changed to XP Windows partitioned you did. To restore your startup disc back to Mac OS, make sure your Mac is turned off. 1. Plug the power back and press the power button ON. When you hear the power On sound, press and hold the ALT key on your keyboard until you see the hardrives. 2. Select the HD that says MAc OS, then your mac will boot back to Mac OS.
    Let me know if you have more problems, maybe I can help.
    Abel

  • Mac mini won't boot after RAM upgrade.

    Tried installing new RAM in my Mac Mini, 512MB stock to 2GB of Crucial. Followed the directions to a T, grounded myself the whole time.
    Things I've tried so far:
    1. Resetting the PRAM, no luck.
    2. Holding option at start-up, shows no icon.
    3. Holding shift, no luck.
    4. Holding X, nothing.
    How do I get it to accept a CD if it won't boot?

    Welcome to Apple Discussions!
    You clearly have a problem, but you don't describe exactly what that is other than that your mini won't boot after the upgrade. What happens when it starts up? Does it attempt to start and hang up on the grey or blue screens, or does it start beeping at you almost immediately after you try and start it up, and also flash the power light?
    If the former, then you may have dislodged a connector while working inside the system, in which case opening it up and checking that everything is firmly connected would be the first thing to do. If the latter, then the beeping/light flashing is the system telling you it has failed the power-on self test and the pattern of beeps/lights indicates why. In your case likely the system can't find workable memory. In that instance, opening the system and ensuring that the RAM is firmly and fully seated would be a good step, and if the mini continues to fail, then replacing the new RAM with the original to test that the system will then start.
    It is not likely that anything had damaged your MacOS install in the process of upgrading, thus normally no reason to need to boot to CD as a result of a RAM issue.

  • Mac mini won't boot - hardware test error

    my mac mini isn't booting... stuck on the grey apple screen with spinning circle.
    have ran the hardware test on the OSX DVD and i get the following error
    **ERROR*CODE***ERROR*CODE**
    2STF/8/3: ATA-100 ata-6 - Master
    **ERROR*CODE***ERROR*CODE**
    i assume this means that the HDD is knackered ?

    The variable reports on the hard drive are not entirely unusual with a drive that has problems, but it's not a good sign in general that you are having issues with booting to the install disk. That has potential to reflect a controller error that could be minor in nature and even be as simple as a poor connection on the drive carrier which has both drives mounted to it.
    Try booting to the OS installer again. If you can get past the language selection screen it means OSX (the very basic version on the installer) has loaded, and that's a good sign. There's no reason from that point that the Utilities menu wouldn't pull down as normal and disk utility run from there. If you can get that far, see if the internal drive is visible on the left of the disk utility app, and if so, select it (there may be two entries for it, either will do) then click the repair disk button.

  • Mac Mini Won't Boot after 2008 008 Security Update

    I have 2 mac mini's both identical systems - ran the security update at home - rebooted and noticed the movements of the mouse and the mail application was 1/2 to a second slow/behind - decided to restart - it took 3 restarts and it finally came back and then locked up
    I ran Disk Warrior and version 4.0.1 could not fix the problem - version 3.0.3 said it could and replaced the directory - but upon restart it would not boot - I became mesmerized by the spinning dial
    I will not run the update at work and had to substitute my titanium at home in the meantime
    ugly...

    Hi thecincykid, and a warm welcome to the forums!
    If you have another Mac around, try FW Target Mode, which will turn your iMac into an External Firewire Drive...
    http://docs.info.apple.com/article.html?artnum=58583
    To either reapply the Security update, or the big Combo update...
    The combo update for PowerPC-based Macs...
    http://www.apple.com/support/downloads/macosx10411comboupdateppc.html
    The combo update for Intel-based Macs...
    http://www.apple.com/support/downloads/macosx10411comboupdateintel.html
    Repair Permissions before & after re-install, then reboot again each time.

  • Mac Mini won't boot after 10.6.6 / Airport update

    I just reinstalled 10.6.3 on a unibody Mac Mini, updated to 10.6.6 - and it booted fine. I ran another software update, and it suggested two more updates - which I believe was an Airport Utility update and a Java update. Now the Mac Mini fails to boot, stopping at the Apple logo.
    The last lines of verbose startup goes like this:
    Airport: Link Down on en1. Reason 8 (Disassociated because station leaving).
    Aut result for: (MAC address) succeded
    AirPort: Link Up on en1
    AirPort: RSN handshake complete on en1
    AppleBCM5701Ethernet: 0 0 setFixedSpeed - logic error, speed any?
    Suggestions?
    H

    I experienced a similar problem today after a recent upgrade to 10.6.6. I ran Tech Tool Pro 5 on the machine, which reported everything as just dandy after about 6 hours of testing, but it still wouldn't boot. Next, I tried booting in Verbose mode, which revealed that my iMac was hanging on:
    AppleBCM5701Ethernet: 0 0 setFixedSpeed - logic error, speed any?
    I used Safe Single User mode (turn on power, then immediately press and hold Shift-Command-S until text starts appearing) to boot to a command line. Single User mode provides instructions on how to mount the file system read/write. I executed the `fsck` command as instructed, and after a few minutes it reported that it had made changes to the file system. At that point, I skipped the `mount` command and went directly to `exit` to continue the boot process, which completed. I turned AirPort back on (I had it turned off), then rebooted normally without any trouble.

  • Mac Mini won't boot to Mac after partitioning for Windows 7

    system: 
    Mac Mini, late 2009
    Intel
    4 gig ram
    500 gig hard drive, brand new
    OSX
    Mtn Lion with Mavericks just installed, runs ok
    problem:
    Adding 90 gig partition for Windows 7, now won't boot to either Mac or Windows
    After a little bit sticky install of Mavericks, I had the thing running fine. I downloaded support sw onto the USB drive as per Bootcamp instructions, and started going through the wizard to install Windows 7.
    First try:  "error" while creating the partition. I ran the Disk Utitliy, Verify Disk, found an error, ran Repair, it fixed the error
    Second try: it started making the partition again, and then apparently just zipped through the partition making real fast (it finished so fast I could hardly catch it), then shut down in an apparent restart (as it's supposed to?), and from then on it won't reboot all the way. I get about 15 seconds of gray screen, the Win 7 disk jerks a little, then screen goes blank and silence. No hd activity. Tried restarting with all the usual key combinations (Command-R, "X" key, Option key, etc, etc). Nothing will bring the Mac login screen up again.
    What gives? It is such b.s. for this stuff to be so flaky. This is all totally current software on the Mac side, running fine for days, and an apparently ok partition created. Fix me, Apple.

    Got it. Thanks for the help.  Isn't there any boot disk thing that I can just stick in there that will jerk the OS sideways and give me the Mac login screen, or did the Bootcamp/partition attack just wreck everything?  I don't see why I have to do an entire scrape of my totally updated and formerly working OSX just to retry a routine Bootcamp partition, which the girl at the Mac Store in Seattle here assured me has worked for them all the time.   It really is a crock. Maybe I shouldn't bother trying to put Windows 7 on there at all if all these latest versions are so flimsy. I wouldn't want to have to do it all again. But it looks like I'll have to at least once. And send Apple the bill for my wasted time. I ain't feelin' the glamour.

  • Mac mini won't wake properly since osx mavericks

    Since I downloaded OSX mavericks, my Mac Mini doesn't wake from sleep. I can see notifications top right of screen and the mouse pointer, so the screen is on and working. Only way to get it going is to hold down the power button to power off and then resatrt. Not very convenient!

    Please read this whole message before doing anything.
    This procedure is a diagnostic test. It’s unlikely to solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.
    The purpose of the test is to determine whether the problem is caused by third-party software that loads automatically at startup or login, by a peripheral device, or by corruption of certain system caches. 
    Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards. Boot in safe mode and log in to the account with the problem. Note: If FileVault is enabled on some models, or if a firmware password is set, or if the boot volume is a software RAID, you can’t do this. Ask for further instructions.
    Safe mode is much slower to boot and run than normal, and some things won’t work at all, including sound output and  Wi-Fi on certain models. The next normal boot may also be somewhat slow.
    The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin. Test while in safe mode. Same problem? After testing, reboot as usual (i.e., not in safe mode) and verify that you still have the problem. Post the results of the test.

  • FileMaker Server problem on Mac Mini Server - Mac Mini won't boot

    I just installed a brand new Mac Mini Server today, and also FileMaker Server 11. A first-timer for both Mac OS X Server and FileMaker Server, I made an error as explained below, and right now I don't know how to get back on track with the system. It won't boot.
    So, how did this happen?
    At first everything was proceeding according to plan. I configured the pre-installed Mac OS X Server on the Mac Mini with users, groups and services. This was tested from clients and this seemed to work just fine. Then I installed and configured FileMaker Server. This was also tested from a client, and the example database that came with FMS was served up just fine.
    The problem arose when I tried to install my existing FileMaker databases. I simply checked to see where in the file system the example database was located, and then copied my old databases to that location (I think it was Library > FileMaker Server > Data > Databases or something close to it - can't check it now...). I had the FileMaker Server Admin Console running, and hit the Refresh button hoping that this would make FileMaker Server find the databases.
    This was my first error. I should have read ahead in the instructions to see that one is supposed to use an Upload Database assistant instead...
    What happened when I hit refresh was that the FileMaker Server Admin Console became completely unresponsive with a spinning ball as cursor. I left it for about an hour hoping it would terminate, but gave up and tried to shut it down. It wouldn't close, so I force quit it from the Finder. Then I tried to shut down FileMaker Server, but I needed to force quit this as well. After this I thought it would be best to reboot the Mac Mini, so I shut it down, but now it won't even boot, it just stays on the screen with the spinning wheel for ever!
    I have tried all the keyboard options while booting, but nothing seems to help. In safe mode, the grey progress bar just grows to about one third, then disappears and leaves the eternally spinning wheel.
    The server version of the Mac Mini doesn't have an optical drive, only two internal hard drives. I tried to reinstall from scratch using the optical drive on another Mac on the network. The startup disk appeared when I tried to boot the Mac Mini holding down the option key, and after about 20 minutes or so of the spinning wheel I could actually access the discs. I started by running Disk Utility to check disk permissions. There were a lot of repairs concerning permissions and groups, especially on "Library". It said "ACL differs on Library", I don't know what this is but this was repaired. I then ran Repair Disk. The volume appeared to be OK.
    When I tried to reinstall Mac OS X Server however, this failed with the message
    "You can't upgrade this version of Mac OS X because a newer version is installed. Mac OS X Server couldn't be installed on this disk." I don't know how this can be, but I may have run software update earlier today.
    What should I try next? Should I erase the primary HD and try to install again? Or should I install the system software on the secondary HD? Or should I just try to reboot as is in the hope that the disk permission repairs did the trick...?
    Any helpful pointers would be greatly appreciated!

    Hello there, I came across your post when browsing the forum for passive advice. I am in the same boat as you and am a first timer for both of these tools. I work for a company who now needs to expand its network and database capabilities. I have been assigned this task and these are the tools i have opted for. I have not yet purchased them and i am pleased to find someone who has my desired setup. Could you please advise on the simplicity of the setup and whether an advanced knowledge is required.
    I want to use it in a mixed operating system environment. Is this possible?
    Regards
    Matthew

  • Mac Mini Won't Boot with VGA Monitor Connected

    I have a new Mac Mini connected to an older VGA monitor using the Apple brand VGA adapter.  The mini is fully up to date and runs perfectly when booted.  However, if I reboot the mini with the VGA monitor connected, it fails to boot.  I just hear the faint chime sound every other second.  There is no output to the monitor and the only way I can get it to boot is to disconnect the monitor and then power cycle the mini.  I can reconnect the monitor just seconds after powering back on and it finishes booting properly.
    Anyone else experience this?  It is very frustrating.  I've also tested with an HDMI connected monitor (without the VGA adapter) and it boots just fine and the display works properly.
    Thanks!

    Okay, I'm back with good news: I have found two remedies for the problem which will hopefully solve it for you as well.
    Given that the issue only occurs when certain monitors are connected, I concluded that the root of it must be a bug in the Mac's firmware related to DDC (Display Data Channel) handling, and that the most promising way to address it should be to just disable the DDC.
    Workaround #1: If your monitor has BNC connectors, use a VGA to BNC cable.
    In this configuration the DDC pins are not connected to the monitor at all. This did indeed fix the problem - my Mac mini booted without a problem with the monitor connected. However, I was not completely satisfied with this solution, because VGA to BNC cables are usually quite heavy and inflexible, and do no go together well with Apple's MDP to VGA adapter and the Mini Displayport/Thunderbolt port which has no locking mechanism.
    Workaround #2: Remove pin 12 of the VGA plug.
    Pin 12 of the VGA plug connects the serial data line of the DDC. Pulling out this pin with a pair of needle nose pliers will effectively disable DDC. I hesitated to do this to my cable (a direct MDP to VGA cable which eliminates the need for a separate adapter dangling from the Mac) and therefore bought a tiny VGA male to female adapter (also called port saver, e.g. Delock 65250) to perform the surgery on that. This has done the trick and my Mac mini has started up fine ever since.
    Of course, without DDC the Mac won't know the model name and capabilities of the attached monitor and thus offer some resolution and frequency settings which the monitor may not support, but that's a small drawback compared to having to pull out the monitor cable everytime you turn on or restart your Mac.

  • Mac Mini won't boot past Apple logo and spinning wheel

    Hello,
    I have a Mac mini (late 2009) running 10.8.2. Today, I tried to log into the computer. It accepted my username and password, but then the screen turned gray instead of logging in. I left it like that for about twenty minutes, then gave up on waiting and Ctrl-Command-Power rebooted it. It then wouldn't reboot: it gets to the Apple logo and spinning loading wheel, but won't go past there.
    So I went into single-user mode and was able to access the HD fine. I ran a filesystems check using the recommended syntax (/sbin/fsck -fy, I think). It said that the volume looked okay, and that it had been modified. I took this as a good sign (that it had been repaired) and typed "reboot" to restart the machine. I held Command-Shift-V to perform a Verbose Safe Boot.
    The computer makes no further progress after the following four lines:
    vboxdrv: fAsync=0 offMin0x809 offMax=0x2bc3
    VBoxDrv: version 3.2.12 r68302; IOCtl version 0x140001; IDC version 0x10000; dev major=34
    VBoxFltDrv: version 3.2.12 r68302
    VBoxAdpDrv: version 3.2.12 r68302
    I'm assuming all the instances of "vbox" are in reference to Oracle's VirtualBox VM. I do have VirtualBox installed, but haven't used it in a while (months), so I don't see why it's suddenly causing a problem.
    To clarify, the computer doesn't "hang" after these lines: I can still type text into the terminal. The entire log is being saved to /dev/console, so I could probably grab it from Single-User Mode if necessary.
    Everything else seems to be working properly: even the wl0 drivers are loaded.
    Does anyone have any suggestions about how to fix this, or at least disable VirtualBox so the computer can start?
    Thanks!
    WC

    Cult of Mac post:
    When the Apple Logo appears your Mac has found a valid system disk, and Mac OS X begins loading.
    Apple Logo with Spinning Gear
    Once the spinning gear appears the BSD kernel (Darwin) has assumed command and begins loading device drivers.  Shortly thereafter it transfers command to the almighty (and controversial) launchd process.  Such are the workings of UNIX.
    What this means for us mortals is that when a Mac stalls at the Apple logo or the logo with a spinning gear, it probably has a corrupt Mac OS X installation.  It may also be having trouble accessing an internal or external hardware component, but this is less-likely.
    Rebooting your Mac in Safe Mode can sometimes get things working well-enough that a second, normal reboot then works normally  Hold down the Shift key at startup to boot in Safe Mode.  DiskWarrior is also worth a shot (this is by far my most used disk utility).  If that doesn’t work, an Archive & Install may be needed.
    Read more at http://www.cultofmac.com/50685/how-to-fix-common-mac-startup-problems-macrx/#CGI mG3jeGEBtysX1.99

  • Mac Mini won't boot with install disk

    tried booting with install disc in and pushing "c" on keyboard and doesn't work. Using a apple wireless keyboard. Also used the keyboard that came with Mac Pro but didn't work nor did a wired logitech.
    any ideas?
    Thanks!

    +What is the source of the idea that the mac aluminum keyboard won't work with the mini?+
    Dozens of reports in this forum over the past year.
    Keep in mind that by "not working" what was meant was that the startup keys wouldn't work. The Alu keyboard otherwise works fine with the Mini.
    It has also been reported that the Alu Keyboard does work for startup keys if it is plugged into a hub with an external power supply.

  • Mac Mini won't Boot after Target Disk Mode

    We just bought a new iMac and used target disk mode via firewire from our older Mac Mini running OSX 10.4 to transfer data.  Now when we go to restart the mini, the grey screen appears with apple logo and it seems to try to boot up but after a long time alway just ends up with a blue screen.  I don't  think I "ejected" the mini properly from the imac after the target disk mode transfer.  Could the mini be stuck in target disk mode?  I've tried to restart in different modes eg. safe mode, pram by holding down keys on start up but doesnt make a difference at all almost as if the keyboard isn't registering (and its a wired keyboard).  Any ideas???
    Thanks

    Try starting up from the Recovery Partition holding the Option (Alt) key and see if you can Repair your Macintosh HD, as per > OS X: About OS X Recovery

Maybe you are looking for