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

KPOM

macrumors P6
Original poster
Oct 23, 2010
18,308
8,320
To those with the 2016 MacBook, you may want to hold off installing the latest El Capitan Beta if you need to access USB drives. I noticed that any drives requiring USB 3.0 power do not seem to mount with the new beta. If I revert to 10.11.4 the drives mount with no issue. Kudos to the Genius Bar rep who spend 30 minutes with my MacBook trying various tests and then encouraged me to try downgrading before sending it back (saved me the hassle of being without the MacBook for a few days).
 

KPOM

macrumors P6
Original poster
Oct 23, 2010
18,308
8,320
FYI, this is still present in the current beta 4.
 

KPOM

macrumors P6
Original poster
Oct 23, 2010
18,308
8,320
Must be your drive. Works fine for me.
Not my drive. I tried it with 2 different flash drives and a USB Ethernet adapter. None of them worked. All 3 work fine in 10.11.4 and for that matter in 10.11.5 on my old MacBook. Apple replied to me in less than 24 hours when they normally take weeks. Maybe it's my MacBook. I sent Apple my System Diagnosis files. I'll keep you posted.
 

KPOM

macrumors P6
Original poster
Oct 23, 2010
18,308
8,320
my usb drives are working fine here in 10.11.5pb3 and now pb4...
Are you using a 2016 MacBook?

For me everything was fine in 10.11.4. I even migrated from my 2015 using Target Disk Mode over a USB 3.1 cable. But as soon as it downloaded and installed the beta the USB port stopped working correctly. If I reinstall 10.11.4 it works. Perhaps it is a software incompatibility with something I'm using, but I have a fairly simple setup.
 

fisherking

macrumors G4
Jul 16, 2010
11,252
5,563
ny somewhere
Are you using a 2016 MacBook?

For me everything was fine in 10.11.4. I even migrated from my 2015 using Target Disk Mode over a USB 3.1 cable. But as soon as it downloaded and installed the beta the USB port stopped working correctly. If I reinstall 10.11.4 it works. Perhaps it is a software incompatibility with something I'm using, but I have a fairly simple setup.

oops, sorry, no; macbook pro. :rolleyes:
 

XboxMySocks

macrumors 68020
Oct 25, 2009
2,239
213
Oh sorry, I was under the impression you were on a retina MacBook Pro. The R threw me off - I too am on an retina MacBook Pro not a retina MacBook.
 

cgrm

macrumors newbie
May 8, 2016
2
0
France
Same here : 2016 retina macbook, USB 3 drives work perfectly on 10.11.4 and not on 10.11.5 beta.
USB 2 drives have no problem on either version of El Capitan.
 

KPOM

macrumors P6
Original poster
Oct 23, 2010
18,308
8,320
Same here : 2016 retina macbook, USB 3 drives work perfectly on 10.11.4 and not on 10.11.5 beta.
USB 2 drives have no problem on either version of El Capitan.

It is my impression that USB-c peripherials can be hit and miss at the moment. Is it possible to test with another drive OP?

These aren't USB-C peripherals. We are noticing this issue plugging in USB-A 3.0 peripherals into App,e's adapters with the latest build. USB 2.0 devices seem to work. That suggests to me that the beta software is interfering with the voltage needed to mount USB 3.0 devices.
 

cgrm

macrumors newbie
May 8, 2016
2
0
France
May 12 11:13:53 Greyhound kernel[0]: 001730.290724 IOUSBHostDevice@14500000: IOUSBHostDevice::start: failed to get device descriptor
May 12 11:13:53 Greyhound kernel[0]: 001730.291005 SSP1@14500000: AppleUSBXHCIPort::resetAndCreateDevice: failed to start device
May 12 11:13:53 Greyhound kernel[0]: 001730.291016 SSP1@14500000: AppleUSBXHCIPort::resetAndCreateDevice: failed to create device (0xe00002e9)
May 12 11:13:53 Greyhound kernel[0]: 001730.448457 IOUSBHostDevice@14500000: IOUSBHostDevice::getDescriptorGated: compliance violation: USB 2.0 9.3.5: device returned more than wLength data

Here's what happens when i plug my usb 3 SSD on my macbook. I unfortunately couldn't find any info that i could understand :/

9.3 USB Device Requests• 9.3.5 wLength – This field specifies the length of the data transferred during the second phase of the control transfer. • On an input request, a device must never return more data than is indicated by the wLength value; it may return less. • On an output request, wLength will always indicate the exact amount of data to be sent by the host. USB 2.0 Specification - Chapter 9 - Device 59 Framework
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.