Powering down external HDs on an iMac when shut down

Hi to all, hope you can help .....
I recently added two external WD Studio HDs to my iMac connected as a RAID1 array. This was done using the Mac disc utility and without any reference to the pre installed WD software. I also have a separate Studio HD as my Time Machine and since all 3 have a Firewire connection I daisy chained the cable to all 3 devices (the iMac only has 1 Firewire port) since I thought this would be the fastest option. All 3 HDs appear to function correctly, except when I power my system down the drives remain awake.
Before I added the 2 in RAID array the original Time Machine HD did power down automatically when the Mac was turned off, so for some reason the system doesn't seem to want to cope with 3 HDs.
I've checked in system preferences/energy saving and the box for powering down HDs when possible is ticked.
Any ideas / solutions greatfully received, Cheers !!

Hi Roy,
I'd stick with Firewire. It's faster and I have always considered it more reliable. (It takes a technical discussion to explain why.)
There is no assurance that using USB will make your external drives power down. Again, I want to emphasize that not all drives will power down automatically when you shut down your Mac. Some drives do, some never do, and some have a 3-way switch that allows you to select the power-down behavior. And there may be something about your 2-drive software controlled RAID setup that affects things here.
The energy saver preference item for powering down drives whenever possible applies, I believe, only when the Mac is turned on and idle. (I do not believe it controls powering down external drives when you shut down your Mac.)
Unmounting the drive is as simple as what you wrote - eject it in the Finder. Alternatively, if you have the drive icons on your desktop, you can drag them to the trash to unmount the drive(s). Keep in mind that when you shut down your Mac, it automatically umounts the drives itself anyway.
External drives will automatically remount next time you start your Mac (unless the drive is powered off). If you unmount a drive and then decide you need to remount it while your Mac is still running, you can use Disk Utility. Open Disk Utility, select the drive you want to mount and then click the Mount button.

Similar Messages

AirPort Extreme powers down when iMac is shut down

9-month old AirPort Extreme, with two hardwire connections: one to the DSL modem, and one to an iMac. After months of perfect performance and reliability, the AirPort extreme now completely powers down as soon as the iMac is shut down or goes to sleep. It powers back up with the iMac. Logging out the iMac to another user account does not shut down the AE.
Naturally, we checked the electrical supply for all three devices and they are all plugged into a perfectly ordinary surge supressor strip.
We're thinking the AE has a hardware failure...but what kind of bizarre symptom is this that it shuts down when it loses signal from it's only Ethernet client?

This is certainly odd. Have you tried a different port on the AEX?
It may be best to contact Apple about a warranty exchange.

IMac is shutting down when it attempts to sleep with 'hibernate image' error

Our iMac is shutting down when it attempts to sleep. This started following a Yosemite security update, though of course it is difficult to determine for sure that that was the cause.
In the console, the following message occurs before every shut down:
kernel[0]: Failed to get hibernate image filename
Suggestions? Does someone perhaps know what exactly the hibernate image is (we have a tiled screensaver that shows an iPhoto album -- could it be that one of those files is corrupt?) so that I can attempt to change it to see if that fixes the problem?
Thanks!
System: iMac (21.5-inch, Mid 2011), OS X 10.10.2
Already tried:
I reset the SMC by following Apple's instructions for this computer (turn off, unplug, wait, replug, wait, turn on)

More information:
1. It looks like the crash/shut down is happening when the display tries to sleep (timing is 15 min after the beginning of automatic sleep).
2. When sleep is first initiated, I am seeing this in the console (not normal?):
2015-03-25 9:22:05.987 AM ScreenSaverEngine[485]: Preflight for plugin com.apple.ILPhotosPlugin failed, so it will not load. Error Domain=NSCocoaErrorDomain Code=3587 "The bundle “iLMBPhotosPlugin” couldn’t be loaded because it is damaged or missing necessary resources." (dlopen_preflight(/Library/Application Support/iLifeMediaBrowser/Plug-Ins/iLMBPhotosPlugin.ilmbplugin/Contents/MacOS/i LMBPhotosPlugin): Library not loaded: /System/Library/PrivateFrameworks/PhotoLibraryPrivate.framework/Versions/A/Phot oLibraryPrivate
Referenced from: /Library/Application Support/iLifeMediaBrowser/Plug-Ins/iLMBPhotosPlugin.ilmbplugin/Contents/MacOS/i LMBPhotosPlugin
Reason: image not found) UserInfo=0x7fed83841320 {NSLocalizedFailureReason=The bundle is damaged or missing necessary resources., NSLocalizedRecoverySuggestion=Try reinstalling the bundle., NSFilePath=/Library/Application Support/iLifeMediaBrowser/Plug-Ins/iLMBPhotosPlugin.ilmbplugin/Contents/MacOS/i LMBPhotosPlugin, NSDebugDescription=dlopen_preflight(/Library/Application Support/iLifeMediaBrowser/Plug-Ins/iLMBPhotosPlugin.ilmbplugin/Contents/MacOS/i LMBPhotosPlugin): Library not loaded: /System/Library/PrivateFrameworks/PhotoLibraryPrivate.framework/Versions/A/Phot oLibraryPrivate
Referenced from: /Library/Application Support/iLifeMediaBrowser/Plug-Ins/iLMBPhotosPlugin.ilmbplugin/Contents/MacOS/i LMBPhotosPlugin
Reason: image not found, NSBundlePath=/Library/Application Support/iLifeMediaBrowser/Plug-Ins/iLMBPhotosPlugin.ilmbplugin, NSLocalizedDescription=The bundle “iLMBPhotosPlugin” couldn’t be loaded because it is damaged or missing necessary resources.}
The iLMBPhotosPlugin file does exist:
ls -al "/Library/Application Support/iLifeMediaBrowser/Plug-Ins/iLMBPhotosPlugin.ilmbplugin/Contents/MacOS/"
total 80
drwxr-xr-x 3 root wheel 102 30 Jan 07:46 .
drwxr-xr-x 7 root wheel 238 30 Jan 07:46 ..
-rwxr-xr-x 1 root wheel 99840 29 Sep 01:41 iLMBPhotosPlugin
The Library PhotoLibraryPrivate.framework/Versions/A/PhotoLibraryPrivate does not (there is no directory called /System/Library/PrivateFrameworks/PhotoLibraryPrivate.framework)
sudo ls -ald "/System/Library/PrivateFrameworks/Photo"*
drwxr-xr-x 3 root wheel 102 11 Sep 2014 /System/Library/PrivateFrameworks/PhotoLibrary.framework

