Fresh Build - Slot Timeouts and Smart Errors?

Status
Not open for further replies.
M

Motorhead

Dabbler
Joined
Dec 18, 2015
Messages
16
I turned on some additional debugging during the smartctl test:
Code:
Jan 29 09:17:10 FreeNAS (noperiph:ahcich0:0:0:-1): debugging flags now 40
Jan 29 09:18:24 FreeNAS (noperiph:ahcich0:0:0:-1): debugging flags now 8
Jan 29 09:18:45 FreeNAS (pass0:ahcich0:0:0:0): ATA_IDENTIFY. ACB: ec 00 00 00 00 40 00 00 00 00 01 00
Jan 29 09:18:45 FreeNAS (pass0:ahcich0:0:0:0): SMART. ACB: b0 d0 00 4f c2 40 00 00 00 00 01 00
Jan 29 09:18:45 FreeNAS (pass0:ahcich0:0:0:0): SMART. ACB: b0 d4 81 4f c2 40 00 00 00 00 00 00
Jan 29 09:19:05 FreeNAS ahcich0: Timeout on slot 0 port 0
Jan 29 09:19:05 FreeNAS ahcich0: is 00000000 cs 00000001 ss 00000000 rs 00000001 tfd d0 serr 00000000 cmd 0004c017
Jan 29 09:19:05 FreeNAS (aprobe0:ahcich0:0:0:0): ATA_IDENTIFY. ACB: ec 00 00 00 00 40 00 00 00 00 00 00
Jan 29 09:19:05 FreeNAS (aprobe0:ahcich0:0:0:0): SETFEATURES SET TRANSFER MODE. ACB: ef 03 00 00 00 40 00 00 00 00 46 00
Jan 29 09:19:05 FreeNAS (aprobe0:ahcich0:0:0:0): SETFEATURES ENABLE SATA FEATURE. ACB: ef 10 00 00 00 40 00 00 00 00 02 00
Jan 29 09:19:06 FreeNAS (aprobe0:ahcich0:0:0:0): SET_MULTI. ACB: c6 00 00 00 00 40 00 00 00 00 10 00
Jan 29 09:19:06 FreeNAS (ada0:ahcich0:0:0:0): SETFEATURES ENABLE RCACHE. ACB: ef aa 00 00 00 40 00 00 00 00 00 00
Jan 29 09:19:06 FreeNAS (ada0:ahcich0:0:0:0): SETFEATURES ENABLE WCACHE. ACB: ef 02 00 00 00 40 00 00 00 00 00 00



It nearly falls in line with this smartmontools defect posted a while back: https://www.smartmontools.org/ticket/303
I set a stopwatch on my tests and they all timeout at exactly 20 seconds.

I'm wondering, can someone test the following smart test against one of their drives?
smartctl -t short -C /dev/<disktotest>

 
hugovsky

hugovsky

Guru
Joined
Dec 12, 2011
Messages
567
I have re-read the all thread and have a few points for you:

Motorhead said:
smartctl -t short -C /dev/<disktotest>
Click to expand...
- per freebsd manual, you shouldn't use "-C" option when using the drive. I think that is what gives you the timeout errors. I don't have any spare disks to try this. You should run this command line: smartctl -t long /dev/???" Are you sure that your disk is not being used?


Anyway, this shouldn't give you errors in the drive. That's a different matter.


