DEGRADED To many errors

[frouty]

hi,
What are the best practice for that kind of problem?
Or if you know some docs somewhere I'm ready to read.

It is said 'Determine if the device needs to be replaced'
How do I do that ? whith smartctl?
'and clear the errors' how do I do that?

Do I have to replace the degraded hard drive one by one, all at once?

Thanks
========
# zpool status
pool: boot-pool
state: ONLINE
config:

NAME STATE READ WRITE CKSUM
boot-pool ONLINE 0 0 0
da0p2 ONLINE 0 0 0

errors: No known data errors

pool: mnemosys
state: DEGRADED
status: One or more devices has experienced an unrecoverable error. An
attempt was made to correct the error. Applications are unaffected.
action: Determine if the device needs to be replaced, and clear the errors
using 'zpool clear' or replace the device with 'zpool replace'.
see: https://zfsonlinux.org/msg/ZFS-8000-9P
scan: resilvered 32.0G in 00:06:22 with 0 errors on Fri Dec 11 20:36:03 2020
config:

NAME STATE READ WRITE CKSUM
mnemosys DEGRADED 0 0 0
raidz2-0 DEGRADED 0 0 0
gptid/b4d452cd-fc7f-11e4-841d-0cc47a0d7e71.eli DEGRADED 0 0 0 too many errors
gptid/b5f13efb-fc7f-11e4-841d-0cc47a0d7e71.eli DEGRADED 0 0 0 too many errors
gptid/b6c546f2-fc7f-11e4-841d-0cc47a0d7e71.eli ONLINE 0 0 0
gptid/b79eee77-fc7f-11e4-841d-0cc47a0d7e71.eli DEGRADED 0 0 0 too many errors
gptid/b8752eba-fc7f-11e4-841d-0cc47a0d7e71.eli DEGRADED 0 0 0 too many errors
gptid/b94ad25f-fc7f-11e4-841d-0cc47a0d7e71.eli DEGRADED 0 0 0 too many errors

errors: No known data errors
==========

 

[Heracles]

Hey @frouty,

Things are not looking good at all here! 5 degraded drives in a single Raid-Z2, that is way above what is required to loose your pool.

So first thing is not to panic.

Second thing is to refresh your backups ASAP (you do have backups don't you ?....)

Once your backups have been refreshed and are up-to-date, you can start working on your situation. For that many drives to end up with that many errors all at once, the root cause is often related to the cables / connectors / HBA / motherboard. It is rare that so many drives fail individually together.

So once your data are safe in a complete backup, I would power off the server and re-do all the connections. After a reboot, check back the pool and see how well it is doing. If indeed your drives are back, next step would be to do a scrub on your pool to ensure all the integrity controls are put back right.

 

[frouty]

So OK I'm on my way.
I setup a new backup server machine and install backuppc and it is running now. But it took a long time.
So I'll be back later on.
thanks

 

[joeschmuck]

For that many drives to end up with that many errors all at once, the root cause is often related to the cables / connectors / HBA / motherboard. It is rare that so many drives fail individually together.

That is an assumption that the errors just started. Maybe the OP just noticed them but they have been around for a while. But i agree with the troubleshooting steps...
1) Cables/Connectors
2) Run smartctl -a /dev/ada0 or it could be da0 depending on your setup, and post the output of each drive in your system. (Look in my signature for Hard Drive Troubleshooting Guide for help)
3) If your drives have no critical errors (ID5, ID 197, ID 198, ID 200 for example) then move to step 4.
4) If you have not run a SMART Short Short or Long test in the past 96 hours, recommend you run a SMART Short Test. Check the results and if there are no failures continue. If there are errors then you may have a drive failure, post the data in question for someone to look at.
5) If you find out there are no drive issues, look at the HBA.

Also, what version of FreeNAS are you running and what is your machine makeup and configuration? Why don't people post this anymore? It could make a difference in what we tell you to do and we want to get you up on your feet as soon as possible.

 

[frouty]

