Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Yosemite Optical Bay Drive Not Recognized

T

tgd85

macrumors member
Original poster
Sep 18, 2013
41
6
After spending hours scouring various forums, I have not been able to fix an ongoing issue I've been having since upgrading to Yosemite. The issue is my MBP fails to recognize any device installed internally in the optical bay. This applies to both the original SuperDrive an to a 2nd hard drive installed using the data doubler caddy.

Currently I have a Samsung SSD installed in the main hard drive bay with TRIM enabled using Trim Enabler. Kext signing has been disabled to allow for TRIM. I recently installed a clean version of Yosemite on the SSD. At first, the OS X recognized the SuperDrive, however, after several restarts, the drive disappeared from the system. No sign of it in System Information or in Disk Utility. There have been a few occasions when a device will appear as "Unidentified Device" under SATA, but even then it is not recognized by Disk Utility.

I decided to swap out the SuperDrive with the original hard drive my machine shipped with - an Hitachi 500GB @7200rmp using the data doubler. My goal is to use the 2nd hard drive as an independent drive with no affiliation to the SSD. After installing, I booted into recovery and formatted the HDD. After a restart, Yosemite booted property, recognized the drive in both Sys Info and Disk Utility, and mounted it in Finder.

However, after the very first time my machine went to sleep, I received an error message telling me I failed to properly eject the 2nd drive. Since then, my machine has not recognized the device. I can hear the drive spinning, but it's no where to be found and is not listed in using DiskUtil list through Terminal.

I was able to track down the kernel panic that was recorded from the improper ejection:

5/26/15 2:43:46.000 AM kernel[0]: SATA WARNING: Enable Drive PHY PM failed.
5/26/15 2:43:48.000 AM kernel[0]: Failed to issue COM RESET successfully after 3 attempts. Failing...
5/26/15 2:43:48.000 AM kernel[0]: disk1s2: no such device.
5/26/15 2:43:48.000 AM kernel[0]: disk1s2: media is not present.
5/26/15 2:43:48.000 AM kernel[0]: disk1s2: media is not present.
5/26/15 2:43:48.000 AM kernel[0]: disk1s2: media is not present.
5/26/15 2:43:48.000 AM kernel[0]: disk1s2: media is not present.
5/26/15 2:43:48.000 AM kernel[0]: disk1s2: media is not present.
5/26/15 2:43:48.000 AM kernel[0]: disk1s2: media is not present.
5/26/15 2:43:48.000 AM kernel[0]: disk1s2: media is not present.
5/26/15 2:43:48.000 AM kernel[0]: jnl: disk1s2: do_jnl_io: strategy err 0x6
5/26/15 2:43:48.000 AM kernel[0]: jnl: disk1s2: end_transaction: only wrote 0 of 139776 bytes to the journal!
5/26/15 2:43:48.000 AM kernel[0]: disk1s2: media is not present.
5/26/15 2:43:48.000 AM kernel[0]: disk1s2: media is not present.
5/26/15 2:43:48.000 AM kernel[0]: hfs: unmount initiated on Macintosh HDD on device disk1s2
5/26/15 2:43:48.000 AM kernel[0]: jnl: disk1s2: close: journal 0xffffff802a436a80, is invalid. aborting outstanding transactions
5/26/15 2:43:48.233 AM sandboxd[141]: ([173]) mds_stores(173) deny file-read-data /Volumes/Macintosh HDD/.Spotlight-V100/Store-V2
​
My feeling is that this some sort of Kext issue where Yosemite fails to load the proper driver for for any device connecting through that SATA connection on the logic board. I'm confident the HDD isn't damaged and it doesn't make sense to me that the system won't recognize the SuperDrive or the HDD, both of of which were part of machine's original configuration (I'd assume that Apple would have working drivers for it's own hardware) I'm also confident this isn't an issue with a loose or faulty cable. The logic board is brand new (recently repaired discrete graphics issue).

I've tried resetting PRAM and SMC a bunch, so that's not the issue either. I hoping others have had similar problems and have figured out a way to fix this.

Appreciate the help.
 
D

doowop

macrumors newbie
Jun 9, 2015
5
0
tgd85 said:
After spending hours scouring various forums, I have not been able to fix an ongoing issue I've been having since upgrading to Yosemite. The issue is my MBP fails to recognize any device installed internally in the optical bay. This applies to both the original SuperDrive an to a 2nd hard drive installed using the data doubler caddy.

