Jump to content
Sign in to follow this  
nnhoang

Old Drive with lots of SMART errors

5 posts in this topic Last Reply

Recommended Posts

Hi guys, I've had this drive in cold storage for years. Last I remember, this drive had issues with one of my motherboards and caused data corruption. I contacted Seagate and they sent me a brand new drive which still works today. That being said, I never really checked it after that and found it in an old box. I popped it in and it had a lot of SMART data errors, but it's overall-health is marked as PASS.

 

It's a Seagate ST2000DM001-1CH164 drive, just wanted the community's opinion to see if it's safe to use?

 

 

 

Screenshot from 2020-06-28 17-44-18.png

Share this post


Link to post

As shown, that's a definite NO to using it in the parity protected array. It could possibly be ok to use as a scratch drive for transitory data you don't care about if it passes an extended smart test and reallocates or verifies those current pending sectors.

 

Never use a questionable drive in the parity array, all drives must be read perfectly from end to end to reconstruct a failed drive.

Share this post


Link to post

I dont think these values are super high IMO. I would use the drive for a month outside the array with a bit of daily use and compare a new screenshot to this one and see if there is no change. If there is not, then most likely this drive is just refurbished. 

Share this post


Link to post

Exactly the same issue I had or still have with 1 of my 4TB Seagate Ironwolf HDDs out of the box & the HDD is still functional till this day without an issue, although I trust it less to last.

did a Preclear test on it and there wasn't any issues so I use it in my backup server.

Share this post


Link to post
4 hours ago, jonathanm said:

As shown, that's a definite NO to using it in the parity protected array. It could possibly be ok to use as a scratch drive for transitory data you don't care about if it passes an extended smart test and reallocates or verifies those current pending sectors.

 

Never use a questionable drive in the parity array, all drives must be read perfectly from end to end to reconstruct a failed drive.

Great point, I thought I'd put it in the array and it if fails, the rest of them can rebuild it, but I forgot that other drives could fail before it and cause even more issues. 2TB just isn't worth it for the headaches it can cause.

 

I'll run an extended pre-clear run on it, maybe 5 rounds and if nothing changes, it'll go in the backup server to backup the backups. Thanks for your input everyone.

Share this post


Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this