[Help] OCW Data Doubler w/Second Hard Drive Randomly Ejecting...

Discussion in 'Mac Basics and Help' started by csalvato, Aug 5, 2013.

  1. csalvato macrumors newbie

    Joined:
    Aug 5, 2013
    #1
    I have been searching high and wide for a solution to this problem but I can't seem to find anything relevant. I know I can't be the only one suffering from this problem.

    I have a mid 2012 MacBook Pro 15 inch.

    I removed the stock hard drive, and installed a 180 GB SSD as my primary boot drive. Here are it's specs from System Information:

    Media Name: Corsair Force GT Media
    Medium Type: SSD
    Protocol: SATA
    Internal: Yes
    Partition Map Type: GPT (GUID Partition Table)
    S.M.A.R.T. Status: Verified​

    I then installed the OCW Data Doubler, and removed the optical drive. In this bay, I installed a 750 GB HDD. Here are it's specs from System Information:

    Physical Drive:
    Media Name: ST750LX003-1AC154 Media
    Medium Type: Rotational
    Protocol: SATA
    Internal: Yes
    Partition Map Type: GPT (GUID Partition Table)
    S.M.A.R.T. Status: Verified​

    I have downloaded TRIM Enabler, and enabled TRIM for the SSD.

    [​IMG]

    I have set up my SSD as the boot drive. I have my home folder (with all media) on my second hard drive, since it is substantially bigger. I saw this in a blog post when I first set this up 6 months ago, and it works fine when things are going normally...

    ...but, the problem is that the drive will eject "randomly". Since my home folder is on the second hard drive, the ejection requires me to completely reboot. The whole process takes about 5-10 minutes.

    I also say "randomly" because it isn't exactly random. It sometimes happens out of the blue, but oftentimes it will eject when the drive is being used (like backing up the disk, editing video, etc.)

    Also, my computer tends to get much more hot, and will even power down in the summer when it gets too warm for the system to cool itself (even if it is on a hard surface, not on my lap).

    I feel like I have something misconfigured with the hard drive that is causing these problems. Is there anything that I can do to fix this?

    Thanks!
     
  2. asad.palekar macrumors newbie

    Joined:
    Sep 3, 2014
    #2
    Any solutions

    Hi,

    I am facing the same problem. The setup did work for me initially. But now the disk keeps ejecting itself.

    Have you found any solution for this?

    Thanks.
     
  3. inscrewtable macrumors 65816

    inscrewtable

    Joined:
    Oct 9, 2010
    Location:
    Australia
    #3
    you might be better leaving your home folder on the SSD and only putting particularly large folders on the HDD for example you could just point itunes to the HDD.
     
  4. csalvato thread starter macrumors newbie

    Joined:
    Aug 5, 2013
    #4
    Asad,

    I just left things as they were. It was annoying, but only happened once every few days at most. Sometimes I would go weeks at a time with no problem.

    I think this was a mistake, though. That MacBook Pro (late 2011 model) had just turned off one day while I was using it. I went to the Genius bar and they told me the MLB (logic board) had failed, and that had caused the Top Case to also fail.

    I was out of warrantee, and I was unable to wait for the repair, so I wound up purchasing a new retina Macbook Pro.

    I would not use the OCR data doubler again. After some reading, I realized that constant errors like this can cause faults in the logic board.

    My gut, though, is that I wasn't cleaning dust out of the fans often enough, which is apparently a big problem with the late 2011 design. But that's just my opinion.

    Sorry the news isn't better for you. If it's any condolence, it cost me $2600 to get a new computer...so hopefully it won't cost you as much.

    My recommendation: Get a mega big SSD for your main drive (500-1TB) and just shell out the extra cash. It's a lot easier in the long run.
     
  5. asad.palekar macrumors newbie

    Joined:
    Sep 3, 2014
    #5
    Thanks csalvato,

    Sad to hear that. What makes me crazy is that the setup worked fine for around 6 months. I was under the impression that maybe a recent update might have caused this. But other reason could be that the macbook faced some damage over time with this setup. :(

    If i would have known this earlier, would have invested for a larger drive. But after getting a 256 GB, i think i wont be able to go in for another drive :(

    Thanks anyways. :)
     

Share This Page