Mini won't reboot after last patch install.

I was installing the patch yesterday and during the patch install it said there was a problem with the install. After that the computer was running slow so I decided to reboot. Now all I can get is the circle of sticks with the apple logo but I never get beyond that.
I can eject a CD by holding the mouse button.
I press C while the install disc is in but it never re-installs
All my data is on an external USB drive so I don't mind reinstalling but I'd like to be able to do so without paying someone at the apple store to do it.
Also tried holding the option key.. nothing
tried the open firmware combination.. nothing
What else can I do?

Hi Fastfwd, and a warm welcome to the forums!
Tough without the Install disc working, but some things to try...
Mini PMU reset...
http://support.apple.com/kb/HT2183
Does it boot to Single User Mode, CMD+s keys at bootup, if so try...
/sbin/fsck -fy
Repeat until it shows no errors fixed.
(Space between fsck AND -fy important).
Resolve startup issues and perform disk maintenance with Disk Utility and fsck...
http://docs.info.apple.com/article.html?artnum=106214
Tough without the Tiger Disk problems, but try fsck...
To use fsck, you must run it from the command line. Unlike using your mouse to open an application to do something, you'll need to type a text command at the prompt (#) to tell fsck what to do. The Terminal application (/Applications/Utilities) and single-user mode are two examples of command-line interfaces in which you can type such commands. To use fsck:
1. Start up your computer in single-user mode to reach the command line. Hold CMD+s keys down at bootup. Note: If necessary, perform a forced restart as described in the Emergency Troubleshooting Handbook that came with your computer. On desktop computers, you can do this by pressing the reset/interrupt button (if there is one) or holding down the power button for several seconds. On portable computers, simultaneously press the Command-Control-power keys. If your portable computer doesn't restart with this method, you may need to reset the Power Manager.
2. At the command-line prompt, type /sbin/fsck -fy
(SPACE between fsck AND -fy important)
3. Press Return. fsck will go through five "phases" and then return information about your disk's use and fragmentation. Once it finishes, it'll display this message if no issue is found: 
The volume (nameofvolume) appears to be OK  If fsck found issues and has altered, repaired, or fixed anything, it will display this message: *** FILE SYSTEM WAS MODIFIED ***   Important: If this message appears, repeat the fsck command you typed in step 2 until fsck tells you that your volume appears to be OK (first-pass repairs may uncover additional issues, so this is a normal thing to do).
4. When fsck reports that your volume is OK, type reboot at the prompt and then press Return.
http://docs.info.apple.com/article.html?artnum=106214
Then Safe Boot, (holding Shift key down at bootup), & use Disk Utility from there to Repair Permissions, reboot once more.
Then Safe Boot from the HD, (holding Shift key down at bootup), run Disk Utility in Applications>Utilities, then highlight your drive, click on Repair Permissions, reboot when it completes.
Do you have another 10.4.x Mac around?
How to use FireWire target disk mode...
http://docs.info.apple.com/article.html?artnum=58583

Similar Messages

Mac Mini won't start after installing OS X 10.6.3

My Mac Mini won't start after installing Mac OS X Snow Leopard 10.6.3. When I turn it on, the Apple logo appears and the initialization line starts to fill, but it suddenly stops. It does that again and stops at the same point, but this time it shuts down. What should I do?

If you are coming from 10.5.8, hopefully you backed up your important data first. Your mini will need at minimum, 1 GB of RAM to install Snow Leopard and at least 5 GB of storage remaining on your boot drive.
I treat 10.6.3 as a fresh, full install over a 10.5.8 system. That means I choose Disk Utility from the Installer's menu and repartition the boot drive as a single partition, Mac OS X Extended (Journaled) format, and use the GUID partition scheme from the options button. At this point, while still in Disk Utility, I would verify the drive under First Aid.
Then I turn the installer loose, and reboot into a working 10.6.3 system, ready for the software updates that take the machine to 10.6.8.
So, following the above guidelines, reinstall 10.6.3.

Unknown Error (-53) after last "Patch Tuesday"

