Fails to shut-down

when computer is put to sleep it starts up agan, when shut down it restarts.

joanlyons wrote:
Bingo! My terabyte Mac USB drive is causing the problem-- but I need the drive connected. Any way to overcome this problem?
OK, I just conducted a very unscientific experiment, which was to drop a 1TB drive into my USB toaster and see if I could get the computer to sleep, which I could do without a problem.  (I hooked up to the front-panel USB spigot on the machine.) 
I am assuming that your external drive is not bus powered?  (Not sure the USB spec has enough oomph to spin a 1TB anyway, so this is probably correct.)
Just for kicks, what is the status of your Energy Saver "Put the hard disk(s) to sleep when possible" checkbox?  Checked or not?
Ah, and finally, what is the brand and model of the external drive?

Similar Messages

  • Why Does Mac Book Pro fail to shut down?

    I hope I am placing this in the correct place, as I have had enough difficulty finding where to "Post a Topic" Bought a new MacBook Pro with Leopard on 1/4/08. It fails to shut down, all I get is the spinning wheel (for want of a better word) until I am forced to press the shut off button. To date, In-store tech support has archived and re-installed, re-set the PRAM, and I don't know what's left! It seems that every time I do "something" i.e., backup, download photos, etc., even when I carefully close out the applications, and wait, the machine fails to shut down.
    Does anyone out there have a solution to this problem? Is Apple working on this or are they taking the "it's you" attitude? Please advise and many thanks.
    Maxsgirl
    Levittown, NY

    The "Genius Bar" at the Apple Store turned off the "Sync" to the iDisk. This has seemed to resolve the issue, however, MacBook Pro is not problem-free. Let me know if we "share" any other issues. Recently attempted to use Adobe Photoelements, by the way, after being told it was compatible with Leopard, IT IS NOT. So now I am going to try Aperture. Just thought I'd throw that in as "one of the other" issues! Thanks for responding to me!
    Fibrogirl

  • MBP fails to shut down

    Lately my MBP fails to shut down. I quit all apps and then click shut down, the dock and menu bar go away just leaving the apple desktop and the mouse (turns to the beach ball after a while). Last week I wiped my computer and started from scratch hoping it would fix the problem but it didn't. I have repaired permissions and reset the PRAM and have taken out the battery and held the power button for five seconds to reset something else (i forget what it is called). I am thinking this has something to do with time machine and my time capsule. Sometimes time machine will attempt to backup, but will sit at preparing for hours without ever mounting the image. I try to stop it but it wont stop and at that point I can't shut down. Isn't time machine supposed to stop when I shut down? Even if i force quit the backupdb process in activity monitor, my computer will not shut down. So as far as I can tell, time machine is doing something to prevent shutdown or something is but it is really getting annoying. Any help is appreciated.

    Check your console log using the Console application and look around about your shut down time. Look for information about a process that did not shut down. Usually shutdown problems occur because an application you are using does not completely shut down or stops responding.
    Does the computer shut down normally if you don't run any applications? Have you tried creating a new user account, then logging into that account instead of your normal account? Does the computer now shut down normally? Have you tried booting into safe mode to see if the computer will shut down normally?

  • MacPro Fails to shut down

    After I upgrade my 2009 MacBook Pro to Lion, I has problems shutting down.  It locks up and fails to shutdown.

    By chance any applications open  when shut-down is clicked.
    Some times some open applications prevent computer from shutting down.
    It happened to me couple of years ago.

  • Leopard Failing to shut down

    Intermittently, I have been getting this message when I try to shut down my Core2Duo Macbook running Leopard 10.5.1: "Logout has timed out because the application 'X' failed to quit. Try again, quit 'X' and choose Log Out from the Apple menu," where "X" is a random program (although most of the time it is Preview). The problem is is that "X" application is not open or is running when I look at the Console. When I open application "X," quit the application, then try to Shut Down, I get the same message but with a different application. These applications are not running when I look at the Activity Monitor. I haven't found what the cause is and it doesn't occur every time. I have noticed that it will do it when I've had a problem waking up my Macbook from sleep mode (it will give me a black screen after logging-in but will awake from sleep if I close my Macbook and try again).
    My event log shows the following:
    12/24/07 9:34:15 AM com.apple.dyld[820] updatedyld_sharedcache: warning can't use root /Applications/Safari.app/Contents/MacOS/Safari: can't open file, errno=2
    12/24/07 9:34:15 AM com.apple.dyld[820] updatedyld_sharedcache: warning can't use root /Applications/Mail.app/Contents/MacOS/Mail: can't open file, errno=2
    12/24/07 9:34:15 AM com.apple.dyld[820] updatedyld_sharedcache: warning can't use root /Applications/iChat.app/Contents/MacOS/iChat: can't open file, errno=2
    12/24/07 9:34:19 AM loginwindow[39] ERROR | WSActivateApp | SetFrontProcess({0, 352342}) returned error -600. Unable to activate process.
    12/24/07 9:34:24 AM com.apple.launchd[1] (com.apple.dyld) Throttling respawn: Will start in 51 seconds
    12/24/07 9:35:02 AM loginwindow[39] ERROR | WSActivateApp | SetFrontProcess({0, 352342}) returned error -600. Unable to activate process.
    12/24/07 9:35:09 AM bootpd[171] can't open /etc/bootptab
    12/24/07 9:35:09 AM bootpd[171] server name Macbook.local
    12/24/07 9:35:09 AM bootpd[171] interface en0: ip 192.168.2.1 mask 255.255.255.0
    12/24/07 9:35:09 AM bootpd[171] interface fw0: ip 192.168.3.1 mask 255.255.255.0
    12/24/07 9:35:09 AM bootpd[171] interface en1: ip 192.168.0.104 mask 255.255.255.0
    12/24/07 9:35:09 AM bootpd[171] interface en2: ip 192.168.4.1 mask 255.255.255.0
    12/24/07 9:35:09 AM bootpd[171] interface en2: ip 169.254.9.247 mask 255.255.0.0
    12/24/07 9:35:09 AM bootpd[171] interface en3: ip 10.211.55.2 mask 255.255.255.0
    12/24/07 9:35:09 AM bootpd[171] dhcp: re-reading lease list
    12/24/07 9:35:15 AM com.apple.dyld[823] updatedyld_sharedcache: warning can't use root /Applications/Safari.app/Contents/MacOS/Safari: can't open file, errno=2
    12/24/07 9:35:15 AM com.apple.dyld[823] updatedyld_sharedcache: warning can't use root /Applications/Mail.app/Contents/MacOS/Mail: can't open file, errno=2
    12/24/07 9:35:15 AM com.apple.dyld[823] updatedyld_sharedcache: warning can't use root /Applications/iChat.app/Contents/MacOS/iChat: can't open file, errno=2
    12/24/07 9:35:15 AM com.apple.launchd[1] (com.apple.dyld) Throttling respawn: Will start in 60 seconds
    12/24/07 9:36:04 AM natd[789] failed to write packet back (No route to host)
    12/24/07 9:36:16 AM com.apple.dyld[824] updatedyld_sharedcache: warning can't use root /Applications/Safari.app/Contents/MacOS/Safari: can't open file, errno=2
    12/24/07 9:36:16 AM com.apple.dyld[824] updatedyld_sharedcache: warning can't use root /Applications/Mail.app/Contents/MacOS/Mail: can't open file, errno=2
    12/24/07 9:36:16 AM com.apple.dyld[824] updatedyld_sharedcache: warning can't use root /Applications/iChat.app/Contents/MacOS/iChat: can't open file, errno=2
    Anyone else with this problem or know why it is doing this?
    Message was edited by: pup975

    It is likely that you are experiencing some conflicts.
    The main conflicts are cache, permissions, fonts and login items.
    If you did an upgrade of Leopard over Tiger you could have all 3.
    The log seems to point to some cache problems.
    So let's start with user cache.
    In Finder click on Go>Home>Library and pull the Caches folder to the Trash.
    Then click on the hard drive icon in the sidebar and double click on this Library and remove Caches here too.
    Click on the apple>System Preferences>Accounts and unlock the lock.
    Click on login items and remove all items from the window.
    Then Go>Utilities>Disk Utility and select your hard drive volume then Verify Disk.
    If the disk passes then Repair Disk Permissions.
    Once any repairs are done, quit Disk Utility.
    Click on Go>Applications>Font Book.
    In Font Book choose All Fonts in the 1st column, then click into the second column.
    Check for a black dot to the right of any of the fonts in the list in the second column.
    If there are any dots the click on Edit>Select All.
    Next Edit>Resolve Duplicates.
    Next File>Validate Fonts.
    Put a check mark in the box to the left of all fonts that shows problems and click on Remove Checked.
    Next boot to the Leopard install disk >Utilities>Reset Password.
    Click on your hard drive volume>home directory user name>Reset permissions and ACL's at the bottom.
    Then restart your computer.
    This will rebuild some Cache files so it will be slow on this startup.

  • JNI native threads causing JRE to fail to shut down?

    Hello,
    I am using JNI to communicate with a COM object. I am reasonably certain at this point that my JNI code is handling this properly and the third party COM library is releasing the object in question. We allocate and release hundreds of these objects and we aren't observing any memory leaks. Likewise in our handling of events we receive from the COM object. We attach the thread to Java, deliver the event, and then detach the thread from Java, with very careful error handling around the event delivery to ensure that whatever else happens the detach gets called. This code is very robust and stable in operation and has been working at load in the field for over a year now without any customer problems in the JNI area.
    However, since day one, when I go to shut down the application, the JNI isn't winding down properly. As it happens, since the JRE is running a Tomcat, driven by a wrapper service, the wrapper eventually gives up waiting and shoots the JRE in the head, but the user experience of stopping the wrapper service is ugly and we'd like to clean that up. The JNI code, of course, runs as shared code in the Tomcat.
    It is possible that the third-party library, which does network communications, is keeping a thread pool for use with any of the COM objects even after all COM objects are released. This would be experienced as a one-time hit when the first object is allocated and not as a continual leak, so we'd be unlikely to notice it otherwise.
    Will native non-Java threads running in the JRE but not allocated by the JRE itself cause the JRE to hang on until they've spontaneously decided to clean themselves up? Threads that have never been attached to the JVM? How about threads that were briefly attached to the JVM but then detached? Any worse?
    Ralph

    Hi Ralph,
    I will need some more information regarding this issue.
    1. What platform are you on?
    2. Which JRockit version are you running?
    3. If you remove the wrapper service, does JRockit freeze without exiting properly?
    As a general recommendation I would try to upgrade to the latest JRockit version. It can be downloaded from the OTN http://www.oracle.com/technology/software/products/jrockit/index.html
    You may also try some verbose printouts to debug the issue a little further. Try
    -Xverbose:thread=debug,jni=debug
    This might give us some more insight in what is going on.
    Also when JRockit freezes you can output a Java stack trace using our 'jrcmd' tool which you can find in the same folder as the java executable. Run this tool without any parameters and it will output identifiers (numbers) for every running JRockit instance on your machine. Run the same tool again, this time append the identifier you believe is the one running the Tomcat and add the command 'print_threads', ie
    jrcmd <some_id_here> print_threads
    This may show what JRockit is waiting for.
    Cheers,
    /Henrik

  • Phone frequently fails to shut down cleanly

    Somewhat regularly when I go to shut off my phone, instead of shutting down after displaying the swirling circle, the passcode screen displays instead. I can enter my passcode, or cancel or do nothing and the phone turns off about 4 seconds later.
    The next time I turn the phone on it takes a long time to start up (similar to after doing a reset, but not quite as long). Also the usage minutes show as - until I fully charge the phone again, which is the same thing that happens after doing a reset.
    At that point if I turn off my phone it turns off without issue. It seems to be more likely to occur, the longer I've had my phone on without turning it off.
    It's obvious that something the phone isn't shutting down cleanly when this happens. Is there some way to diagnose what's going on or figure out why this happens?

    There is some corrupted code or settings in the phone. Try the following troubleshooting steps as needed:
    1. Reset phone - press both home and sleep/wake button until the Apple logo appears.
    2. Settings > General > Reset > REset All Settings.
    3. Restore phone in iTunes using a backup.
    4. Restore as a new iPhone.

  • Brand new MacBook Air fails to shut down

    I took ownership of a brand new 13" MacBook Air on Friday 15th, have been trying it since then and found that on occasion it hangs during the shutdown process. This has happened five times in two days of use (it's now the 17th). The only way to get the MBA to shut down is to hit the start button for an extended period otherwise it will sit spinning for eternity. I have experimented and tried to shutdown programmes first before shutting down the MBA, but this doesn't appear to help.
    I have only installed a few programmes on the MBA since receiving it, (Lightroom and 1Password), everything else is as it was when it was delivered, brand new. I purchased it via the online store and requested that it was upgraded with 8GB RAM and a 1.7GHz processor, so it came from China with these upgrades carried out.
    Could this be a memory problem? I understand that MBs can be fussy about what type of memory is installed. It seems odd as the memory was installed in the factory.
    Should I do a VRAM and/ or PROM reset? Are either of these responsible for controlling shut down procedures?
    It is very disappointing as I had been really looking forward to getting the MBA and I am concerned that this might be an inherent fault with this particular machine. Any help would be appreciated. I will contact Apple Support as I have 90 days phone support, but I thought I should try you all first.
    Chris

    RAM should not be a factor for a brand new Mac. Third party software is often the culprit.
    Make sure to log out of 1Password before shutting down >  https://discussions.agilebits.com/discussion/5265/1password-cancels-logout
    Tip ... there's no need for a third party password manager. The pre installed Keychain Access app can do that for you.
    HD > Applications > Utilities
    How to manage passwords with Keychain Access | Macworld

  • Failed to shut down.  cannot reboot

    MacBook Pro.  Didn't shut down because applications open.  Then cannot use, open, close.  Mouse moves, but nothing functions. Force quit application, still locked.  How can I shut down or reboot?

    That works too: Force an app to close on your Mac - Apple Support

  • Fail to Shut Down or Restart Macbook Pro

    So I don't know if this has to do with Mavericks or just my Mac in general, but my mouse is constantly a spinning color wheel when on my homescreen. It won't let me open finer either, and when I do try to restart my computer it says finder is still running operations and to stop them before restarting. I have exited out of finder, tried quitting everything, but it still won't even shut down.

    This what I would start with:  First a SMC and PRAM resets:
    http://support.apple.com/kb/ht3964
    http://support.apple.com/kb/ht1379
    Then a Safe Boot:
    http://support.apple.com/kb/HT1564?viewlocale=en_US
    Ciao.

  • Frequent crashes, fails to shut down

    Hey guys. I've had this macbook since June 2006, and its performance has gone steadily downhill. It runs unusually slowly, compared to all the other (many) Macbooks on my college campus, and various programs cause different problems. Photobooth would never quit fully, nor would iPhoto (they would stay in the dock). Finder crashes several times a week, and when I go to restart it in the force quit menu, it never comes back. Often, the computer would not shut down. I had to hold down the button constantly to force it to power off.
    I erased everything and reinstalled to eliminate these problems, and for a few days everything was great. Now, if I wake from sleep and try to click a new tab in Firefox, the whole system goes into beach-ball shock. Even if that hasn't happened, It absolutely will not shut down at all, simply stalling for hours on my desktop pattern and never powering off.
    I'm in college, and this laptop is my lifeline. We don't have a proper mac store in this town (Eugene, Oregon) so I'd have to send it in, which I don't have time to do (finals are soon). I've concluded since everything was erased and reainstalled that I must be experiencing some sort of hardware issue. Direct me. I'm tired of calling this the worst computer I've ever owned.
    Macbook 1.83   Mac OS X (10.4.8)   512, 60gb

    I erased everything and reinstalled to eliminate
    these problems, and for a few days everything was
    great.
    That seems to indicate it is a software problem. You could try doing some maintenance using OnyX:
    http://www.macupdate.com/info.php/id/11582
    and/or AppleJack:
    http://www.macupdate.com/info.php/id/15667

  • IMac Losing Bluetooth and then becomes slow, and fails to shut down without holding the button. Happens 3 times a day randomly.

    Hey guys,
    Hope you are having a good day!
    My IMac 3.1Ghz Intel Core I5, 16GB 1333MHz DDR3 memory running OSX 10.9.2 is having serious issues.
    About 3 times per day sporadically it loses connectivity to the bluetooth keyboard and mouse, and is irrecoverable (I have tried everything, and it is not trying to connect to another device - e.g. IPAD).
    When this happens, I am usually using an audio program (e.g. Logic Pro X, or Ableton Live), and when sound is playing, the event stops the sound altogether as well.
    If I then hold the power button, the message asking if I want to shutdown or restart comes up, and the system appears responsive. However, there is no way for me to select anything because of the keyboard and mouse being down.
    However, I jumped the gun and got a free IPAD app. that gives me limited control with a keyboard and mouse on there, enough that I am able to select to shut the computer down.
    When this happens, the computer takes 5-10 minutes to force quit all active applications (e.g. logic pro, active audio interface program RME totalmix, etc.). When it finally, finally quits everything, and attempts to shutdown, it takes a very long time and gets stuck on a white screen. When it gets there the computer stops making noise altogether but has not properly shutdown yet, so it appears some sort of system failure is taking place.
    It is really frustrating that this is happening, and I really hope my computer isn't broken. I would really appreciate any help or advice provided.
    Thanks so much!!!!!!!!!!

    When you have the problem, note the exact time: hour, minute, second.
    If you have more than one user account, these instructions must be carried out as an administrator.
    Launch the Console application in any of the following ways:
    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
    ☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
    Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left. If you don't see that menu, select
    View ▹ Show Log List
    from the menu bar.
    Each message in the log begins with the date and time when it was entered. Scroll back to the time you noted above. Select the messages entered from then until the end of the episode, or until they start to repeat, whichever comes first. Copy the messages to the Clipboard by pressing the key combination command-C. Paste into a reply to this message (command-V).
    The log contains a vast amount of information, almost all of it useless for solving any particular problem. When posting a log extract, be selective. In most cases, a few dozen lines are more than enough. It is never necessary or helpful to post more than about 100 lines. "The more, the better" is not the rule here.
    Please do not indiscriminately dump thousands of lines from the log into this discussion.
    Important: Some private information, such as your name, may appear in the log. Anonymize before posting.

  • AOL failing to shut down without a forced quit?

    Just downloaded AOL for Mac, works fine, but every time I try to close it down it fails to close, just gives me the spinning wheel sign & requires a forced quit, is this usual for other AOL users?
    I have reported it to Apple after each occasion, how long before they get fed up & fix it!?!

    Welcome To  Discussions DSL2!
    No that is not normal.
    I use AOL on all of my Macs, and do not have that problem.
    I have not installed Leopard 10.5.x yet, but I have not read that your issue is common, with the that system.
    "...I did not know that AOL were not supporting software for MAC..."
    That is exactly accurate.
    If you have a paid AOL account, you can still get help from AOL Support, no matter which version of AOL you have installed, but you probably don't need that.
    And AOL is developing a new Mac version.
    The 10.5.2 Combo Update, is what corrected some known issues with AOL & Leopard, but as per your specs, you have already installed that.
    Did you run Repair Permissions after the update was intalled?
    More info here Important Message for users who have installed Mac OS X 10.5 (Leopard).
    Repost, if you would like me to help you resolve the problem you are having with AOL.
    ali b

  • OPen Captivate 4 project in Captivate 5 fails and shuts down Captivate 5

    I have a small project (6 slides) that was created using Captivate 4. When I attempt to open this in Captivate 5, I see the progress bar indicating that the slides are being upgraded to 5 and once that completes, I get an error message that it encountered an error and needs to close. I tried a couple other projects created in Captivate 4 and those open fine in 5.
    I saved the text file created as a result of the error, but don't know what it is trying to tell me. I don't see an option here to attach the file.
    I appreciate any assistance or direction you can provide.

    Hi
    Can you please send the text file containing the error report?
    You can share the text file using your Acrobat.com account.
    Regards
    Chinmay Baid
    http://blogs.adobe.com/captivate

  • When exporting an illustrator image to jpg and creating image map illustrator fails and shuts down.

    save as rgb high quality image map client side AND server side fail

    Hi erinKitchenrestock,
    Can you please provide the URL name ?
    Thanks & Regards,
    Raghuveer

Maybe you are looking for