Currently I have a Samsung SSD installed in the main hard drive bay with TRIM enabled using Trim Enabler. Kext signing has been disabled to allow for TRIM. I recently installed a clean version of Yosemite on the SSD. At first, the OS X recognized the SuperDrive, however, after several restarts, the drive disappeared from the system. No sign of it in System Information or in Disk Utility. There have been a few occasions when a device will appear as "Unidentified Device" under SATA, but even then it is not recognized by Disk Utility.

I decided to swap out the SuperDrive with the original hard drive my machine shipped with - an Hitachi 500GB @7200rmp using the data doubler. My goal is to use the 2nd hard drive as an independent drive with no affiliation to the SSD. After installing, I booted into recovery and formatted the HDD. After a restart, Yosemite booted property, recognized the drive in both Sys Info and Disk Utility, and mounted it in Finder.

However, after the very first time my machine went to sleep, I received an error message telling me I failed to properly eject the 2nd drive. Since then, my machine has not recognized the device. I can hear the drive spinning, but it's no where to be found and is not listed in using DiskUtil list through Terminal.

I was able to track down the kernel panic that was recorded from the improper ejection:

5/26/15 2:43:46.000 AM kernel[0]: SATA WARNING: Enable Drive PHY PM failed.
5/26/15 2:43:48.000 AM kernel[0]: Failed to issue COM RESET successfully after 3 attempts. Failing...
5/26/15 2:43:48.000 AM kernel[0]: disk1s2: no such device.
5/26/15 2:43:48.000 AM kernel[0]: disk1s2: media is not present.
5/26/15 2:43:48.000 AM kernel[0]: disk1s2: media is not present.
5/26/15 2:43:48.000 AM kernel[0]: disk1s2: media is not present.
5/26/15 2:43:48.000 AM kernel[0]: disk1s2: media is not present.
5/26/15 2:43:48.000 AM kernel[0]: disk1s2: media is not present.
5/26/15 2:43:48.000 AM kernel[0]: disk1s2: media is not present.
5/26/15 2:43:48.000 AM kernel[0]: disk1s2: media is not present.
5/26/15 2:43:48.000 AM kernel[0]: jnl: disk1s2: do_jnl_io: strategy err 0x6
5/26/15 2:43:48.000 AM kernel[0]: jnl: disk1s2: end_transaction: only wrote 0 of 139776 bytes to the journal!
5/26/15 2:43:48.000 AM kernel[0]: disk1s2: media is not present.
5/26/15 2:43:48.000 AM kernel[0]: disk1s2: media is not present.
5/26/15 2:43:48.000 AM kernel[0]: hfs: unmount initiated on Macintosh HDD on device disk1s2
5/26/15 2:43:48.000 AM kernel[0]: jnl: disk1s2: close: journal 0xffffff802a436a80, is invalid. aborting outstanding transactions
5/26/15 2:43:48.233 AM sandboxd[141]: ([173]) mds_stores(173) deny file-read-data /Volumes/Macintosh HDD/.Spotlight-V100/Store-V2
​
My feeling is that this some sort of Kext issue where Yosemite fails to load the proper driver for for any device connecting through that SATA connection on the logic board. I'm confident the HDD isn't damaged and it doesn't make sense to me that the system won't recognize the SuperDrive or the HDD, both of of which were part of machine's original configuration (I'd assume that Apple would have working drivers for it's own hardware) I'm also confident this isn't an issue with a loose or faulty cable. The logic board is brand new (recently repaired discrete graphics issue).

I've tried resetting PRAM and SMC a bunch, so that's not the issue either. I hoping others have had similar problems and have figured out a way to fix this.

Appreciate the help.
Click to expand...


Hi,

I'm having the same problem since updating to Yosemite, I too have searched, been on forums etc, it's a pain trying to get help.

I have a Macbook, late 2011, I replaced both the internal drive drive & the optical drive with SSD 1TB drives

I replaced the optical drive with a caddy & a HDD, all was fine until now.

To be fair, the only problem that I am having is that I can't add folders to the drive, everything else seems to be fine. When I try & add anything like a pic or something, I get the "The operation can't be completed because an unexpected error occurred (error code -50)"

I have removed the HDD from the optical drive caddy & connected it by Sata to USB & it works fine, so clearly it's just because it's plugged into the optical drive is where the roblem is, at least that's my take on it.

I'm hoping there's a software fix somewhere . . . . .

Can anyone help . . . ?

Thanks . . . .
 
simonsi

simonsi