I'm unable to sync my iPod Touch since the day after last "Patch Tuesday". I get an alert referencing an "unknown error (-53)" every time I try to sync. I've tried the usual windows steps; uninstall and reinstall, reboot multiple times, disable all anti-virus, anti-spam, firewall, curse, pray, etc. I've done a search here and Googled but haven't seen any discussions.
Is anybody else having this problem or is it just another windows anomaly requiring a format and clean install?

thokra wrote:
Experience the same problem after installing the latest update and cant do anything now.
Have someone with a PC running Windows XP download the shuffle Reset Utility and apply it to your shuffle.

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.

My iTunes won't open after last update.

My iTunes won't open after last update. Can anybody help me?

I had similar problem this time and last time when I upgrade/update iTune, and subsequently solved the problem through the help of this person. You may give it a try and see if this works for you. It works for me now and then. Good luck.
https://discussions.apple.com/thread/3800524
Oliver

MacBook Pro won't boot after trying to install 10.7.3 update. Start up stalls at Apple logo and spinning gear.

MacBook Pro won't boot after trying to install 10.7.3 update. Start up stalls at Apple logo and spinning gear. Computer won't even start in safe mode.

My daughter's MacBook Pro was doing exactly the same thing. I don't know if it had anything to do with the latest update. She called me about a week ago saying that her MacBook began running slower by the day . She then called me Friday and told me that it wouldn't get past the gray screen and the gear just kept on spinning. I did everything I could over the phone including Safe mode which it wouldn't go into and thought maybe it was the hard drive. She took it to the Apple store. Originally, they also thought it was the hard drive. It ended up being a corrupted operating system (Lion). Apple genius simply re-installed Lion and she's back up and running. Good thing she backed up right before it crapped out. She'll be restoring everything tonight. Don't know if re-installing Lion will help your situation, but it did the trick for my daughter.

4s won't reboot after ios7 update. I have restored 4 times. Every time it gets stuck on Apple icon with update bar at 10%

4s won't reboot after ios7 update. I have restored 4 times. Every time it gets stuck on Apple icon with update bar at 10%
HELP!

