[PLEASE HELP] smartd [51888]: Device: /dev/ada2 1 Currently unreadable (pending) sectors

[VividClarity]

Just logged into my FreeNas Server and noticed this error in the Alerts Tab from June 30th, 2019 in the upper right of FreeNas I've spent hours trying to figure out what the issue I've been getting the same error repeatedly since June. I'm hoping someone can help me I have since turned on email notifications for errors like this so I don't go this long without fixing it.

 

[Chris Moore]

Please look at this resource:
https://www.ixsystems.com/community/resources/uncle-festers-freenas-beginners-guide.120/

It has guides on how to configure many things in FreeNAS, one of those things is SSH, so you can access a better terminal window than the one offered by the WebGUI. These screen captures are a serious pain to look at.

It looks as if you have a series of failed SMART tests, both short and extended. When that happens, it is normally time to replace the drive.

 

[Chris Moore]

PS. If you want to show us a listing in text, you would use the code tags, like this [CODE] with your text inside [/CODE] to force the forum site to display formatted text as it is intended. As an example:

Code:

NAME                                            STATE     READ WRITE CKSUM
        tank                                            ONLINE      31     0     0
          mirror-0                                      ONLINE       0     0     0
            gptid/a60d10a0-33c0-11e8-bc03-000c29765447  ONLINE       0     0     0
            gptid/c75756e7-a4c4-11e6-97d6-000c29765447  ONLINE       0     0     0
          mirror-1                                      ONLINE       0     0     0
            gptid/d664dad6-a4c4-11e6-97d6-000c29765447  ONLINE       0     0    33
            gptid/d715ad71-a4c4-11e6-97d6-000c29765447  ONLINE       0     0     0
          mirror-2                                      ONLINE      31     0     8
            gptid/dc3311ff-18b7-11e9-93b9-000c29765447  ONLINE       0     0    67  (resilvering)
            gptid/eb190cbd-a4c4-11e6-97d6-000c29765447  ONLINE      31     0    30  (resilvering)
          mirror-3                                      ONLINE       0     0     0
            gptid/ff3f0754-a4c4-11e6-97d6-000c29765447  ONLINE       0     0     0
            gptid/fff412af-a4c4-11e6-97d6-000c29765447  ONLINE       0     1     8  (resilvering)
          mirror-4                                      ONLINE       0     0     0
            gptid/1319baba-a4c5-11e6-97d6-000c29765447  ONLINE       0     0     0
            gptid/3cf45e81-1b0c-11e9-93b9-000c29765447  ONLINE       0     0     0  (resilvering)
        logs
          mirror-5                                      ONLINE       0     0     0
            gptid/0ad3c651-a4dc-11e6-849d-000c29765447  ONLINE       0     0     0
            gptid/0b59661a-a4dc-11e6-849d-000c29765447  ONLINE       0     0     0

 

[VividClarity]

Please look at this resource:
https://www.ixsystems.com/community/resources/uncle-festers-freenas-beginners-guide.120/

It has guides on how to configure many things in FreeNAS, one of those things is SSH, so you can access a better terminal window than the one offered by the WebGUI. These screen captures are a serious pain to look at.

It looks as if you have a series of failed SMART tests, both short and extended. When that happens, it is normally time to replace the drive.

Ok thank you, I will check it out I've passed all of the tests I have taken I'm starting to think it's the motherboard. I Disconnected all of the Sata cables and switch them to different drives and I started getting the error on ada0 instead of ada2 like the first time. I then replaced the sata cable to see if it was a sata issue, but the satas aren't the issue so I'm thinking it's the motherboard sata connection being broken.

 

[Chris Moore]

I Disconnected all of the Sata cables and switch them to different drives and I started getting the error on ada0 instead of ada2 like the first time.

The number assigned to a particular drive does not relate at all to the port it is connected to and the number can change from one power cycle to the next even if no cable change happens. Look at the serial numbers to ensure it is not the same drive that is generating the error.
The results of the smart test that you posted:



Those are from the drive. If the drive is failing an internal test, it is usually the drive. I can't tell you how many hundreds of drives I have replaced, but I have seen this a lot at work, and at home for that matter.

 

[VividClarity]

