Multiple Drive Issues

TAC · Sep 7, 2019

I am looking for recommendations on dealing with the following. I'm pretty sure this is an intermittent issue with my Serveraid M1015 (46M0831) controller since I just replaced both 4-way cables from the M1015 and I doubt 3 HDs are failing at the same time. In the past I was getting Read and Write errors and reseating the cables and rebooting cleared them.

This time I had a disk in the first Vdev log a number of errors and on replacing it the replacement drive started reporting errors and went offline. While all this was going on, da4 in the second Vdev faulted.

Wasn't sure if I should just reboot and see what happens. Or shutdown, unplug new drive in the first Vdev that I was replacing, and then power up.
The 182 Write errors on da4 should clear on a reboot either way.

PhiloEpisteme · Sep 7, 2019

I noticed those failing drives in your other thread. If I were you the first place I'd look is to the long SMART self tests. That may give some indication as to whether it is an issue with the drive or an issue with communicating with the controller. I'd also make sure you have up-to-date backups, just in case.

TAC · Sep 8, 2019

My Data1 pool is now being reported as HEALTHY and none of my drives are reporting any read, write, or checksum errors.

To get here I performed the following steps:
1) Replaced the OFFLINE drive with a new disk in my first Vdev
2) Resilvered my Pool
3) Rebooted which cleared the Write errors on da4
4) After rebooting da4 showed 14 checksum errors so I ran 'zpool clear Data1 gptid/206a16af-b56e-11e9-9264-00259046814d'

I've started long SMART test on dirves da4 and da5 and will see what that reports. Drive da4 is an old HGST 4TB unit and da5 is a brand new Toshiba 6TB N300. Due to the nature of the failures on drive da5 (see below) I was told these look more like disk controller or cable problems than actual hard disk failures. Since I've already changed the cables on my M1015 maybe I should order another Serveraid M1015.

Code:

 (da5:mps0:0:9:0): SCSI sense: HARDWARE FAILURE asc:44,0 (Internal target failure)
(da5:mps0:0:9:0): Error 5, Unretryable error
(da5:mps0:0:9:0): READ(10). CDB: 28 00 00 40 00 a0 00 00 e0 00
(da5:mps0:0:9:0): CAM status: SCSI Status Error
(da5:mps0:0:9:0): SCSI status: Check Condition
(da5:mps0:0:9:0): SCSI sense: HARDWARE FAILURE asc:44,0 (Internal target failure)
(da5:mps0:0:9:0): Error 5, Unretryable error
(da5:mps0:0:9:0): READ(10). CDB: 28 00 00 40 02 a0 00 00 e0 00
(da5:mps0:0:9:0): CAM status: SCSI Status Error
(da5:mps0:0:9:0): SCSI status: Check Condition
(da5:mps0:0:9:0): SCSI sense: HARDWARE FAILURE asc:44,0 (Internal target failure)
(da5:mps0:0:9:0): Error 5, Unretryable error
(da5:mps0:0:9:0): READ(16). CDB: 88 00 00 00 00 02 ba a0 f0 a0 00 00 00 e0 00 00
(da5:mps0:0:9:0): CAM status: SCSI Status Error
(da5:mps0:0:9:0): SCSI status: Check Condition
(da5:mps0:0:9:0): SCSI sense: HARDWARE FAILURE asc:44,0 (Internal target failure)
(da5:mps0:0:9:0): Error 5, Unretryable error
(da5:mps0:0:9:0): READ(16). CDB: 88 00 00 00 00 02 ba a0 f2 a0 00 00 00 e0 00 00
(da5:mps0:0:9:0): CAM status: SCSI Status Error
(da5:mps0:0:9:0): SCSI status: Check Condition
(da5:mps0:0:9:0): SCSI sense: HARDWARE FAILURE asc:44,0 (Internal target failure)
(da5:mps0:0:9:0): Error 5, Unretryable error
(da5:mps0:0:9:0): READ(10). CDB: 28 00 00 40 00 a0 00 00 e0 00
(da5:mps0:0:9:0): CAM status: SCSI Status Error
(da5:mps0:0:9:0): SCSI status: Check Condition
(da5:mps0:0:9:0): SCSI sense: HARDWARE FAILURE asc:44,0 (Internal target failure)
(da5:mps0:0:9:0): Error 5, Unretryable error
(da5:mps0:0:9:0): READ(10). CDB: 28 00 00 40 02 a0 00 00 e0 00
(da5:mps0:0:9:0): CAM status: SCSI Status Error
(da5:mps0:0:9:0): SCSI status: Check Condition
(da5:mps0:0:9:0): SCSI sense: HARDWARE FAILURE asc:44,0 (Internal target failure)
(da5:mps0:0:9:0): Error 5, Unretryable error
(da5:mps0:0:9:0): READ(16). CDB: 88 00 00 00 00 02 ba a0 f0 a0 00 00 00 e0 00 00
(da5:mps0:0:9:0): CAM status: SCSI Status Error
(da5:mps0:0:9:0): SCSI status: Check Condition
(da5:mps0:0:9:0): SCSI sense: HARDWARE FAILURE asc:44,0 (Internal target failure)
(da5:mps0:0:9:0): Error 5, Unretryable error
(da5:mps0:0:9:0): READ(16). CDB: 88 00 00 00 00 02 ba a0 f2 a0 00 00 00 e0 00 00
(da5:mps0:0:9:0): CAM status: SCSI Status Error
(da5:mps0:0:9:0): SCSI status: Check Condition
(da5:mps0:0:9:0): SCSI sense: HARDWARE FAILURE asc:44,0 (Internal target failure)
(da5:mps0:0:9:0): Error 5, Unretryable error
(da5:mps0:0:9:0): READ(10). CDB: 28 00 00 40 00 a0 00 00 e0 00
(da5:mps0:0:9:0): CAM status: SCSI Status Error
(da5:mps0:0:9:0): SCSI status: Check Condition
(da5:mps0:0:9:0): SCSI sense: HARDWARE FAILURE asc:44,0 (Internal target failure)
(da5:mps0:0:9:0): Error 5, Unretryable error
(da5:mps0:0:9:0): READ(10). CDB: 28 00 00 40 02 a0 00 00 e0 00
(da5:mps0:0:9:0): CAM status: SCSI Status Error
(da5:mps0:0:9:0): SCSI status: Check Condition
(da5:mps0:0:9:0): SCSI sense: HARDWARE FAILURE asc:44,0 (Internal target failure)
(da5:mps0:0:9:0): Error 5, Unretryable error
(da5:mps0:0:9:0): READ(16). CDB: 88 00 00 00 00 02 ba a0 f0 a0 00 00 00 e0 00 00
(da5:mps0:0:9:0): CAM status: SCSI Status Error
(da5:mps0:0:9:0): SCSI status: Check Condition
(da5:mps0:0:9:0): SCSI sense: HARDWARE FAILURE asc:44,0 (Internal target failure)
(da5:mps0:0:9:0): Error 5, Unretryable error
(da5:mps0:0:9:0): READ(16). CDB: 88 00 00 00 00 02 ba a0 f2 a0 00 00 00 e0 00 00
(da5:mps0:0:9:0): CAM status: SCSI Status Error
(da5:mps0:0:9:0): SCSI status: Check Condition
(da5:mps0:0:9:0): SCSI sense: HARDWARE FAILURE asc:44,0 (Internal target failure)
(da5:mps0:0:9:0): Error 5, Unretryable error

