Apple TV no longer boots

I have the latest Apple TV its worked fine for months then..... When I switched it on the TV showed a picture suggesting that it needed to be plugged into to iTunes via a USB cable. Interesting in that I have never connected th Apple TV directly to iTunes. Now when I connect the Apple TV to the Mac and connect to power it is completely dead.
Any suggestions, if not what is the return policy?
Thanks Andrew

You do not need to have connected to it before it's just a way of resetting the system.
Here are the support pages for you ATV
Apple TV: Unable to restore using iTunes - Apple Support
Apple TV (2nd and 3rd generation): Restoring your Apple TV - Apple Support
Hope this helps.
PJRS

Similar Messages

Macbook no longer boots

Hi,
This past Tuesday night I downloaded the new software updates for my macbook. There was an error during the installation and the updates did not complete. A screen popped up on my macbook which told me that I needed to re-start my macbook. I clicked ok and re-started. After the re-start my macbook will not boot, and remains stuck on the screen which reads "Starting Mac OS X..." I have tried resetting the PRAM and SMC, as well as using the Disk Utility to repair the disk. So far nothing has worked and the macbook remains stuck in boot-limbo...
Has anyone experienced anything similar after installing apple updates? Any help would be appreciated. Bought my macbook in June 2006 and my applecare just expired this past june.
Thanks!

Hi,
i'm following the disscussion since i've notice that my problem is very similar to UptownTopRanking. My macbook freezed when i was uptading (4 uptade at the time including Mac OS X). I shut it down by pressing the power button for few seconds.
And after the computer no longer boots and freeze on the grey screen.
I've tried the solutions proposed on the apple support page but it still not working.
When i saw this topic, i tried to do the same, archive and install the Mac OS X program with my original CD.
The problem is that everytime I'm trying to install it, the program stop after few minutes an ask me to reboot because and error occured. The Error message says : (i'm translating from french)
The installation program didn't succeed to install some files in the "/Volumes/MacintoshHD". Contact the editor of the program to have some help.
And then they ask me to restart the computer, and when i'm trying to intall again, the installation process is still crashing..
Is there anything i can do?

Can no longer boot into Mavericks 10.9.5