I done the backup.
I didn't use smartcl at the beginning.
I use the utilities from Western Digital which run on freedos. https://support.wdc.com/downloads.aspx?p=2
I made quick test and extended test for all the hard drive. (8h by 4To Drives)
It found one hard drive with too many errors. I replace it with a new hard drive Seagate same size (Storage / Pool / Satus/ Offline, shutdown, replace Storage / Pool / Status / Replace
It found also an other hard drive with errors but said : repaired.

zpool status -v
pool: boot-pool
state: ONLINE
scan: scrub repaired 0B in 01:19:05 with 0 errors on Sun Dec 20 05:12:58 2020
config:

NAME STATE READ WRITE CKSUM
boot-pool ONLINE 0 0 0
da0p2 ONLINE 0 0 0

errors: No known data errors

pool: mnemosys
state: DEGRADED
status: One or more devices is currently being resilvered. The pool will
continue to function, possibly in a degraded state.
action: Wait for the resilver to complete.
scan: resilver in progress since Thu Dec 24 19:51:31 2020
1.41T scanned at 997M/s, 808G issued at 556M/s, 5.30T total
134G resilvered, 14.88% done, 02:21:48 to go
config:

NAME STATE READ WRITE CKSUM
mnemosys DEGRADED 0 0 0
raidz2-0 DEGRADED 0 0 0
gptid/b4d452cd-fc7f-11e4-841d-0cc47a0d7e71.eli DEGRADED 0 0 0 too many errors
gptid/b5f13efb-fc7f-11e4-841d-0cc47a0d7e71.eli DEGRADED 0 0 0 too many errors
gptid/b6c546f2-fc7f-11e4-841d-0cc47a0d7e71.eli ONLINE 4 0 0
gptid/b79eee77-fc7f-11e4-841d-0cc47a0d7e71.eli DEGRADED 0 0 0 too many errors
gptid/723b301a-4664-11eb-8f01-0cc47a0d7e71.eli ONLINE 0 0 0 (resilvering)
gptid/b94ad25f-fc7f-11e4-841d-0cc47a0d7e71.eli DEGRADED 0 0 0 too many errors

errors: No known data errors

I got also many error in dmesg:
(ada3:ahcich3:0:0:0): ATA status: 41 (DRDY ERR), error: 40 (UNC )
(ada3:ahcich3:0:0:0): RES: 41 40 90 02 40 40 00 00 00 00 00
(ada3:ahcich3:0:0:0): Retrying command, 0 more tries remain
(ada3:ahcich3:0:0:0): READ_FPDMA_QUEUED. ACB: 60 10 90 02 40 40 00 00 00 00 00 00
(ada3:ahcich3:0:0:0): CAM status: ATA Status Error
(ada3:ahcich3:0:0:0): ATA status: 41 (DRDY ERR), error: 40 (UNC )
(ada3:ahcich3:0:0:0): RES: 41 40 90 02 40 40 00 00 00 00 00
(ada3:ahcich3:0:0:0): Error 5, Retries exhausted
GEOM_ELI: g_eli_read_done() failed (error=5) gptid/b6c546f2-fc7f-11e4-841d-0cc47a0d7e71.eli[READ(offset=270336, length=8192)]

/var/log/messages:
Dec 24 20:04:40 truenas 1 2020-12-24T20:04:40.182628-08:00 truenas.local smartd 1666 - - Device: /dev/ada3, 1 Currently unreadable (pending) sectors
Dec 24 20:04:40 truenas 1 2020-12-24T20:04:40.439179-08:00 truenas.local smartd 1666 - - Device: /dev/ada3, ATA error count increased from 28 to 38

And ada3 is on the hard drive with errors and repared by WD Data Lifeguard Diagnostic for DOS on freedos.

So let's try smartctl -a /dev/ada3 as asked by joeschmuck
and read some of the docs in the signature.
=== START OF INFORMATION SECTION ===
Model Family: Western Digital Red
Device Model: WDC WD40EFRX-68WT0N0
Serial Number: WD-WCC4E1SKV8D1
LU WWN Device Id: 5 0014ee 260d5c30d
Firmware Version: 82.00A82
User Capacity: 4,000,787,030,016 bytes [4.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 5400 rpm
Device is: In smartctl database [for details use: -P show]
ATA Version is: ACS-2 (minor revision not indicated)
SATA Version is: SATA 3.0, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is: Thu Dec 24 20:32:53 2020 PST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: (56220) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 562) minutes.
Conveyance self-test routine
recommended polling time: ( 5) minutes.
SCT capabilities: (0x703d) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 94
3 Spin_Up_Time 0x0027 176 174 021 Pre-fail Always - 8191
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 151
5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0
7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0
9 Power_On_Hours 0x0032 043 043 000 Old_age Always - 41814
10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0
11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 150
192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 95
193 Load_Cycle_Count 0x0032 199 199 000 Old_age Always - 3771
194 Temperature_Celsius 0x0022 115 103 000 Old_age Always - 37
196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0
197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 1
198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0
200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0

SMART Error Log Version: 1
ATA Error Count: 38 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 38 occurred at disk power-on lifetime: 41813 hours (1742 days + 5 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 10 90 02 40 40 Error: UNC 16 sectors at LBA = 0x00400290 = 4194960

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 10 90 02 40 40 08 00:23:31.006 READ DMA
c8 00 10 90 02 40 40 08 00:23:27.742 READ DMA
c8 00 10 90 02 40 40 08 00:23:24.479 READ DMA
c8 00 10 90 02 40 40 08 00:23:21.215 READ DMA
c8 00 10 90 02 40 40 08 00:23:17.961 READ DMA

Error 37 occurred at disk power-on lifetime: 41813 hours (1742 days + 5 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 10 90 02 40 40 Error: UNC 16 sectors at LBA = 0x00400290 = 4194960

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 10 90 02 40 40 08 00:23:27.742 READ DMA
c8 00 10 90 02 40 40 08 00:23:24.479 READ DMA
c8 00 10 90 02 40 40 08 00:23:21.215 READ DMA
c8 00 10 90 02 40 40 08 00:23:17.961 READ DMA
c8 00 e0 a0 00 40 40 08 00:23:14.698 READ DMA

Error 36 occurred at disk power-on lifetime: 41813 hours (1742 days + 5 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 10 90 02 40 40 Error: UNC 16 sectors at LBA = 0x00400290 = 4194960

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 10 90 02 40 40 08 00:23:24.479 READ DMA
c8 00 10 90 02 40 40 08 00:23:21.215 READ DMA
c8 00 10 90 02 40 40 08 00:23:17.961 READ DMA
c8 00 e0 a0 00 40 40 08 00:23:14.698 READ DMA
c8 00 e0 a0 00 40 40 08 00:23:11.435 READ DMA

Error 35 occurred at disk power-on lifetime: 41813 hours (1742 days + 5 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 10 90 02 40 40 Error: UNC 16 sectors at LBA = 0x00400290 = 4194960

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 10 90 02 40 40 08 00:23:21.215 READ DMA
c8 00 10 90 02 40 40 08 00:23:17.961 READ DMA
c8 00 e0 a0 00 40 40 08 00:23:14.698 READ DMA
c8 00 e0 a0 00 40 40 08 00:23:11.435 READ DMA
c8 00 e0 a0 00 40 40 08 00:23:08.171 READ DMA

Error 34 occurred at disk power-on lifetime: 41813 hours (1742 days + 5 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 10 90 02 40 40 Error: UNC 16 sectors at LBA = 0x00400290 = 4194960

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 10 90 02 40 40 08 00:23:17.961 READ DMA
c8 00 e0 a0 00 40 40 08 00:23:14.698 READ DMA
c8 00 e0 a0 00 40 40 08 00:23:11.435 READ DMA
c8 00 e0 a0 00 40 40 08 00:23:08.171 READ DMA
c8 00 e0 a0 00 40 40 08 00:23:04.875 READ DMA

SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Conveyance offline Completed without error 00% 41751 -
# 2 Conveyance offline Completed without error 00% 41751 -
# 3 Short offline Completed without error 00% 41542 -

SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

Next step for me is to wait the end of resilvering and change the hard drive on ada3.

Well... Is this still a hard drive problem or a motherboard problem?

------------------
Version:
TrueNAS-12.0-BETA2.1
Base Board Information
Manufacturer: Supermicro
Product Name: X9SCL/X9SCM
5 HDD WD and 1 New Seagate 4To
Geli encrypted disk.

 

[sretalla]

Well... Is this still a hard drive problem or a motherboard problem?

OK, so for sure ada3 is not a good disk to continue working with... you need to replace it:

Code:

1 Raw_Read_Error_Rate     0x002f   200   200   051    Pre-fail  Always       -       94
197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       1

40 51 10 90 02 40 40  Error: UNC 16 sectors at LBA = 0x00400290 = 4194960

Is there another problem with your disk controller (the motherboard one, I assume)? maybe.

It's possible that the controller just isn't handling the errors being thrown by that disk very well and it's having trouble with communicating with the other disks as a result.

Try removing that disk (check the serial number: WD-WCC4E1SKV8D1 before removing anything from the case) and boot with the other disks in place.

You may find that your pool is only now degraded due to one missing disk, in which case replace the removed one and it's happy days from there.

 

[joeschmuck]

Yes, drive S/N: WCC4E1SKV8D1 is failing, ID 197 is the first solid indication

197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 1

Before assuming you have other problems such as controller/motherboard, replace the hard drive. I doubt you will have further problems with the drive connected to this port/cable. If ID 199 were any value other than zero then I would suspect a communications issue as well. Do not take on more than one problem at a time unless you are experienced at troubleshooting these types of problems, it can be easy to think they are the same problem when they are not. Fix one thing then move on to the next one. I've said that twice now, for good reason.

 

[frouty]

zpool status
pool: boot-pool
[...]
errors: No known data errors

pool: mnemosys
state: DEGRADED
status: One or more devices has experienced an unrecoverable error. An
attempt was made to correct the error. Applications are unaffected.
action: Determine if the device needs to be replaced, and clear the errors
using 'zpool clear' or replace the device with 'zpool replace'.
see: https://zfsonlinux.org/msg/ZFS-8000-9P
scan: resilvered 906G in 03:30:31 with 0 errors on Fri Dec 25 18:22:02 2020
config:

NAME STATE READ WRITE CKSUM
mnemosys DEGRADED 0 0 0
raidz2-0 DEGRADED 0 0 0
gptid/b4d452cd-fc7f-11e4-841d-0cc47a0d7e71.eli DEGRADED 0 0 0 too many errors
gptid/b5f13efb-fc7f-11e4-841d-0cc47a0d7e71.eli DEGRADED 0 0 0 too many errors
gptid/b6c546f2-fc7f-11e4-841d-0cc47a0d7e71.eli ONLINE 1 0 0
gptid/b79eee77-fc7f-11e4-841d-0cc47a0d7e71.eli DEGRADED 0 0 0 too many errors
gptid/723b301a-4664-11eb-8f01-0cc47a0d7e71.eli ONLINE 0 0 0
gptid/b94ad25f-fc7f-11e4-841d-0cc47a0d7e71.eli DEGRADED 0 0 0 too many errors

errors: No known data errors

So I'm going to set offline the gptid/b6c546f2-fc7f-11e4-841d-0cc47a0d7e71.eli / shutdown / physicaly replace hard drive by brand new hard drive / boot on / and I will get a pool with only one hdd ONLINE, and 4 DEGRADED.
Storage /pool / status/ ada3 replace / resilvering.
#zpool clear as asked in zpool status -x
#zpool status -x
all pools are healthy

OK.

it's really hard to interprete the data returned by smartctl. But I read the doc from joeschmuck to improve my skill.
I found this interesting too : https://kb.acronis.com/search?ap=All&s=attribut smart&f[0]=os:900
Thanks