-
Intel 520 60GB - Day 114
Drive hours: 2,681
ASU GiB written: 854,340.34 GiB (834.32 TiB)
Avg MB/s: 93.53 MB/s (237 hours)
MD5: OK
Host GB written (F1): 860,355.69 GiB (840.19 TiB, 27531382 raw)
NAND writes (F9): 609,064 GiB (594.79 TiB)
Reallocated sectors (05): 0
Failure count (AB, AC): 0 program, 0 erase
Raw Error Rate (8B): 104 normalized
Available Reserved Space (AA): 100 normalized
Media Wearout Indicator (E9): 1
Sandisk Extreme G25 - 120gb - Day 14
Drive hours: 335
ASU GiB written: 142,234.58 GiB (138.90 TiB)
Avg MB/s: 121.58 MB/s (237 hours)
MD5: OK
Host GB written (F1): 143,170 GiB (139.81 TiB)
NAND writes (E9): 106,775 GiB (104.27 TiB)
Retired Block Count (05): 4 raw
Failure count (AB, AC): 1 program, 1 erase
Raw Error Rate (01): 105 normalized
Media Wearout Indicator (E7): 73 normalized
Wear Range Delta (B1): 3 raw
Reported Uncorrectable Errors (BB): 0 raw
@Anvil: can you change ASU so that it reads the file for MD5 checking off the disk, rather then out of memory cache. My endurance computer has 8gig RAM so reading in the file for MD5 checking just seems to be checking my memory rather then the disk! Since I fixed my memory a while back, it probably won't find any faults there!
I've just been noticing that the total host reads haven't been increasing on my drives at all! Running HDD-scan though (while ASU is running) does seem to increase the host reads like it should
Last edited by canthearu; 06-19-2012 at 05:05 AM.
Tags for this Thread
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
Bookmarks