13" MBP Stuck at startup (II)

My sons MacBook Pro (13-inch, Mid 2012)

is tuck at start up has the spinning daisy.

I have tried to reinstall OS but it continually says there is an error and wont allow it to happen.


When I use CMD +Option+R - and try to reinstall OS - I get this Message.

"You can't upgrade this version of OS X because a newer version is installed"

I found that the HD has 10.9.3 on it.

When I attempt safe start up - it still hangs up -

I re-started in safe and held down shift-command-V and at the very end when it stopped showing me information on progress it reached

"BootCacheControl: Unable to to open / var/db/BootCache.playlist: 2 No such file or directory" next line "pci pause: SDXC"

MacBook Pro, OS X Mavericks (10.9.3)

Posted on Jul 17, 2014 7:25 AM

Reply
14 replies

Jul 17, 2014 3:27 PM in response to apiselli

Take each of these steps that you haven't already tried. Stop when the problem is resolved.

Step 1

The first step in dealing with a startup failure is to secure the data. If you want to preserve the contents of the startup drive, and you don't already have at least one current backup, you must try to back up now, before you do anything else. It may or may not be possible. If you don't care about the data that has changed since the last backup, you can skip this step.


There are several ways to back up a Mac that is unable to start. You need an external hard drive to hold the backup data.

a. Start up from the Recovery partition, or from a local Time Machine backup volume (option key at startup.) When the OS X Utilities screen appears, launch Disk Utility and follow the instructions in this support article, under “Instructions for backing up to an external hard disk via Disk Utility.” The article refers to starting up from a DVD, but the procedure in Recovery mode is the same. You don't need a DVD if you're running OS X 10.7 or later.

b. If Step 1a fails because of disk errors, and no other Mac is available, then you may be able to salvage some of your files by copying them in the Finder. If you already have an external drive with OS X installed, start up from it. Otherwise, if you have Internet access, follow the instructions on this page to prepare the external drive and install OS X on it. You'll use the Recovery installer, rather than downloading it from the App Store.

c. If you have access to a working Mac, and both it and the non-working Mac have FireWire or Thunderbolt ports, start the non-working Mac in target disk mode. Use the working Mac to copy the data to another drive. This technique won't work with USB, Ethernet, Wi-Fi, or Bluetooth.

d. If the internal drive of the non-working Mac is user-replaceable, remove it and mount it in an external enclosure or drive dock. Use another Mac to copy the data.

Step 2

If the startup process stops at a blank gray screen with no Apple logo or spinning "daisy wheel," then the startup volume may be full. If you had previously seen warnings of low disk space, this is almost certainly the case. You might be able to start up in safe mode even though you can't start up normally. Otherwise, start up from an external drive, or else use the technique in Step 1b, 1c, or 1d to mount the internal drive and delete some files. According to Apple documentation, you need at least 9 GB of available space on the startup volume (as shown in the Finder Info window) for normal operation.

Step 3

Sometimes a startup failure can be resolved by resetting the NVRAM.

Step 4

If you use a wireless keyboard, trackpad, or mouse, replace or recharge the batteries. The battery level shown in the Bluetooth menu item may not be accurate.

Step 5

If there's a built-in optical drive, a disc may be stuck in it. Follow these instructions to eject it.

Step 6

Press and hold the power button until the power shuts off. Disconnect all wired peripherals except those needed to start up, and remove all aftermarket expansion cards. Use a different keyboard and/or mouse, if those devices are wired. If you can start up now, one of the devices you disconnected, or a combination of them, is causing the problem. Finding out which one is a process of elimination.

Step 7

If you've started from an external storage device, make sure that the internal startup volume is selected in the Startup Disk pane of System Preferences.

Start up in safe mode. Note: If FileVault is enabled, or if a firmware password is set, or if the startup volume is a Fusion Drive or a software RAID, you can’t do this. Post for further instructions.

Safe mode is much slower to start and run than normal, and some things won’t work at all, including wireless networking on certain Macs.

The login screen appears even if you usually log in automatically. You must know the login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.

When you start up in safe mode, it's normal to see a dark gray progress bar on a light gray background. If the progress bar gets stuck for more than a few minutes, or if the system shuts down automatically while the progress bar is displayed, the startup volume is corrupt and the drive is probably malfunctioning. In that case, go to Step 11. If you ever have another problem with the drive, replace it immediately.


If you can start and log in in safe mode, empty the Trash, and then open the Finder Info window on the startup volume ("Macintosh HD," unless you gave it a different name.) Check that you have at least 9 GB of available space, as shown in the window. If you don't, copy as many files as necessary to another volume (not another folder on the same volume) and delete the originals. Deletion isn't complete until you empty the Trash again. Do this until the available space is more than 9 GB. Then restart as usual (i.e., not in safe mode.)


If the startup process hangs again, the problem is likely caused by a third-party system modification that you installed. Post for further instructions.

Step 8


Launch Disk Utility in Recovery mode (see Step 1.) Select the startup volume, then run Repair Disk. If any problems are found, repeat until clear. If Disk Utility reports that the volume can't be repaired, the drive has malfunctioned and should be replaced. You might choose to tolerate one such malfunction in the life of the drive. In that case, erase the volume and restore from a backup. If the same thing ever happens again, replace the drive immediately.


This is one of the rare situations in which you should also run Repair Permissions, ignoring the false warnings it may produce. Look for the line "Permissions repair complete" at the end of the output. Then restart as usual.

Step 9

