deadvoid
Cadet
- Joined
- Oct 17, 2019
- Messages
- 2
hi, long time listener, first time caller
I have a few WD Red 3TB drives that I've tested with this script, which i know perhaps isn't kosher here since jgreco wrote a script for it, but i noticed that the one in github (by using badblocks) puts more emphasis in read & write while jgreco's does seek time & read speed. The first drive more or less passed the test (1 pass completed in around 56 hours or so), came out with 0/6/0 (read/write/corruption) errors, while the 2nd failed on 0x55 pattern write phase at around 25th hour mark.
So while this does not entirely have anything to do with Freenas, what do you guys think about the method employed by this script, or specifically by badblocks? Is it useful to expose or speeding up bad drives or maybe it's actually harmful to a perfectly fine/healthy disk?

I have a few WD Red 3TB drives that I've tested with this script, which i know perhaps isn't kosher here since jgreco wrote a script for it, but i noticed that the one in github (by using badblocks) puts more emphasis in read & write while jgreco's does seek time & read speed. The first drive more or less passed the test (1 pass completed in around 56 hours or so), came out with 0/6/0 (read/write/corruption) errors, while the 2nd failed on 0x55 pattern write phase at around 25th hour mark.
So while this does not entirely have anything to do with Freenas, what do you guys think about the method employed by this script, or specifically by badblocks? Is it useful to expose or speeding up bad drives or maybe it's actually harmful to a perfectly fine/healthy disk?