That's one of the weird things.. it recognizes it maybe 10% of the time. And usually, only after I do the two-button reset. Problem is.. since it won't charge above 2%, anytime I try to do a restore or anything like that using iTunes, my device shuts off and I lose whatever progress I'd made.
So, an update... after reading through a bunch of similar complaints (there are literally 1000's of them so there's NO WAY this isn't somehow ios7 related, thanks a lot APPLE ) I decided to try a restore in recovery mode. After 3 hours and several disconnections... I ended up having to just set it up as a new iPad, as the restore did nothing. Weirdly though... as I was doing the restore in recovery mode.. I noticed I'd gotten up to a 10% charge.. higher than it's been since September, so after setting it up as a new device, I turned it off and plugged it in using the wall charger. 2 hours later and I was up to 38%. Still not great, as my iPad, before ios7 could've fully charged twice in the amount of time it took for me to now get 28% more of a charge. And that's with a fully cleaned out device.. so that really ***** and I'm now more confused than ever.
But I'm gonna leave it overnight charging and see what I come up with tomorrow. Sadly, when I paid $600 for it in February, I never expected to have to play "wait and see" with it...

Mac Mini Won't Sleep after installing 10.4.6

My Mac Mini wakes itself up after just 1 minute of putting it to sleep mode. I've tried restarting my mini, and tried quitting all apps and disabling airport and bluetooth- but it still won't sleep! Anyone else experiencing this problem, I didn't have this problem with 10.4.5 and I've installed no other software since then...

This is for a Mac that won't sleep.
First, read things in Apple doc.#25801 on sleep settings.
USB devices and hubs often cause Macs to not sleep or wake quickly from sleep (notably HP printers and scanners, HP all in ones, and Cannon scanners). Disconnect all USB except for keyboard and mouse and try. If it sleeps, add one back at a time testing after each one to find the culprit.
If you've set your Mac to recieve faxes, it may not be able to sleep. It might also have a damaged preferences file.
If you use your Mac for faxing, open System Preferences. click Print & Fax, click the Faxing tab, and uncheck the Recieve Faxes On This Computer box.
If that does'nt work or you've never faxed on your Mac, go to Finder/Hard Drive /Library/Preferences/SystemConfiguration and delete the com.apple.PowerManagement.plist and com..apple.AutoWake.plist files (if your Mac asks, type your admin. password).
If the latter file isn't present in the folder, go to user name(probably your name)/Library/Preferences, delete the com.apple.systemuiserver.plist file, and reboot your Mac.
Hope this helps!
P.S. One member here reported this (Michael Gleason);
"I have had this problem with my IMac G5. It is surprisingly irritating. LaCie's Silverkeeper backup software was the cause. By default it gave itself permission to wake up the computer to check if a backup was needed. Do you have this or a similar program installed which has scheduled activities including wake-up permissions as an option?"
Dave Hamilton provided this link, xlr8yourmac.com, to a member, which addresses failure of deep sleep with some users that updated and added new FireWire and USB cards.
tomhorvat adds this; After few days of messing around I found out that I had desktop background (wallpaper) set to change every 1 minute.
After unchecking "Change picture..." in system preferences (under Desktop/Screen saver), my powerbook went to sleep all by itself.
Cheers!
DALE

Force software reboots after Software Updates install, and do a WUA rescan upon reboot and install any remaining patches?

Running SCCM 2007 SP2 R3 and having two big issues with SUP that impacted us severely with the February patches. An RDP patch from November broke our 2-factor authentication (2FA) method, so we stopped deployment until Microsoft could fix the
patch. Rather than fixing the patch...they made a patch for the patch.
We divided our servers up into multiple Day/Time maintenance windows, like SUN, MON, TUE, and from 0200 to 0600 AM, and we run deployments weekly as needed.
There doesn't seem to be a way in SUP to "let SCCM control reboot" and ALWAYS reboot (whether the patches request it or not), and, as a result, we seem to have an awful lot of servers that are stuck at "reboot pending" after patch installation,
and have actually taken to using a third-party program to reboot the servers.
There also doesn't seem to be a way to force SCCM SUP to rescan the computer after the patch is applied until after a day...or, for servers, a week (from Mon to Mon, for example).
What happened this time around was that the first patch installed and broke 2FA, the second patch is not recognized as being needed until after a reboot and rescan--since that did not occur, it took up to a week to get the second patch installed (IF the
server ever was rebooted), which...was unacceptable.
Soooo...how can I:
1. ALWAYS force SCCM to reboot after patching (60-min countdown if user logged-on), just like we do with our normal deployment advertisement, package, program.
2. Force a WUA scan after this reboot, so, if remaining patches from this patch group are needed, they get detected and installed, and hopefully this will all work within the 4-hour window (we might be able to extend it earlier,
but, not past 0600).
Thanks!

Thanks, Don. OK, if there is a "reboot required" returned at the end of the patch deployment...shouldn't the computer then reboot? We see a large number of computers with "reboot required" that never reboot. Is there something wrong in
the setup to stop a reboot from occurring?
Thanks.
It looks like you've continued the conversation with Jason and it's taken an interesting turn ;)
But, in the case where a reboot_required is the returned resultcode, CCM will look to your MW and deployment settings, and the context of the installation event (enforcement etc), to determine if the reboot request should be honoured or refused.
You should be able to see all the to-and-fro of this logic within the client logfiles, as it's occurring (or after the event).
If you do some spelunking into the logfiles, don't forget to look at windowsupdate.log (the WUAgent logfile), as that can, with the CCM logfiles, paint a more complete picture of the "flow of things".
This does all assume that the client machine is in a healthy and predictable state to begin with.
If there is already some other pending_reboot hiding in the background, or, WUAgent is running with it's own configuration (potentially fighting with CCM), or, it's Win8 with the "Automatic Maintenance" scheduled task, you can get some unexpected behaviour
(but usually that is unexpected reboot, rather than unexpected no-reboot)
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