Motorhead said:
  • ATA Error Count: 5
  • 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 5 occurred at disk power-on lifetime: 6240 hours (260 days + 0 hours)
  • When the command that caused the error occurred, the device was in an unknown state.
  • After command completion occurred, registers were:
  • ER ST SC SN CL CH DH
  • -- -- -- -- -- -- --
  • 04 51 00 00 00 00 00 Error: ABRT
  • Commands leading to the command that caused the error were:
  • CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
  • -- -- -- -- -- -- -- -- ---------------- --------------------
  • 00 00 00 00 00 00 00 ff 12:02:35.753 NOP [Abort queued commands]
  • b0 d4 00 81 4f c2 40 00 12:02:15.597 SMART EXECUTE OFF-LINE IMMEDIATE
  • b0 d0 01 00 4f c2 40 00 12:02:15.521 SMART READ DATA
  • ec 00 01 00 00 00 40 00 12:02:15.514 IDENTIFY DEVICE
  • ea 00 00 00 00 00 40 00 12:02:14.274 FLUSH CACHE EXT
  • Error 4 occurred at disk power-on lifetime: 6229 hours (259 days + 13 hours)
  • When the command that caused the error occurred, the device was in an unknown state.
  • After command completion occurred, registers were:
  • ER ST SC SN CL CH DH
  • -- -- -- -- -- -- --
  • 04 51 00 00 00 00 00 Error: ABRT
  • Commands leading to the command that caused the error were:
  • CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
  • -- -- -- -- -- -- -- -- ---------------- --------------------
  • 00 00 00 00 00 00 00 ff 00:52:05.721 NOP [Abort queued commands]
  • b0 d4 00 82 4f c2 40 00 00:51:45.566 SMART EXECUTE OFF-LINE IMMEDIATE
  • b0 d0 01 00 4f c2 40 00 00:51:45.485 SMART READ DATA
  • ec 00 01 00 00 00 40 00 00:51:45.476 IDENTIFY DEVICE
  • ea 00 00 00 00 00 40 00 00:51:44.172 FLUSH CACHE EXT
  • Error 3 occurred at disk power-on lifetime: 6229 hours (259 days + 13 hours)
  • When the command that caused the error occurred, the device was in an unknown state.
  • After command completion occurred, registers were:
  • ER ST SC SN CL CH DH
  • -- -- -- -- -- -- --
  • 04 51 00 00 00 00 00 Error: ABRT
  • Commands leading to the command that caused the error were:
  • CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
  • -- -- -- -- -- -- -- -- ---------------- --------------------
  • 00 00 00 00 00 00 00 ff 00:16:58.564 NOP [Abort queued commands]
  • b0 d4 00 81 4f c2 40 00 00:16:38.408 SMART EXECUTE OFF-LINE IMMEDIATE
  • b0 d0 01 00 4f c2 40 00 00:16:38.326 SMART READ DATA
  • ec 00 01 00 00 00 40 00 00:16:38.318 IDENTIFY DEVICE
  • 60 00 20 90 8d 80 48 00 00:16:38.058 READ FPDMA QUEUED
  • Error 2 occurred at disk power-on lifetime: 6228 hours (259 days + 12 hours)
  • When the command that caused the error occurred, the device was in an unknown state.
  • After command completion occurred, registers were:
  • ER ST SC SN CL CH DH
  • -- -- -- -- -- -- --
  • 04 51 00 00 00 00 00 Error: ABRT
  • Commands leading to the command that caused the error were:
  • CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
  • -- -- -- -- -- -- -- -- ---------------- --------------------
  • 00 00 00 00 00 00 00 ff 03:31:19.669 NOP [Abort queued commands]
  • b0 d4 00 81 4f c2 40 00 03:30:59.515 SMART EXECUTE OFF-LINE IMMEDIATE
  • b0 d0 01 00 4f c2 40 00 03:30:59.445 SMART READ DATA
  • ec 00 01 00 00 00 40 00 03:30:59.437 IDENTIFY DEVICE
  • ea 00 00 00 00 00 40 00 03:30:56.877 FLUSH CACHE EXT
  • Error 1 occurred at disk power-on lifetime: 6228 hours (259 days + 12 hours)
  • When the command that caused the error occurred, the device was in an unknown state.
  • After command completion occurred, registers were:
  • ER ST SC SN CL CH DH
  • -- -- -- -- -- -- --
  • 04 51 00 00 00 00 00 Error: ABRT
  • Commands leading to the command that caused the error were:
  • CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
  • -- -- -- -- -- -- -- -- ---------------- --------------------
  • 00 00 00 00 00 00 00 ff 03:12:36.389 NOP [Abort queued commands]
  • b0 d4 00 81 4f c2 40 00 03:12:16.234 SMART EXECUTE OFF-LINE IMMEDIATE
  • b0 d0 01 00 4f c2 40 00 03:12:16.158 SMART READ DATA
  • ec 00 01 00 00 00 40 00 03:12:16.150 IDENTIFY DEVICE
  • ea 00 00 00 00 00 40 00 03:12:11.789 FLUSH CACHE EXT
