Fire-Dragon-DoL
Contributor
- Joined
- Dec 22, 2018
- Messages
- 103
I've been running disk-burning tests on my new HDDs using https://forums.freenas.org/index.ph...for-freenas-scripts-including-disk-burnin.28/
Of 4 HDDs, 3 of them are showing a lot of read errors.
Are they really all damaged? 1 of them is a WD blue (meant for backups, not to run inside the NAS, just plug-in and plug-out), the other 2 are WD Red and I'm surprised they all come with damages (they have been bought various years apart from each other)
I must point out that I updated the script to use the -c 262143 flag:
Which should speed up the process (it's been running for 3 days straight and it's still far from being completed. URGH).
Do I have to change all those disks? Could it be a software problem related to the readings and the -c flag?
Of 4 HDDs, 3 of them are showing a lot of read errors.
Are they really all damaged? 1 of them is a WD blue (meant for backups, not to run inside the NAS, just plug-in and plug-out), the other 2 are WD Red and I'm surprised they all come with damages (they have been bought various years apart from each other)
I must point out that I updated the script to use the -c 262143 flag:
badblocks -b 4096 -c 262143 -wsv -o "$BB_File" /dev/"$Drive"
Which should speed up the process (it's been running for 3 days straight and it's still far from being completed. URGH).
Do I have to change all those disks? Could it be a software problem related to the readings and the -c flag?