bht
bulk hdd testing with badblocks script (by ezonakiusagi)
burnin-drive
By samuelkadolph
bht | burnin-drive | |
---|---|---|
7 | 1 | |
214 | 1 | |
- | - | |
0.0 | 2.6 | |
7 months ago | 2 months ago | |
Shell | Python | |
GNU General Public License v3.0 only | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
bht
Posts with mentions or reviews of bht.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-12-12.
-
Bought a few of these Ultrastar 16TB for $169 each. Is a burn-in script enough to spot any issues with them? Will be used in ZFS mirrors for 24/7 CCTV recording and Jellyfin server
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.
-
2 brand new drive failures in 1 week -- 18TB drive curse, thank god for ZFS or I'd have lost it all
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).
-
6 things that can go wrong when you're hellbent on using old hardware to crossflash an HBA and to burn-in 8 new drives. Details in the comment.
bht github link
-
Used SAS drive checklist?
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?
-
This is how long it takes to "burn in" a Toshiba MG09 18 TB drive using badblocks. Around 8 days + 1 more day if you add a long S.M.A.R.T test at the end. I recommend doing so before trusting a new drive with my data. Especially one so large. I ran badblocks via tmux on my TrueNas server.
Here is link number 1 - Previous text "bht"
- [O] [US] 10TB HGST SAS 4Kn drives $100
burnin-drive
Posts with mentions or reviews of burnin-drive.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-06-05.
-
This is how long it takes to "burn in" a Toshiba MG09 18 TB drive using badblocks. Around 8 days + 1 more day if you add a long S.M.A.R.T test at the end. I recommend doing so before trusting a new drive with my data. Especially one so large. I ran badblocks via tmux on my TrueNas server.
Yeah, it's a set and forget thing. I wrote a little python script to do it all for me. I fire it up in a screen session and just leave it be. You aren't limited to testing 1 drive a time. So if I'm expanding my NAS or building one for a client, I test all the drives at once. The 4 patterns that badblocks uses by default are definitely overkill but I'm not in a rush.