SMART Utility für Mac

Does anyone know if this developer post is from 2019? I just see a date of 8-Jan. I believe it is from 2019 and does indicate development is continuing. Yay! https://www.volitans-software.com/2019/01/the-future-of-smart-utility-2/ The Future of SMART Utility We wanted to give an update on SMART Utility. As you probably know, version 4.0 is much delayed. This lead to a re-evaluation of the roadmap. Version 4.0 was too ambitious for a single release, especially re-designing the interface. So the revise plan is this: Version 3.3 (out in a few weeks): Some new features and a bunch of bug fixes Version 4.0 (out in six months): Re-work the algorithm to better match todays drives Version 5.0 (out in one to two years): Re-design the interface

Users need to realize, this app (and similar ones) are dependent and/or influenced by several external factors.
1) The information returned by SMART is open to interpretation. In many cases, manufacturers themselves don't adhere to the same interpretation of what a particular data field means relative to their product. Ultimately, the manufacturer of the drive decides how and what to report back. There really isn't any enforcement to keep manufacturers in line as far as how their devices report.

Once data is returned, then SOME programs that try to calculate and give a 'probability' of failure or life expectancy rating.; these ratings need to be taken in context, or at least take with grain of salt. There are several industry studies which have shown that correlation between SMART data, predictions made based on the data and actual failure rates, is NOT that strong...possibly only correlated in less than a third of hard drive failures. I've had rotational drives during the initial 'burn in' period that show a increase in some of the so called negative indicators (bad sectors reallocated); but then 'settle down' and continue working fine for years afterwards with no increases. Don't get caught up too much in what SMART data is saying, unless you see a trend overtime. Your strategy should be to always have multiple backups of key data, so that when and if a drive fails, your data is safe, rather than obsessing about whether to replace a drive the first time it shows any negative indication.

2) Regards SSDs, the SMART standard and specification was developed at a time when all drives were rotational. When it comes to SSD/non mechanical drives, many of the data types/info defined by SMART are ambiguous at best, or meaningless, or at worse used by manufacturers to bolster their product when in fact they are irrelevant. Some makers have added on additional data fields to report so called 'SSD' specific info, but other makers are not required to use them, or if they do, don't necessarily report back the same data, since the definition is so open. Or worse, they will come up with a way to report back a lower value and use that in a positive spin, even the meaning of what that data really indicates has been redefined by them. A perfect example is data field 231, loosely defined as 'Life Left' for SSD drive. Remember, this is data reported back by the drive based on the manufacturer's interpretation. Using different criteria, Samsung drives might report back a million erase cycles remaining, but Crucial drives might use that field to report back that 50% reserved space is left.

So, in the case of Samsung, if the drive was rated for 2 million erases cycles, does that mean the drive has 50% of life remaining; on a Crucial drive, if you never get close to using the full capacity, 50% reserved space isn't really a factor; and what actually can be inferred from that as far as 'Life Remaining'. For example, when a manufacturer says this SSD drive reports 'zero' whatever, i.e. my product is good....well, actually ALL SSDs are going to report a zero for that data, or some might report '100', but so what, because it has no relevance for non-mechanical drives.

Most people I suspect pay particular attention to the 'reallocated bad sector' data; for rotational drives that makes good sense. For SSDs, the data has less relevance, because the standard hasn't evolved to define what that really means for SSDs, so manufacturer's have, of course, used this ambiguity to dictate the data returned to put their product in a better light. With modern SSDs and controlers using techniques likes over provisioning, trim, garbage collection, etc. it can be open to interpretation what a 'bad sector' is. Manufacturer's can take a problem 'memory location' and move it to the over provisioning bucket of memory, or mark it to never be trimmed or garbage collected....does that mean they have to report it as a 'bad sector'. It's straight forward to associate an actual physical location of a bad sector when it comes to rotational device; for a memory device, it's a little more complicated. A "sector of data" on a rotational drive is 512 bytes at a physical location on the disk. With SSDs the smallest block is 512 KB (a thousand times larger), made up of pages, which can be variable, but frequently 4KB. These pages may or not be continguous in the 'traditional' sense, and can CHANGE internally without any knowledge to the operating system. This happens when an SSD drive performs it's own internal clean up, provisioning and trim operations. Windows and macOS still see that 'sector' of your Word document as sitting at sector 143,245; but internally, the drive can move the location and composition of that block around.

3) In order to retrieve SMART data, requires either an interface that is capable of doing so, or a direct method to the drive which requires specific knowledge of the model and how to retrieve the info (without using the standard interface commands). Internal drives on a SATA bus have no issues, the SATA spec provides for the proper commands to query a drive and report back the data. External drives are dependent on the chipset of the enclosure as to whether the interface supports the SMART commands needed to query the drive and return the SMART data. Older USB external interfaces (as well as Firewire) did not have this pass through capability. Newer interfaces which support USB Attached SCSI (UAS) or USB Attached SCSI Protocol (UASP). do allow for SMART data retrieval, so when you buy an external drive or stand alone enclosure or drive dock, make sure it supports UASP

End of the day, it's fine we have programs that report back SMART info. For rotational drives, more useful, for SSD's, not as much. How you personally, or the programs that retrieve data, interpret what that data means, can be subjective, particularly when it comes to trying to predict failure or life expectancy (again, better for rotational, not so much SSDs). Generally speaking, mechanical devices physically wear down over time, so may be possible to see a trend and they 'fail over time'. Pure electronic components tend to not show 'symptoms' or degradation over time, for lack of a better word; they work until such time that they don't work. That's why I said it's better to be sure that you have multiple backups rather than obsess too much about whether a particular device is showing signs of failure or going to fail.

No responses from developer to any queries. No updates since Oct. 2016 despite the MANY advances and changes in drive tech. No way.

THIS DOES NOT WORK ON SSDs (Solid State Drives) — IT ONLY WORKS ON HDDs (Hard Disk Drives, which Apple abandoned years ago in all MacBooks). Developer, please correct me if I’m wrong. If I’m not, do the right thing and indicate as much in your app’s introduction. BTW, DriveDX DOES work on SSDs. So now I have to abandon this $25 license and buy a $25 DriveDX license.

I've owned a 10-pack license and used SMART Utility since mid-2010. I do IT support and offend diagnose the "spinning beachball" on client computers as bad drive sectors. I find it amazing that even a single bad sector, even if reallocated, can cause such problems but they do. S-U has provided the info I need to point out that a replacement HDD is needed and get the client back running smoothly. I look forward to the announced, but late, release of v4!