search

kasbert / OS-X-SAT-SMART-Driver

Max OS X kernel driver for providing access to external drive SMART data
578 stars 74 forks source link

OUSBFamily was not able to enumerate the device #36

Open paullinford opened 9 years ago

paullinford commented 9 years ago

after installing driver, drive is ultimately ejected

3/29/15 7:28:06.000 AM kernel[0]: USBF: 283.561 The IOUSBFamily is having trouble enumerating a USB device that has been plugged in. It will keep retrying. (Port 5 of Hub at 0xfd000000) 3/29/15 7:28:12.000 AM kernel[0]: USBF: 289.532 AppleUSBEHCI::Found a transaction which hasn't moved in 5000 milliseconds on bus 0xfd, timing out! (Addr: 0, EP: 0) 3/29/15 7:28:18.000 AM kernel[0]: USBF: 295.535 AppleUSBEHCI::Found a transaction which hasn't moved in 5000 milliseconds on bus 0xfd, timing out! (Addr: 0, EP: 0) 3/29/15 7:28:24.000 AM kernel[0]: USBF: 301.538 AppleUSBEHCI::Found a transaction which hasn't moved in 5000 milliseconds on bus 0xfd, timing out! (Addr: 0, EP: 0) 3/29/15 7:28:30.000 AM kernel[0]: USBF: 307.539 AppleUSBEHCI::Found a transaction which hasn't moved in 5000 milliseconds on bus 0xfd, timing out! (Addr: 0, EP: 0) 3/29/15 7:28:36.000 AM kernel[0]: USBF: 313.541 AppleUSBEHCI::Found a transaction which hasn't moved in 5000 milliseconds on bus 0xfd, timing out! (Addr: 0, EP: 0) 3/29/15 7:28:42.000 AM kernel[0]: USBF: 319.544 AppleUSBEHCI::Found a transaction which hasn't moved in 5000 milliseconds on bus 0xfd, timing out! (Addr: 0, EP: 0) 3/29/15 7:28:42.000 AM kernel[0]: USBF: 320. 78 The IOUSBFamily was not able to enumerate the device (Port 5 of Hub at 0xfd000000).

SYSTEM INFORMATION

Report Timestamp : March 29, 2015 7:29:00 AM PDT Report Timestamp (ISO 8601 format) : 2015-03-29T07:29:00

Application Name : DriveDx Application Version : 1.3.0.444 App SubBuild : 0 Application Edition : 1 DriveDx Knowledge Base Revision : 1/1 Computer Model : MacPro5,1 OS Name : Mac OS X OS Version : 10.8.5 OS Build : 12F2501 OS Kernel Version : Darwin 12.6.0

Same device, same issue on MacPro4,1

I'll try and add some more info like alvarnell suggested.

satsmart driver came with drivedx 1.3.0. Device is a bridge card DATOptic FWBU2DSATA12, FW800 and USB. Device was direct connect to front USB ports of MacPro4,1 and MacPro5,1. They are each independent busses as far as I can tell, no external or internal hub. I think it has UF934DS_V1_10_Release.bin if that means anything. I had been using FW800 exclusively, I guess this driver can't get SMART that way. USB behaves with driver removed.

alvarnell commented 9 years ago

You certainly haven't given kasbert much to go on here. Not surprising that it isn't platform related, but I suspect he's going to need to know:

Also did you check http://sourceforge.net/apps/trac/smartmontools/wiki/Supported_USB-Devices? If the options column has anyting, but "-d sat", the enclosure does not support SAT and therefore does not work with this driver.

-Al-

On Sun, Mar 29, 2015 at 08:08 AM, paullinford wrote:

after installing driver, drive is ultimately ejected