My problem is that I can no longer boot into Mavericks 10.9.5 on my mid-2012 Macbook Pro. The problem arose suddenly without any known major changes to my software or hardware. The booting process freezes with the apple visible and the circle below it spinning endlessly. Every several seconds, the display very briefly gets brighter, then the circle starts spinning again and the process repeats itself. It never gets to the user login screen.
Other than keeping various apps up to date, I don't recall any recent major operating system or other major software updates, nor have I made any recent hardware changes. I've searched a multitude of threads and and tried any number of fixes without success. Here's what I've tried so far (and probably a few more that I can't remember): (1) Repaired the startup disk with both Recovery HD -> Disk Utility and single-user mode -> /sbin/fsck -fy; (2) Repaired the startup disk permissions with Recovery HD -> Disk Utility; (3) Reloaded the Mavericks 10.9.5 operating system twice; (4) deleted /Library/Preferences/com.apple.loginwindow.plist; (5) reset PRAM and NVRAM; (6) booted with "D" pressed and ran the Apple hardware test, which ran for about 40 minutes and reported no problems; (7) tried booting from a bootable clone of Mavericks 10.9.5 on an external hard drive, which also failed at the same place with the apple showing and the circle below it spinning endlessly. ***Oddly, I am able to boot from a bootable clone of Mountain Lion on an external hard drive. It's Mavericks that won't boot.***
Here is the part of the system log the repeats itself over and over and seems to correlate with the repeated failed attempts to complete the booting process. Any help would be appreciated beyond words:
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: Server is starting up
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: Session 256 retained (2 references)
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: Session 256 released (1 references)
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: Session 256 retained (2 references)
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: init_page_flip: page flip mode is on
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: Found 54 modes for display 0x00000000 [54, 0]
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: Found 1 modes for display 0x00000000 [1, 0]
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: Found 51 modes for display 0x00000000 [51, 0]
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: Found 1 modes for display 0x00000000 [1, 0]
May 2 12:49:01 --- last message repeated 1 time ---
May 2 12:49:01 SCH-MacBookPro kernel[0]: IOHIDSystem::registerScreenGated: Screen 0 recycled from pid 343
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: mux_initialize: Mode is dynamic
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: Found 54 modes for display 0x00000000 [54, 0]
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: Found 1 modes for display 0x00000000 [1, 0]
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: Found 51 modes for display 0x00000000 [51, 0]
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: Found 1 modes for display 0x00000000 [1, 0]
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: WSMachineUsesNewStyleMirroring: true
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: MPServiceForDisplayDevice: Invalid device alias (0)
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: Display 0x04248378: GL mask 0x10; bounds (0, 0)[2560 x 1440], 51 modes available
Main, Active, on-line, enabled, Vendor 610, Model 9227, S/N 162f0ab5, Unit 4, Rotation 0
UUID 0x3ef17c2fc9ab601507ec022fbd95576c
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: Display 0x003f003d: GL mask 0x2; bounds (0, 0)[4096 x 2160], 2 modes available
off-line, enabled, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 1, Rotation 0
UUID 0xffffffffffffffffffffffffffffffff
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: Display 0x003f0041: GL mask 0x20; bounds (0, 0)[0 x 0], 1 modes available
off-line, enabled, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 5, Rotation 0
UUID 0xffffffffffffffffffffffffffffffff
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: Display 0x003f003f: GL mask 0x8; bounds (0, 0)[0 x 0], 1 modes available
off-line, enabled, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 3, Rotation 0
UUID 0xffffffffffffffffffffffffffffffff
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: Display 0x04280142: GL mask 0x5; bounds (2560, 0)[1680 x 1050], 54 modes available
Active, on-line, enabled, built-in, boot, Vendor 610, Model a005, S/N 0, Unit 2, Rotation 0
UUID 0xde23f9c1cf7b915b2afe83aecee77b54
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: WSSetWindowTransform: Singular matrix
May 2 12:49:01 --- last message repeated 1 time ---
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: Display 0x04248378: GL mask 0x10; bounds (0, 0)[2560 x 1440], 51 modes available
Main, Active, on-line, enabled, Vendor 610, Model 9227, S/N 162f0ab5, Unit 4, Rotation 0
UUID 0x3ef17c2fc9ab601507ec022fbd95576c
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: Display 0x003f003d: GL mask 0x2; bounds (3584, 0)[1 x 1], 2 modes available
off-line, enabled, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 1, Rotation 0
UUID 0xffffffffffffffffffffffffffffffff
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: Display 0x003f0041: GL mask 0x20; bounds (3585, 0)[1 x 1], 1 modes available
off-line, enabled, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 5, Rotation 0
UUID 0xffffffffffffffffffffffffffffffff
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: Display 0x003f003f: GL mask 0x8; bounds (3586, 0)[1 x 1], 1 modes available
off-line, enabled, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 3, Rotation 0
UUID 0xffffffffffffffffffffffffffffffff
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: Display 0x04280142: GL mask 0x5; bounds (435, -1050)[1680 x 1050], 54 modes available
Active, on-line, enabled, built-in, boot, Vendor 610, Model a005, S/N 0, Unit 2, Rotation 0
UUID 0xde23f9c1cf7b915b2afe83aecee77b54
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: CGXPerformInitialDisplayConfiguration
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]:   Display 0x04248378: Unit 4; Vendor 0x610 Model 0x9227 S/N 372181685 Dimensions 23.50 x 13.23; online enabled, Bounds (0,0)[2560 x 1440], Rotation 0, Resolution 1
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]:   Display 0x003f003d: Unit 1; Vendor 0xffffffff Model 0xffffffff S/N -1 Dimensions 0.00 x 0.00; offline enabled, Bounds (3584,0)[1 x 1], Rotation 0, Resolution 1
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]:   Display 0x003f0041: Unit 5; Vendor 0xffffffff Model 0xffffffff S/N -1 Dimensions 0.00 x 0.00; offline enabled, Bounds (3585,0)[1 x 1], Rotation 0, Resolution 1
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]:   Display 0x003f003f: Unit 3; Vendor 0xffffffff Model 0xffffffff S/N -1 Dimensions 0.00 x 0.00; offline enabled, Bounds (3586,0)[1 x 1], Rotation 0, Resolution 1
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]:   Display 0x04280142: Unit 2; Alias(2, 0x5); Vendor 0x610 Model 0xa005 S/N 0 Dimensions 13.03 x 8.15; online enabled built-in, Bounds (435,-1050)[1680 x 1050], Rotation 0, Resolution 1
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: CGXMuxBoot: Boot normal
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: GLCompositor: GL renderer id 0x01024400, GL mask 0x00000003, accelerator 0x00004f2f, unit 0, caps QEX|MIPMAP, vram 1024 MB
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: GLCompositor: GL renderer id 0x01024400, GL mask 0x00000003, texture max 16384, viewport max {16384, 16384}, extensions FPRG|NPOT|GLSL|FLOAT
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: GLCompositor: GL renderer id 0x01022727, GL mask 0x0000003c, accelerator 0x00004907, unit 2, caps QEX|MIPMAP, vram 1024 MB
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: GLCompositor: GL renderer id 0x01022727, GL mask 0x0000003c, texture max 16384, viewport max {16384, 16384}, extensions FPRG|NPOT|GLSL|FLOAT
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: GLCompositor enabled for tile size [256 x 256]
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: CGXGLInitMipMap: mip map mode is on
May 2 12:49:01 SCH-MacBookPro.local loginwindow[353]: **DMPROXY** Found `/System/Library/CoreServices/DMProxy'.
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: Display 0x04248378: Unit 4; ColorProfile { 2, "Thunderbolt Display"}; TransferFormula (1.000000, 1.000000, 1.000000)
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: Display 0x04280142: Unit 2; ColorProfile { 3, "Color LCD"}; TransferTable (256, 12)
May 2 12:49:01 SCH-MacBookPro.local launchctl[356]: launchctl: Dubious permissions on file (skipping): /Library/LaunchAgents/com.adobe.AAM.Updater-1.0.plist
May 2 12:49:01 SCH-MacBookPro.local launchctl[356]: com.apple.findmymacmessenger: Already loaded
May 2 12:49:01 SCH-MacBookPro.local com.apple.SecurityServer[23]: Session 100021 created
May 2 12:49:01 SCH-MacBookPro.local UserEventAgent[357]: Failed to copy info dictionary for bundle /System/Library/UserEventPlugins/alfUIplugin.plugin
May 2 12:49:01 SCH-MacBookPro.local airportd[71]: _doAutoJoin: Already associated to “schuyler”. Bailing on auto-join.
May 2 12:49:01 SCH-MacBookPro.local loginwindow[353]: Setting the initial value of the magsave brightness level 1
May 2 12:49:01 SCH-MacBookPro.local loginwindow[353]: Login Window Started Security Agent
May 2 12:49:01 SCH-MacBookPro.local ManagedClient[362]: ApplePersistence=YES
May 2 12:49:01 SCH-MacBookPro.local SecurityAgent[363]: Failed to create agent mechanism, failing authentication!
May 2 12:49:01 SCH-MacBookPro.local com.apple.authd[84]: engine[353]: error creating mechanism agent
May 2 12:49:01 SCH-MacBookPro.local com.apple.authd[84]: engine[353]: evaluate returned -60008 returning errAuthorizationInternal
May 2 12:49:01 SCH-MacBookPro.local loginwindow[353]: Login Window - Returned from Security Agent
May 2 12:49:01 SCH-MacBookPro.local loginwindow[353]: ERROR | -[LoginApp performAuthPluginRequest:] | AuthorizationRef doesn't have a username. Exiting.
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: CGXRestartSessionWorkspace: session workspace exited for session 256 (on console)
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: Session 256 released (1 references)
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: Session 256 released (0 references)
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: loginwindow connection closed; closing server.
May 2 12:49:03 SCH-MacBookPro com.apple.launchd[1] (com.apple.loginwindow): Throttling respawn: Will start in 1 seconds
May 2 12:49:04 SCH-MacBookPro.local loginwindow[364]: Login Window Application Started
May 2 12:49:04 SCH-MacBookPro com.apple.launchd[1] (com.apple.WindowServer): Throttling respawn: Will start in 7 seconds

Hi
You got a prob I think, if you can boot a windows, MSconfig, startup options might restore the boot files.Only other thing is to try and either load a new windows and let it setup a boot file, or perhaps a win98 startup disk, and fdisk, then set active partiton, which will set an MBR. But that would leave a load of work to do, I think I'd opt for an install of XP, and let it repair existing installation, and make a new boot file.
Hope you don't need the info on disks. If you do, I would install another HDD, load XP, then copy original Disk to save place.
Good luck
Jocko

Can no longer boot to MacOSX after bootcamp install

Hello all, I have an issue to where I can no longer boot into the Mac OSX partition after what appears to be a failed Windows bootcamp install. As I was running the bootcamp assistant process, a reboot occurred and I was greeted with the "No bootable device -- insert boot disk and press any key". I have no idea how to get past this and boot back to OSX.
Things I have tried:
Holding down the "option" key does nothing, even using a USB keyboard
Resetting PRAM (CMD + OPT + P + R) does nothing, even with USB keyboard
I have put in a MAC OSX 10.7 Disk and cannot boot to disk using CMD + C on startup
I also pulled the hard drive out and connected it to another PC and wiped the drive completely. I put it back in the macbook and I am still presented with this error. It seems, even though I get the Mac startup tone, that it is stuck in which ever OS it tried to run previously, that being Windows. Not sure why I am still receiving this error even after wiping the drive completely clean.
As far as hardware goes, I am pretty sure its a late 2010 Alumn. Macbook Pro. I cant get the current model number since I cant boot the OS. Any help is appreciated.

Please reset SMC as well.
You can get the serial number from the back cover and use https://selfsolve.apple.com/agreementWarrantyDynamic.do to find the model.

Apple remote no longer works?!

Hi everyone,
I recently replaced the 120 GB hard drive with a 200 GB hard drive, clean install (no disk imaging or time machine). I did it myself having seen it been done before and relatively knowledgeable about computer hardware. I grounded myself and was careful to put everything back as I saw it.
Everything went well EXCEPT *my Apple Remote no longer works*. The light in the button to open the laptop works fine and my remote works on other computers, but in System Preferences the option to pair the remote doesn't even exist anymore. I understand I probably screwed something up when I opened my laptop up, but I have a few questions first.
My first question is this: *Is there some sort of software setting/diagnostic that I can run to test the connection to the infrared receiver?*
My other question is: *Is there anything special I should know about the infrared receiver hardware? Any known issues, typical problems, or things I should check to make sure everything is connected?*
I've double-checked the connection, the receiver is DEFINITELY connected to the mini-strip (along with the button light).
Thanks,
- Keith

The Hardware Tests (boot from the install DVD and hold d) should show if the receiver isn't working.
In System Preferences/Security is "Disable remote control infrared receiver" checked by any chance, try checking/un-checking it and see if Pair lights up ? (I don't Pair, I leave it to work with any remote as I have three floating about)

After installing Mavericks, my laptop no longer boots.

After installing Mavericks, my laptop no longer boots. How can I restore it using the internet, or get it to start up again?
Thanks in Advance.

If a SMC reset does not restore life, make an appointment at an Apple store genius bar.
http://support.apple.com/kb/HT3964
Ciao.
You might also look at this:
http://support.apple.com/kb/TS1367?viewlocale=en_US
Message was edited by: OGELTHORPE

My PowerBook g4 no longer boots up mouse pointer just keeps spinning, I was getting a message to delete some files as start up disk is nearly full. Would like to reformat mac and reload wanted applications/files

My G4 power book no longer boots up mouse pointer just keeps spinning. I was getting a message the disks pace is nearly full, can only force quit by holding the power button

For the spinning wheel on startup: http://support.apple.com/kb/TS2570
Free up hard drive space: http://thexlab.com/faqs/freeingspace.html

Canon printer driver update - iMac no longer boots up

This morning my Mac displayed an update for my Canon MP560 printer. After the download and install my Mac no longer boots, it just hangs on the white apple logo. I have left it for ages and it rebooted itself but hangs again.

Booted from DVD and did repair permissions. Seems to have sorted it out now.

My trusty Mac LC no longer boots from the HD

I purchased a new Mac LC many years ago and it has served me well until recently when it would no longer boot from the hard drive. When I boot from a Disk Tools floppy, I get some limited success but do not ever hear the HD spin up. The startup chime also does not sound. When used as the boot disk and trying to use the installer option, the program can't find a SCSI drive, only the floppy drive. The 5V & 12V to the HD are right on and a new PRAM battery is installed. I can load and run programs using the floppy drive but that requires a lot of disk swapping. I tried substuting a tested Apple LC HD with the same results and now I suspect the problem is not the HD but is somewhere else. Any help would be gratefully appreciated. Thanks!

Thanks to Jan & Jeff for their quick response to my question. Here is some additional background information which may give you both some more ideas.
The original 40 MB HD was replaced with a 120 MB HD along with an increase in RAM to 4 MB sometime in the first year after I bought the LC. The 40 MB HD was installed in an APS (?) external SCSI box with its own power supply. OS 7 was just becoming available and Apple gave me a set of disks even though OS 6.x was in the computer so I put OS 7 on the external (40 MB) HD. Everything worked great for 20 years although there were periods of intermittent use when I used other computers for work, Internet, and e-mail. I powered up the external HD infrequently but it worked fine the last time I tried it some months back.
Then when I fired the LC up 6 or 7 weeks ago, it would not boot unless I turned the power switch on & off 2 or 3 times in succession then everything functioned normally. Then it would not boot at all even from the external HD.
Now, to address some of your comments and observations:
All connectors, plugs, SIMMs, and socketed RAM devices were removed, examined and replaced. All electrolytic caps showed no signs of leakage or swelling and the PWB looked in its original condition.
The +5, -5 and +12 voltages measured at the power supply connector were within 1%. When I originally thought I had a HD problem, I opened up the 120 MB HD and when trying to boot, the platter would give a slight twitch with no tendency to spin. A friend of a friend (a MAC serviceman) brought a couple of vintage drives SCSI over to try with similar results. The Apple HD I purchased was tested and guaranteed, although wiped clean. It has since been returned. As I said in my original question, the Installer on the floppy could not find a SCSI drive. In all of my efforts I could never get any of the hard drives to spin up.
Although I have a MacMini (OS 10.6.8), I still used the LC because for drawing schematics and floor plans, printing labels, etc., simple is better for me. Is there any hope that I can get my LC working again?
Many thanks for your help and suggestions. len-35

MacBook Pro no longer boots Yosemite

I have had Yosemite installed for about a week and everything seemed to be working fine. For some reason my laptop (MacBook Pro Early 2011) no longer boots. I have managed to install a new copy of OSX, but that didn't fix it. I also ran Disk Utility, but that didn't fix my issue either.
What should be my next step? Luckily I do use Carbon Copy Cloaner, so I have a bootable drive to start from and a restore option.
Thanks

Hello Mr.1977,
Thank you for using Apple Support Communities.
You didn't specify exactly what happens when it fails to boot, but it is just showing a gray screen, this article should be of use:
Mac OS X: Gray screen appears during startup
Regards,
Jeff D.

G4 PowerMac no longer boots from External FireWire Hard Drive

What would cause a G4 PM to no longer boot from an Ext. FW HD that was working fine yesterday and in fact still mounts fine on the desktop..... but when I go into system pref's and attempt to select the ext. HD (and it does show up as an option to boot from since it has an OS in Mac OS Extended Format, Journaled) but after selecting said drive the system simply defaults to the main HD instead and not the external HD I selected within system pref's.???
(I've run apple's disc utilities / First Aid ..... it simply says no repairs were necessary).
The HD in question is a Maxtor 120GB 7200 ATA133 in the following ADS enclosure:
Click Here
Same enclosure works fine with a pionner 110D S-Drive.
Any Suggestions (short of installing the Maxtor hard drive internally which I may have to try anyway)?

MBP 13 + 10.6.2 - forbidden sign + no longer boots

Hi,
After updating to 10.6.2 my MBP 13 no longer boots it hangs in the startup gray screen with a forbidden sign instead of the Apple logo and the spinner spinning forever...
Any ideas ?
Jorge.

Attempting a boot with cmd-v shows:
Lots of:
Can't load kext com.apple.blahblahblah
Kext blahblahblah not found
Failed to load kext blahblahblah (error 0xdc00800e)
Can't load kext blahblahblah - failed to resolve library dependencies.
(same messages repeted many times, for different kexts)
Couldn't alloc class this
Couldn't alloc class that
Still waiting for root device
Still waiting for root device
Still waiting for root device
Still waiting for root device
Still waiting for root device
Still waiting for root device
Jorge.

White Question Mark instead of White Apple comes up when booting up. Why?

White Question Mark instead of White Apple comes up when booting up.
Hi guys,
It happens regularly on booting up and then booting up stops, and I have to turn the iMac off and turn it back on again, sometimes several times, before getting a regular boot up.
What is that about, and how to avoid it?
Thanks,
Raphael

Thanks.
I just found an Apple article dedicated to that called "Gray screen on startup."
Symptoms
Instead of seeing the Finder or the login window after startup, your computer may stop responding and the display may only show a persistent gray screen (you may also see an Apple logo, spinning gear, spinning globe, prohibitory sign, or a folder with a flashing question mark on it). Note: The below steps may not apply if a blue screen appears during start up.
Products Affected
Mac OS X 10.4, Mac OS X 10.6, Mac OS X 10.5
Resolution
Note: Some steps below may reset preference settings or registration settings.
Disconnect, test peripheral devices and network cables
Note: "Peripheral devices" refers to external devices other than what came with your Mac, such as hard drives, printers, or hubs that you connect via a USB or FireWire cable.
Shut down your Mac. If necessary, hold your Mac's power button for several seconds to force it to power down.
Disconnect all peripheral devices such as external hard drives or printers (leave only the display, a keyboard, and mouse connected).
Disconnect any Ethernet cables.
Start up your Mac.
If you can start up this way, one or more of your peripheral devices (or installed software related to the device) is probably causing the gray screen issue. Connect one device, then restart your Mac to test for the issue. Repeat the process until you locate the device at issue. Make sure the device is powered if it needs to be to operate correctly. Check with the manufacturer of the device for support or possible software driver or firmware updates that may be available for the device. Try a different cable with the device if possible (such as a different USB or FireWire cable).
Note: If you have multiple peripheral devices and the issue only occurs when they are all connected, but not when each device is the only peripheral connected, see the Additional Information section below.
If you are using a desktop Mac with a third-party keyboard and/or mouse device, and the issue still occurs, try starting up with an Apple keyboard and mouse connected instead. Try starting with no keyboard and mouse connected, then connect them after start up. Also, try a different USB port on your Mac.
If the gray screen issue persists with no devices connected, go to the next section (with the peripherals still disconnected).
Perform a Safe Boot
Simply performing the Safe Boot may resolve this issue.
Shut down your Mac. If necessary, hold your Mac's power button for several seconds to force it to power down.
Start your Mac, then immediately hold the Shift key. This performs a Safe Boot. Advanced tip: If you want to see the status of a Safe Boot as it progresses, you can hold Shift-Command-V during start up (instead of just Shift).
Note: A Safe Boot takes longer than a typical start up because it includes a disk check and other operations.
If your Mac starts up as expected, immediately try restarting.
If the Safe Boot does not work, or the restart after a successful Safe Boot does not work, go to the next section.
Reset the NVRAM / PRAM
Shut down your Mac. If necessary, hold your Mac's power button for several seconds to force it to power down.
Reset the NVRAM / PRAM.
If the gray screen issue persists, go to the next section.
Start from your Mac OS X Install disc; use Disk Utility
Insert your Mac OS X 10.4 or 10.5 installation disc (if you have discs with both versions, use whichever is closest to the Mac OS X version installed on your Mac; do not use a startup disc which came with a different Mac or which contains an earlier version of Mac OS X).
Shut down your Mac. If necessary, hold your Mac's power button for several seconds to force it to power down.
Start up your Mac while holding the C key to start from the disc.
Once started from the disc, choose Disk Utility from the Utility menu.
Note: If the gray screen issue persists and you can't start from the disc, go to the "Disconnect peripheral devices" section.
In Disk Utility, perform a disk repair of your Mac OS X volume; if no issues are found, perform a permissions repair as well. If issues are found during the disk repair, try repairing again.
After the Disk Utility operations are complete, restart without holding any keys.
If the gray screen issue persists, go to the next section.
Check your cables and power source
Make sure your power cables are secure (especially if you use a desktop Mac). Try a different cable or outlet if possible. If you use a surge protecter, try connecting directly to an outlet as a test.
If you have power-related issues (such as your desktop Mac shutting down or restarting, or room lights dimming when an appliance comes on, consider contacting a certified electrician to check your outlets and electrical wiring).
If the gray screen issue persists, go to the next section.
Remove third-party RAM and internal hardware
Note: Skip this section if only Apple-brand RAM is installed in your Mac.
Remove any non-Apple RAM or other third-party hardware upgrades (such as expansion cards or third-party optical drives or hard drives, if present) to help isolate the issue. This is necessary to get as close as possible to the original factory hardware configuration of your Mac.
If you are not sure which RAM modules or other hardware is Apple or third-party, or if you are not comfortable performing these steps, or if you have a Mac mini, consider contacting an Apple Authorized Service Provider for assistance. Otherwise, perform these steps before going to the next section.
Shut down your Mac. If necessary, hold your Mac's power button for several seconds to force it to power down.
Open your Mac to access the memory slots. Refer to the User Guide that came with your Mac, or search Apple Support Manuals for a PDF copy of your Mac's User Guide.
Remove any third-party RAM that has been installed.
Reinstall the Apple RAM that came with the computer if available. Note that Mac OS X 10.5 requires 512 MB or more of RAM; Mac OS X 10.4 requires 256 MB or more of RAM.
If your Mac starts up with only Apple RAM installed, contact the vendor of your third-party RAM.
If the gray screen issue persists, go to the next section.
Perform an Archive and Install installation of Mac OS X
If the above steps do not resolve the issue, and you can successfully start from your Mac OS X Install disc as noted above:
Insert your Mac OS X 10.4 or 10.5 installation disc (if you have discs with both versions, use whichever is closest to the Mac OS X version installed on your Mac; do not use a startup disc which came with a different Mac or which contains an earlier version of Mac OS X).
Shut down your Mac. If necessary, hold your Mac's power button for several seconds to force it to power down.
Start up your Mac while holding the C key to start from the disc.
Perform an Archive and Install installation (preserving users and network settings).
After installation, if the gray screen issue persists, go to the next section.
Perform an Erase and Install installation of Mac OS X as a last resort
Important: You should only perform this step after trying all of the above steps. This process will erase all files from your Mac OS X volume. If possible, back up important files first, or use Time Machine. You may be able to connect your Mac to another Mac with a FireWire cable and FireWire target disk mode, in order to try to manually back up files. Alternatively, you may wish to make an appointment with a Mac Genius at an Apple store, or contact an Apple Authorized Service Provider for assistance.
To erase your Mac OS X volume and reinstall Mac OS X:
Insert your Mac OS X 10.4 or 10.5 installation disc.
Shut down your Mac. If necessary, hold your Mac's power button for several seconds to force it to power down.
Startup your Mac while holding the C key to start from the disc.
Perform an Erase and Install installation of Mac OS X.
After installing, starting from your Mac OS X volume, and verifying the issue is resolved, you should use Software Update to update to the latest available version of Mac OS X.
Additional Information
If the issue persists after you follow the above steps, you may wish to make an appointment with a Mac Genius at an Apple store, contact AppleCare via phone, or contact an Apple Authorized Service Provider for assistance.
If the issue only occurs when multiple peripheral devices are connected
If a gray screen appears during start up only when several peripheral devices (that is, USB and/or FireWire devices) are connected, and you don't want to have only one device connected at a time, the issue may be caused by a combination of the peripheral devices.
To illustrate this hypothetically, you may have three USB devices, which we'll call "A", "B", and "C". The issue may be that peripherals A and C have a conflict of some sort, and a gray screen only appears if they both are connected, but not if each one is connected separately. In the above "Disconnect, test peripheral devices and network cables" section you may have inferred that you have an issue only with device C because it was added after A. To avoid an inaccurate analysis, connect device C to your computer with no other devices. If your Mac has the startup issue with only device C connected, then you know it is the source of the issue. However if your Mac starts up, you have a conflict of devices to work out. To do this add the other devices one at a time with device C connected until your startup issue occurs (restart after adding one device). Repeat this process until you have just the minimum set of devices to produce your startup issue.
What can you do?
You should make sure each device has the latest firmware installed if applicable--check with the manufacturer for more information. You should also check for the latest driver versions, and if necessary install them while started in Safe Mode per above.
If any of the devices requires a separate power source, be sure that power is connected to the device (for example, even if a device appears to be powered when connected via USB without the power cable, connect its power cable).
Try different USB or FireWire cables with each device, as applicable.
If you have a device similar to one of the conflicting devices, try replacing it with another one.
Contact each device manufacturer or the materials that came with the device. for more support information or, if needed, service options.

[SOLVED] After pacman update, system no longer boots

Updated pacman packages, and half-way through the upgrade proces fails (it mentions not being able to find package-control). Upon investigating, I notice no programs are working. I ls /usr/bin and it is empty! In a panic, I restart the machine, and it no longer boots up.
My boot is on sda3 and /root is sda5.
When bash starts up, it loads the kernel fine, and then after a second it panics and exclaims: "No init found. Try passing init=bootarg".
I load up my trusty Arch livecd and fsck the partitions. Fsck claims both partitions are clean. I am able to mount them and examine the file structure: all files look like they are there. I then try to chroot the mounted partition (sda5, my /root), and get the error that "/bin/bash" is not found, even though it is there in the correct directory. Not sure what to do now.
My grub entry, which has always worked fine prior to this:
legacy_kernel '/linux344-ck' 'acpi_osi=Linux' 'root=/dev/sda5' 'rootfstype=ext4' 'init=/sbin/init' 'pcie_aspm=force' 'acpi_backlight=vendor' 'i915.i915_enable_rc6=1' 'i915.i915_enable_fbc=1' 'i915.lvds_downclock=1' 'ipv6.disable=1' 'i915.semaphores=1' 'modprobe.blacklist=bluetooth,uvcvideo' 'ro'
legacy_initrd '/initramfs-linux-fallback.img' '/initramfs-linux-fallback.img'
UPDATE: solved issue. I didn't read the news. Upgrading via pacman broke my system because of this. Now I know! System is running smooth again.
Last edited by corruptz0r (2012-07-15 20:26:53)

Huh. I guess the problem was a couple of stale and crusty {,f}getty .service files, and an obsolete slim.service file I created a while back.
Removing them fixed my problem, although tty1 still shows boot messages (not a problem, and may not even be "new" behaviour)
Cheers Tomegun.

Z77A-GD65 no longer boots with 4 RAM modules

I had 4 x 8GB Cosair Vengeance LP that used to work fine, but no longer boots into Windows with 4 but only with 2 RAM modules. Any help in solving the issue would be appreciated. ( I need 32 GB as I run many virtual machines )
The 4 modules worked fine for few months until couple weeks ago, when I saw issues with booting into Windows 7. The workaround was to "warm up" by leaving the PC in BIOS for about 5 minutes and it would boot fine. Since couple days ago, it would POST but not boot into Windows or into live Linux on USB, so I started troubleshooting with bare bones first ( MB, CPU, 1 RAM, PS ) and then starting adding more and more components until I found that 1 and 2 RAM modules worked in either black or blue rail but with 4 RAM modules, it will POST, but not boot at all into either USB based live system or into Windows 7.
Memtest with 2 separate sets of modules pass with flying colors. Mixing the sets work fine too, but add 2nd set (i.e. 4 modules) and it fails to boot. I am leaning more toward believing the issue is with the MB than with the RAM since mixing them doesn't throw any memory error.
Any suggestion on how to check if it's the RAM or MB ?

Quote from: PirateDog on 25-November-13, 00:23:30
If these were 2 kits mixed, ...
These were 2 mixed kits.
Quote from: XFM on 25-November-13, 07:01:42
What voltage is the RAM running? A slight bump up in voltage might help.
As to voltage, I started with standard 1.5 and then incrementally upped it to 1.65v. At 1.6v and above, it does boot into Windows, but intermittently goes into BSOD... Works perfect with 1.5v with 2 RAM modules.
I'll save the money for next build instead of going for 32GB kit. ... guess I'll live with 16GB for now.
Thank you all for the advice.

Apple TV no longer boots

Similar Messages

Maybe you are looking for