Disk Utility SMART Status "Not Supported", but DriveDx SMART Support "Enabled"

Question

Disk Utility SMART Status "Not Supported", but DriveDx SMART Support "Enabled"

travelswagger opened this issue 4 years ago · comments

Hello. Could you kindly assist? I'm running macOS High Sierra 10.13.6 with DriveDx 1.10.1. I have 2 Western Digital EasyStore WD080EZAZ-11TDBA0, both with multiple volumes. Both WD drives are physically connected directly (no USB hub) to USB 3.0 ports on a 2012 Mac mini (Late 2012) Model A1347 with 2.3 GHz Intel Core i7.

Is SAT Smart driver 0.10.2 installed and running correctly?

macOS Disk Utility shows each drive SMART Status to be "Not Supported"
however, DriveDx SMART Support indicates "Enabled"
furthermore, DriveDx Advanced SMART Status indicates "OK"

Thank you for clarifying as I am not technical but wish to diagnose and monitor my external drives.

Al Varnell · Answer 1 · Tue Dec 01 2020 19:53:48 GMT+0800 (China Standard Time)

Sounds like your driver is installed and running correctly.

SAT-SMART has not been supported here for several years now, so there's a good chance nobody will notice your request. Perhaps DriveDx or SMART Utilities can help. I know DriveDX posts about "driver v0.8.2 (try if v0.10.2 is not compatible with external drive)"

BinaryFruit · Answer 2 · Wed Dec 09 2020 08:56:59 GMT+0800 (China Standard Time)

Thanks for your interest in our software.
Please check our online FAQ - Disk Utility reports SMART status as “Not Supported”, but DriveDx reports SMART support as “Enabled”.

Al Varnell · Answer 3 · Wed Dec 09 2020 09:19:30 GMT+0800 (China Standard Time)

Note that the OP is running macOS High Sierra and your FAQ applies to macOS Catalina and above.

BinaryFruit · Answer 4 · Wed Dec 09 2020 09:48:57 GMT+0800 (China Standard Time)

Note that the OP is running macOS High Sierra and your FAQ applies to macOS Catalina and above.

Ok, thanks. It was relatively long ago, so we don't remember exactly the moment when these changes were included in macOS. Yes, most probably this happened in macOS 10.13.6 - as macOS 10.13.6 is the minimum OS required for Notarization.

BinaryFruit · Answer 5 · Wed Dec 09 2020 10:08:19 GMT+0800 (China Standard Time)

All in all, this issue related to the so-called "Hardened Runtime" and "Secure Boot" features of recent macOS versions. Since 10.13.6 macOS components do not load any non-Apple dylibs (like for example SATSMARTLib.plugin) and since Big Sur - macOS kernel does not load non-Apple kexts during system startup process (like for example SATSMARTDriver.kext) even on Macs without T2 chip (on Macs with T2 chip "Secure Boot" was introduced before Big Sur).