disk-burnin-and-testing
minio-service
Our great sponsors
| disk-burnin-and-testing | minio-service | |
|---|---|---|
| 18 | 2 | |
| 787 | 358 | |
| - | 3.4% | |
| 0.0 | 4.9 | |
| 10 months ago | 3 months ago | |
| Shell | Shell | |
| GNU General Public License v3.0 or later | - |
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.
disk-burnin-and-testing
-
[HDD] Seagate EXOs 12TB SATA Hard Drive - $99.99 ($8.33/TB) (Refurbished)
Verify authenticity or integrity? I run this on all of the drives I get in: https://github.com/Spearfoot/disk-burnin-and-testing
-
Should I return my drives?
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
- Just got some new drives. What do you think? Is this good enough packing?
-
Family member wants to stress test 4x20TB drives before using them. Need help....
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.
-
About to finish testing my 12x mechanical drives and not sure how to test my SSDs now
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.
-
Used SAS drive checklist?
I'm starting this process tonight and this is the best ressource I've found so far to do disk burnin and testing.
-
Harddrive beaten in shipping, how can I confirm if it's reliable?
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.
- It ain’t much but it’s my first big boy storage drive. Question: I always run a full error scan on new HDD’s with HD Tune, is this necessary to ensure a full working drive or is it overkill? Should I just check SMART attributes?
-
Software to test harddrives?
I use this for new drives https://github.com/Spearfoot/disk-burnin-and-testing
-
Create vdev while completing burnin
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.
minio-service
-
MinIO on OpenBSD 7.2: Install
Per https://github.com/minio/minio-service it is advised to run minio with more file descriptors than what is allowed by the default daemon login class.
-
Make "minio server" survive a reboot
Service files we maintain here, most pepole would be looking at linux distributed - https://github.com/minio/minio-service/tree/master/
What are some alternatives?
stressdisk - Stress test your disks / memory cards / USB sticks before trusting your valuable data to them
scriptsrep - Contains useful scripts
FreeNAS-scripts - Handy shell scripts for use on FreeNAS servers
restic-automatic-backup-scheduler - Automatic restic backup using Backblaze B2 storage and either Linux systemd timers, macOS LaunchAgent, Windows ScheduledTask or simply cron.
TrueNAS-Scripts
bash-ini-file - Get keyvalues by its section/keyword from an INI-format (v1.4) file in bash (also works with systemd, NetworkManager config files)
freenas-iocage-nextcloud - Script to create an iocage jail on FreeNAS for the latest Nextcloud 28 release, including Caddy, MariaDB or PostgreSQL, and Let's Encrypt
namespaced-wireguard-vpn - Systemd configuration for a network namespace containing a WireGuard VPN connection
truenas-useful-scripts - A collection of scripts for TrueNAS to display useful information, do some reporting by email and backup the TrueNAS config.
src - Read-only git conversion of OpenBSD's official CVS src repository. Pull requests not accepted - send diffs to the tech@ mailing list.
grafana-unraid-stack - Meet Gus! He has everything you need to start monitoring Unraid (Grafana - Influxdb - Telegraf - Loki - Promtail).
go - The Go programming language