The number assigned to a particular drive does not relate at all to the port it is connected to and the number can change from one power cycle to the next even if no cable change happens. Look at the serial numbers to ensure it is not the same drive that is generating the error.
The results of the smart test that you posted:

View attachment 32212

Those are from the drive. If the drive is failing an internal test, it is usually the drive. I can't tell you how many hundreds of drives I have replaced, but I have seen this a lot at work, and at home for that matter.

Ok thank you, I'm sure your right. I will double check on my end to see if it's the same serial number and I will hookup another drive to the sata port that I suspect is faulty on the motherboard. This is a bummer I have WD Red NAS Drives and haven't had them that long so this makes me not really trust the Quality of these drives especially because they aren't cheap.

 

[VividClarity]

Ok thank you, I'm sure your right. I will double check on my end to see if it's the same serial number and I will hookup another drive to the sata port that I suspect is faulty on the motherboard. This is a bummer I have WD Red NAS Drives and haven't had them that long so this makes me not really trust the Quality of these drives especially because they aren't cheap.\

Maybe I shouldn't have my drives running 24/7 after all. I had a power outage about a month ago so maybe that contributed to this issue, also no errors in a scrub tests.

 

[danb35]

I really have to ask, what's so hard to understand about "Currently unreadable (pending) sectors"? What part of that says anything other than "bad sectors", and therefore "failing drive"? This is a serious question, not rhetorical--there are dozens, if not hundreds, of threads on this exact error (so a forum search would have been a good idea before posting), and they're invariably just like this, without any apparent inkling of what the problem might be (and always with the comment that "there aren't any errors on the scrub", as though that means anything). And with as clear as the error message is, I'm really having trouble understanding why so many people appear to have trouble understanding it.

This is a bummer I have WD Red NAS Drives and haven't had them that long so this makes me not really trust the Quality of these drives especially because they aren't cheap.

Any mechanical device will fail. The disk is under warranty, RMA it--or better yet, advance RMA it, so you don't have to have a degraded pool for the time it takes to ship the disk back and forth. And make sure to burn in the replacement before putting it into service.

Maybe I shouldn't have my drives running 24/7 after all. I

Yes, you should. You should also have a UPS so that your system can shut down cleanly on power failure.

 

[VividClarity]

I really have to ask, what's so hard to understand about "Currently unreadable (pending) sectors"? What part of that says anything other than "bad sectors", and therefore "failing drive"? This is a serious question, not rhetorical--there are dozens, if not hundreds, of threads on this exact error (so a forum search would have been a good idea before posting), and they're invariably just like this, without any apparent inkling of what the problem might be (and always with the comment that "there aren't any errors on the scrub", as though that means anything). And with as clear as the error message is, I'm really having trouble understanding why so many people appear to have trouble understanding it.

Any mechanical device will fail. The disk is under warranty, RMA it--or better yet, advance RMA it, so you don't have to have a degraded pool for the time it takes to ship the disk back and forth. And make sure to burn in the replacement before putting it into service.

Yes, you should. You should also have a UPS so that your system can shut down cleanly on power failure.

It's not hard to understand I just haven't ever gone through a HDD this fast before so I wanted to make sure that I did everything I could do before making a decision to just swap it out. I did do my research and some people just had issues with the sata connections so I was hoping that was my issue I've now come to that conclusion that I'm needing to get a new HDD so I went ahead and RMA'd the drive. Thank you @Chris Moore for the help. @danb35 Any recommendations on UPS brands that are reliable, but won't break the bank? When you say burnin test are you talking about the short and long test and/or Block test?

 

[danb35]

It's not hard to understand I just haven't ever gone through a HDD this fast before so I wanted to make sure that I did everything I could do before making a decision to just swap it out.

Fair enough--it's just that typically (as with yours) the phrasing of the question suggests that you don't have any idea of what the error means--which is why I asked.

Any recommendations on UPS brands that are reliable, but won't break the bank?

APC is the 800-lb gorilla and works fine; CyberPower also seems to work well and is often less expensive. Check the nut HCL to confirm what you're looking at is supported.

When you say burnin test are you talking about the short and long test and/or Block test?

https://www.familybrown.org/dokuwiki/doku.php?id=fester112:hvalid_hdd