Why does my iMac not shut down when I try to shut it down?

Wh does my iMac not shut down, or restart when I try to do either. It just sits there with the little loading circle continuously moving. The only way I can shut it down is if I hold down the power button to shut it down. Can anyone tell me why this is?
Thanks!

Open your Activity Monitor and check to see what is running?
If there is some important Process running, then it is better to wait until it has finished instead of cutting the power and corrupting who knows what?
If there is nothing important running, then follow the instructions in the link below for resetting the SMC.
Intel-based Macs: Resetting the System Management Controller (SMC)

IMac Randomly Shuts Down -Overheating Problem?

I've posted in these forums once before about my iMac randomly shutting down. I believed I had solved the problem by following another users instructions which were as follows:
"Machines that are just randomly shutting down are usually caused by defective hardware. The only thing that can be done about that is to call Apple and have it replaced or serviced. There is probably not any one particular solution as it could be any number of the internal components failing and the resulting symptoms could be the same.
If you'd like to do some hardware tests yourself before calling Apple that can be done. First try resetting the SMC: http://docs.info.apple.com/article.html?artnum=303446
Next insert the original gray install disk, restart your iMac, then hold down the "d" key until it boots up into the Apple Hardware Test. Run the extended test.
Also if you have Apple Care install TechTool Deluxe from the cd provided. Then run TechTool on your system."
I also removed and replaced of a defective external HD that I thought my be causing problems. But after all these steps, the machine kept turning itself off.
I had read in some forums that it was due to the internal temperature of the iMac. So I downloaded smcfancontrol 2.1 and increased the fan speed on the internal fans. This did bring down the temperature as revealed by the iStat Pro widget. However, I still had another shutdown.
So I turned off the machine, went to bed, and this morning when I turned it on iStat Pro said these were the internal temperatures of the iMac:
CPU A 77 degrees F
GPU 85
GPU Diode 88
GPU Heatsink 85
Ambient 61
Memory Cont. 74
Airport Card 112
HD Bay 1 76
I find these numbers to be unbelievable. Especially the airport card. When the whole system seemed to be running hot, the Airport Card said it was 122. It always says something above 100 degrees. The other temperatures also seem out of whack. How can the CPU be 77 degrees after 10 hours of being completely powered down in an office environment that is only 55 degrees?
Has anyone else run into a similar problem?
Has anyone else found the problem to be a faulty temperature sensor (and is there a way to reset it, or does it have to be replaced)?
Overheated? in Oregon...
Message was edited by: OregonMac7