Contributor
Jan 3, 2014
4,851
735
Auckland
doowop said:
To be fair, the only problem that I am having is that I can't add folders to the drive, everything else seems to be fine. When I try & add anything like a pic or something, I get the "The operation can't be completed because an unexpected error occurred (error code -50)"
Click to expand...


I had the same, the drive is in read-only, this is a symptom of the drive cable having errors and needing replacement. I had DriveDX clearly showing an increasing error count which stopped with a new cable. The cable is an easy swap yourself. You will find you can't add or change files or folders, nor can you re-partition etc. Once the cable is swapped the drive will come out of read-only itself.

My cable was the one to the main drive bay, if yours is the one in the optical bay then you also have the optical caddy as a suspect as well as the cable.
 
D

doowop

macrumors newbie
Jun 9, 2015
5
0
Hi,

Thanks for the reply . . .

I actually noticed a little tear in the ribbon that connects the caddy to the mother board, so I'm wondering if that's the problem, I've ordered another caddy, so I get that tomor' . . . .

I'm still not sure if that'll be the reason, I hope so . . .

A lot of people have had problems with their superdrives since updating to Yosemite & apparently Apple doesn't like other SSD disks to be used in their machines, so I figured this was their way of stopping that with Yosemite.

I'll update tomor' when I get the new caddy . . . .

Thanks again . . .
 
simonsi

simonsi

Contributor
Jan 3, 2014
4,851
735
Auckland
doowop said:
A lot of people have had problems with their superdrives since updating to Yosemite & apparently Apple doesn't like other SSD disks to be used in their machines, so I figured this was their way of stopping that with Yosemite.
Click to expand...


Nah, both my SSDs have been fine under Yosemite...I'm confident a cable or caddy fault is the source of the problem.
 
T

tgd85

macrumors member
Original poster
Sep 18, 2013
41
6
Thanks for the replies. In my case, I'm
simonsi said:

Nah, both my SSDs have been fine under Yosemite...I'm confident a cable or caddy fault is the source of the problem.
Click to expand...

SIMONSI - on your 13" early 2011 MBP, are you running the Hitachi HDD as your second hard drive from your optical drive connected through SATA? While it certainly could be a broken cable on my end, which would explain why the CD/DVD drive and the HDD both are having problems, I know for certain that my connections were working perfectly fine under Mavericks and I've only since had trouble with any device in my optical drive with Yosemite.

I'd also like to know if people are still experiencing any of these problems with El Capitan. Perhaps the rootless security will remedy any driver issues experienced with kext-signing and the effect that may have had on systems with third-party SSDs serving as the main hard drive in the normal bay.
 
simonsi

simonsi

Contributor
Jan 3, 2014
4,851
735
Auckland
tgd85 said:
Thanks for the replies. In my case, I'm


SIMONSI - on your 13" early 2011 MBP, are you running the Hitachi HDD as your second hard drive from your optical drive connected through SATA? While it certainly could be a broken cable on my end, which would explain why the CD/DVD drive and the HDD both are having problems, I know for certain that my connections were working perfectly fine under Mavericks and I've only since had trouble with any device in my optical drive with Yosemite.

I'd also like to know if people are still experiencing any of these problems with El Capitan. Perhaps the rootless security will remedy any driver issues experienced with kext-signing and the effect that may have had on systems with third-party SSDs serving as the main hard drive in the normal bay.
Click to expand...

My SSD is in the optical, HDD in the main drive bay. Yosemite has had no issues. If you are having trouble with multiple devices in one bay then logic tells you the issue is the controller or cable or caddy in that bay. Failure timing is just coincidence. Find a way to look at the drive Smart status, errors will be caused by hardware.
 
D

doowop

macrumors newbie
Jun 9, 2015
5
0
tjd85,

My Macbook is a late 2011, if you wanna buy the cable obviously get the one that suits your Mac . .
 
T

tgd85

macrumors member
Original poster
Sep 18, 2013
41
6
So I had the chance to take apart my machine over the weekend and took a look at the SATA connector that connects the caddy to the logic board. On both sides of the "neck" of the connector (the part that becomes narrower closest to the logic board) there seemed to be the SLIGHTEST crack in the plastic, exposing a sliver of copper. It didn't appear that any of the copper was severed, but rather just the black plastic coating had been cut. And when I say slightest, I really mean slightest - I only noticed the defect after looking at it close up under a bright light. I tried a repair with two tiny pieces of electrical tape, but didn't seem to have any effect.

@doowop what did your defect look like when you pulled it out?
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom