| 202 | | I've got a few of these things in 32/64GB and between 3-7 years poweron time. smartctl gives the same results on Linux (rhel and ubuntu). They really are quite crufty devices. :) |
| 203 | | |
| 204 | | |
| | 202 | I've got a few of these things in 32/64GB and between 3-7 years poweron time. smartctl gives the same results on Linux (rhel and ubuntu). |
| | 203 | They really are quite crufty devices with a _very_ low sequential write speed (18/20/40/40MB/s for 8/16/32/64GB) and an endurance of 3000 cycles. |
| | 204 | |
| | 205 | advertising sheets quote them at 110MB/s - that's the read speed only. |
| | 206 | |
| | 207 | One of our vendors has commented that they tend to simply stop working with little-to-no warning - but none of the vendor appliances have been monitoring bad block parameters - assuming that reallocated sectors was valid. That's why I recommended filtering these returns. |
| | 208 | |
| | 209 | What we saw was a dramatic slowdown in write speeds when one of the 64Gb units hit 256 bad blocks - something less than 1MB/s. None of the units has changed the 0x64 "value" field for either bad blocks attribute no matter how many have failed and I'm going to push one through a few write cycles to see if they ever do (I suspect not) |
