Mac Mini won't boot, disk stuck

Hello, for a description of the issue please see the next posting. Thanks for any help!!!

My problem is solved; see http://discussions.apple.com/thread.jspa?threadID=1454230&tstart=0 for the solution. Essentially: you MUST have a WIRED USB connection, not even a PS2 plug with a USB adapter will do, if you need to modify the booting procedure, e.g. boot to the Installation Disk or to Save Mode.
Cheers, and thanks for the help.
Veit

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 - 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 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 or Internet Restore - Hard Drive Boots on Macbook

    Late 2012 Mac Mini. I cloned my 10.10.2 installation of Yosemite over from my Macbook pro 6,2 to a 1TB Samsung 840 SSD. It booted with no issues besides the keychain being lost and all passwords having to be re-entered.
    After a week of going perfectly, it stops recognizing the USB keyboard after I unplugged it and plugged it back in. So I rebooted and get the dreaded stop sign after the boot failed. Oops. I enabled trim before I cloned, but forgot to check if it was working in the cloned drive (seems it was in the end). Since there was no recovery partition, I booted into Internet Recovery, but that hung using both WPA and WPA2 router logins. It obviously was syncing with router, but I got error -2002f in every configuration I tried. It also didn't seem to recognize an ethernet connection. Weird stuff.
    I remembered I had an issue with a previous Mac Mini of the same model and the permissions after a clone. I repaired permissions and that was that. This is different because it wouldn't boot into Safe Mode. Resetting the PRAM did bring back an audible chime at least.
    I pulled the SSD out of the Mac Mini and alt booted in from my Macbook 6,2. No issues (except the keychain thing again( and it loaded quickly. Nothing seemed to be wrong.
    Then I put it back in the Mac Mini and tested it with known working RAM. Still the same thing. So now I am going to sleep on it and try to figure it out. It is unlikely to be a hardware failure as the Mac Mini was made in May 2014 and I bought factory refurbished.  It seems to be an issue relating to the SSD as it boots other drives.
    Any ideas?

    Fix The Bugs Please wrote:
    It is unlikely to be a hardware failure as the Mac Mini was made in May 2014 and I bought factory refurbished.  It seems to be an issue relating to the SSD as it boots other drives.
    Any ideas?
    Is this SSD an additional drive added to your Mac Mini or did you replace the HDD with it? If it's an additional drive and since it's a Samsung, depending where you purchased your drive doubler kit (iFixit or OWC) you can try swapping the drives in the bays. I know for a fact that Samsung SSDs do not work right with the iFixit drive doubler kit's SATA cable. But it does work correctly with the Apple supplied SATA cable. If it's the OWC SATA cable, I know for a fact those are much more reliable with Samsung, OWC, Intel, Crucial SSDs. Another thing, I would NOT enable TRIM (my opinion) using a 3rd party trim enabler if you're running Yosemite. There are issues with trim enablers and Yosemite. Just let the built-in Garbage Collection take care of things.
    If it's not an additional drive that was added, does your Mac Mini boot and work fine with the stock drive that it came with? Even though it's a 2012 model, if you purchased it refurbished from Apple in May 2014, you're still under warranty (same 1yr as new Macs) and if it's having same or similar issues working with the stock drive, you can take it to a local Apple Store for warranty repair. You would need to have only the stock drive installed (no SSD) before you setup an appointment.

  • 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 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

  • Mac Mini won't boot - can't select start-up disk!

    Hi all -
    mid way through an important project, my Mac mini 2.1 hung and I restarted using the power button. When it came back on I just get the grey screen with flashing folder & ?.
    I have tried booting from the install cd & it does this successfully, but when I access disk utility, all the options for repair etc. are greyed out. I can't even reinstall OSX because the startup disk isn't available as an option to write to.
    I've tried running the hardware test by booting and holding d. This came back with no errors.
    I've tried zapping the PRAM and done the SMC thing. No joy.
    Any ideas on how to make the mini see the startup disk?
    Thankyou so much!

    Cheers. Am trying it now, have partitioned a fresh drive and specified it to be bootable thru GUID, then I selected the Leopard dvd as the source and the partition as the destination in the RESTORE function of Disk Utility. Is this correct?
    Will look into Diskwarrior too. Many thanks.

  • Mac mini won't boot into target disk mode

    Hi
    I just bought a Mac mini on eBay. I'm not sure of the spec but I think its a G4.
    When it arrived I plugged it in and switched on to find the question mark folder appear.
    I put in a 10.5 disk but it would not boot from it. [this was a disk I got with another s/h machine though so may not be bootable]
    As I could not install from the disk I figured my best bet would be to target disk in and install osx from a powerbook I have here.
    However I can't get target disk to work.
    The keyboard is definitely working as it allows me to boot into OF and zap the PRAM
    I've also tried pressing what I believe to be the SMU button just behind the connector board to the HD and DVD drive but no luck.
    Anybody got any ideas as to whats going on?
    Cheers

    Ok, I can probably get a copy of OSX
    The problem is I think the DVD drive is faulty as it wouldn't give me my disk back I tried "eject cd" in OF but it didn't work and I had to open it up with a screw driver and take it out.
    If the disk is corrupted is there a way to erase it without putting it in another machine. ie can it be done from OF?
    Thanks for your help btw

  • Mac mini won't boot - keyboard shortcuts don't work

    Older Intel Mac Mini that I use as an entertainment / movie center. Leopard.
    I did a software update recently, but somehow botched it and interrupted the process.
    Ever since then, it won't start up correctly. It chimes, disk powers up, but then it gets stuck on the screen with the apple and rotating propeller. Can go on for hours if you let it.
    Took it to a dealer, who said it started up fine from another system an I should try starting it in target disk mode an reinstall the OS.
    Bought a USB keyboard specifically so I could press the T and tried it.
    It seems that none of the keyboard shortcuts work. I tried target disk mode (T), starting from a system disk (C), tried having it give me a choice of bootable volumes (Option) - nothing. It would appear the Mini doesn't recognize my brand new Apple USB keyboard.
    Tried the keyboard with my MacBook and there it works fine.
    Any ideas?

    OK, just found the answer while browsing the "more like this" answers that appeared after I posted my question.
    I wasn't aware that the new Apple Aluminium Keyboard doesn't play nice with the Mini and that the Mini doesn't recognize this particular keyboard in time for the boot sequence.
    Thank you for these helpful discussions:
    https://discussions.apple.com/message/9306774#9306774
    https://discussions.apple.com/message/9084810?messageID=9084810
    https://discussions.apple.com/thread/1477855?threadID=1477855&tstart=0
    Using the remote (press the menu key during boot-up) worked fine and I could choose to boot from a system disk.
    Spending $60 for a new keyboard that won't do what I bought it for is, however, another story. Grr.

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

Maybe you are looking for