First time building a server. First time running TNS.
I'm troubleshooting my initial build before I start using my primary pool. A month ago or so, shortly after the initial assembly, I started getting error alerts for a single, new disk. The error count accumulated over time such that the alert list was:
I offlined the "failing" drive, as the error count increased, thinking that I didn't need it to be active anyway because I wasn't doing anything w/ the drive yet. I don't know if this was a mistake or not.
After lots of searching and Googling, I followed the best advice I could find, that these error combinations are likely a bad cable. I replaced the HBA SATA cable that connected the erroneous drive, restarted TNS, onlined the "failing" drive, and queued up a LONG SMART test on all drives.
www.truenas.com
All the drives SMART results produced no errors, except the one w/ the failing record. Here are the results:
I have never run this test via CLI before, so I'm not sure how to interpret the results, but based on this:
www.truenas.com
I'm guessing this supports the "bad cable" theory. Is that right?
The log reads like the error count is no longer climbing now that the cable has been replaced. I'm not getting an alert anymore, but I am seeing this alert:
plus "pool status: online" on the dashboard (with a warning symbol, oddly) and when I go to the "storage" page, I see the pool status as "ONLINE (unhealthy)" (red "X"), yet all drives have "status: online". Is there something else I need to do to show "green across the board"? Maybe I didn't set some parameter within the TNS GUI?
I'm troubleshooting my initial build before I start using my primary pool. A month ago or so, shortly after the initial assembly, I started getting error alerts for a single, new disk. The error count accumulated over time such that the alert list was:
Code:
Device: /dev/sdc [SAT], ATA error count increased from 55 to 99.
Device: /dev/sdc [SAT], not capable of SMART self-check.
Device: /dev/sdc [SAT], failed to read SMART Attribute Data.
Device: /dev/sdc [SAT], Read SMART Self-Test Log Failed.
Device: /dev/sdc [SAT], Read SMART Error Log Failed.
Pool tank state is ONLINE: One or more devices has experienced an unrecoverable error. An attempt was made to correct the error. Applications are unaffected.Code:
Pool tank state is DEGRADED: One or more devices could not be used because the label is missing or invalid. Sufficient replicas exist for the pool to continue functioning in a degraded state.
The following devices are not healthy:
Disk 8749933745724940911 is UNAVAILI offlined the "failing" drive, as the error count increased, thinking that I didn't need it to be active anyway because I wasn't doing anything w/ the drive yet. I don't know if this was a mistake or not.
After lots of searching and Googling, I followed the best advice I could find, that these error combinations are likely a bad cable. I replaced the HBA SATA cable that connected the erroneous drive, restarted TNS, onlined the "failing" drive, and queued up a LONG SMART test on all drives.
How-to: First Configuration for Small FreeNAS Deployments
EDIT: This post was written in 2015. A lot of things have changed in FreeNAS since then. Exercise some caution and judiciousness when trying to apply the below today; some still is good advice, of course, but some less so. Note: Many (probably most) of the things I'm putting together here are...
www.truenas.com
All the drives SMART results produced no errors, except the one w/ the failing record. Here are the results:
Code:
root@truenas[~]# smartctl -a /dev/sdc
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.10.109+truenas] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Western Digital Gold
Device Model: WDC WD181KRYZ-01AGBB0
LU WWN Device Id: 5 000cca 284da792a
Firmware Version: 01.01H01
User Capacity: 18,000,207,937,536 bytes [18.0 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 7200 rpm
Form Factor: 3.5 inches
Device is: In smartctl database [for details use: -P show]
ATA Version is: ACS-4 published, ANSI INCITS 529-2018
SATA Version is: SATA 3.3, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Sun Jun 26 10:26:52 2022 EDT
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: (0x82) Offline data collection activity
was completed without error.
Auto Offline Data Collection: Enabled.
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: ( 101) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No 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: (1858) minutes.
SCT capabilities: (0x003d) 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 0x000b 100 100 001 Pre-fail Always - 0
2 Throughput_Performance 0x0005 136 136 054 Pre-fail Offline - 96
3 Spin_Up_Time 0x0007 084 084 001 Pre-fail Always - 330 (Average 329)
4 Start_Stop_Count 0x0012 100 100 000 Old_age Always - 21
5 Reallocated_Sector_Ct 0x0033 100 100 001 Pre-fail Always - 0
7 Seek_Error_Rate 0x000b 100 100 001 Pre-fail Always - 0
8 Seek_Time_Performance 0x0005 140 140 020 Pre-fail Offline - 15
9 Power_On_Hours 0x0012 100 100 000 Old_age Always - 236
10 Spin_Retry_Count 0x0013 100 100 001 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 21
22 Helium_Level 0x0023 100 100 025 Pre-fail Always - 100
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 32
193 Load_Cycle_Count 0x0012 100 100 000 Old_age Always - 32
194 Temperature_Celsius 0x0002 059 059 000 Old_age Always - 35 (Min/Max 22/38)
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0
197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x000a 100 100 000 Old_age Always - 99
SMART Error Log Version: 1
ATA Error Count: 99 (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 99 occurred at disk power-on lifetime: 167 hours (6 days + 23 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
-- -- -- -- -- -- --
84 43 00 00 00 00 00 Error: ICRC, ABRT at LBA = 0x00000000 = 0
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
61 10 00 90 02 40 40 00 00:25:09.967 WRITE FPDMA QUEUED
ec 00 00 00 00 00 00 00 00:25:09.951 IDENTIFY DEVICE
2f 00 01 30 03 00 00 00 00:25:09.950 READ LOG EXT
ef 10 02 00 00 00 00 00 00:25:09.948 SET FEATURES [Enable SATA feature]
ef 02 00 00 00 00 00 00 00:25:09.946 SET FEATURES [Enable write cache]
Error 98 occurred at disk power-on lifetime: 167 hours (6 days + 23 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
-- -- -- -- -- -- --
84 43 00 00 00 00 00 Error: ICRC, ABRT at LBA = 0x00000000 = 0
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
61 10 00 90 02 40 40 00 00:25:09.217 WRITE FPDMA QUEUED
ec 00 00 00 00 00 00 00 00:25:09.200 IDENTIFY DEVICE
2f 00 01 30 03 00 00 00 00:25:09.200 READ LOG EXT
ef 10 02 00 00 00 00 00 00:25:09.198 SET FEATURES [Enable SATA feature]
ef 02 00 00 00 00 00 00 00:25:09.196 SET FEATURES [Enable write cache]
Error 97 occurred at disk power-on lifetime: 167 hours (6 days + 23 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
-- -- -- -- -- -- --
84 43 00 00 00 00 00 Error: ICRC, ABRT at LBA = 0x00000000 = 0
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
61 10 00 90 02 40 40 00 00:25:08.488 WRITE FPDMA QUEUED
ec 00 00 00 00 00 00 00 00:25:08.488 IDENTIFY DEVICE
60 10 00 90 02 40 40 00 00:25:08.473 READ FPDMA QUEUED
ec 00 00 00 00 00 00 00 00:25:08.450 IDENTIFY DEVICE
2f 00 01 30 03 00 00 00 00:25:08.450 READ LOG EXT
Error 96 occurred at disk power-on lifetime: 167 hours (6 days + 23 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
-- -- -- -- -- -- --
84 43 00 00 00 00 00 Error: ICRC, ABRT at LBA = 0x00000000 = 0
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
61 10 00 90 fc 7f 40 00 00:25:07.721 WRITE FPDMA QUEUED
60 10 10 90 02 40 40 00 00:25:07.720 READ FPDMA QUEUED
61 10 08 90 fa 7f 40 00 00:25:07.720 WRITE FPDMA QUEUED
2f 00 01 30 03 00 00 00 00:25:07.700 READ LOG EXT
ef 10 02 00 00 00 00 00 00:25:07.697 SET FEATURES [Enable SATA feature]
Error 95 occurred at disk power-on lifetime: 167 hours (6 days + 23 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
-- -- -- -- -- -- --
84 43 00 00 00 00 00 Error: ICRC, ABRT at LBA = 0x00000000 = 0
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
61 10 00 90 fc 7f 40 00 00:25:06.951 WRITE FPDMA QUEUED
2f 00 01 30 03 00 00 00 00:25:06.950 READ LOG EXT
ef 10 02 00 00 00 00 00 00:25:06.948 SET FEATURES [Enable SATA feature]
ef 02 00 00 00 00 00 00 00:25:06.946 SET FEATURES [Enable write cache]
ef aa 00 00 00 00 00 00 00:25:06.943 SET FEATURES [Enable read look-ahead]
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Extended offline Completed without error 00% 227 -
# 2 Short offline Completed without error 00% 167 -
# 3 Short offline Completed without error 00% 167 -
# 4 Short offline Completed without error 00% 147 -
# 5 Short offline Completed without error 00% 82 -
# 6 Short offline Completed without error 00% 59 -
# 7 Short offline Completed without error 00% 35 -
# 8 Short offline Completed without error 00% 11 -
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.I have never run this test via CLI before, so I'm not sure how to interpret the results, but based on this:
Help interpreting SMART results?
So my zvol was showing Degraded with bad Checksums on a disk yesterday. I did a scrub, and in the zpool status it showed 62 Read Errors for a drive, and eventually kicked it out of the pool I did a long SMART test of the disk in question and from what I can tell it seems ok. Can I get a second...
www.truenas.com
I'm guessing this supports the "bad cable" theory. Is that right?
The log reads like the error count is no longer climbing now that the cable has been replaced. I'm not getting an alert anymore, but I am seeing this alert:
Code:
Pool tank state is ONLINE: One or more devices has experienced an unrecoverable error. An attempt was made to correct the error. Applications are unaffected.
plus "pool status: online" on the dashboard (with a warning symbol, oddly) and when I go to the "storage" page, I see the pool status as "ONLINE (unhealthy)" (red "X"), yet all drives have "status: online". Is there something else I need to do to show "green across the board"? Maybe I didn't set some parameter within the TNS GUI?