Older mac mini won't reboot from Install DVD?

I've passed on my 2006 era mac mini to my daughter. We can't seem to get to a factory settings because it won't reboot from the install DVD. It keeps cycling through to the normal reboot.

Could be damaged disks.
BestBuy sells disk repair kits.
But for about the same price as disk repair kit, you could call 1-800-676-2775 and give them the unit serial number and pay shipping/handling fee for replacement.
Assuming it is bad disks.

Macbook pro won't reboot after installing lion

After installing Lion on a 2007 MacBook pro, it won't reboot. Just gets to the gray screen with the spinning wheel. Have tried re-installing and disk repair to no avail. Anyone else figured out how to fix?

alan81 wrote:
After installing Lion on a 2007 MacBook pro, it won't reboot. Just gets to the gray screen with the spinning wheel. Have tried re-installing and disk repair to no avail. Anyone else figured out how to fix?
Lion only runs on Intel based systems which have to be core2duo. with a minimum of 2GB RAM.
If these is given on your system, in most cases it comes from running old PPC-Applications which are not longer supported since Lion.
Try to start your MB in "Safe Mode" by holding option key (alt) imediately after first chime and disable / delete this applications.
Lupunus

Mac Mini won't boot after update

I have a Mac Mini that won't boot after the most recent software update. Since the Mini has only a bluetooth keyboard and mouse, a number of the usual options (hold down shift, etc.) won't work. I've tried a reset, also no luck. At the moment, I can't locate my Tiger install CD either.
When holding the power button on during boot, I get a series of flashes from the status light on the front (a set of very rapid flashes, followed by a slower set, followed by a slow set) but no startup chime, or fan, or video. My display and power source are both known-good (work fine with my Powerbook)
Any suggestions, other than buying a hardwired keyboard/mouse?

Welcome to Apple Discussions!
The 'newer version of OS X" error occurs because the installer on the DVD you have booted to has by default been set to update the version of MacOS on the hard drive, which of course it can't do because the version of MacOS it is installing is newer. The only way to install in this situation is to select a different option. However, that isn't what you want to do at this point, because as it says, you'll loose your data if you do an 'erase and install'.
Instead, you should see menus at the top of the screen when it's booted to that install disk. Click the Utilities menu, select Disk Utility, and then click the top entry for the internal hard drive on the left. Once done, click on the 'Repair Disk' button (not Repair Permissions). This will test the drive to make sure it's OK. If it reports errors, and then reports 'error or exit' with the drive not repaired, you will either need a 3rd party application such as Alsoft's Disk Warrior, or to perform an erase and install (which of course you don't want to do at this point because your data is not backed up).
If the Repair Disk process completes with no errors, next select Repair Permissions, and let that process complete, then reboot the system as normal to see if you can now access the drive.

Reboot after applying patch 112915-05 realy necessary?

