new MBP 13" 2012 and external USB 3.0 drive problem (not mounting)

Discussion in 'MacBook Pro' started by latestmonkey, Jul 2, 2012.

  1. latestmonkey, Jul 2, 2012
    Last edited: Jul 2, 2012

    latestmonkey macrumors 6502

    Joined:
    Aug 13, 2002
    #1
    I just bought a new Seagate Goflex Desk USB 3.0 drive (last year's model cause it was on sale at Staples) and my new 13" MBP simply won't recognize it.

    When I plug it into my old Snow Leopard Mac USB 2.0, it recognizes it fine. Also, when I switch the adapters (that's one of the features of the GoFlex line) to the FW800, the new MBP recognizes it no problem.

    I don't think my USB 3 ports are faulty as other items plug in fine (although none have been USB 3 before).


    Any suggestions?

    thanks
     
  2. torana355 macrumors 68020

    Joined:
    Dec 8, 2009
    Location:
    Sydney, Australia
    #2
    Only thing i can think of would be a firmware issue with the seagate drive.
     
  3. robvas macrumors 68020

    Joined:
    Mar 29, 2009
    Location:
    USA
    #3
    Open the console and see if any messages appear
     
  4. latestmonkey thread starter macrumors 6502

    Joined:
    Aug 13, 2002
    #4
    I plugged in the serial number on the seagate site and it said no firmware update available.

    What console? I looked in system info / about this mac, if that's what you mean?
     
  5. eagandale4114 macrumors 65816

    eagandale4114

    Joined:
    May 20, 2011
    #5
    Type in console in spotlight. You will find the app. Plug the drive in and post a screenshot of recent logs.
     
  6. latestmonkey thread starter macrumors 6502

    Joined:
    Aug 13, 2002
    #6
    ahhh ok.

    here's what I get:

    Code:
    7/2/12 9:43:13.940 PM com.apple.launchd.peruser.501: (com.akamai.client.plist[915]) Bug: launchd_core_logic.c:4753 (25693):13
    7/2/12 9:43:15.000 PM kernel: USBF:	5380.978	IOUSBInterface[0xffffff800c38b200]::joinPMtree - could not find the hub device
    7/2/12 9:43:15.000 PM kernel: [0xffffff800c38b400](1)/(5) Device not responding
    7/2/12 9:43:16.000 PM kernel: [0xffffff800c391a00](1)/(5) Device not responding
    7/2/12 9:43:17.000 PM kernel: [0xffffff800c391800](1)/(5) Device not responding
    7/2/12 9:43:18.000 PM kernel: [0xffffff800c391800](2)/(5) Device not responding
    7/2/12 9:43:20.000 PM kernel: [0xffffff800c392e00](3)/(5) Device not responding
    7/2/12 9:43:20.000 PM kernel: [0xffffff800c671800](1)/(5) Device not responding
    7/2/12 9:43:21.000 PM kernel: [0xffffff800c392e00](1)/(5) Device not responding
    7/2/12 9:43:22.000 PM kernel: [0xffffff800c393400](2)/(5) Device not responding
    7/2/12 9:43:22.000 PM kernel: [0xffffff800a482200](1)/(5) Device not responding
    7/2/12 9:43:23.000 PM kernel: [0xffffff800c393400](1)/(5) Device not responding
    7/2/12 9:43:24.000 PM kernel: [0xffffff800c392e00](1)/(5) Device not responding
    7/2/12 9:43:25.000 PM kernel: [0xffffff800c391e00](1)/(5) Device not responding
    7/2/12 9:43:29.000 PM kernel: [0xffffff800c391800](4)/(5) Device not responding
    7/2/12 9:43:30.000 PM kernel: [0xffffff800c393400](1)/(5) Device not responding
    7/2/12 9:43:31.000 PM kernel: [0xffffff800c393400](1)/(5) Device not responding
    7/2/12 9:43:33.000 PM kernel: [0xffffff800c393400](3)/(5) Device not responding
    7/2/12 9:43:33.000 PM kernel: [0xffffff800c391800](1)/(5) Device not responding
    7/2/12 9:43:34.000 PM kernel: [0xffffff800c38b400](1)/(5) Device not responding
    7/2/12 9:43:35.000 PM kernel: [0xffffff800c393400](1)/(5) Device not responding
    7/2/12 9:43:36.000 PM kernel: [0xffffff800c393400](2)/(5) Device not responding
    7/2/12 9:43:37.000 PM kernel: [0xffffff800c390400](2)/(5) Device not responding
    7/2/12 9:43:38.000 PM kernel: [0xffffff800c393400](1)/(5) Device not responding
    7/2/12 9:43:40.000 PM kernel: [0xffffff800c38de00](3)/(5) Device not responding
    7/2/12 9:43:40.000 PM kernel: [0xffffff800c671800](1)/(5) Device not responding
    7/2/12 9:43:41.000 PM kernel: [0xffffff800c671800](1)/(5) Device not responding
    7/2/12 9:43:42.000 PM kernel: [0xffffff800c392e00](2)/(5) Device not responding
    7/2/12 9:43:42.000 PM kernel: [0xffffff800c38b400](2)/(5) Device not responding
    7/2/12 9:43:43.000 PM kernel: [0xffffff800c38de00](2)/(5) Device not responding
    7/2/12 9:43:43.000 PM kernel: [0xffffff800c38de00](1)/(5) Device not responding
    
     
  7. eagandale4114 macrumors 65816

    eagandale4114

    Joined:
    May 20, 2011
    #7
    Next item:
    Does the drive work on other computers?
     
  8. latestmonkey thread starter macrumors 6502

    Joined:
    Aug 13, 2002
    #8
  9. Carrotty macrumors newbie

    Joined:
    Jun 23, 2012
    #9
    sorry, this might be irrelevant to this topic but can i just ask a quick question?
    If i have an external hard drive that has usb 2.0 -->

    http://www.amazon.com/Western-Digit...rds=western+digital+external+hard+drive+500gb

    ...will i still be able to enjoy the fast transfer rate when connecting it to the usb 3.0 port of any of these new macbooks? And anyone know how fast it would be, approximately?

    Thanks in advance.
     
  10. eagandale4114 macrumors 65816

    eagandale4114

    Joined:
    May 20, 2011
    #10
    No difference. The max speed of your drive is USB 2.0. Using a faster port will not increase the speed of transfer.
     
  11. Carrotty macrumors newbie

    Joined:
    Jun 23, 2012
    #11
    awesome, thanks!
     
  12. tbl macrumors member

    tbl

    Joined:
    Jul 14, 2010
    #12
    Hey! I'm having the same problem with the same exact drive. After doing some reading up on the issue, it seems that our problem is at least in part due to faulty seagate drivers.

    http://forums.seagate.com/t5/GoFlex-GoFlex-Desk-GoFlex-Pro/Seagate-s-PC-MAC-USB-3-0-Goflex-drivers-not-Mac-compatible/m-p/164008

    After doing what "Adsy" on that thread suggested, I was able to get the drive to mount... but unfortunately it's still a very shaky affair. When i plugged the drive in again, it didn't mount.
     
  13. latestmonkey thread starter macrumors 6502

    Joined:
    Aug 13, 2002
    #13
    I decided to just use it on my Snow Leopard mac via firewire.

    Btw, here's the response I got from Seagate.

    Of course, I specifically told them I had a new MBP 2012 with USB 3 ports. :rolleyes:
     
  14. Yawn66 macrumors member

    Joined:
    Jun 14, 2012
    #14
    Try connecting the USB 3 disk to your Mac via a USB 2 hub. Of course that will slow it down to ~ 30 MB/s, but at least you'll be able to use it.

    It appears Apple's USB 3 drivers are crap, at least their current version. I cannot get any USB 3 drives to work at USB 3 speeds if they are not directly connected to my 2012 MBA. :(

    http://forums.macrumors.com/showthread.php?t=1399179
     
  15. yusukeaoki macrumors 68030

    yusukeaoki

    Joined:
    Mar 22, 2011
    Location:
    Tokyo, Japan
    #15
    I agree.
    It might be the MBP problem rather than the Seagate.
     

Share This Page