WD Red Pro 20 TB Disk Burn-In Duration

TrueNAS General
1

Just finished the Burn-in of 4 WD Red Pro 20 TB Disk Drives
These were brand new Straight from the factory.
Model number (for those interested) are: WDC WD201KFGX-68BKJN0

I downloaded the disk-burnin.sh script from dak180 from github and did a bit of modification to it. Modifications included:

  • speed up badblocks by optionally setting the Blocks_at_once value.
  • send an optional e-mail message when the script succeeded or failed.
  • adding an optional verbose mode to help trace through the script when things weren’t working right
  • adding comments to various sections so when I come back in 6 months I’ll know what I did!

So what did I find?

Average time over the 4 drives for the tests were as follows:
Smart Short Test: 2 Minutes
Smart Long Test: 1 Day, 12 Hours, 42 Minutes, 2 Seconds
BadBlocks Test: 8 Days, 4 Hours, 50 Minutes, 37 Seconds

Average Time for Total Burnin: 11 Days, 6 hours, 18 minutes, 42 Seconds

Now on to Setting adding them to my pools.

2 Likes
2

Are you making a PR so those improvements go upstream?

1 Like
3

What does this mean? Are you running all four test patterns still?

The email addition sounds like a nice touch.

Did you make the recommendation for the changes to @dak180 ?

4

The default value for the BlocksAtOnce value when running badblocks is reading/writing 32 blocks at once. I found that when running badblocks on other large capacity disks (10, 15, and 20 TB) the time was exceedingly long.

Through trial and error I found that on my systems I could bump that value up to 32767 without aborting badblocks due to memory errors. I actually tested with higher numbers and it would get about 3/4 of the way through the first pattern and then abort with a memory error.

Using a higher number seems to reduce the number of read/write operations, though the actual amount of data is still the same.

All 4 patterns are still run, the program simply writes/reads more blocks of data at one time.

3 Likes
5

As for my version of the script. The plan is to make a few more minor modifications and comments, test it on a few smaller drives and then make it available on my github page as part of my offering

In addition, I will add it as a fork to dark180’s version. If dark180 wishes to incorporate the changes and continue to allow modifications, I have no issues with this.

6

I completely understand and know what you are talking about. Thanks for the clarification on what you were doing.

That is @dak180, not dark180.

7

dak180 !! got it! (^&)%&*autocorrect!!!

1 Like