If the startup device is an aftermarket SSD, it may need a firmware update and/or a forced "garbage collection." Instructions for doing this with a Crucial-branded SSD were posted here. Some of those instructions may apply to other brands of SSD, but you should check with the vendor's tech support.

Step 10

Reinstall the OS. If the Mac was upgraded from an older version of OS X, you’ll need the Apple ID and password you used to upgrade.

Step 11

Do as in Step 9, but this time erase the startup volume in Disk Utility before installing. The system should automatically restart into the Setup Assistant. Follow the prompts to transfer the data from a Time Machine or other backup.

Step 12


This step applies only to models that have a logic-board ("PRAM") battery: all Mac Pro's and some others (not current models.) Both desktop and portable Macs used to have such a battery. The logic-board battery, if there is one, is separate from the main battery of a portable. A dead logic-board battery can cause a startup failure. Typically the failure will be preceded by loss of the settings for the startup disk and system clock. See the user manual for replacement instructions. You may have to take the machine to a service provider to have the battery replaced.

Step 13


If you get this far, you're probably dealing with a hardware fault. Make a "Genius" appointment at an Apple Store, or go to another authorized service provider.

Sep 7, 2014 8:54 AM in response to Linc Davis

Hi All,


Exact same problem today with my machine just this morning. Last thing on verbose boot was "pci pause: SDXC". No idea why this started happening. If it matters this is a new iMac with a Fusion Drive. Zapping parameter ram and safe boot did not help. The funny thing is the problem does not appear to be disk related. I booted into single user mode and run fsck and it said the drive was fine no errors. Disc Utility reported the same "OK" earlier this week. I do have one external Thunderbolt drive that I use for backups but it does not seem to impact anything if it is plugged in at boot or not.


I was finally able to boot by booting into single user mode (command-s) and then manually running /sbin/fsck -fy on the HD (and it said all was fine). Used a trick to then disable fsck for the next boot, and performed shutdown -r -n now and simply waited about 10 minutes and finally got things to boot. I re-enabled fsck and re-ran it and Disk Utility and both report no problems at all! So either this Fusion drive hardware is flakey or something else hardware related is going on as something is interfering with the bootup sequence and it is not related to third party software as safe boot did nothing for me.


If it matters, I have also been having little used applications being deleted from my Mac upon wake from sleep!!! Can't find anything about this on the boards. Mavericks seems to have a bug in wake from sleep than combines with Fusion drives and allowing the disk to actually sleep. If you look in the console and log messages, you can see messages about each and every application that was "mysteriously deleted" being little used. My guess is the software/firmware in the Fusion drive detects little used applications and moves them to the none-SD part of the Fusion drive but it is in sleep mode and the actual write is never done, but the copy on the SD side is still being deleted and then wake from sleep happens. Never allowing the drive to sleep made these "disappearing little used Applications problem" go completely away.

These new iMacs with Fusion drives are not exactly solid under Mavericks. Not sure what to do other than keep making backups on my eternal thunderbolt drive until someone can figure out what is going on hardware-wize.


Open to any further diagnostic suggestions. If fsck and Disc Utilities both say the disk is fine, I am not sure how to proceed. Ideas welcome.

Thanks,

Kevin

Sep 8, 2014 7:46 PM in response to Csound1

Hi,

Your joking right? Did you even read the post? Exact same error and exact same symptoms. It points out that that common denominator may be the Thunderbolt support or it may even be just software related (forgetting to properly mask hardware interrupts during critical kernel start-up) and that the problem is NOT tied to just one type of hardware platform. It also shares a technique for getting around the no boot issue that worked for me and others.

Sep 20, 2014 7:29 AM in response to apiselli

I have absolutely the same problem with my MacBookPro 15" here: MacBook Pro Retina Mid 2012 (MacBookPro10,1 NVIDIA GPU)

I bought this MBPro used over eBay and after I got it the seller checked it again and told me it was defect with a black screen.
He brought it to repair in germany and a new mainboard was installed - the MBPro run ok with OSX 10.8 as far I noticed.


So I upgraded to 10.9.5 and install my system from a timemachine backup and now I have the same pci pause: sdxc error :-(

Oct 7, 2014 8:00 AM in response to Technobilder

Hi


I got this message on my same problem!


Perhaps it helps you.


Hi,


I used "That Guys" solution from earlier in this thread and once I had it booting, no problems since. Here are the main points from That Guys post.


1. Enter the Single-user boot mode (cmd+s at launch)

2. Type those lines :

root# /sbin/mount -uw /

root# mv /sbin/fsck /sbin/fsck.off
root# cp /usr/bin/true /sbin/fsck

3. Restart your computer, enter verbose mode (hold cmd+v)

4. Wait for it, it took 2 min to boot (instead of 1h of wasteful wait i had experienced), after being stuck at pci pause : sdxc

5. Now, you might consider putting fsck back.


And to put it back you do the following after everything boots properly.


root# cp /sbin/fsck.off /sbin/fsck


Since I have done this, no problems since. It took my computer about 20-25 minutes to finally boot in his step 4 not the 2 minutes he quoted. I did verify that the fsck run on the boot drive said everything was okay (or run DiskUtility). One other thing I changed was to put fresh batteries in my mouse and keyboard just in case low voltage was causing issues with my wireless mouse/keyboard causing flakey interrupts.


Please give "That Guys" solution a try as it worked for me and I have been rock solid since.


Hope this helps,


Kevin

Reply Like (0)

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

13" MBP Stuck at startup (II)

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.