Doesn't work on Mojave w/ Sabrent External Enclosure

[Dochartaigh]

The Mac program Disk Drill (version 4.7.382) recommended this program to get S.M.A.R.T. reporting on external drives. Just tried SATSMARTDriver-0.10.2 on my 2009 Mac Pro running Mojave 10.14.6 and it's not working.

I'm using a Sabrent EC-DFLT External Enclosure, with a 10TB Western Digital WD100EMAZ hard drive. USB 3.0 interface is via a RedComets U21 card (all pretty standard devices).

Anything I can try? Just had a HDD go bad so would love to be able to start using SMART monitoring on my other external drives moving forward. Thanks.

[RJVB]

You could start by checking if there are no newer forks than mine, which I haven't been keeping up-to-date at all. Also, my 2011 MBP is officially limited to 10.13 so I guess you are using a hack to run a newer OS on your older Mac? I wouldn't be surprised if that has anything to do with it, though it could also be that your U21 card simply doesn't forward the commands, idem for the Sabrent enclosure. Do you have another computer on which you could test that, under Linux or MSWin? You can of course test the enclosure via one of the Mac's own USB2 ports, at least if you can read SMART info from any of your drives.

[Dochartaigh]

You could start by checking if there are no newer forks than mine, which I haven't been keeping up-to-date at all. Also, my 2011 MBP is officially limited to 10.13 so I guess you are using a hack to run a newer OS on your older Mac? I wouldn't be surprised if that has anything to do with it, though it could also be that your U21 card simply doesn't forward the commands, idem for the Sabrent enclosure. Do you have another computer on which you could test that, under Linux or MSWin? You can of course test the enclosure via one of the Mac's own USB2 ports, at least if you can read SMART info from any of your drives.

Hello and thanks for replying. The 2009 and 2010 Mac Pro's have IDENTICAL motherboards - all you need is a newer (like $50 now) video card to run Mojave on the 2009 - so it's 1000% fully supported with everything and shouldn't be a problem.

I'll try your other suggestions and thanks again - don't see any newer forks though (the one other one also says from '9 years ago').

[RJVB]

It's indeed possible that I synced changes made to the repo that I forked, long ago (long enough that I don't even remember off the top of my hat why I forked it!) ... Sorry if I'm not in a hurry to check that! Either way there's very little I would be able to to I fear, without error messages...

[RJVB]

Looking at this some more, and in particular at https://github.com/RJVB/OS-X-SAT-SMART-Driver/blob/RJVB/SATSMARTDriver/Info.plist I notice that - the BundleVersion is set to 0.11 while your screenshot shows 0.10.2 being loaded - there's a whole list of enclosure-specific settings, apparently based on data that comes at least partly from smartmontools (449d52d). It may be that your enclosure needs to be added to that list.

[RJVB]

Sabrent EC-DFLT

Can you go into the USB page of the system info application from which you took a screenshot and confirm if the entry for the Sabrent has any of the following information? ASMedia AS2115 idVendor=0x174c idProduct=0x1153 (or idVendor=5964 idProduct=4435) I have a USB3 enclosure for an m3 SSD that I connect via a Belkin Thunderbolt dock, IIRC it has an ASMedia chipset too, and I can read it just fine. For debugging this it could help if you installed smartmontools (from MacPorts, HB, or any other source), so you can attempt to specify the device type on the commandline rather than in the Info.plist inside a kext: ```

smartctl -d $type -a /dev/disk1

``` there type is one from `sat[,auto][,N][+TYPE], usbcypress[,X], usbjmicron[,p][,x][,N], usbprolific, usbsunplus` (see `man smartctl`).