1 |
On 2020/06/15 at 11:07am, Dale wrote: |
2 |
|
3 |
> I finally bought a 8TB drive. It is used but they claim only a short |
4 |
> duration. Still, I want to test it to be sure it is in grade A shape |
5 |
> before putting a lot of data on it and depending on it. I am familiar |
6 |
> with some tools already. I know about SMART but it is not always 100%. |
7 |
> It seems to catch most problems but not all. I'm familiar with dd and |
8 |
> writing all zeores or random to it to see if it can in fact write to all |
9 |
> the parts of the drive but it is slow. It can take a long time to write |
10 |
> and fill up a 8TB drive. Days maybe?? I googled and found a new tool |
11 |
> but not sure how accurate it is since I've never used it before. The |
12 |
> command is badblocks. It is installed on my system so I'm just curious |
13 |
> as to what it will catch that others won't. Is it fast or slow like dd? |
14 |
|
15 |
If you have a few days, I'd run spinrite |
16 |
(https://www.grc.com/sr/spinrite.htm) on it. It is very slow but very |
17 |
good at checking and repairing disks. (Gibson is working on an updated |
18 |
version that will be much, much faster.) No joke that you would have to |
19 |
leave the current version running for several days (at least) for an 8TB |
20 |
drive, if you ran the most comprehensive test. |
21 |
|
22 |
Aside from time, the drawback is that spinrite costs money. |
23 |
|
24 |
I've used badblocks and it is not fast, but not nearly as slow as |
25 |
spinrite. IIRC, it took maybe a few hours for a 250GB drive. That said, |
26 |
I've been lucky not to have a huge number of problems with drives, so I |
27 |
can't say how much either has helped. |
28 |
|
29 |
-- |
30 |
Chris Spackman chris@××××××××××.com |
31 |
|
32 |
ESL Coordinator The Graham Family of Schools |
33 |
ESL Instructor Columbus State Community College |
34 |
Japan Exchange and Teaching Program Wajima, Ishikawa 1995-1998 |
35 |
Linux user since 1998 Linux User #137532 |