Click to expand...

This are errors with the drive. Can this be because of you using the "-C" option? can't tell. Maybe someone else can.
 
C

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,526
Two questions:

1. When you used the old hard drive and the issue didn't occur, was that hard drive a Seagate?
2. Why are you running captive tests? Do you understand why nowhere, at any time on this forum's history, has captive testing ever been recommended?
 
M

Motorhead

Dabbler
Joined
Dec 18, 2015
Messages
16
cyberjock said:
Two questions:

1. When you used the old hard drive and the issue didn't occur, was that hard drive a Seagate?
Click to expand...

It was a WD GreenPower Caviar 1TB. Honestly though, I would want to run a test on that drive again before confirming my previous findings.


cyberjock said:
2. Why are you running captive tests? Do you understand why nowhere, at any time on this forum's history, has captive testing ever been recommended?
Click to expand...

Yeah man. I realize that now. I was looking through the smartmon manual for ways to test the drive. When the the first captive test failed, I got sucked into trying to figure out why instead of figuring the forums will have procedures for the correct tests to run. For a while there I was pulling my hair out. Then landed on "[How To] Hard Drive Burn-In Testing" a few days ago. The badblocks -ws testing completed this morning without error and I started the final smart long test. We will see how the results turn out. I'm optimistic.

Going of what hugovsky said, there must be something funky going on when the captive test is used specifically on FreeNAS...
 
M

Motorhead

Dabbler
Joined
Dec 18, 2015
Messages
16
I'm concluding this thread. Let it be known, don't use smartctl tests with the -C (captive) option. It will produce kernel timeouts with the ahci drivers. That was my experience at least. Here are the final test results after the following the guide linked in the previous post. Everything checks out OK. The 4 errors listed below are a result from running those captive tests.

Whether or not my old drive was in fact, bad. Well, I don't know anymore.


