Skip navigation

10.8.3 update: issue with HDD in optical bay of MacBook Pro

4419 Views 42 Replies Latest reply: Feb 4, 2014 8:37 AM by Hargitanandor RSS
1 2 3 Previous Next
pebewe Calculating status...
Currently Being Moderated
Mar 17, 2013 5:08 AM

After updating from 10.8.2 to 10.8.3 the second internal HDD which is placed in the optical bay of my MacBook Pro late 09 gets lost after some minutes. That means it suddenly unmounts (with a warning message about improper unmounting) and can't get activated again. Diskutil will not see it any longer. After a restart its mounted - until it spontaneously vanishes again.

 

Before everything has been working flawlessly for about 2 years, with SSD in the original HDD Bay an the HDD in a optical bay caddy. Firmware is EFI 1.6 (downgraded, because 1.7 won't work properly with such a constellation).

 

Has anybody else made similar observations or maybe already found workarounds for this issue? I was forced to go back to 10.8.2 because I need this second drive!

  • nz4ypt Calculating status...

    I have the same issue!!!

     

    Hi Pebewe, how did u go back to 10.8.2? like a restore from time machine or what? any help would be appreciated.

  • GeekBoy.from.Illinois Level 4 Level 4 (2,735 points)

    When you are running Mac OS 10.8.3, what link speed has your SATA drive in teh optical bay negotiated?  I know that there were/are issues with some of the newer machines getting a 6 Gbps link, but the hardware only works reliably at 3 Gbps.  In that case, they have been seeing similar problems as you.

     

    I recently converted my late 2011 MBP to a setup much like yours, and I was having problems with the SSD inthe primary bay dropping out, but the HDD in the optical bay kept on working with no issues.  In my case, I think it was related to the SMS (sudden motion sensor) in the primary bay that was causing the SSD to drop out, as once I disabled that, I haven't had the problem since, but it has also been less than 48 hours, so it may return...

     

    When I look at the SATA section in my System Information for my HDD in the optical bay I see:

    Intel 6 Series Chipset:

     

      Vendor:          Intel

      Product:          6 Series Chipset

      Link Speed:          6 Gigabit

      Negotiated Link Speed:          6 Gigabit

      Description:          AHCI Version 1.30 Supported

     

    Many people have problems when the device in their optical bay negotiates a link speed of 6 Gbps.  You might check to see if your link is trying to negotiate a faster connection than your SSD or HDD can safely work at.  If it is, you may need to go with a different drive in that bay.

  • Hargitanandor Calculating status...

    i have EXACTLY the same issue.

     

    after reboot, the optibay-hdd vanishes at some point - im using it to store my music archive, there were some lags while playing and later it unmounts.

     

    diskutil cant see it, system report does, it says "unknown": http://d.pr/i/vpfp

     

    what the **** just happened in 10.8.3?

     

    my macbook pro is mid2009, with EFI 1.6 (i had to downgrade too and disable the 1.7 update), negotiated speed is 1.5Gbit.

  • Hargitanandor Level 1 Level 1 (0 points)

    These are my console logs from today, regarding the HDD in the optibay.

     

    Are they normal?

    3/18/13 9:11:17.730 AM com.apple.backupd[4251]: Event store UUIDs don't match for volume: BAY

    3/18/13 9:17:54.621 AM com.apple.backupd[4251]: Deep event scan at path:/Volumes/BAY reason:must scan subdirs|new event db|

    3/18/13 9:35:12.023 AM com.apple.backupd[4251]: Copied 49034 files (6.01 GB) from volume BAY.

    3/18/13 9:36:06.477 AM com.apple.backupd[4251]: Copied 5593 files (68.4 MB) from volume BAY.

    3/18/13 10:29:13.112 AM fseventsd[38]: event logs in /Volumes/BAY/.fseventsd out of sync with volume.  destroying old logs. (695 1 1020)

    3/18/13 10:29:13.140 AM fseventsd[38]: log dir: /Volumes/BAY/.fseventsd getting new uuid: B599C55D-3BD9-489F-9531-9E578596423F

    3/18/13 12:16:39.910 PM com.apple.mtmd[60]: open on /Volumes/BAY/.MobileBackups/Computer/2013-03-18-112917/Volume/.autodiskmounted: No such file or directory

    3/18/13 12:16:41.447 PM com.apple.mtmd[60]: Cleaning up local snapshot store on volume /Volumes/BAY because it has been excluded.

    3/18/13 12:35:05.919 PM fseventsd[38]: event logs in /Volumes/BAY/.fseventsd out of sync with volume.  destroying old logs. (3602 0 7552)

    3/18/13 12:35:05.933 PM fseventsd[38]: log dir: /Volumes/BAY/.fseventsd getting new uuid: B5BBC546-4A2C-4926-A2A6-999FBF0A4E5B

    3/18/13 12:35:57.794 PM com.apple.mtmd[70]: Spotlight cannot end the session: 1, for /Volumes/BAY

    3/18/13 12:35:58.648 PM com.apple.mtmd[70]: open on /Volumes/BAY/.MobileBackups/Computer/2013-03-18-123511/Volume/.autodiskmounted: No such file or directory

    3/18/13 3:23:19.241 PM com.apple.mtmd[70]: open on /Volumes/BAY/.MobileBackups/Computer/2013-03-18-133511/Volume/.autodiskmounted: No such file or directory

    3/18/13 3:23:21.278 PM com.apple.mtmd[70]: Cleaning up local snapshot store on volume /Volumes/BAY because it has been excluded.

    3/18/13 3:31:29.794 PM fseventsd[38]: disk logger: failed to open output file /Volumes/BAY/.fseventsd/00000000000e329a (No such file or directory). mount point /Volumes/BAY/.fseventsd

    3/18/13 3:31:29.795 PM fseventsd[38]: disk logger: failed to open output file /Volumes/BAY/.fseventsd/00000000000e329a (No such file or directory). mount point /Volumes/BAY/.fseventsd

    3/18/13 4:22:55.945 PM fseventsd[38]: event logs in /Volumes/BAY/.fseventsd out of sync with volume.  destroying old logs. (9235 0 13618)

    3/18/13 4:22:55.975 PM fseventsd[38]: log dir: /Volumes/BAY/.fseventsd getting new uuid: 30923182-30A2-4CC4-8406-2EDFEF6F95EF

  • Hargitanandor Level 1 Level 1 (0 points)

    okay, a rebooted after writing my first post to this thread, now, the hdd is gone, here are the logs:

     

    3/18/13 5:04:08.000 PM kernel[0]: Failed to issue COM RESET successfully after 3 attempts. Failing...

    3/18/13 5:04:08.000 PM kernel[0]: disk1s2: media is not present.

    3/18/13 5:04:08.000 PM kernel[0]: disk1s2: media is not present.

    3/18/13 5:04:08.000 PM kernel[0]: disk1s2: media is not present.

    3/18/13 5:04:08.000 PM kernel[0]: disk1s2: media is not present.

    3/18/13 5:04:08.000 PM kernel[0]: disk1s2: media is not present.

    3/18/13 5:04:08.000 PM kernel[0]: disk1s2: media is not present.

    3/18/13 5:04:08.000 PM kernel[0]: disk1s2: media is not present.

    3/18/13 5:04:08.000 PM kernel[0]: disk1s2: media is not present.

    3/18/13 5:04:08.000 PM kernel[0]: disk1s2: media is not present.

    3/18/13 5:04:08.000 PM kernel[0]: disk1s2: media is not present.

    3/18/13 5:04:08.000 PM kernel[0]: disk1s2: media is not present.

    3/18/13 5:04:08.000 PM kernel[0]: disk1s2: media is not present.

    3/18/13 5:04:08.000 PM kernel[0]: disk1s2: media is not present.

    3/18/13 5:04:08.000 PM kernel[0]: disk1s2: media is not present.

    3/18/13 5:04:08.000 PM kernel[0]: disk1s2: media is not present.

    3/18/13 5:04:08.000 PM kernel[0]: disk1s2: media is not present.

    3/18/13 5:04:08.000 PM kernel[0]: disk1s2: media is not present.

    3/18/13 5:04:08.000 PM kernel[0]: disk1s2: media is not present.

    3/18/13 5:04:08.000 PM kernel[0]: disk1s2: media is not present.

    3/18/13 5:04:08.000 PM kernel[0]: disk1s2: media is not present.

    3/18/13 5:04:08.000 PM kernel[0]: disk1s2: media is not present.

    3/18/13 5:04:08.000 PM kernel[0]: disk1s2: media is not present.

    3/18/13 5:04:08.000 PM kernel[0]: jnl: disk1s2: do_jnl_io: strategy err 0x6

    3/18/13 5:04:08.000 PM kernel[0]: jnl: disk1s2: write_journal_header: error writing the journal header!

    3/18/13 5:04:09.314 PM com.apple.mtmd[70]: open on /Volumes/BAY/.MobileBackups/Computer/2013-03-18-162326/Volume/.autodiskmounted: No such file or directory

    3/18/13 5:04:09.000 PM kernel[0]: jnl: disk1s2: close: journal 0xffffff803128ecc0, is invalid.  aborting outstanding transactions

    3/18/13 5:04:10.889 PM com.apple.mtmd[70]: Cleaning up local snapshot store on volume /Volumes/BAY because it has been excluded.

  • nz4ypt Level 1 Level 1 (0 points)

    Thanks Pebewe. what I have is early 2011 mbp 15. i replaced optical bay with another intel ssd (OWC data doubler)

  • nz4ypt Level 1 Level 1 (0 points)

    my 2nd SSD is 3giga only, so the negoticate speed was 3giga. but now i can't even see it, so no negoticate speed at all ...

  • Hargitanandor Level 1 Level 1 (0 points)

    any idea how to roll back to 10.8.2? or skip the SATA update in 10.8.3?

  • woodmeister50 Level 4 Level 4 (3,690 points)

    FWIW, have you tried a PRAM and/or SMC reset?  Sometimes

    this can resolve hardware configuration problems by forcing a

    a reload of the hardware parameters.

     

    Also FWIW, there is always a risk of problems with OS updates anytime

    you have a system that is not a standard/supported production

    configuration.  The problem may be corrected with future update

    but as this is not a production configuration Apple is not neccessarily

    responsible to fix it.

  • Hargitanandor Level 1 Level 1 (0 points)

    ok, restore done, now, i suppose, cant install any of the future upgrades, without the risk of failing again.

     

    apple wont help, because "misusing" the optibay.

     

    osx1083grumpdate.png

  • bucketheadbobby Level 1 Level 1 (0 points)

    I have a MBP mid 2009 had to downgrade to EFI 1.6 to make it work. With the HDD. Just upgraded to 10.8.3. Now locked up with spinning wheel.

    It would seem from all the coments that there is a problem with compatibility with this particular MBP. Apple don't seem willing to acknowledge the problem but we all know it exists

      I guess I'll have to downgrade to 10.8.2. I hope it all works OK

1 2 3 Previous Next

Actions

More Like This

  • Retrieving data ...

Bookmarked By (1)

Legend

  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.