3/29/15 7:28:06.000 AM kernel[0]: USBF: 283.561 The IOUSBFamily is having trouble enumerating a USB device that has been plugged in. It will keep retrying. (Port 5 of Hub at 0xfd000000) 3/29/15 7:28:12.000 AM kernel[0]: USBF: 289.532 AppleUSBEHCI::Found a transaction which hasn't moved in 5000 milliseconds on bus 0xfd, timing out! (Addr: 0, EP: 0) 3/29/15 7:28:18.000 AM kernel[0]: USBF: 295.535 AppleUSBEHCI::Found a transaction which hasn't moved in 5000 milliseconds on bus 0xfd, timing out! (Addr: 0, EP: 0) 3/29/15 7:28:24.000 AM kernel[0]: USBF: 301.538 AppleUSBEHCI::Found a transaction which hasn't moved in 5000 milliseconds on bus 0xfd, timing out! (Addr: 0, EP: 0) 3/29/15 7:28:30.000 AM kernel[0]: USBF: 307.539 AppleUSBEHCI::Found a transaction which hasn't moved in 5000 milliseconds on bus 0xfd, timing out! (Addr: 0, EP: 0) 3/29/15 7:28:36.000 AM kernel[0]: USBF: 313.541 AppleUSBEHCI::Found a transaction which hasn't moved in 5000 milliseconds on bus 0xfd, timing out! (Addr: 0, EP: 0) 3/29/15 7:28:42.000 AM kernel[0]: USBF: 319.544 AppleUSBEHCI::Found a transaction which hasn't moved in 5000 milliseconds on bus 0xfd, timing out! (Addr: 0, EP: 0) 3/29/15 7:28:42.000 AM kernel[0]: USBF: 320. 78 The IOUSBFamily was not able to enumerate the device (Port 5 of Hub at 0xfd000000).

SYSTEM INFORMATION

Report Timestamp : March 29, 2015 7:29:00 AM PDT Report Timestamp (ISO 8601 format) : 2015-03-29T07:29:00

Application Name : DriveDx Application Version : 1.3.0.444 App SubBuild : 0 Application Edition : 1 DriveDx Knowledge Base Revision : 1/1 Computer Model : MacPro5,1 OS Name : Mac OS X OS Version : 10.8.5 OS Build : 12F2501 OS Kernel Version : Darwin 12.6.0

Same device, same issue on MacPro4,1

� Reply to this email directly or view it on GitHub.

kasbert commented 9 years ago

Would you try version 0.11-Debug, please ? If needed, allow unsigned kernel extensions with command: sudo nvram boot-args="kext-dev-mode=1

I have occasionally seen the enumeration failing with my LaCie enclosure, but haven't been able to reproduce the error. I suspect that the enclosure is not ready for identify command during the driver initialization, so I delayed the identify a bit.

paullinford commented 9 years ago

Hi Jarkko I installed SATSMARTDriver-0.11-Debug.dmg Console now shows when it is attached 4/12/15 10:33:09.000 AM kernel[0]: USBMSC Identifier (non-unique): 00027a2400004798 0x3873 0x924 0x0, 2

The bridge device doesn't seem to be SAT SMART anyway. No info via USB or FW800 using DriveDX.

Any info I can give you or do I consider the bridge device too old?

UPATE: Computer will not restart now. Guess I'll have to figure out how to uninstall that. Previous to restarting I just tried power cycling external drives.

Paul

On Sun, Apr 12, 2015 at 4:02 AM, Jarkko Sonninen notifications@github.com wrote:

Would you try version 0.11-Debug, please ? If needed, allow unsigned kernel extensions with command: sudo nvram boot-args="kext-dev-mode=1

I have occasionally seen the enumeration failing with my LaCie enclosure, but haven't been able to reproduce the error. I suspect that the enclosure is not ready for identify command during the driver initialization, so I delayed the identify a bit.

— Reply to this email directly or view it on GitHub https://github.com/kasbert/OS-X-SAT-SMART-Driver/issues/36#issuecomment-92032826 .

kasbert commented 9 years ago

So now the drive works (does not fail to enumerate), but the SMART info is not available and it is causing problems in starting ?

Resetting pram might help, since the kernel should no longer allow the driver to load.

It's possible that the bridge does not support SAT commands, because it is a raid one. Does the driver show drive model correctly ?

paullinford commented 9 years ago

I've removed it. Guess I can install and look, then remove before starting.

On Sunday, April 12, 2015, Jarkko Sonninen notifications@github.com wrote:

So now the drive works (does not fail to enumerate), but the SMART info is not available and it is causing problems in starting ?

Yes, SMART status not supported, and would not complete startup.

Resetting pram might help, since the kernel should no longer allow the driver to load.

I booted to recovery and ran modified terminal commands to remove the driver and plugin.

It's possible that the bridge does not support SAT commands, because it is a raid one. Does the driver show drive model correctly ?

Yes it is capable of raid via a jumper I think. It is currently JBOD, and both channels have hot swap bays, but at the moment only one drive is inserted.

— Reply to this email directly or view it on GitHub https://github.com/kasbert/OS-X-SAT-SMART-Driver/issues/36#issuecomment-92228243 .