Code:
smartctl 6.3 2014-07-26 r3976 [FreeBSD 9.3-RELEASE-p31 amd64] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Seagate NAS HDD
Device Model:     ST4000VN000-1H4168
Serial Number:    Z305P6BE
LU WWN Device Id: 5 000c50 087bd7bd7
Firmware Version: SC46
User Capacity:    4,000,787,030,016 bytes [4.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5900 rpm
Form Factor:      3.5 inches
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-2, ACS-3 T13/2161-D revision 3b
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Tue Feb  2 19:41:06 2016 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:  (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:         (  107) 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:      (   1) minutes.
Extended self-test routine
recommended polling time:      ( 509) minutes.
Conveyance self-test routine
recommended polling time:      (   2) minutes.
SCT capabilities:            (0x10bd)    SCT Status supported.
                    SCT Error Recovery Control supported.
                    SCT Feature Control supported.
                    SCT Data Table supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   120   100   006    Pre-fail  Always       -       237029208
  3 Spin_Up_Time            0x0003   094   094   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       7
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   100   253   030    Pre-fail  Always       -       33308
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       84
10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       7
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
188 Command_Timeout         0x0032   100   100   000    Old_age   Always       -       17180131332
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   071   068   045    Old_age   Always       -       29 (Min/Max 22/30)
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       0
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       5
193 Load_Cycle_Count        0x0032   100   100   000    Old_age   Always       -       7
194 Temperature_Celsius     0x0022   029   040   000    Old_age   Always       -       29 (0 22 0 0 0)
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0

SMART Error Log Version: 1
ATA Error Count: 4
    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 4 occurred at disk power-on lifetime: 1 hours (0 days + 1 hours)
  When the command that caused the error occurred, the device was in an unknown state.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  04 51 00 00 00 00 00  Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  00 00 00 00 00 00 00 ff      01:52:41.239  NOP [Abort queued commands]
  b0 d4 00 81 4f c2 40 00      01:52:21.083  SMART EXECUTE OFF-LINE IMMEDIATE
  b0 d0 01 00 4f c2 40 00      01:52:21.009  SMART READ DATA
  ec 00 01 00 00 00 40 00      01:52:21.002  IDENTIFY DEVICE
  60 00 00 ff ff ff 4f 00      01:51:26.879  READ FPDMA QUEUED

Error 3 occurred at disk power-on lifetime: 1 hours (0 days + 1 hours)
  When the command that caused the error occurred, the device was in an unknown state.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  04 51 00 00 00 00 00  Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  00 00 00 00 00 00 00 ff      01:38:13.372  NOP [Abort queued commands]
  b0 d4 00 81 4f c2 40 00      01:37:53.217  SMART EXECUTE OFF-LINE IMMEDIATE
  b0 d0 01 00 4f c2 40 00      01:37:53.151  SMART READ DATA
  ec 00 01 00 00 00 40 00      01:37:53.143  IDENTIFY DEVICE
  e3 00 00 00 00 00 40 00      01:37:46.942  IDLE

Error 2 occurred at disk power-on lifetime: 0 hours (0 days + 0 hours)
  When the command that caused the error occurred, the device was in an unknown state.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  04 51 00 00 00 00 00  Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  00 00 00 00 00 00 00 ff      00:18:57.175  NOP [Abort queued commands]
  b0 d4 00 81 4f c2 40 00      00:18:37.022  SMART EXECUTE OFF-LINE IMMEDIATE
  b0 d0 01 00 4f c2 40 00      00:18:36.944  SMART READ DATA
  ec 00 01 00 00 00 40 00      00:18:36.936  IDENTIFY DEVICE
  b0 d5 01 09 4f c2 40 00      00:09:56.247  SMART READ LOG

Error 1 occurred at disk power-on lifetime: 0 hours (0 days + 0 hours)
  When the command that caused the error occurred, the device was in an unknown state.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  04 51 00 00 00 00 00  Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  00 00 00 00 00 00 00 ff      00:08:32.283  NOP [Abort queued commands]
  b0 d4 00 81 4f c2 40 00      00:08:12.127  SMART EXECUTE OFF-LINE IMMEDIATE
  b0 d0 01 00 4f c2 40 00      00:08:12.051  SMART READ DATA
  ec 00 01 00 00 00 40 00      00:08:12.043  IDENTIFY DEVICE
  b0 d5 01 09 4f c2 40 00      00:07:02.014  SMART READ LOG

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%        81         -
# 2  Conveyance offline  Completed without error       00%        11         -
# 3  Extended offline    Completed without error       00%        11         -
# 4  Extended offline    Interrupted (host reset)      80%         3         -
# 5  Short offline       Completed without error       00%         2         -
# 6  Short captive       Interrupted (host reset)      70%         1         -
# 7  Short captive       Interrupted (host reset)      70%         1         -
# 8  Short captive       Interrupted (host reset)      70%         0         -
# 9  Short captive       Interrupted (host reset)      70%         0         -

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.
 
Status
Not open for further replies.

Important Announcement for the TrueNAS Community.

The TrueNAS Community has now been moved. This forum will now become READ-ONLY for historical purposes. Please feel free to join us on the new TrueNAS Community Forums.

Related topics on forums.truenas.com for thread: "Fresh Build - Slot Timeouts and Smart Errors?"

Similar threads

sesipod
  • Locked
Is it time to replace my 2 smart error drives?
Replies
10
Views
2K
Johnnie Black
Johnnie Black
T
  • Locked
SSD Smart error, is it serious?
Replies
3
Views
3K
Stellardata
S
B
Areca 1882 for ZFS
Replies
6
Views
1K
dlavigne
D
V
  • Locked
Hard drive smart error
Replies
18
Views
3K
virusbcn
V
C
  • Locked
Is this hard drive dying? SmartCtl Extended test also not progressing
2
Replies
26
Views
6K
joeschmuck
joeschmuck
Top