Array has 1 disk with read errors. Disk4: just sick or dead-man-walking?

[PhilipJFry]

Hi guys,
Recently I emptied an older 1TB WDC drive and added it to the array.

It was originally one of those desktop usb style drives that i gutted and installed into the server.

This morning, during the scheduled parity run, the drive has been flagged with read errors.

SMART report attached along with its attributes.

Should I retire this drive? or is it still safe to use for a little longer.

 

And the big picture question:

"At what point in a drives lifecycle should it be deemed no longer viable?".

 

Obviously, the bad sector(s) are a pre-emptive indication that the drive will fail completely at some point. But until that happens, could it still be used for non-critical data and/or as a temporary scratch share (e.g for docker containers working directory)?

 

With thanks

PJF

futurama-smart-20221010-0709.zip

[JorgeB]

It's logged as disk problem, you can run an extended SMART test to confirm, it it fails replace it, or depending on the situation, you might try to do a full disk write, pending sectors should go back to zero then see if they come back again soon or not.

[PhilipJFry]

On 10/10/2022 at 8:03 PM, JorgeB said:

It's logged as disk problem, you can run an extended SMART test to confirm, it it fails replace it, or depending on the situation, you might try to do a full disk write, pending sectors should go back to zero then see if they come back again soon or not.

Cheers 4 the info @JorgeB.
Try as I might, SMART extended test kept returning read errors... so guess that's a negative for continued use.

I tried unsuccessfully to remove it from the array. My fault for not following the instructions properly. But its now gone.. yay... sort of.

PJF
Feedback: it would be nice if the guides (and the required actions) were a little more newbie focused... i.e 1 click (old school clippy comes to mind 🙂 ). For many of us oldies, we don't breath unRaid everyday 😜.