Can btrfs track / avoid bad blocks?
I have a HDD which I don’t entirely trust, but still want to use (burstcoin mining, where if I get a bad block in a file, I’ll only lose a few cents).
badblocks
Linux – Repairing bad blocks on a RAID1 array with GPT
The tl;dr: how would I go about fixing a bad block on 1 disk in a RAID1 array?
What are the pros and cons of badblock’s two non-destructive tests?
I use badblocks to test my 32GB class-10 microSD card that I use to boot my RPi. I already have a functioning file system on it, so I don’t want to scan it with the -w option (destructive read-write test).
How do you use badblocks?
I need to do a destructive (rw) test on a new drive, and a read-only on a drive that fell out of my RAID array. I want to see if it finds problems and how far along it is.
How to interpret badblocks output
The man pages for badblocks do not seem to mention what the three numbers in the output mean in particular:
Is interrupting badblocks risky?
I’m running badblocks to check for bad segments on an external drive, and it’s been about an hour and it has not yet finished. Now, I need to go and consider cancelling. Is this somehow risky? Should I avoid this?