Issue
So, your SuperDrive has decided to stop working (perhaps after upgrading to Mountain Lion, Lion, or Snow Leopard)? Maybe it spits out discs after spinning them up, making some noise, but not actually doing anything? or perhaps it simply doesn’t read discs like it should? Well, here are the steps to get your SuperDrive working again:
Steps to Fix the Issue
-
Clean the SuperDrive’s slot with compressed gas
You’ll want to perform this step first. Why? Because if you spend two hours attempting to get your drive working only to discover that a dozen seconds or so with a can of compressed gas would have fixed your issue, you’ll be a bit disappointed with yourself. What you’ll want to do with the compressed gas is fairly simple: Stick the end of the nozzle/tube into the SuperDrive’s slot and then spray compressed gas (being careful to keep the can right side up, as the liquid inside the can could damage the SuperDrive’s internals) the full length of the slot; next, spray the compressed gas in short burst every centimeter or so along the SuperDrive’s slow (again putting the nozzle/tube just inside the slot’s covering).Didn’t fix your issue? Try 2. -
Reset the NVRAM/PRAM and SMC
Some settings on your Mac are stored in NVRAM or PRAM, which your Mac uses will depend on its model, but you can find reset instructions for both here: About NVRAM and PRAM. In addition to the NVRAM/PRAM, your Mac has a system management controller (SMC), which stores some settings related to system hardware. Instructions for resetting to SMC can be found here: Intel-based Macs: Resetting the System Management Controller (SMC)Didn’t fix your issue? Try 3. -
Delete the Finder’s preference files
Some people have reported successfully fixing SuperDrive issues by deleting the Finder’s preference files (don’t worry, the Finder will automatically make new ones). You’ll want to delete two files: “com.apple.finder.plist” and “com.apple.sidebarlists.plist”. Both of these files are located in Users > [Your User] > Library > Preferences. You can choose whether you want to move the files to a new location (or simply append “.old” or something similar to the file names) or delete them, either way should work. Once you’ve deleted both preference files (n.b., the “.sidebarlists” one might not exist, that isn’t necessarily a problem), you’ll need to relaunch Finder. You can accomplish this by restarting your Mac or by bringing up the force quit menu with Command + Option + Esc (if you go this route, simply select Finder and click Relaunch; n.b., Finder will probably be at the bottom of the list).Didn’t fix your issue? Try 4. -
Visit an Apple Store
At this point, you are probably facing a hardware issue. Take your computer in to an Apple Store and have one of Apple’s service technicians look at the machine. If they determine that you do, in fact, have a hardware issue, get them to give you a quote on replacement/repair. Take this quote and get a comparison quote from an Apple-authorized service provider. The second quote will probably be lower.Your other option, of course, is to purchase an external DVD burner. Personally, I use this one: OWC Mercury Pro 14X Blu-ray Burner+SuperMultiDrive FW800/400/USB2/eSATA +Toast 11 Titanium from Other World Computing and could not be more pleased with its performance.
Original Article Contents
This article was updated to include more extensive troubleshooting/repair steps. The original content of the article can be seen by expanding this section:
Background and Issue
Over the past day or two I’ve been configuring an older MacBook Pro (5,3) to quintuple boot (i.e., OS X 10.8 Mountain Lion, Windows XP, Windows 7, Windows 8, and Ubuntu). Along the way, I’ve run into issues with the SuperDrive ejecting CDs/DVDs after spinning up and making the usual “I’m trying to read the disc” noises. Unfortunately, I didn’t happen to resort to my networking knowledge and check Layer 1 (i.e., the physical hardware) first. So, after wasting time attempting to see if there was a software issue or other problem and then attempting to boot from USB flash drives, USB hard drives, and a few other methods, I found a very simple solution: compressed gas.
Short Answer
If your SuperDrive is ejecting CDs/DVDs, try cleaning it with compressed gas. The issue may be as simple as dust on the lens. Just grab a can of compressed gas and spray it into the slot on the SuperDrive (be careful to keep it right side up as the liquid contents of the can could potentially damage your SuperDrive’s internals). First, go the length of the drive’s slot spraying compressed gas into the slot; then, spray compressed gas into the slot in short bursts every centimeter or so.
Additional Steps
Once you’ve completed this simple cleaning procedure, your drive should be able to read CDs/DVDs again without problem. If this doesn’t fix your issue, then you’re left with two other possibilities: 1. it’s a software (e.g., driver) issue or 2. it’s a hardware issue. As a software issue is very unlikely on a Mac (for a number of reasons), the latter is, unfortunately, likely the culprit if cleaning doesn’t resolve your issue. Your best bet is to take the computer to an Apple Store and get them to confirm that there is a hardware issue. Once they’ve confirmed that your SuperDrive is defective, see how much it would cost for them to replace it (perhaps you’re in luck and it’s still within warranty). After you have their quote, go get a quote from an Apple-authorized service provider. More likely than not, the authorized service provider will be the less expensive route.
4 Responses to “How to Fix a MacBook (Pro) SuperDrive Which Continually Ejects Discs”
“as a software issue is very unlikely on a Mac”
ha ha!
There are countless Apple forum reports by people like me of SuperDrives not working with Mountain Lion
In my case, a virtually new MacBoo Pro Retina with out-of-the-box SuperDrive
See
https://discussions.apple.com/thread/4183278?start=45&tstart=0
https://discussions.apple.com/thread/4150905?start=0&tstart=0
…and many others
I’m starting to regret switching from Windows to Mac
Countless reports on forums does not automatically equal a software issue. Most computer issues reported on such forums come from users who are relatively inexperienced with the hardware/software they are using.
Reports related to slot-loading drives (and, to be fair, regular tray-type drives, too) spitting out discs have pretty much been routinely popping up on forums and other such sites since the drives were introduced. The issue is not limited to Macs and is usually solvable with a few relatively simple troubleshooting steps.
As I see this article is getting some search engine traffic, I’ll go ahead and expand on the troubleshooting steps a bit in a day or two (e.g., I’ll add information shout resetting the SMC and PRAM, when applicable).
Hi Corey if you read the forums, you’ll see that there are many, many posts by experienced people reporting that 1) their SuperDrive was working 100%, the 2) they upgraded to Mountain Lion, and it immediately stopped working. Several report that Apple told them it was a ML problem that ‘may be fixed around October 2013″
I’ve read through (at least a portion) of a number of the threads and it seems like different people have found different solutions to this particular issue. While some of them could be considered a software issue (e.g., the Finder preferences fix, supra), the solutions do not seem consistent across machines/setups. While it does seem highly coincidental that many of the issues arise immediately after an OS upgrade (notably, these reports have not been contained only to Mountain Lion upgrades), it does not necessarily mean that there is an issue with the OS. More likely than not, upgrades are exposing underlying issues with preference or other files on the affected machines (most likely by attempting to make updates to the already corrupt or otherwise affected preference files).
At any rate, I have added additional troubleshooting/repair steps to this article. Let me know if your machine is still experiencing the issue after you’ve gone through the first three steps listed, supra. It would be interesting to see what fixes the issue if not the steps I’ve listed.