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

[latestmonkey]

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

 

[torana355]

Only thing i can think of would be a firmware issue with the seagate drive.

 

[robvas]

Open the console and see if any messages appear

 

[latestmonkey]

Only thing i can think of would be a firmware issue with the seagate drive.

I plugged in the serial number on the seagate site and it said no firmware update available.

Open the console and see if any messages appear

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

 

[eagandale4114]

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?

Type in console in spotlight. You will find the app. Plug the drive in and post a screenshot of recent logs.

 

[latestmonkey]

ahhh ok.

here's what I get:

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

 

[eagandale4114]

ahhh ok.

here's what I get:

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

Next item:
Does the drive work on other computers?

 

[latestmonkey]

yes, via USB 2.0.

I've been doing some research and it seems I'm not the only person with this issue. People with rMBPs and 2012 MBAs also are having their hard drives unrecognized via their usb3.0 ports.

http://www.zdnet.com/blog/apple/pro...usb-3-0-external-drives-on-new-macbooks/13188

I guess i'm lucky enough to have the issue with the regular MBP too!

 

[Carrotty]

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.

 

[eagandale4114]

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.

No difference. The max speed of your drive is USB 2.0. Using a faster port will not increase the speed of transfer.

 

[Carrotty]

No difference. The max speed of your drive is USB 2.0. Using a faster port will not increase the speed of transfer.

awesome, thanks!

 

[tbl]

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.

 

[latestmonkey]

I decided to just use it on my Snow Leopard mac via firewire.

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

Thank you for contacting Seagate.

Macs in general tend to have issues with USB 3, however, usually they will at least show up. Did your Mac actually come with a USB 3 port? USB 3 will be no faster unless it is plugged into a USB 3 port, which Apple has stated they are not supporting at this time. Do any other USB 3 devices work on your Lion Mac?

If you have any additional questions you may call us during your regional business hours listed below. For your convenience we also have on-line chat assistance.

Of course, I specifically told them I had a new MBP 2012 with USB 3 ports.

 

[Yawn66]

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.

https://forums.macrumors.com/threads/1399179/

 

[yusukeaoki]

I agree.
It might be the MBP problem rather than the Seagate.