Certainly sounds like a case of the left hand not knowing from the right, huh
Well, I have my call in, and I am getting onsite service to replace the logic board, as per Apple's recommendation.
I'm reading the other longer thread (171 replies), and it's disheartening to hear how some of the "geniuses" are handling this problem. They can't replicate it by leaving the mac running overnight, so "the problem doesn't exist". Hello! It's *random*! As in, not easy to replicate!
I'm also a bit disillusioned that the popular Mac sites (TUAW, etc) haven't picked up on this story yet. I emailed TUAW the link to the long thread, and they ignore it. Usually when this gets more "mainstream" press, then Apple finally steps up, acknowledges a problem, and serious fixes are made. Right now, it's a bunch of complainers (me included) in some threads on the Apple site.
I took a huge leap last November, and went from PCs to the Mac platform, after working on my personal migration plans for a month prior - how to move from my photo editing on the PC to the Mac (I wasn't about to buy another full copy of Photoshop, for eg, but I did find out I could upgrade from Win PS to Mac PS), if all the programs I use for photography and design were available on the Mac, learning the ins and outs of shortcut keys, how things are done, etc etc, and was so happy initially when I got the Mac and said goodbye to the PC.
Now I'm literally afraid to do any serious work on the Mac for fear of the "pulled plug" syndrome losing the last 20, 30 minutes of work I've been doing because I didn't save every 2 minutes. And iLife's Pages doesn't autosave (much to my chagrin), so I've lost some long correspondence and articles typed because I didn't save it before the pulled plug o' death.
Not a very nice computing experience.
As a suggestion, maybe everyone reading this and the other thread can flood TUAW.com with a news suggestion to cover this problem. Engadget, Gizmodo too while you're at it. I think once these million-viewers a day blogs cover it, we'll see some real action from Apple.
Just a thought....
Mark

MacMini Hangs When Shutting Down

Hi all.
I've tried looking up the answers to this but I have a slightly different issue from others who had issues when shutting down.
This started a few months ago. What happens is when I click to shut down the computer, everything starts closing out. The top menu bar disappears but then nothing else happens. I'm basically looking at my wallpaper with nothing on it but my dock will still be up. When I look on my dock the only thing that appears to be active is the "Finder" folder. When I click on it nothing happens, however, if I right click it says that the application is not responding and gives me the option to relaunch, but nothing happens. So it seems like there's something going on with the "Finder" folder that is preventing it from shutting down.
For what it's worth, I did run "Verify Disk" from Disk Utilities that said everything came back okay. I unplugged any external devices hooked up via USB like my USB hub to see if there was something going on there.
I have a 2012 Mac Mini.
In the past, I have let it go all night to see if it would eventually shut down and it won't. I have to force shut it down. Ideally, I don't want to do this. Has anyone else had this issue?
Thanks!

These instructions must be carried out as an administrator. If you have only one user account, you are the 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 and start typing the name.
Step 1
For this step, the title of the Console window should be All Messages. If it isn't, select
          SYSTEM LOG QUERIES ▹ All Messages
from the log list on the left. If you don't see that list, select
          View ▹ Show Log List
from the menu bar at the top of the screen.
In the top right corner of the Console window, there's a search box labeled Filter. Initially the words "String Matching" are shown in that box. Enter "BOOT_TIME" (without the quotes.)
Each message in the log begins with the date and time when it was entered. Select the BOOT_TIME log message that corresponds to the last boot time when you had the problem. Now clear the search box to reveal all messages. Select the ones logged before the boot, during the time something abnormal was happening. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.
For example, if the system was unresponsive or was failing to shut down for three minutes before you forced a restart, post the messages timestamped within three minutes before the boot time, not after. Please include the BOOT_TIME message at the end of the log extract—not at the beginning.
If there are long runs of repeated messages, please post only one example of each. Don’t post many repetitions of the same message.
When posting a log extract, be selective. A few dozen lines are almost always more than enough.
Some private information, such as your name, may appear in the log. Anonymize before posting.
Please don't indiscriminately dump thousands of lines from the log into this discussion.
Please don't post screenshots of log messages—post the text.
Step 2
In the Console window, select
          DIAGNOSTIC AND USAGE INFORMATION ▹ System Diagnostic Reports
(not Diagnostic and Usage Messages) from the log list on the left. If you don't see that list, select
          View ▹ Show Log List
from the menu bar.
There is a disclosure triangle to the left of the list item. If the triangle is pointing to the right, click it so that it points down. You'll see a list of reports. A crash report has a name that begins with the name of the crashed process and ends in ".crash". A panic report has a name that begins with "Kernel" and ends in ".panic". A shutdown stall report has a name that ends in ".shutdownstall". Select the most recent of each, if any. The contents of the report will appear on the right. Use copy and paste to post the entire contents—the text, not a screenshot. It's possible that none of these reports exists.
I know the report is long, maybe several hundred lines. Please post all of it anyway.
If you don't see any reports listed, but you know there was a crash or panic, you may have chosen Diagnostic and Usage Messages from the log list. Choose DIAGNOSTIC AND USAGE INFORMATION instead.
In the interest of privacy, I suggest that, before posting, you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if it’s present (it may not be.)
Please don’t post other kinds of diagnostic report—they're very long and rarely helpful.

Another iMac Randomly Shutting Down!!

Hey Everyone. I'm new to the forums, though i've always used them as a resource over the years to learn more or troubleshoot issues. Hopefully, now, someone can help me with mine personally.. :-/
I have an intel 2.8gH Aluminum iMac that I purchased fall of 2007. Only now, almost 2 years later is it suddenly (just started yesterday) turning off randomly. Everytime it will not allow me to turn it back on until a minute or so has passed. I have reset the SMC as well as the PRAM several times. This afternoon, it is now to the point where I cannot even keep it running long enough to download an app to up the fan speeds. Although, I don't think it is overheating in the first place.
I'm really hoping it is just the power supply, as I've seen that be the fix for SOME iMacs i've found at other online forums. Though, the upper corner of my iMac is not hot or smelling burnt out at all. I have found more than several online forums of people complaining about their iMacs randomly shutting down, and am praying it is not the logic board, as that is a $900+ fix.
please, someone give me insight to how i can check if its the power supply or something else? I use this iMac for recording all of my music, editing video, and (of course) playing WoW lol. Currently using my 1st gen macbook.

I bought my iMac 20" in May 2006. I had been very impressed with it until one day I shut it down to move it to another room. I could not get it to turn back on. I had to leave it unplugged for a few hours. Since then it has started randomly shutting itself down, turning itself off and not starting up again until I unplug and leave it unplugged for a few hours. I had purchased the Apple Care? Extended Warranty, and the fault occurred during this three year period, though I failed to take the fault seriously and did not phone during the period. It was just after the three year warranty that I phoned Apple Care? about it and everyone I spoke to said they had not heard of this problem occurring. I wonder now, why the Apple Customer Service Team don't visit the discussions.apple.com where they will find quite a significant number of like problems occurring with the iMac sold in 2006.
My reason for paying the nearly triple price point for an Apple Computer was the quality of the build and my expectation that I would get far longer life out of my purchase. I don't like buying throw away products and I gladly save and wait longer to buy better quality products. Just as an example and point of reference. In 2000 I purchased a second hand Dell with 8GB HDD and 256Mb RAM. I paid $1000 for it and I gave it to my father when I got this iMac and he still has it running today. It has not had a single hardware issue in nine years. Good luck I suppose. However, after spending around $3000 on this iMac, and Apple now telling me the Logic Board is generically, non specifically 'failing', it goes against my pure desire for non disposable, throw away products to buy another Logic Board for AUS $1064. For one, I don't believe it has given me anywhere near the life that I expected from a product with such a high price point and solid reputation for quality, nor do I feel confidence in buying anything more 'Apple' after the dealings I have had with them over this problem. I am amazed that Apple would sell a 'failing' Computer to their customers and then expect that the customer will spend more money, considerably more, on a product that may be equally faulty and that they will not stand behind either.

IMac's shutting down

My wife and I both have the 20" iMac. Model ID "iMac 8,1. Today they both started shutting down randomly, like a complete power loss shut down. Once powered off, they will not turn back on, you hit the power button and nothing happens. The only thing that gets them back on is if I leave them unplugged for a few minutes, then they will power on but only after hitting the power button twice, it never works the first time. Once on the computers randomly shut down after 3-10 minutes and the process starts over. It doesn't matter if they're being used heavily or just sitting at the log in screen. Both iMacs have the exact same symptoms and started happening on the same day. Anyone know whats going on?

Well, it looks like I actually have a power issue in the room, maybe there's low voltage or a short somewhere. I moved them to another room in the house and they seem to be working fine.

IMac G5 shuts down unexpectedly

Hi friends at Apple Discussions,
This week my iMac has shut down by itself unexpectedly about once a day. Immediately after it shuts down it will not start up, although after a 10 minute wait or so, it will start up and run just fine. Nothing had been changed, hardware or software, recently that should have caused this.
It is a Rev A machine. Serial number is QP507XXXX. Within the first 6 months of ownership, she had a power supply failure that was repaired under warranty by an Apple Retailer. Everything has been great since then.
I understand that this might be another Rev A hardware failure issue and I believe I am still inside the three year repair window. However, I also understand that there are often preliminary steps to take before jumping to that conclusion.
Any advice as to what action should be taken next? I appreciate your expertise.
James
iMac G5 1.8 GHz 20" Rev A 768 MB RAM (Crucial). Mac OS X (10.3.9) iBook G4 12"

Status report...
In previous posts I did not mention that I am not under AppleCare. The tech was willing to help but suggested that I might try isolating/replicating the problem on my own. Otherwise, if I take it in and they find it is a software issue, not the hardware issue, I get charged.
His suggestion: Try an archive and install for a couple of days, see if problem still occurs. That will determine if it is a hardware or software problem. Actually, I believe I'll do a clean install instead for a couple of days, as my entire hard drive is cloned & bootable on my external LaCie drive. This is an inconvenience and steals my time, but its easy enough to do, I guess.
So I'll do it, but the question lingering in the back of my mind is...is this actually necessary? Does software shut a machine down randomly and prevent it from booting up again for the duration of some unknown 'cooldown' period? Besides, the only software change I have made relativly recently was installing Camino I am highly skeptical that its a software issue. But because I am not an expert, I will follow the suggestions.
Any comments on this?
James

IMac 27 shuts down at intro

hello my iMac 27 shuts down at intro or when i trying to set it up ,i think its Fan or HDD but not sure , maybe anyone knows where is a problem ?

Is it an earlier iMac that came with say a 10.6 Install Disc?
"Try Disk Utility
1. Insert the Mac OS X Install disc, then restart the computer while holding the C key.
2. When your computer finishes starting up from the disc, choose Disk Utility from the Installer menu at top of the screen. (In Mac OS X 10.4 or later, you must select your language first.)
*Important: Do not click Continue in the first screen of the Installer. If you do, you must restart from the disc again to access Disk Utility.*
3. Click the First Aid tab.
4. Select your Mac OS X volume.
5. Click Repair Disk, (not Repair Permissions). Disk Utility checks and repairs the disk."
http://docs.info.apple.com/article.html?artnum=106214
Then try a Safe Boot, (holding Shift key down at bootup), run Disk Utility in Applications>Utilities, then highlight your drive, click on Repair Permissions, reboot when it completes.
(Safe boot may stay on the gray radian for a long time, let it go, it's trying to repair the Hard Drive.)
If perchance you can't find your install Disc, at least try it from the Safe Boot part onward.

IMac just shuts down during iDVD build

*4 week old 20 inch iMac just shuts down during iDVD build of a dvd. Its really weird, because it is rendering and encoding and all of a sudden it just shuts down without a know. Then when I turn it back on it ejects the blank dvd out and starts. I had my SuperDrive replaced also like 2 days ago from the apple store. I have pasted the system.log if that helps?*
7/22/09 10:39:01 AM com.apple.launchctl.System[2] launchctl: Please convert the following to launchd: /etc/mach_init.d/dashboardadvisoryd.plist
7/22/09 10:39:01 AM com.apple.launchd[1] (com.apple.blued) Unknown key for boolean: EnableTransactions
7/22/09 10:39:01 AM com.apple.launchd[1] (com.apple.usbmuxd) Unknown key for boolean: EnableTransactions
7/22/09 10:39:01 AM com.apple.launchd[1] (org.cups.cups-lpd) Unknown key: SHAuthorizationRight
7/22/09 10:39:01 AM com.apple.launchd[1] (org.cups.cupsd) Unknown key: SHAuthorizationRight
7/22/09 10:39:01 AM com.apple.launchd[1] (org.ntp.ntpd) Unknown key: SHAuthorizationRight
7/22/09 10:39:01 AM com.apple.launchd[1] (org.x.privileged_startx) Unknown key for boolean: EnableTransactions
7/22/09 10:39:07 AM org.ntp.ntpd[27] Error : nodename nor servname provided, or not known
7/22/09 10:39:14 AM com.apple.launchd[1] (com.apple.aslmanager) Throttling respawn: Will start in 3 seconds
7/22/09 10:39:14 AM com.apple.launchd[1] (com.apple.UserEventAgent-LoginWindow[74]) Exited: Terminated
7/22/09 10:39:14 AM com.apple.launchd[1] (com.apple.ScreenSharing.server[73]) Exited: Terminated
7/22/09 10:39:15 AM com.apple.launchd[81] (com.apple.AirPortBaseStationAgent) Unknown key for boolean: EnableTransactions
7/22/09 10:39:15 AM com.apple.launchd[81] (org.x.startx) Unknown key for boolean: EnableTransactions
7/22/09 10:39:15 AM Dock[95] _DESCRegisterDockExtraClient failed 268435459
7/22/09 10:39:16 AM com.apple.launchd[81] ([email protected][85]) Exited with exit code: 1
7/22/09 10:39:17 AM [0x0-0xf00f].SoftwareUpdateCheck[104] SoftwareUpdateCheck: network unreachable
7/22/09 10:39:17 AM com.apple.launchd[81] ([0x0-0xf00f].SoftwareUpdateCheck[104]) Exited with exit code: 3
7/22/09 10:40:55 AM com.apple.loginwindow[36] Shutdown NOW!
7/22/09 10:40:55 AM com.apple.loginwindow[36] System shutdown time has arrived
7/22/09 10:41:29 AM com.apple.launchctl.System[2] launchctl: Please convert the following to launchd: /etc/mach_init.d/dashboardadvisoryd.plist
7/22/09 10:41:29 AM com.apple.launchd[1] (com.apple.blued) Unknown key for boolean: EnableTransactions
7/22/09 10:41:29 AM com.apple.launchd[1] (com.apple.usbmuxd) Unknown key for boolean: EnableTransactions
7/22/09 10:41:29 AM com.apple.launchd[1] (org.cups.cups-lpd) Unknown key: SHAuthorizationRight
7/22/09 10:41:29 AM com.apple.launchd[1] (org.cups.cupsd) Unknown key: SHAuthorizationRight
7/22/09 10:41:29 AM com.apple.launchd[1] (org.ntp.ntpd) Unknown key: SHAuthorizationRight
7/22/09 10:41:29 AM com.apple.launchd[1] (org.x.privileged_startx) Unknown key for boolean: EnableTransactions
7/22/09 10:41:35 AM org.ntp.ntpd[27] Error : nodename nor servname provided, or not known
7/22/09 10:41:39 AM com.apple.launchd[1] (com.apple.UserEventAgent-LoginWindow[80]) Exited: Terminated
7/22/09 10:41:39 AM com.apple.launchd[1] (com.apple.ScreenSharing.server[79]) Exited: Terminated
7/22/09 10:41:39 AM com.apple.launchd[86] (com.apple.AirPortBaseStationAgent) Unknown key for boolean: EnableTransactions
7/22/09 10:41:39 AM com.apple.launchd[86] (org.x.startx) Unknown key for boolean: EnableTransactions
7/22/09 10:41:42 AM com.apple.launchd[86] ([email protected][90]) Exited with exit code: 1
7/22/09 10:42:06 AM com.apple.loginwindow[36] Shutdown NOW!
7/22/09 10:42:06 AM com.apple.loginwindow[36] System shutdown time has arrived
7/22/09 8:39:44 PM com.apple.launchctl.System[2] launchctl: Please convert the following to launchd: /etc/mach_init.d/dashboardadvisoryd.plist
7/22/09 8:39:44 PM com.apple.launchd[1] (com.apple.blued) Unknown key for boolean: EnableTransactions
7/22/09 8:39:44 PM com.apple.launchd[1] (com.apple.usbmuxd) Unknown key for boolean: EnableTransactions
7/22/09 8:39:44 PM com.apple.launchd[1] (org.cups.cups-lpd) Unknown key: SHAuthorizationRight
7/22/09 8:39:44 PM com.apple.launchd[1] (org.cups.cupsd) Unknown key: SHAuthorizationRight
7/22/09 8:39:44 PM com.apple.launchd[1] (org.ntp.ntpd) Unknown key: SHAuthorizationRight
7/22/09 8:39:44 PM com.apple.launchd[1] (org.x.privileged_startx) Unknown key for boolean: EnableTransactions
7/22/09 8:39:50 PM org.ntp.ntpd[27] Error : nodename nor servname provided, or not known
7/22/09 8:39:54 PM com.apple.launchd[1] (com.apple.UserEventAgent-LoginWindow[74]) Exited: Terminated
7/22/09 8:39:54 PM com.apple.launchd[1] (com.apple.ScreenSharing.server[73]) Exited: Terminated
7/22/09 8:39:56 PM com.apple.launchd[81] (com.apple.AirPortBaseStationAgent) Unknown key for boolean: EnableTransactions
7/22/09 8:39:56 PM com.apple.launchd[81] (org.x.startx) Unknown key for boolean: EnableTransactions
7/22/09 8:40:00 PM Dock[98] _DESCRegisterDockExtraClient failed 268435459
7/22/09 8:40:01 PM com.apple.launchd[81] ([email protected][85]) Exited with exit code: 1
7/22/09 8:51:04 PM iDVD[117] Warning once: This application, or a library it uses, is using NSQuickDrawView, which has been deprecated. Apps should cease use of QuickDraw and move to Quartz.
7/22/09 8:51:05 PM com.apple.loginwindow[36] Shutdown NOW!
7/22/09 8:51:05 PM com.apple.loginwindow[36] System shutdown time has arrived
7/22/09 9:18:06 PM com.apple.launchctl.System[2] launchctl: Please convert the following to launchd: /etc/mach_init.d/dashboardadvisoryd.plist
7/22/09 9:18:06 PM com.apple.launchd[1] (com.apple.blued) Unknown key for boolean: EnableTransactions
7/22/09 9:18:06 PM com.apple.launchd[1] (com.apple.usbmuxd) Unknown key for boolean: EnableTransactions
7/22/09 9:18:06 PM com.apple.launchd[1] (org.cups.cups-lpd) Unknown key: SHAuthorizationRight
7/22/09 9:18:06 PM com.apple.launchd[1] (org.cups.cupsd) Unknown key: SHAuthorizationRight
7/22/09 9:18:06 PM com.apple.launchd[1] (org.ntp.ntpd) Unknown key: SHAuthorizationRight
7/22/09 9:18:06 PM com.apple.launchd[1] (org.x.privileged_startx) Unknown key for boolean: EnableTransactions
7/22/09 9:18:17 PM org.ntp.ntpd[27] Error : nodename nor servname provided, or not known
7/22/09 9:18:20 PM com.apple.launchd[1] (com.apple.UserEventAgent-LoginWindow[74]) Exited: Terminated
7/22/09 9:18:20 PM com.apple.launchd[1] (com.apple.ScreenSharing.server[73]) Exited: Terminated
7/22/09 9:18:21 PM com.apple.launchd[83] (com.apple.AirPortBaseStationAgent) Unknown key for boolean: EnableTransactions
7/22/09 9:18:21 PM com.apple.launchd[83] (org.x.startx) Unknown key for boolean: EnableTransactions
7/22/09 9:18:24 PM com.apple.launchd[83] ([email protected][87]) Exited with exit code: 1
7/22/09 9:30:03 PM iDVD[135] Warning once: This application, or a library it uses, is using NSQuickDrawView, which has been deprecated. Apps should cease use of QuickDraw and move to Quartz.
7/22/09 9:54:14 PM com.apple.launchd[83] (com.apple.Spotlight[93]) Exited abnormally: Segmentation fault
7/22/09 10:00:26 PM iDVD[228] Warning once: This application, or a library it uses, is using NSQuickDrawView, which has been deprecated. Apps should cease use of QuickDraw and move to Quartz.
7/23/09 10:53:01 AM com.apple.launchctl.System[2] launchctl: Please convert the following to launchd: /etc/mach_init.d/dashboardadvisoryd.plist
7/23/09 10:53:01 AM com.apple.launchd[1] (com.apple.blued) Unknown key for boolean: EnableTransactions
7/23/09 10:53:01 AM com.apple.launchd[1] (com.apple.usbmuxd) Unknown key for boolean: EnableTransactions
7/23/09 10:53:01 AM com.apple.launchd[1] (org.cups.cups-lpd) Unknown key: SHAuthorizationRight
7/23/09 10:53:01 AM com.apple.launchd[1] (org.cups.cupsd) Unknown key: SHAuthorizationRight
7/23/09 10:53:01 AM com.apple.launchd[1] (org.ntp.ntpd) Unknown key: SHAuthorizationRight
7/23/09 10:53:01 AM com.apple.launchd[1] (org.x.privileged_startx) Unknown key for boolean: EnableTransactions
7/23/09 10:53:14 AM com.apple.launchd[1] (com.apple.aslmanager) Throttling respawn: Will start in 9 seconds
7/23/09 10:53:14 AM com.apple.launchd[1] (com.apple.aslmanager) Throttling respawn: Will start in 9 seconds
7/23/09 10:53:14 AM com.apple.launchd[1] (com.apple.aslmanager) Throttling respawn: Will start in 9 seconds
7/23/09 10:53:16 AM com.apple.launchd[1] (com.apple.UserEventAgent-LoginWindow[74]) Exited: Terminated
7/23/09 10:53:16 AM com.apple.launchd[1] (com.apple.ScreenSharing.server[73]) Exited: Terminated
7/23/09 10:53:16 AM com.apple.launchd[80] (com.apple.AirPortBaseStationAgent) Unknown key for boolean: EnableTransactions
7/23/09 10:53:16 AM com.apple.launchd[80] (org.x.startx) Unknown key for boolean: EnableTransactions
7/23/09 10:53:17 AM com.apple.launchd[80] ([email protected][84]) Exited with exit code: 1
7/23/09 10:55:26 AM com.apple.launchctl.System[2] fsck_hfs: Volume is journaled. No checking performed.
7/23/09 10:55:26 AM com.apple.launchctl.System[2] fsck_hfs: Use the -f option to force checking.
7/23/09 10:55:29 AM com.apple.launchctl.System[2] launchctl: Please convert the following to launchd: /etc/mach_init.d/dashboardadvisoryd.plist
7/23/09 10:55:29 AM com.apple.launchd[1] (com.apple.blued) Unknown key for boolean: EnableTransactions
7/23/09 10:55:29 AM com.apple.launchd[1] (com.apple.usbmuxd) Unknown key for boolean: EnableTransactions
7/23/09 10:55:29 AM com.apple.launchd[1] (org.cups.cups-lpd) Unknown key: SHAuthorizationRight
7/23/09 10:55:29 AM com.apple.launchd[1] (org.cups.cupsd) Unknown key: SHAuthorizationRight
7/23/09 10:55:29 AM com.apple.launchd[1] (org.ntp.ntpd) Unknown key: SHAuthorizationRight
7/23/09 10:55:29 AM com.apple.launchd[1] (org.x.privileged_startx) Unknown key for boolean: EnableTransactions
7/23/09 10:55:39 AM com.apple.launchd[1] (com.apple.UserEventAgent-LoginWindow[72]) Exited: Terminated
7/23/09 10:55:39 AM com.apple.launchd[1] (com.apple.ScreenSharing.server[71]) Exited: Terminated
7/23/09 10:55:41 AM com.apple.launchd[81] (com.apple.AirPortBaseStationAgent) Unknown key for boolean: EnableTransactions
7/23/09 10:55:41 AM com.apple.launchd[81] (org.x.startx) Unknown key for boolean: EnableTransactions
7/23/09 10:55:50 AM com.apple.launchd[81] ([email protected][85]) Exited with exit code: 1
7/23/09 11:17:51 AM com.apple.launchctl.System[2] fsck_hfs: Volume is journaled. No checking performed.
7/23/09 11:17:51 AM com.apple.launchctl.System[2] fsck_hfs: Use the -f option to force checking.
7/23/09 11:17:54 AM com.apple.launchctl.System[2] launchctl: Please convert the following to launchd: /etc/mach_init.d/dashboardadvisoryd.plist
7/23/09 11:17:54 AM com.apple.launchd[1] (com.apple.blued) Unknown key for boolean: EnableTransactions
7/23/09 11:17:54 AM com.apple.launchd[1] (com.apple.usbmuxd) Unknown key for boolean: EnableTransactions
7/23/09 11:17:54 AM com.apple.launchd[1] (org.cups.cups-lpd) Unknown key: SHAuthorizationRight
7/23/09 11:17:54 AM com.apple.launchd[1] (org.cups.cupsd) Unknown key: SHAuthorizationRight
7/23/09 11:17:54 AM com.apple.launchd[1] (org.ntp.ntpd) Unknown key: SHAuthorizationRight
7/23/09 11:17:54 AM com.apple.launchd[1] (org.x.privileged_startx) Unknown key for boolean: EnableTransactions
7/23/09 11:18:10 AM com.apple.launchd[1] (com.apple.UserEventAgent-LoginWindow[75]) Exited: Terminated
7/23/09 11:18:10 AM com.apple.launchd[1] (com.apple.ScreenSharing.server[74]) Exited: Terminated
7/23/09 11:18:10 AM com.apple.launchd[82] (com.apple.AirPortBaseStationAgent) Unknown key for boolean: EnableTransactions
7/23/09 11:18:10 AM com.apple.launchd[82] (org.x.startx) Unknown key for boolean: EnableTransactions
7/23/09 11:18:12 AM com.apple.launchd[82] ([email protected][86]) Exited with exit code: 1
7/23/09 11:19:23 AM [0x0-0x12012].com.apple.Safari[115] Debugger() was called!
7/23/09 11:55:06 AM com.apple.launchctl.System[2] fsck_hfs: Volume is journaled. No checking performed.
7/23/09 11:55:06 AM com.apple.launchctl.System[2] fsck_hfs: Use the -f option to force checking.
7/23/09 11:55:08 AM com.apple.launchctl.System[2] launchctl: Please convert the following to launchd: /etc/mach_init.d/dashboardadvisoryd.plist
7/23/09 11:55:08 AM com.apple.launchd[1] (com.apple.blued) Unknown key for boolean: EnableTransactions
7/23/09 11:55:08 AM com.apple.launchd[1] (com.apple.usbmuxd) Unknown key for boolean: EnableTransactions
7/23/09 11:55:08 AM com.apple.launchd[1] (org.cups.cups-lpd) Unknown key: SHAuthorizationRight
7/23/09 11:55:08 AM com.apple.launchd[1] (org.cups.cupsd) Unknown key: SHAuthorizationRight
7/23/09 11:55:08 AM com.apple.launchd[1] (org.ntp.ntpd) Unknown key: SHAuthorizationRight
7/23/09 11:55:08 AM com.apple.launchd[1] (org.x.privileged_startx) Unknown key for boolean: EnableTransactions
7/23/09 11:55:25 AM com.apple.launchd[1] (com.apple.UserEventAgent-LoginWindow[76]) Exited: Terminated
7/23/09 11:55:25 AM com.apple.launchd[1] (com.apple.ScreenSharing.server[75]) Exited: Terminated
7/23/09 11:55:25 AM com.apple.launchd[82] (com.apple.AirPortBaseStationAgent) Unknown key for boolean: EnableTransactions
7/23/09 11:55:25 AM com.apple.launchd[82] (org.x.startx) Unknown key for boolean: EnableTransactions
7/23/09 11:55:25 AM com.apple.launchd[82] ([email protected][86]) Exited with exit code: 1
7/23/09 12:02:59 PM iMac EFI Firmware Update[140] TMPDIR is set to '/var/folders/GC/GCWw-4RiGJSH3cFjActCtE+TI/-Tmp-/', unsetting it.
7/23/09 12:02:59 PM iMac EFI Firmware Update[140] iMac EFI Firmware Update version 1.4
7/23/09 12:02:59 PM iMac EFI Firmware Update[140] OS version is 10.5.7 build 9J61.
7/23/09 12:02:59 PM iMac EFI Firmware Update[140] No AppleEFINVRAM
7/23/09 12:03:01 PM [0x0-0x19019].com.apple.updaters.imac.efifirmwareupdater14[140] Run the executable in the Contents/MacOS folder with '-h' option to learn about running remotely.

most likely caused by overheating due to video encoding increasing cpu usage (system freezing and shutdowns is a problem with older intel imacs). monitor your internal temps using an app like istat. temporary workaround is to use an fan control app like imacfancontrol and increase the cpu fan speeds. but this does not actually fix the problem which may arise more periodically as the system gets older.
http://www.islayer.com/apps/istatpro/
http://www.derman.com/Download/Special/iMacFanControl.html
there's a very long thread regarding this problem:
http://discussions.apple.com/thread.jspa?threadID=1467276&tstart=0

Since installing OSX 10 my iMac randomly shuts down and restarts. I can not determine why this is happening. Any ideas?

Since installing OSX 10, my iMac randomly shuts down and restarts. I can not determine why this is happening. Any ideas?

1. This is a comment on what you should and should not do to protect yourself from malicious software ("malware") that circulates on the Internet. It does not apply to software, such as keystroke loggers, that may be installed deliberately by an intruder who has hands-on access to the victim's computer. That threat is in a different category, and there's no easy way to defend against it. If you have reason to suspect that you're the target of such an attack, you need expert help.
If you find this comment too long or too technical, read only sections 5, 6, and 10.
OS X now implements three layers of built-in protection specifically against malware, not counting runtime protections such as execute disable, sandboxing, system library randomization, and address space layout randomization that may also guard against other kinds of exploits.
2. All versions of OS X since 10.6.7 have been able to detect known Mac malware in downloaded files, and to block insecure web plugins. This feature is transparent to the user, but internally Apple calls it "XProtect." The malware recognition database is automatically checked for updates once a day; however, you shouldn't rely on it, because the attackers are always at least a day ahead of the defenders.
The following caveats apply to XProtect:
It can be bypassed by some third-party networking software, such as BitTorrent clients and Java applets.
It only applies to software downloaded from the network. Software installed from a CD or other media is not checked.
As new versions of OS X are released, it's not clear whether Apple will indefinitely continue to maintain the XProtect database of older versions such as 10.6. The security of obsolete system versions may eventually be degraded. Security updates to the code of obsolete systems will stop being released at some point, and that may leave them open to other kinds of attack besides malware.
3. Starting with OS X 10.7.5, there has been a second layer of built-in malware protection, designated "Gatekeeper" by Apple. By default, applications and Installer packages downloaded from the network will only run if they're digitally signed by a developer with a certificate issued by Apple. Software certified in this way hasn't necessarily been tested by Apple, but you can be reasonably sure that it hasn't been modified by anyone other than the developer. His identity is known to Apple, so he could be held legally responsible if he distributed malware. That may not mean much if the developer lives in a country with a weak legal system (see below.)
Gatekeeper doesn't depend on a database of known malware. It has, however, the same limitations as XProtect, and in addition the following:
It can easily be disabled or overridden by the user.
A malware attacker could get control of a code-signing certificate under false pretenses, or could simply ignore the consequences of distributing codesigned malware.
An App Store developer could find a way to bypass Apple's oversight, or the oversight could fail due to human error.
For the reasons given above, App Store products, and other applications recognized by Gatekeeper as signed, are safer than others, but they can't be considered absolutely safe. "Sandboxed" applications may prompt for access to private data, such as your contacts, or for access to the network. Think before granting that access. Sandboxing security is based on user input. Never click through any request for authorization without thinking.
4. Starting with OS X 10.8.3, a third layer of protection has been added: a "Malware Removal Tool" (MRT). MRT runs automatically in the background when you update the OS. It checks for, and removes, malware that may have evaded the other protections via a Java exploit (see below.) MRT also runs when you install or update the Apple-supplied Java runtime (but not the Oracle runtime.) Like XProtect, MRT is effective against known threats, but not against unknown ones. It notifies you if it finds malware, but otherwise there's no user interface to MRT.
5. The built-in security features of OS X reduce the risk of malware attack, but they're not absolute protection. The first and best line of defense is always going to be your own intelligence. With the possible exception of Java exploits, all known malware circulating on the Internet that affects a fully-updated installation of OS X 10.6 or later takes the form of so-called "Trojan horses," which can only have an effect if the victim is duped into running them. The threat therefore amounts to a battle of wits between you and the malware attacker. If you're smarter than he thinks you are, you'll win.
That means, in practice, that you always stay within a safe harbor of computing practices. How do you know what is safe?
Any website that prompts you to install a “codec,” “plug-in,” "player," "extractor," or “certificate” that comes from that same site, or an unknown one, is unsafe.
A web operator who tells you that you have a “virus,” or that anything else is wrong with your computer, or that you have won a prize in a contest you never entered, is trying to commit a crime with you as the victim. (Some reputable websites did legitimately warn visitors who were infected with the "DNSChanger" malware. That exception to this rule no longer applies.)
Pirated copies or "cracks" of commercial software, no matter where they come from, are unsafe.
Software of any kind downloaded from a BitTorrent or from a Usenet binary newsgroup is unsafe.
Software that purports to help you do something that's illegal or that infringes copyright, such as saving streamed audio or video for reuse without permission, is unsafe. All YouTube "downloaders" are outside the safe harbor, though not all are necessarily harmful.
Software with a corporate brand, such as Adobe Flash Player, must be downloaded directly from the developer’s website. If it comes from any other source, it's unsafe. For instance, if a web page warns you that Flash is out of date, do not follow an offered link to an update. Go to the Adobe website to download it, if you need it at all.
Even signed applications, no matter what the source, should not be trusted if they do something unexpected, such as asking for permission to access your contacts, your location, or the Internet for no obvious reason.
"FREE WI-FI !!!" networks in public places are unsafe unless you can verify that the network is not a trap (which you probably can't.) Even then, do not download any software or transmit any private information while connected to such a network, regardless of where it seems to come from or go to.
6. Java on the Web (not to be confused with JavaScript, to which it's not related, despite the similarity of the names) is a weak point in the security of any system. Java is, among other things, a platform for running complex applications in a web page, on the client. That was always a bad idea, and Java's developers have proven themselves incapable of implementing it without also creating a portal for malware to enter. Past Java exploits are the closest thing there has ever been to a Windows-style virus affecting OS X. Merely loading a page with malicious Java content could be harmful.
Fortunately, client-side Java on the Web is obsolete and mostly extinct. Only a few outmoded sites still use it. Try to hasten the process of extinction by avoiding those sites, if you have a choice. Forget about playing games or other non-essential uses of Java.
Java is not included in OS X 10.7 and later. Discrete Java installers are distributed by Apple and by Oracle (the developer of Java.) Don't use either one unless you need it. Most people don't. If Java is installed, disable it — not JavaScript — in your browsers.
Regardless of version, experience has shown that Java on the Web can't be trusted. If you must use a Java applet for a task on a specific site, enable Java only for that site in Safari. Never enable Java for a public website that carries third-party advertising. Use it only on well-known, login-protected, secure websites without ads. In Safari 6 or later, you'll see a lock icon in the address bar with the abbreviation "https" when visiting a secure site.
Follow the above guidelines, and you’ll be as safe from malware as you can practically be. The rest of this comment concerns what you should not do to protect yourself.
7. Never install any commercial "anti-virus" or "Internet security" products for the Mac, as they all do more harm than good, if they do any good at all. Any database of known threats is always going to be out of date. Most of the danger is from unknown threats. If you need to be able to detect Windows malware in your files, use one of the free anti-virus products in the Mac App Store — nothing else.
Why shouldn't you use commercial "anti-virus" products?
Their design is predicated on the nonexistent threat that malware may be injected at any time, anywhere in the file system. Malware is downloaded from the network; it doesn't materialize from nowhere.
In order to meet that nonexistent threat, the software modifies or duplicates low-level functions of the operating system, which is a waste of resources and a common cause of instability, bugs, and poor performance.
To recognize malware, the software depends on a database of known threats, which is always at least a day out of date. Most of the real danger comes from highly targeted "zero-day" attacks that are not yet recognized.
By modifying the operating system, the software itself may create weaknesses that could be exploited by malware attackers.
8. An anti-malware product from the App Store, such as "ClamXav," doesn't have these drawbacks. That doesn't mean it's entirely safe. It may report email messages that have "phishing" links in the body, or Windows malware in attachments, as infected files, and offer to delete or move them. Doing so will corrupt the Mail database. The messages should be deleted from within the Mail application.
An anti-virus app is not needed, and should not be relied upon, for protection against OS X malware. It's useful only for detecting Windows malware. Windows malware can't harm you directly (unless, of course, you use Windows.) Just don't pass it on to anyone else.
A Windows malware attachment in email is usually easy to recognize. The file name will often be targeted at people who aren't very bright; for example:
♥♥♥♥♥♥♥♥♥♥♥♥♥♥!!!!!!!H0TBABEZ4U!!!!!!!.AVI♥♥♥♥♥♥♥♥♥♥♥♥♥♥.exe
Anti-virus software may be able to tell you which particular trojan it is, but do you care? In practice, there's seldom a reason to use the software unless an institutional policy requires it.
The ClamXav developer won't try to "upsell" you to a paid version of the product. Other developers may do that. Don't be upsold. For one thing, you should not pay to protect Windows users from the consequences of their choice of computing platform. For another, a paid upgrade from a free app will probably have the disadvantages mentioned in section 7.
9. It seems to be a common belief that the built-in Application Firewall acts as a barrier to infection, or prevents malware from functioning. It does neither. It blocks inbound connections to certain network services you're running, such as file sharing. It's disabled by default and you should leave it that way if you're behind a router on a private home or office network. Activate it only when you're on an untrusted network, for instance a public Wi-Fi hotspot, where you don't want to provide services. Disable any services you don't use in the Sharing preference pane. All are disabled by default.
10. As a Mac user you don't have to live in fear that your computer may be infected every time you install software, read email, or visit a web page. But neither should you assume that you will always be safe from exploitation, no matter what you do. The greatest harm done by security software is precisely its selling point: it makes people feel safe. They may then feel safe enough to take risks from which the software doesn't protect them. Nothing can lessen the need for safe computing practices.

My iMac 27" shuts down please HELP

hello my iMac 27 shuts down at intro or when i trying to set it up ,i think its Fan or HDD but not sure , maybe anyone knows where is a problem ?
iMac

Safe Boot, (holding Shift key down at bootup), run Disk Utility in Applications>Utilities, then highlight your drive, click on Repair Permissions, reboot when it completes.
(Safe boot may stay on the gray radian for a long time, let it go, it's trying to repair the Hard Drive.)
If 10.7.0 or later...
Bootup holding CMD+r, or the Option/alt key to boot from the Restore partition & use Disk Utility from there to Repair the Disk, then Repair Permissions.

My iMac never shuts down properly

My iMac never shuts down properly, sometimes it says that i need to force quit my wireless internet but even when i do that it just has the white screen and I have to hold the power button down to turn it off properly, why is this and how can i stop it

Hello,
One way to test is to 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, Test for problem in Safe Mode...
PS. Safe boot may stay on the gray radian for a long time, let it go, it's trying to repair the Hard Drive
Reboot, test again.
If it only does it in Regular Boot, then it could be some hardware problem like Video card, (Quartz is turned off in Safe Mode), or Airport, or some USB or Firewire device, or 3rd party add-on, Check System Preferences>Accounts (Users & Groups in later OSX versions)>Login Items window to see if it or something relevant is listed. Or an errant process eating up RAM.
Check the System Preferences>Other Row, for 3rd party Pref Panes.
Also look in these if they exist, some are invisible...
/private/var/run/StartupItems
/Library/StartupItems
/System/Library/StartupItems
/System/Library/LaunchDaemons
/Library/LaunchDaemons

Why does my 2009 27" imac keep shutting down?

why does my 2009 27" imac keep shutting down?

Could, also, be failing hard drive , power supply or logic board.
You may have to make an appointment and take your iMac in to Apple or Apple authorized repair center for diagnostics and a repair estimate.
If your iMac has a 1 TB internal hard drive, it maybe a Seagate drive and maybe eligible for free replacement under the Apple Seagate 1 TB internal hard drive replacement program.
If you can get your iMac running, you need to backup all of your data ASAP!. Either backup to optical disc, flash drive/s or purchase an external hard drive for backup. You can use a data cloning program such as CarbonCopyCloner or SuperDuper to make an exact copy of your iMac's internal hard drive.
You can check for eligibility for free hard drive replacement by inputting your iMac's serial number here.
http://www.apple.com/support/imac-harddrive/

Powering down external HDs on an iMac when shut down

Similar Messages

Maybe you are looking for