Hi,
I have a short question about the patch 112915-05 which i have to apply to our sol9 servers. The patchdescription tells me to reboot the server after the installation.
But now i woundering about the patch content. Only the file /usr/sbin/snoop will be replaced with this patch. I have downloaded the patch and had a short look into it, there is realy only the snoop binary in the patch. Is this a wrong information in the patch description or is the reboot realy necessary?
Thanks for Help
[http://sunsolve.sun.com/search/document.do?assetkey=112915|http://sunsolve.sun.com/search/document.do?assetkey=112915]
Files Included in this Patch:
/usr/sbin/snoop
Special Install Instructions:
NOTE 1: Perform patch installation in single user mode.
Reboot the system after patch installation.

For patch 119810-05 ( http://sunsolve.sun.com/search/document.do?assetkey=1-21-119810-05-1)
Installation Requirements:NAThis means no reboot required and you don't even have to be in single-user mode to do the install of this patch.
Contrast this with a patch where you MUST be in single-user and MUST reboot after patch installed:
For patch 127111-10 ( http://sunsolve.sun.com/search/document.do?assetkey=1-21-127111-10-1 )
Installation Requirements:Reboot immediately after installing this patch on an active boot environment to bring the system to a consistent state. An alternative may be specified in the Special Install instructions.
Use Single User Mode (run level S) when installing this patch on an active boot environment. An alternative may be specified in the Special Install Instructions..
Special Install Instructions: -----------------------------
NOTE 1: Before installing this patch, please install the latest patch
utilities patches for your OS. This list of patches is defined
at - http://sunsolve.sun.com
Please use the pull down list which appears after the text:
"Latest Patch Update: To ensure the correct functioning of the
patching utilities on your system, stay up to date on the
following patches"
README -- Last modified date: Friday, March 7, 2008

IPad mini retina constantly reboots after iOS 8.1 update - help!

Hello,
I've downloaded on iPad mini Retina 16 GB iOS 8.1 update and installed it directly from the device (so no iTunes involvement). After it got installed with black apple on white screen (process seemed to be finished) - it started rebooting, but instead of starting up it shows shortly (for just a second) blue screen, after goes black and then reboots again - and all this in constant flux: white screen with black apple - blue flash - black screen - white screen with apple. Connecting to iTunes doesn't make anything - it doesn't recognise the device while in state of reboot.
What can I do?
Help!

Hey there,
Got exactly the same problem here. Can't even reset/ shut off the device, so it keeps on flashing with the blue screen.
Ipad Air 1

Help! My Mac mini won't reboot

Hi. I posted yesterday (in the Safari forum) concerning a problem I was having with Safari 3.0.4 after updating to 10.4.11. Basically, it wouldn't run. Anyway, I did a bunch of searches on the Web (including this forum) to try to figure out what to do. One piece of advice was to move System/Library/Frameworks/ApplicationServices.frameworkapplicationservices.fram ework to the desktop.
Well, I did that, and things started acting weird. I tried to copy it back, but the process just seemed to hang. So, I did what I thought was obvious but was apparently a bad idea: I rebooted. Guess what--now my Mac won't reboot. I just get a perpetual hourglass.
I tried doing repairs with Disk Utility, but that didn't fix the problem. I also did a superfluous Hardware Check from the same OS disk, and that turned out normal.
So, what's the solution? A visit to my friendly Apple dealer for some service? Or am I just permanently hosed with no recourse? Please let me know what I can do. Thanks!

Sadly Apple stores are rarely set up for the purpose of completing backups and securing data, so that's not something you can rely on them to do. Some Apple approved service providers are better equipped for doing this, but in the end, it's not a good (or comfortable) proposition to trust your data to anyone else, and the more important that data, the less good, (or comfortable) it is if you have to.
The risk of data loss is relatively small in this situation - particularly if you ran 'repair disk' from disk utility and it reported no errors. That generally would indicate the drive is healthy and there are no indications of damaged data or file structures. Still there is always a risk!
In your situation, if I were faced with the knowledge that I was going to be buying an external drive for future backups, I'd be inclined to buy it now (selecting a firewire-connected hard drive of at least the same, if not much larger capacity than the internal), and then run Disk Utility again, this time (carefully) selecting the external drive, partitioning it under the Apple scheme, then formatting it (MacOS Extended (journaled) and then installing MacOS on it from your 10.3 installer. After that, I'd boot to it by holding down the option key during startup, then selecting the external drive from the list that (after a couple of minutes) should appear. Then the internal drive will be mounted on the desktop under the external which has booted the system. That will give you to option to copy your iPhoto and iTunes libraries to the external drive, and thus secure your data.
Once that's done, you can reboot to the install disk and basically even erase and install, because your data is safe on the external drive!
After the internal is set up again, and fully updated, it then becomes a simple matter of moving your data back to it, and then erasing the external once more, and setting up your backups with SuperDuper! or CCC.
It might sound like a bit of messing about, but that would keep your data safe in your own hands!

Mini won't reboot after last patch install.

Similar Messages

Maybe you are looking for