You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

superdrive not loading discs after upgrading to el capitan

After upgrading to el capitan, my superdrive no longer loads discs into the tray.

I have turned off and restarted my mac and no improvement.


Any further suggestions?

MacBook Pro with Retina display, OS X El Capitan (10.11)

Posted on Oct 3, 2015 1:37 PM

Reply
42 replies

Oct 5, 2015 1:08 PM in response to RyLodz

Same problem here.


Superdrive connected to 27in iMac via USB port on connected dual Thunderbolt screen. Superdrive shows up in System Information but won't load discs.


Have tried SMC reset and PRAM reset - doesn't resolve issue.


Have connected the drive via USB port on second Thunderbolt screen connected to a MacBook Pro that is still running Yosemite and it works fine!


Definitely an El Capitan problem.

Oct 10, 2015 11:44 AM in response to iPadHeadache

This issue isn't really solved. Yes, I can restart my MBP with the SuperDrive connected, and it will work. But it should be recognized and accept disks even if it's connected after boot -- just as it did with Yosemite. I spoke with Apple several times, and engineers took a look at my logs. They thought there was a conflict with Logitech's Control Center, so I uninstalled it. But that did not solve the problem.

Oct 18, 2015 12:25 PM in response to RyLodz

Hello,

the problem is the lack of record "mbasd = 1" in the system. To solve this problem you need to open the "/Library/Preferences/SystemConfiguration/com.apple.Boot.plist." and edit "apple.Boot.plist" - Text Edit is sufficient.

The key "Kernel Flags" is empty. You must add between start and end string "mbasd = 1" and the problem is resolved.

Oh one more problem: to manipulate the system, you must be "root" user and is not the end, because in this version of OSX is active

the "System Integrity Protection" or SIP for short. This is actually a way for Apple to push again the limits of the safety of your machine, prohibiting all users (including God Root) touching some critics judged files.

So even root will not have the right to go to copy any document in the following folders:

/ System

/ bin

/ usr

/ sbin

The idea behind this, is obviously to protect the user against any possible threat, a risk that weighs increasingly heavy with the growing popularity of OS X. After the much-maligned "Gatekeeper" (which required developers to sign their applications), Apple demanded that the systems extensions are in turn signed (and thus validated). Now it is the entire system that was padlocked. By doing so, Apple protects against particular vulnerabilities already present in OS X, and sometimes allow to "mount" the privileges of a normal user, to become administrator of the machine.

Fortunately for developers and hackers, there are (still) a way to disable SIP. To do this, reboot into "Recovery" mode (Command-R at startup) and run a terminal.

Then type the following line:

csrutil disable

Reboot and everything will be as before: the root and the administrator will again play with the system files.

I imagine you know how to activate root account :-)

Oct 18, 2015 12:36 PM in response to Eric Root

Hello,

the problem is the lack of record "mbasd = 1" in the system. To solve this problem you need to open the "/Library/Preferences/SystemConfiguration/com.apple.Boot.plist." and edit "apple.Boot.plist" - Text Edit is sufficient.

The key "Kernel Flags" is empty. You must add between start and end string "mbasd = 1" and the problem is resolved.

Oh one more problem: to manipulate the system, you must be "root" user and is not the end, because in this version of OSX is active

the "System Integrity Protection" or SIP for short. This is actually a way for Apple to push again the limits of the safety of your machine, prohibiting all users (including God Root) touching some critics judged files.

So even root will not have the right to go to copy any document in the following folders:

/ System

/ bin

/ usr

/ sbin

The idea behind this, is obviously to protect the user against any possible threat, a risk that weighs increasingly heavy with the growing popularity of OS X. After the much-maligned "Gatekeeper" (which required developers to sign their applications), Apple demanded that the systems extensions are in turn signed (and thus validated). Now it is the entire system that was padlocked. By doing so, Apple protects against particular vulnerabilities already present in OS X, and sometimes allow to "mount" the privileges of a normal user, to become administrator of the machine.

Fortunately for developers and hackers, there are (still) a way to disable SIP. To do this, reboot into "Recovery" mode (Command-R at startup) and run a terminal.

Then type the following line:

csrutil disable

Reboot and everything will be as before: the root and the administrator will again play with the system files.

I imagine you know how to activate roo account

superdrive not loading discs after upgrading to el capitan

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