Is disk really bad if mkfs.ext4 -c -c reports errors?

[Chris Green]

On Wed, Jan 11, 2017 at 12:20:29PM -0500, Rashkae wrote:
> On 17-01-11 11:46 AM, Chris Green wrote:
> 
> > 
> >      Testing with pattern 0x55:  67.02% done, 23:57:16 elapsed. (0/78947/0 errors)
> > 
> 
> 
> Very interesting that you complete one pass with no errors, then on the
> second pass, start getting large number of *write* errors, with no
> indication of a problem in SMART.
> 
> I would say, off the top of my head, this is indicative of an I/O problem on
> the Motherboard, but it doesn't rule out either the drive or cable...
> 
> Unfortunately, I don't know of any easy way to diagnose a failure like this.
> I would have to separate the suspect drive from the suspect computer and
> test them independently.  That is, put the drive in a different computer and
> re-run the test.  At the same time, put a different drive in the existing
> computer and format it there.
> 
Exactly what I'm about to do.  I have taken the suspect drive out of
the system where it was and have put a new WD 3TB drive there instead.
I'm just about to start formatting it.

I will put the bad/suspect drive in an old test system and run the
badblocks test again.

-- 
Chris Green