PhiloEpisteme · Sep 8, 2019

TAC said:
I've started long SMART test on dirves da4 and da5 and will see what that reports.

Ideally your system will be configured to run daily short tests and weekly long tests.

TAC said:
Due to the nature of the failures on drive da5 (see below) I was told these look more like disk controller or cable problems than actual hard disk failures. Since I've already changed the cables on my M1015 maybe I should order another Serveraid M1015.

I would agree that this is the likely issue. Results from a long smart self-test may reveal this information.

TAC · Sep 9, 2019

Maybe my problem is with my drives and not my SATA controller.

I pulled the da4 4TB HGST drive out of the FreeNAS box and put it in a Synology NAS, ran a long SMART test and it reported back SMART 5 (Reallocated Sectors Count) of 77 and SMART 197 (Reallocated Event Count) of 87.

The da5 6TB Toshiba N300 still in my FreeNAS box is reporting SMART 5: 65320, SMART 196: 7738.

Code:

root@freenas:~ # smartctl -a /dev/da5
smartctl 6.6 2017-11-05 r4594 [FreeBSD 11.2-STABLE amd64] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model:     TOSHIBA HDWN160
Serial Number:    39S2K09YFAXG
LU WWN Device Id: 5 000039 92b783188
Firmware Version: FS1M
User Capacity:    6,001,175,126,016 bytes [6.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    7200 rpm
Form Factor:      3.5 inches
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   ATA8-ACS (minor revision not indicated)
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Mon Sep  9 10:37:42 2019 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:                (  120) 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:        ( 639) 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   050    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0005   100   100   050    Pre-fail  Offline      -       0
  3 Spin_Up_Time            0x0027   100   100   001    Pre-fail  Always       -       11460
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       21
  5 Reallocated_Sector_Ct   0x0033   100   100   050    Pre-fail  Always       -       65320
  7 Seek_Error_Rate         0x000b   100   100   050    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0005   100   100   050    Pre-fail  Offline      -       0
  9 Power_On_Hours          0x0032   098   098   000    Old_age   Always       -       800
 10 Spin_Retry_Count        0x0033   100   100   030    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       21
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       -       18
193 Load_Cycle_Count        0x0032   100   100   000    Old_age   Always       -       21
194 Temperature_Celsius     0x0022   100   100   000    Old_age   Always       -       32 (Min/Max 20/42)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       7738
197 Current_Pending_Sector  0x0032   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   253   000    Old_age   Always       -       0
220 Disk_Shift              0x0002   100   100   000    Old_age   Always       -       0
222 Loaded_Hours            0x0032   098   098   000    Old_age   Always       -       800
223 Load_Retry_Count        0x0032   100   100   000    Old_age   Always       -       0
224 Load_Friction           0x0022   100   100   000    Old_age   Always       -       0
226 Load-in_Time            0x0026   100   100   000    Old_age   Always       -       550
240 Head_Flying_Hours       0x0001   100   100   001    Pre-fail  Offline      -       0

SMART Error Log Version: 1
ATA Error Count: 3
        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 3 occurred at disk power-on lifetime: 771 hours (32 days + 3 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
  -- -- -- -- -- -- --
  04 31 00 1b 50 ad 02

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  ec 00 00 00 00 00 00 00      09:01:19.792  IDENTIFY DEVICE
  aa aa aa aa aa aa aa ff      09:00:33.626  [RESERVED]
  ea 00 00 00 00 00 00 00      08:59:19.603  FLUSH CACHE EXT
  61 20 00 b0 53 1e 40 00      08:59:19.602  WRITE FPDMA QUEUED
  61 20 00 20 a0 04 40 00      08:59:19.601  WRITE FPDMA QUEUED

Error 2 occurred at disk power-on lifetime: 769 hours (32 days + 1 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
  -- -- -- -- -- -- --
  04 31 00 12 78 8e 09

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  ea 00 00 00 00 00 00 00      12:07:34.944  FLUSH CACHE EXT
  61 10 00 f8 d2 4b 40 00      12:07:34.943  WRITE FPDMA QUEUED
  61 08 48 a8 18 eb 40 00      12:07:20.964  WRITE FPDMA QUEUED
  61 08 40 68 e8 4b 40 00      12:07:20.964  WRITE FPDMA QUEUED
  61 08 08 98 c5 4e 40 00      12:07:20.964  WRITE FPDMA QUEUED

Error 1 occurred at disk power-on lifetime: 5 hours (0 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
  -- -- -- -- -- -- --
  04 31 00 36 ef 7a 0d

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  ec 00 00 00 00 00 00 00      03:08:59.776  IDENTIFY DEVICE
  aa aa aa aa aa aa aa ff      03:08:56.746  [RESERVED]
  ea 00 00 00 00 00 00 00      03:07:25.472  FLUSH CACHE EXT
  61 08 00 98 0f f4 40 00      03:07:25.470  WRITE FPDMA QUEUED
  61 08 00 d8 21 40 40 00      03:07:25.470  WRITE FPDMA QUEUED

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%       785         -
# 2  Extended offline    Interrupted (host reset)      90%       771         -
# 3  Short offline       Completed without error       00%       725         -
# 4  Short offline       Completed without error       00%       491         -
# 5  Short offline       Completed without error       00%       392         -
# 6  Short offline       Completed without error       00%       296         -
# 7  Short offline       Completed without error       00%       224         -
# 8  Short offline       Completed without error       00%       128         -
# 9  Short offline       Completed without error       00%        56         -
#10  Short offline       Completed without error       00%        26         -
#11  Extended offline    Interrupted (host reset)      90%         5         -
#12  Short offline       Completed without error       00%         4         -

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 found the following sites useful in decoding these SMART tests.
https://en.wikipedia.org/wiki/S.M.A.R.T.#Known_ATA_S.M.A.R.T._attributes
https://www.backblaze.com/blog/what-smart-stats-indicate-hard-drive-failures/

PhiloEpisteme · Sep 9, 2019

TAC said:
The da5 6TB Toshiba N300 still in my FreeNAS box is reporting SMART 5: 65320, SMART 196: 7738.

Yes, you're right this typically indicates an issue with your drive, especially with that many reallocated sectors. You could be having unfortunate issues with the drive AND the card. If I were you I'd figure any drive reporting SMART values like that are likely bad. If you're also seeing errors related to issues communicating with the drives you may consider replacing cables or your HBA. Often a non-zero RAW_VALUE in


199 UDMA_CRC_Error_Count

will indicate an issue communicating with the drive.

TAC said:
I pulled the da4 4TB HGST drive out of the FreeNAS box and put it in a Synology NAS, ran a long SMART test and it reported back SMART 5 (Reallocated Sectors Count) of 77 and SMART 197 (Reallocated Event Count) of 87.

Were you unable to run the SMART tests from your FreeNAS machine?

TAC · Sep 9, 2019

PhiloEpisteme said:
Were you unable to run the SMART tests from your FreeNAS machine?

Since this drive was listed as FAILED or OFFLINE and didn't show up in of the reports (and I had a spare 4TB drive) I just swapped it out.

Important Announcement for the TrueNAS Community.

Multiple Drive Issues

TAC

Contributor

PhiloEpisteme

Guru

TAC

Contributor

PhiloEpisteme

Guru

TAC

Contributor

PhiloEpisteme

Guru

TAC

Contributor

Similar threads

Important Announcement for the TrueNAS Community.

Multiple Drive Issues

TAC

Contributor

PhiloEpisteme

Guru

TAC

Contributor

PhiloEpisteme

Guru

TAC

Contributor

PhiloEpisteme

Guru

TAC

Contributor

Important Announcement for the TrueNAS Community.

Related topics on forums.truenas.com for thread: "Multiple Drive Issues"

Similar threads