The remaining lifetime as a percentage is likely to be floor(AD/2) but this doesn’t quite match (it currently predicts 97% where SSD Scope reports 98%). It seems AD starts off at 199 (from my initial review) and decrements to zero at the end of life. However, again, the attribute AD seems to most closely reflect the wear out indicator – which SSD Scope reports at 98%. This is shown by decoding 0x0046 = 70 decimal, 0x0094 = 148 decimal, 0x0024 = 36 decimal, which matches the reported values from SSD Scope.Īs a result, if you select 10 DEC – 2 Byte display option, the values come up directly! So now you don’t need to use SSD Scope to work out the erase counts!Īnother frustration is the wear-out indicator, which doesn’t correlate well with most of the values which are set to 100. Looking at attribute AD, it is clear that the erase count is being encoded as 16-bit values packed side by side. SSD Scope currently reports the drive to have an average erase count of 70, maximum of 148 and minimum of 36. Of these vendor specific variables, only A9, AD, E9 and EA are non zero.
Of interest are the vendor specific attributes A7, A9, AA, AD, AF, E9, EA, F0. The named attributes are generally “defined” attributes, and are of little interest to us. This allows us to easily visualize the binary data being returned by the attributes. The first step of making sense of the data is to switch the view over to HEX. As a result, this article contributes new information to the community.įrustrated, I decided to delve into the SMART data to get a little bit more of a look. Of note is that despite CrystalDiskInfo 5.1.14 being used in this posting, I upgraded straight-after to 6.3.0 with no real changes in the SMART data definitions observed. Even with most variables showing 100, SSD Scope was returning MWI of 99% or 98%. That being said, Transcend’s SSD Scope offers its own SMART tool in SSD Scope which offers an ability to report the Average, Minimum and Maximum Erase Count plus the Wear out indicator. The latest firmware update wiped most of the user-visible attributes, but retained the undocumented values. Even to this date, CrystalDiskInfo still does not understand the vast majority of the attributes which are Vendor Specific and generally undocumented. Having reviewed the Jmicron JMF667H based Transcend SSD340, one of my biggest frustrations was the lack of documented SMART data variables.
0 kommentar(er)
