Want to highlight a helpful answer? Upvote!
Did someone help you, or did an answer or User Tip resolve your issue? Upvote by selecting the upvote arrow. Your feedback helps others! Learn more about when to upvote >
Did someone help you, or did an answer or User Tip resolve your issue? Upvote by selecting the upvote arrow. Your feedback helps others! Learn more about when to upvote >
My iMac 27 late 2012 is running the latest version of Maverics.
since vour weeks now the macine stops during boot wit the following line: (taken from verbose boot)
pci pause: sdxc
I can boot from a external device just fine and ran Apple disgnostics and internet recovery since I did assume a problem with internal hard drive.
however the last line during verbose boot refers to the SD slot. this slot is unused ever since.
any idea what is going wrong here?
So far I tried a lot basic trouble shootinhg. Reset SMC, PR, repartition and formatting of the disk, new installation with import of my data, new installation without migration assistant.
the machine still hangs every now and then.
Inserting a SMD card into rhe slot lets the machine repeat the message : PCI Pause: SDXC but nothing more. The machine isnt booting.
I have the exact same problem, with the most up-to-date iMac after 2 month of usage. Any help would be really appreciated!
Currently I am on the last try. Complete reinstallation without migration. I kept my files on a backup and imported critical data manually, but no programs.
No problem since but that doesn't mean anything. I will see in a few weeks if that problem occurs. In that case the machine goes to Apple for repair.
Alright, you might try to consider what I did so.
As we are speaking, I managed to boot on it by removing the fsck at the boot :
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.
For the record, I tried without success :
Credit to acme.mail.order (http://hintsforums.macworld.com/showthread.php?p=727403) for his tip.
Hope it will help!
Not sure if this helps, however I seemed to have this same issue. Isolated it to an external USB HDD, in fact, the one that comes with the iMac as its primary. I have it in a USB3 chassis. Unplugged it, it would boot fine, plugged it in, slow boot. I realized the chassis was powered on (power button was switched to on), even though it wasn't spinning or anything. I guess I'm used to just unmounting the drive and not powering it off. Turned it off, booted computer, boom, no problem. Not sure if that fix is specific to me, but I thought I'd throw it out there.
Problem solved!
I installed Little Snitch a while ago, and I just noticed that during the boot phase, Little Snitch was launched with something like this (by memory) :
LS (4092) : Little Snitch started
So, once I achieved to boot on my computer, I just uninstalled Little Snitch, and no problem ever since that! Yay! 😎
Hope this will help someone!
i have the same problem since tree days ago, i tried the same things that you hegel and nothing (reset SMC, pram, repartition and formatting of the disk, new installation with import of my data, new installation without migration assistan), any help will be appreciated
Pd: i am from Latin America my English is very bad
I had Litle Snitch instaled too, but uninstalled some months ago. However since a clean install worked while my backup failed it is possible that there was sonething left that wasnt uninstalled.
i never had little Snitch installed, at lest for me, litles Snitch comes installedas default ?
No, it is a third party firewall that monitors communication from you machine to other servers. It is sometime troubling how reckless developer send data to other server and Little Snitch can control that.
It is not proven that Little Snitch did cause any problems. Possible some user files where simply defective.
Either way, no problems since a clean install and manually copying over of my data. No bigy with iCloud.
how i do to install manually the mac OS, i re-install the software whit the OS X Recovery Disk Assistant and the problem persist
You backup your Data first. You can use an external Drive or partition. With Carbon Copy Cloner you get a bootable copy of the system as fallback, but just copying your data to a stick or drive will do. Sadly Time Capsule has a chance to copy the error. (did it in my case)
When you have your data secured reboot the mac an enter recovery mode. Format the drive and install a fresh copy of OS X.
When the installation is done, the migration assistant will offer you to copy your data and programs. Skip that step for now.
Just create a new user and see if everything works and if the error is gone.
If no, you should see a service provider for help.
If yes, you can copy your stuff back. If did this three times. First time I just reinstalled like you. The second time I did use the migration assistant and ended up with the same error again. So I had to wipe the drive and install the os again. This time I just copied some programs manually back. Same with my user folder. Basically everything except the library. Since that I have no problems for a month now. I never went into find out with try and error the exact file that caused the problem. Just not worth the time.
In your case just a reinstall of the system without formatting the drive didn't work already. That means the problem is somewhere in your user folder. I doubt the migration assistant will skip the problematic file, but worth a shoot if you can invest the time.
Bottom line:
A nacked OS X installation without any copied userdata should work always flawless.
If not check with a service provider to find the problem.
Hope that helps
Yesterday evening I had the same problem.
Brand new iMacs (arrived 2 days ago) with Mavericks preinstalled. I had imported user folders from another machine (no programs or common files), set up Bootcamp, and installed the first programs (PS Elements 10, Lightroom 5 + VSCO Plugins, Spyder4Pro). Went into WIndows to install Spyder4Pro there as well, and when I returned, the machine was stuck in boot. Verbose mode, "pci pause: SDXC". HW diagnostics showed no problem, so after some research, I decided to restore my system from a time machine back up I had taken before installling Spyder4Pro (but after installing Elements and Lightroom). That helped.
Now, one could assume the Spyder4Pro software caused the issue somehow, but no. I installed it again, exactly the same way, and the problem did not reoccur.
On one hand, that's good (I like to calibrate my screen), on the other hand, it means the issue can happen anytime again, because basically, I have no clue what caused it. 😟
I googled a bit and it seems "PCI pause" is a device driver feature related to the hot-plug-capabilities of Thunderbolt. When a new device is plugged into Thunderbolt, it can happen that the OS needs to rearrange the address spaces assigned to the various PCIe device drivers, so it sends them all a request to pause while it does that. Of course I did not add any devices while booting, so the "pci pause" in question must be something that happens while the OS builds the very first PCIe device tree. Maybe (and these are just wild guesses) a bug in the SDXC device driver, or a sporadic HW fault of the SDXC reader, or something bad in the OS. Anyway, I strongly suspect reinstalling the OS just masks the bug and does not completely avoid it.
Of course, this would be a question for the actual developers. Is there any way to get them engaged to look into the issue?
"Bottom line:
A nacked OS X installation without any copied userdata should work always flawless.
If not check with a service provider to find the problem."
Yes, but what if there is a bug in the device driver, or the OS which only shows after some (as such, completely legal) configuration changes, or maybe even randomly some time after the reinstall.? No support from Apple in that case? I would hope not...
(Anyone who still remembers the famous Patriot bug? - as long as you rebooted every few hours there was no problem at all...)
<Post Edited By Host>
Which poves my point. A system shold work flawless directly after boot.
iMac 27 pci pause: sdxc
