bht VS disk-burnin-and-testing

bht is a great script I use to burn in my drives from TheArtOfServer's channel. https://github.com/ezonakiusagi/bht. Allows you to run 4 badblocks tests back-to-back completely writing through the entire disk to fully test its health.

Either use badblocks followed by a long smart test or use bht (https://github.com/ezonakiusagi/bht) if you want to test multiple drives at once (also followed by a long smart test).

bht github link

Igmyeongui, I found a similar tool https://github.com/ezonakiusagi/bht which looks like its easier to run on multiple disks at once since the tool you linked mentions having to open multiple sessions and run the tool manually each time. Have you seen BHT? If so I was wondering if there was something you liked about the one you linked over BHT?

Here is link number 1 - Previous text "bht"

Verify authenticity or integrity? I run this on all of the drives I get in: https://github.com/Spearfoot/disk-burnin-and-testing

You could check them using badblocks or the script available at this github repo https://github.com/Spearfoot/disk-burnin-and-testing. If they fail, send the seller the log file as evidence and getting a refund/replace should be pretty straightforward

I used this script fine on 18TB drives. I don't know why it wouldn't work on 20TB https://github.com/Spearfoot/disk-burnin-and-testing . It uses badblocks, but honestly I don't know much about this stuff. If it passes I consider it good to deploy. It does look like it uses a 8192 block size.

Hello, I'm using Spearfoot's disk-burnin script for smart short, smart long and bad blocks tests. I read here and there that we shouldn't test bad blocks on SSDs and I'm curious why. I'd also like to know how to test SSDs with the Spearfoot script since I already know how to test multiple disks at the same time with screens in Putty. I've read the documentation and scrolled through the script and I can't find a way to deactivate the bad blocks test and only do smart short and smart long.

I'm starting this process tonight and this is the best ressource I've found so far to do disk burnin and testing.

You can do a 'burn-in' test for 48 hours in an attempt to give yourself some confidence that they are okay. In my experience unless they were going into a high-redundancy array the risk associated with keeping them is much higher than the downside of replacing them right away, if you can. Shouldnt be any guilt with returning them, the shop that sold them should be able to make a claim against the shipping company and should sell them as used/returned drives and the person who does buy them understands and accepts that risk.

I use this for new drives https://github.com/Spearfoot/disk-burnin-and-testing

So I'm currently testing a new pair of drives in my TrueNAS Server. I'm running Spearfoot's burnin script and it has finished running badblocks and has launched the final smartctl long-test.