Status of byte-for-byte validation in 2019?
Posted: Mon Dec 24, 2018 3:57 pm
We've had discussions here over the years on SSDs, byte-for-byte validation, and DRAT.
For those new to the topic, Deterministic TRIM (DRAT) is a capability that must be supported by the SSD to prevent byte-for-byte validation failures in TeraByte Image.
I had to replace a drive, and searched everywhere for documentation on whether drives support DRAT. That information is apparently not provided by vendors.
I had to buy on faith, hoping that the more expensive server-grade SSD would support DRAT.
I purchased the Samsung Electronics DAV 883 DCT 240G, and I'm happy to report that it does work with Image and byte for byte validation.
However, this is not really sustainable or scalable.
What are other users doing about this issue?
1) Buying SSDs without knowing whether they support DRAT and hoping for the best? If so, how is it working out?
2) Giving up on byte for byte validation, and hoping Image's "internal consistency checks" are sufficient to detect any errors?
From Terabyte's point of view, do you see byte for byte validation as an less-useful feature that is effectively deprecated in the age of the SSD? If not, is there any way that Image could be extended to accommodate byte-for-byte validation with Non-deterministic TRIM SSDs? For example, when byte discrepancies are found in a disk block, cross reference in the file system, and determine if that block was allocated or unallocated before considering the error as fatal and failing the validation.
For those new to the topic, Deterministic TRIM (DRAT) is a capability that must be supported by the SSD to prevent byte-for-byte validation failures in TeraByte Image.
I had to replace a drive, and searched everywhere for documentation on whether drives support DRAT. That information is apparently not provided by vendors.
I had to buy on faith, hoping that the more expensive server-grade SSD would support DRAT.
I purchased the Samsung Electronics DAV 883 DCT 240G, and I'm happy to report that it does work with Image and byte for byte validation.
However, this is not really sustainable or scalable.
What are other users doing about this issue?
1) Buying SSDs without knowing whether they support DRAT and hoping for the best? If so, how is it working out?
2) Giving up on byte for byte validation, and hoping Image's "internal consistency checks" are sufficient to detect any errors?
From Terabyte's point of view, do you see byte for byte validation as an less-useful feature that is effectively deprecated in the age of the SSD? If not, is there any way that Image could be extended to accommodate byte-for-byte validation with Non-deterministic TRIM SSDs? For example, when byte discrepancies are found in a disk block, cross reference in the file system, and determine if that block was allocated or unallocated before considering the error as fatal and failing the validation.