Sign in to follow this  
Followers 0
Vova

HDD failed with HUGE write count

8 posts in this topic

Hi. after being on a vacation with my unraid box turned on 24/7 today i've noticed that one of the data HDD was put in a disabled state. there were 187 errors on the Main tab in UI. Also, what was surprising is that the write count on this drive was very huge. i'm talking about very big number like 18,000,000,000,000,000 or even more zeroes. Unfortunately, i've stopped/starter the array w/o taking the screenshot before and that counters were zeroed out.

 

I have a question - why did i have such a big number of writes for this HDD? i assume that because of this HUGE number of writes the drive has failed.

attaching the diag file.

Please help to identify the root cause.

tower-diagnostics-20170619-1516.zip

0

Share this post


Link to post
Share on other sites
56 minutes ago, Vova said:

I have a question - why did i have such a big number of writes for this HDD?

 

That huge number is the result of the disk dropping offline, not the cause, unfortunately your syslog is filled with:
 

Jun 18 10:40:02 Tower kernel: aacraid 0000:08:0e.0: AAC0:aac_check_health: Host adapter dead -1
Jun 18 10:40:03 Tower kernel: aacraid 0000:08:0e.0: AAC0:aac_check_health: Host adapter dead -1

so we can't see what happened, but SMART looks fine so check/replace cables and rebuild to the same disk.

0

Share this post


Link to post
Share on other sites

Thank you. i've removed the Adaptec controller which was rubbishing the logs. 

after that i've run the rebuild procedure and seems the drive is flapping. i'm attaching the log.

 

please give me some clues here. should i replace the cable/backplane?

i've seen very similar errors on completely other drives on this Microserver G8 on Centos 7 before (2TB WD SEs)

tower-diagnostics-20170621-1421.zip

0

Share this post


Link to post
Share on other sites

Looks to me more like a disk problem rather than cable/backpane issue, but trade backplanes with another disk, if it fails again it's the disk.

0

Share this post


Link to post
Share on other sites

Johhnie, given that i've seen the same errors previously with centos on completely other disks - does it provide any valuable info to reconsider the verdict?

 

0

Share this post


Link to post
Share on other sites

It's easy to confirm by using the disk in a different backplane, unless there's a general problem with the server/controller.

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0

Copyright © 2005-2017 Lime Technology, Inc. unRAID® is a registered trademark of Lime Technology, Inc.