ATA Status Error

Kortex

Dabbler
Joined
Mar 2, 2015
Messages
48
Hi All,

My machine has been off for a while because I was out of town. I turned it on and CAM Status: ATA Status Errors started showing up.

Code:
Jul  4 21:58:18 freenas (ada4:ahcich13:0:0:0): READ_FPDMA_QUEUED. ACB: 60 00 80 03 40 40 00 00 00 01 00 00
Jul  4 21:58:18 freenas (ada4:ahcich13:0:0:0): CAM status: ATA Status Error
Jul  4 21:58:18 freenas (ada4:ahcich13:0:0:0): ATA status: 41 (DRDY ERR), error: 40 (UNC )
Jul  4 21:58:18 freenas (ada4:ahcich13:0:0:0): RES: 41 40 b0 03 40 40 00 00 00 00 00
Jul  4 21:58:18 freenas (ada4:ahcich13:0:0:0): Retrying command


This repeats a while. I tried a smart test on all drives. ADA4 had issues:
Code:
smartctl 6.6 2017-11-05 r4594 [FreeBSD 11.1-STABLE amd64] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Red
Device Model:     WDC WD30EFRX-68EUZN0
Firmware Version: 82.00A82
User Capacity:    3,000,592,982,016 bytes [3.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:    Sat Jul  4 22:30:34 2020 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:  (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:                (39060) 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:        ( 392) 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       -       40
  3 Spin_Up_Time            0x0027   181   181   021    Pre-fail  Always       -       5908
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       43
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   200   200   000    Old_age   Always       -       1
  9 Power_On_Hours          0x0032   069   069   000    Old_age   Always       -       22869
 10 Spin_Retry_Count        0x0032   100   253   000    Old_age   Always       -       0
 11 Calibration_Retry_Count 0x0032   100   253   000    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       43
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       16
193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       259
194 Temperature_Celsius     0x0022   119   111   000    Old_age   Always       -       31
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       0
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   200   200   000    Old_age   Offline      -       0
                                                                                                                                    
SMART Error Log Version: 1
ATA Error Count: 6 (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 6 occurred at disk power-on lifetime: 22869 hours (952 days + 21 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 61 00 00 00 00 40
                                                                                                                                    
  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  e0 00 00 00 00 00 40 08   1d+17:33:23.352  STANDBY IMMEDIATE
  b0 d5 01 01 4f c2 40 08   1d+17:29:55.339  SMART READ LOG
  b0 d5 01 06 4f c2 40 08   1d+17:29:55.338  SMART READ LOG
                                                                                                                                    
Error 5 occurred at disk power-on lifetime: 22850 hours (952 days + 2 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 61 10 90 02 40 40  Device Fault; Error: ABRT 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      23:04:33.130  READ DMA
  c8 00 10 90 02 40 40 08      23:04:33.130  READ DMA
  c8 00 10 90 02 40 40 08      23:04:33.130  READ DMA
  c8 00 10 90 02 40 40 08      23:04:33.129  READ DMA
  c8 00 10 90 02 40 40 08      23:04:33.129  READ DMA
                                                                                                                                    
Error 4 occurred at disk power-on lifetime: 22850 hours (952 days + 2 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 61 10 90 02 40 40  Device Fault; Error: ABRT 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      23:04:33.130  READ DMA
  c8 00 10 90 02 40 40 08      23:04:33.130  READ DMA
  c8 00 10 90 02 40 40 08      23:04:33.129  READ DMA
  c8 00 10 90 02 40 40 08      23:04:33.129  READ DMA
                                                                                                                                    
Error 3 occurred at disk power-on lifetime: 22850 hours (952 days + 2 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 61 10 90 02 40 40  Device Fault; Error: ABRT 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      23:04:33.130  READ DMA
  c8 00 10 90 02 40 40 08      23:04:33.129  READ DMA
  c8 00 10 90 02 40 40 08      23:04:33.129  READ DMA
                                                                                                                                    
Error 2 occurred at disk power-on lifetime: 22850 hours (952 days + 2 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 61 10 90 02 40 40  Device Fault; Error: ABRT 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      23:04:33.129  READ DMA
  c8 00 10 90 02 40 40 08      23:04:33.129  READ DMA
                                                                                                                                    
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%     22823         -
# 2  Short offline       Completed without error       00%     22744         -
# 3  Short offline       Completed without error       00%     22576         -
# 4  Extended offline    Completed without error       00%     22487         -
# 5  Short offline       Completed without error       00%     22408         -
# 6  Short offline       Completed without error       00%     22168         -
# 7  Extended offline    Completed without error       00%     22080         -
# 8  Short offline       Completed without error       00%     22001         -
# 9  Short offline       Completed without error       00%     21833         -
#10  Extended offline    Completed without error       00%     21744         -
#11  Short offline       Completed without error       00%     21666         -
#12  Short offline       Completed without error       00%     21474         -
#13  Extended offline    Completed without error       00%     21385         -
#14  Short offline       Completed without error       00%     21306         -
#15  Short offline       Completed without error       00%     21138         -
#16  Extended offline    Completed without error       00%     21050         -
#17  Short offline       Completed without error       00%     20971         -
#18  Short offline       Completed without error       00%     20731         -
#19  Extended offline    Completed without error       00%     20642         -
#20  Short offline       Completed without error       00%     20563         -
#21  Short offline       Completed without error       00%     20395         -
                                                                                                                                    
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
Error 2 occurred at disk power-on lifetime: 22850 hours (952 days + 2 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 61 10 90 02 40 40  Device Fault; Error: ABRT 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      23:04:33.129  READ DMA
  c8 00 10 90 02 40 40 08      23:04:33.129  READ DMA
                                                                                                                                    
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%     22823         -
# 2  Short offline       Completed without error       00%     22744         -
# 3  Short offline       Completed without error       00%     22576         -
# 4  Extended offline    Completed without error       00%     22487         -
# 5  Short offline       Completed without error       00%     22408         -
# 6  Short offline       Completed without error       00%     22168         -
# 7  Extended offline    Completed without error       00%     22080         -
# 8  Short offline       Completed without error       00%     22001         -
# 9  Short offline       Completed without error       00%     21833         -
#10  Extended offline    Completed without error       00%     21744         -
#11  Short offline       Completed without error       00%     21666         -
#12  Short offline       Completed without error       00%     21474         -
#13  Extended offline    Completed without error       00%     21385         -
#14  Short offline       Completed without error       00%     21306         -
#15  Short offline       Completed without error       00%     21138         -
#16  Extended offline    Completed without error       00%     21050         -
#17  Short offline       Completed without error       00%     20971         -
#18  Short offline       Completed without error       00%     20731         -
#19  Extended offline    Completed without error       00%     20642         -
#20  Short offline       Completed without error       00%     20563         -
#21  Short offline       Completed without error       00%     20395         -
                                                                                                                                    
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.


And then..
Code:
CRITICAL: July 4, 2020, 9:58 p.m. - Device: /dev/ada4, 4 Currently unreadable (pending) sectors
CRITICAL: July 4, 2020, 10:04 p.m. - The volume jvol state is DEGRADED: One or more devices has experienced an unrecoverable error. An attempt was made to correct the error. Applications are unaffected.


Is the drive dead? Should I turn off the whole machine until I can order a replacement? It didn't have issues before as far as I know. Thanks. Very worried
 

sretalla

Powered by Neutrality
Moderator
Joined
Jan 1, 2016
Messages
9,703
Is the drive dead?
No, but it's not healthy and will probably soon die, so it's time to replace it.

Should I turn off the whole machine until I can order a replacement?
Not necessarily, as long as you're not thrashing the remaining drives in the meantime, it should be fine. You may want to physically remove the failing disk as a restart will initiate an attept at resilver, which may put stress on the other disks for no good reason.

I assume you're on a RAIDZ1 setup (hence being very worried now you have no fault tolerance), so be careful, but your pool is still available for use if you need it.
 

subhuman

Contributor
Joined
Nov 21, 2019
Messages
121
The commands leading to the errors were READ_DMA, so it's possibly a bad SATA port, bad cable or loose cable connection.
I don't think this will be the case, because I haven't seen that cause the pending sector count to increment, however you may want to start checking the simple stuff first: connect the drive to a different SATA port and use a different data cable.
All the indicators point to the drive itself, raw_read_errors and not UDMA_CRC_errors, but sometimes it pays off to check the $5 part before replacing the $100 part.
 

Kortex

Dabbler
Joined
Mar 2, 2015
Messages
48
No, but it's not healthy and will probably soon die, so it's time to replace it.


Not necessarily, as long as you're not thrashing the remaining drives in the meantime, it should be fine. You may want to physically remove the failing disk as a restart will initiate an attept at resilver, which may put stress on the other disks for no good reason.

I assume you're on a RAIDZ1 setup (hence being very worried now you have no fault tolerance), so be careful, but your pool is still available for use if you need it.

Thank you for the reply sir. Actually I'm running RAIDZ2 but a nervous nancy :oops:. What sucks is that I currently have four new drives sitting here (4x8TB) and I was planning on migrating the data over soon. I don't know if it's safe now and I might have to buy a new drive and use it for a few days.
 

Kortex

Dabbler
Joined
Mar 2, 2015
Messages
48
The commands leading to the errors were READ_DMA, so it's possibly a bad SATA port, bad cable or loose cable connection.
I don't think this will be the case, because I haven't seen that cause the pending sector count to increment, however you may want to start checking the simple stuff first: connect the drive to a different SATA port and use a different data cable.
All the indicators point to the drive itself, raw_read_errors and not UDMA_CRC_errors, but sometimes it pays off to check the $5 part before replacing the $100 part.

INTERESTING. I blew dust out of the machine and unplugged/replugged all of the cables. I'm going to check the connections
 

Kortex

Dabbler
Joined
Mar 2, 2015
Messages
48
I checked all the cables and made sure everything was dust free. I powered the system back on. The system reports:

Code:
 CRITICAL: July 6, 2020, 11:03 p.m. - The volume jvol state is ONLINE: One or more devices has experienced an unrecoverable error. An attempt was made to correct the error. Applications are unaffected.


Logfile below

Code:
Jul  6 23:02:17 freenas syslog-ng[1731]: syslog-ng starting up; version='3.7.3'
Jul  6 23:02:17 freenas Copyright (c) 1992-2017 The FreeBSD Project.
Jul  6 23:02:17 freenas Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
Jul  6 23:02:17 freenas     The Regents of the University of California. All rights reserved.
Jul  6 23:02:17 freenas FreeBSD is a registered trademark of The FreeBSD Foundation.
Jul  6 23:02:17 freenas FreeBSD 11.1-STABLE #0 r321665+79f05c3dd3d(HEAD): Wed Jan 23 12:02:34 EST 2019
Jul  6 23:02:17 freenas root@nemesis.tn.ixsystems.com:/freenas-releng/freenas/_BE/objs/freenas-releng/freenas/_BE/os/sys/FreeNAS.amd64 amd64
Jul  6 23:02:17 freenas FreeBSD clang version 5.0.0 (tags/RELEASE_500/final 312559) (based on LLVM 5.0.0svn)
Jul  6 23:02:17 freenas CPU: Intel(R) Atom(TM) CPU  C2750  @ 2.40GHz (2400.06-MHz K8-class CPU)
Jul  6 23:02:17 freenas Origin="GenuineIntel"  Id=0x406d8  Family=0x6  Model=0x4d  Stepping=8
Jul  6 23:02:17 freenas Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
Jul  6 23:02:17 freenas Features2=0x43d8e3bf<SSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,TSCDLT,AESNI,RDRAND>
Jul  6 23:02:17 freenas AMD Features=0x28100800<SYSCALL,NX,RDTSCP,LM>
Jul  6 23:02:17 freenas AMD Features2=0x101<LAHF,Prefetch>
Jul  6 23:02:17 freenas Structured Extended Features=0x2282<TSCADJ,SMEP,ERMS,NFPUSG>
Jul  6 23:02:17 freenas VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID
Jul  6 23:02:17 freenas TSC: P-state invariant, performance statistics
Jul  6 23:02:17 freenas real memory  = 17985175552 (17152 MB)
Jul  6 23:02:17 freenas avail memory = 16559050752 (15791 MB)
Jul  6 23:02:17 freenas Event timer "LAPIC" quality 600
Jul  6 23:02:17 freenas ACPI APIC Table: <INTEL  TIANO   >
Jul  6 23:02:17 freenas WARNING: L1 data cache covers less APIC IDs than a core
Jul  6 23:02:17 freenas 0 < 1
Jul  6 23:02:17 freenas FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs
Jul  6 23:02:17 freenas FreeBSD/SMP: 1 package(s) x 8 core(s)
Jul  6 23:02:17 freenas WARNING: VIMAGE (virtualized network stack) is a highly experimental feature.
Jul  6 23:02:17 freenas ioapic0 <Version 2.0> irqs 0-23 on motherboard
Jul  6 23:02:17 freenas SMP: AP CPU #6 Launched!
Jul  6 23:02:17 freenas SMP: AP CPU #7 Launched!
Jul  6 23:02:17 freenas SMP: AP CPU #4 Launched!
Jul  6 23:02:17 freenas SMP: AP CPU #5 Launched!
Jul  6 23:02:17 freenas SMP: AP CPU #2 Launched!
Jul  6 23:02:17 freenas SMP: AP CPU #3 Launched!
Jul  6 23:02:17 freenas SMP: AP CPU #1 Launched!
Jul  6 23:02:17 freenas Timecounter "TSC-low" frequency 1200028956 Hz quality 1000
Jul  6 23:02:17 freenas random: entropy device external interface
Jul  6 23:02:17 freenas kbd1 at kbdmux0
Jul  6 23:02:17 freenas module_register_init: MOD_LOAD (vesa, 0xffffffff80fc84d0, 0) error 19
Jul  6 23:02:17 freenas random: registering fast source Intel Secure Key RNG
Jul  6 23:02:17 freenas random: fast provider: "Intel Secure Key RNG"
Jul  6 23:02:17 freenas nexus0
Jul  6 23:02:17 freenas cryptosoft0: <software crypto> on motherboard
Jul  6 23:02:17 freenas aesni0: <AES-CBC,AES-XTS,AES-GCM,AES-ICM> on motherboard
Jul  6 23:02:17 freenas padlock0: No ACE support.
Jul  6 23:02:17 freenas acpi0: <ALASKA A M I > on motherboard
Jul  6 23:02:17 freenas acpi0: Power Button (fixed)
Jul  6 23:02:17 freenas cpu0: <ACPI CPU> on acpi0
Jul  6 23:02:17 freenas cpu1: <ACPI CPU> on acpi0
Jul  6 23:02:17 freenas cpu2: <ACPI CPU> on acpi0
Jul  6 23:02:17 freenas cpu3: <ACPI CPU> on acpi0
Jul  6 23:02:17 freenas cpu4: <ACPI CPU> on acpi0
Jul  6 23:02:17 freenas cpu5: <ACPI CPU> on acpi0
Jul  6 23:02:17 freenas cpu6: <ACPI CPU> on acpi0
Jul  6 23:02:17 freenas cpu7: <ACPI CPU> on acpi0
Jul  6 23:02:17 freenas hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0
Jul  6 23:02:17 freenas Timecounter "HPET" frequency 14318180 Hz quality 950
Jul  6 23:02:17 freenas Event timer "HPET" frequency 14318180 Hz quality 350
Jul  6 23:02:17 freenas Event timer "HPET1" frequency 14318180 Hz quality 340
Jul  6 23:02:17 freenas Event timer "HPET2" frequency 14318180 Hz quality 340
Jul  6 23:02:17 freenas atrtc0: <AT realtime clock> port 0x70-0x77 irq 8 on acpi0
Jul  6 23:02:17 freenas atrtc0: Warning: Couldn't map I/O.
Jul  6 23:02:17 freenas atrtc0: registered as a time-of-day clock, resolution 1.000000s
Jul  6 23:02:17 freenas Event timer "RTC" frequency 32768 Hz quality 0
Jul  6 23:02:17 freenas attimer0: <AT timer> port 0x40-0x43,0x50-0x53 irq 0 on acpi0
Jul  6 23:02:17 freenas Timecounter "i8254" frequency 1193182 Hz quality 0
Jul  6 23:02:17 freenas Event timer "i8254" frequency 1193182 Hz quality 100
Jul  6 23:02:17 freenas Timecounter "ACPI-fast" frequency 3579545 Hz quality 900
Jul  6 23:02:17 freenas acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0
Jul  6 23:02:17 freenas pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
Jul  6 23:02:17 freenas pcib0: _OSC returned error 0x10
Jul  6 23:02:17 freenas pci0: <ACPI PCI bus> on pcib0
Jul  6 23:02:17 freenas pcib1: <ACPI PCI-PCI bridge> mem 0xdf740000-0xdf75ffff irq 16 at device 1.0 on pci0
Jul  6 23:02:17 freenas pci1: <ACPI PCI bus> on pcib1
Jul  6 23:02:17 freenas pcib2: <ACPI PCI-PCI bridge> mem 0xdf720000-0xdf73ffff irq 20 at device 3.0 on pci0
Jul  6 23:02:17 freenas pci2: <ACPI PCI bus> on pcib2
Jul  6 23:02:17 freenas pcib3: <ACPI PCI-PCI bridge> mem 0xdf500000-0xdf51ffff irq 22 at device 0.0 on pci2
Jul  6 23:02:17 freenas pci3: <ACPI PCI bus> on pcib3
Jul  6 23:02:17 freenas pcib4: <PCI-PCI bridge> irq 23 at device 1.0 on pci3
Jul  6 23:02:17 freenas pci4: <PCI bus> on pcib4
Jul  6 23:02:17 freenas ahci0: <Marvell 88SE9172 AHCI SATA controller> port 0xc040-0xc047,0xc030-0xc033,0xc020-0xc027,0xc010-0xc013,0xc000-0xc00f mem 0xdf410000-0xdf4101ff irq 23 at device 0.0 on pci4
Jul  6 23:02:17 freenas ahci0: AHCI v1.00 with 2 6Gbps ports, Port Multiplier supported with FBS
Jul  6 23:02:17 freenas ahcich0: <AHCI channel> at channel 0 on ahci0
Jul  6 23:02:17 freenas ahcich1: <AHCI channel> at channel 1 on ahci0
Jul  6 23:02:17 freenas pcib5: <PCI-PCI bridge> irq 23 at device 5.0 on pci3
Jul  6 23:02:17 freenas pci5: <PCI bus> on pcib5
Jul  6 23:02:17 freenas pcib6: <PCI-PCI bridge> irq 23 at device 0.0 on pci5
Jul  6 23:02:17 freenas pci6: <PCI bus> on pcib6
Jul  6 23:02:17 freenas vgapci0: <VGA-compatible display> port 0xb000-0xb07f mem 0xde000000-0xdeffffff,0xdf000000-0xdf01ffff irq 23 at device 0.0 on pci6
Jul  6 23:02:17 freenas vgapci0: Boot video device
Jul  6 23:02:17 freenas pcib7: <PCI-PCI bridge> irq 21 at device 7.0 on pci3
Jul  6 23:02:17 freenas pci7: <PCI bus> on pcib7
Jul  6 23:02:17 freenas igb0: <Intel(R) PRO/1000 Network Connection, Version - 2.5.3-k> port 0xa000-0xa01f mem 0xdf300000-0xdf37ffff,0xdf380000-0xdf383fff irq 21 at device 0.0 on pci7
Jul  6 23:02:17 freenas igb0: Using MSIX interrupts with 5 vectors
Jul  6 23:02:17 freenas igb0: Ethernet address: d0:50:99:c0:9d:02
Jul  6 23:02:17 freenas igb0: Bound queue 0 to cpu 0
Jul  6 23:02:17 freenas igb0: Bound queue 1 to cpu 1
Jul  6 23:02:17 freenas igb0: Bound queue 2 to cpu 2
Jul  6 23:02:17 freenas igb0: Bound queue 3 to cpu 3
Jul  6 23:02:17 freenas pcib8: <PCI-PCI bridge> irq 23 at device 9.0 on pci3
Jul  6 23:02:17 freenas pci8: <PCI bus> on pcib8
Jul  6 23:02:17 freenas igb1: <Intel(R) PRO/1000 Network Connection, Version - 2.5.3-k> port 0x9000-0x901f mem 0xdf200000-0xdf27ffff,0xdf280000-0xdf283fff irq 23 at device 0.0 on pci8
Jul  6 23:02:17 freenas igb1: Using MSIX interrupts with 5 vectors
Jul  6 23:02:17 freenas igb1: Ethernet address: d0:50:99:c0:9d:03
Jul  6 23:02:17 freenas igb1: Bound queue 0 to cpu 4
Jul  6 23:02:17 freenas igb1: Bound queue 1 to cpu 5
Jul  6 23:02:17 freenas igb1: Bound queue 2 to cpu 6
Jul  6 23:02:17 freenas igb1: Bound queue 3 to cpu 7
Jul  6 23:02:17 freenas pcib9: <ACPI PCI-PCI bridge> mem 0xdf700000-0xdf71ffff at device 4.0 on pci0
Jul  6 23:02:17 freenas pci9: <ACPI PCI bus> on pcib9
Jul  6 23:02:17 freenas ahci1: <Marvell 88SE9230 AHCI SATA controller> port 0xd050-0xd057,0xd040-0xd043,0xd030-0xd037,0xd020-0xd023,0xd000-0xd01f mem 0xdf610000-0xdf6107ff irq 23 at device 0.0 on pci9
Jul  6 23:02:17 freenas ahci1: AHCI v1.20 with 8 6Gbps ports, Port Multiplier not supported
Jul  6 23:02:17 freenas ahci1: quirks=0x900<NOBSYRES,ALTSIG>
Jul  6 23:02:17 freenas ahcich2: <AHCI channel> at channel 0 on ahci1
Jul  6 23:02:17 freenas ahcich3: <AHCI channel> at channel 1 on ahci1
Jul  6 23:02:17 freenas ahcich4: <AHCI channel> at channel 2 on ahci1
Jul  6 23:02:17 freenas ahcich5: <AHCI channel> at channel 3 on ahci1
Jul  6 23:02:17 freenas ahcich6: <AHCI channel> at channel 4 on ahci1
Jul  6 23:02:17 freenas ahcich7: <AHCI channel> at channel 5 on ahci1
Jul  6 23:02:17 freenas ahcich8: <AHCI channel> at channel 6 on ahci1
Jul  6 23:02:17 freenas ahcich9: <AHCI channel> at channel 7 on ahci1
Jul  6 23:02:17 freenas pci0: <base peripheral, IOMMU> at device 15.0 (no driver attached)
Jul  6 23:02:17 freenas ehci0: <Intel Avoton USB 2.0 controller> mem 0xdf763000-0xdf7633ff irq 23 at device 22.0 on pci0
Jul  6 23:02:17 freenas usbus0: EHCI version 1.0
Jul  6 23:02:17 freenas usbus0 on ehci0
Jul  6 23:02:17 freenas usbus0: 480Mbps High Speed USB v2.0
Jul  6 23:02:17 freenas ahci2: <Intel Avoton AHCI SATA controller> port 0xe0d0-0xe0d7,0xe0c0-0xe0c3,0xe0b0-0xe0b7,0xe0a0-0xe0a3,0xe040-0xe05f mem 0xdf762000-0xdf7627ff irq 19 at device 23.0 on pci0
Jul  6 23:02:17 freenas ahci2: AHCI v1.30 with 4 3Gbps ports, Port Multiplier not supported
Jul  6 23:02:17 freenas ahcich10: <AHCI channel> at channel 0 on ahci2
Jul  6 23:02:17 freenas ahcich11: <AHCI channel> at channel 1 on ahci2
Jul  6 23:02:17 freenas ahcich12: <AHCI channel> at channel 2 on ahci2
Jul  6 23:02:17 freenas ahcich13: <AHCI channel> at channel 3 on ahci2
Jul  6 23:02:17 freenas ahci3: <Intel Avoton AHCI SATA controller> port 0xe090-0xe097,0xe080-0xe083,0xe070-0xe077,0xe060-0xe063,0xe020-0xe03f mem 0xdf761000-0xdf7617ff irq 19 at device 24.0 on pci0
Jul  6 23:02:17 freenas ahci3: AHCI v1.30 with 2 6Gbps ports, Port Multiplier not supported
Jul  6 23:02:17 freenas ahcich14: <AHCI channel> at channel 0 on ahci3
Jul  6 23:02:17 freenas ahcich15: <AHCI channel> at channel 1 on ahci3
Jul  6 23:02:17 freenas isab0: <PCI-ISA bridge> at device 31.0 on pci0
Jul  6 23:02:17 freenas isa0: <ISA bus> on isab0
Jul  6 23:02:17 freenas uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
Jul  6 23:02:17 freenas uart2: <16550 or compatible> port 0x248-0x24f irq 3 on acpi0
Jul  6 23:02:17 freenas ichwd0: <Intel Avoton/Rangeley SoC watchdog timer> on isa0
Jul  6 23:02:17 freenas ichwd0: ICH WDT present but disabled in BIOS or hardware
Jul  6 23:02:17 freenas device_attach: ichwd0 attach returned 6
Jul  6 23:02:17 freenas wbwd0: <Nuvoton NCT6776 (0xc3/0x33) Watchdog Timer> at port 0x2e-0x2f on isa0
Jul  6 23:02:17 freenas ichwd0: <Intel Avoton/Rangeley SoC watchdog timer> at port 0x430-0x437,0x460-0x47f on isa0
Jul  6 23:02:17 freenas ichwd0: ICH WDT present but disabled in BIOS or hardware
Jul  6 23:02:17 freenas device_attach: ichwd0 attach returned 6
Jul  6 23:02:17 freenas orm0: <ISA Option ROMs> at iomem 0xc0000-0xc7fff,0xcb000-0xcbfff on isa0
Jul  6 23:02:17 freenas sc0: <System console> at flags 0x100 on isa0
Jul  6 23:02:17 freenas sc0: CGA <16 virtual consoles, flags=0x300>
Jul  6 23:02:17 freenas vga0: <Generic ISA VGA> at port 0x3d0-0x3db iomem 0xb8000-0xbffff on isa0
Jul  6 23:02:17 freenas atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
Jul  6 23:02:17 freenas atkbd0: <AT Keyboard> irq 1 on atkbdc0
Jul  6 23:02:17 freenas kbd0 at atkbd0
Jul  6 23:02:17 freenas atkbd0: [GIANT-LOCKED]
Jul  6 23:02:17 freenas coretemp0: <CPU On-Die Thermal Sensors> on cpu0
Jul  6 23:02:17 freenas est0: <Enhanced SpeedStep Frequency Control> on cpu0
Jul  6 23:02:17 freenas coretemp1: <CPU On-Die Thermal Sensors> on cpu1
Jul  6 23:02:17 freenas est1: <Enhanced SpeedStep Frequency Control> on cpu1
Jul  6 23:02:17 freenas coretemp2: <CPU On-Die Thermal Sensors> on cpu2
Jul  6 23:02:17 freenas est2: <Enhanced SpeedStep Frequency Control> on cpu2
Jul  6 23:02:17 freenas coretemp3: <CPU On-Die Thermal Sensors> on cpu3
Jul  6 23:02:17 freenas est3: <Enhanced SpeedStep Frequency Control> on cpu3
Jul  6 23:02:17 freenas coretemp4: <CPU On-Die Thermal Sensors> on cpu4
Jul  6 23:02:17 freenas est4: <Enhanced SpeedStep Frequency Control> on cpu4
Jul  6 23:02:17 freenas coretemp5: <CPU On-Die Thermal Sensors> on cpu5
Jul  6 23:02:17 freenas est5: <Enhanced SpeedStep Frequency Control> on cpu5
Jul  6 23:02:17 freenas coretemp6: <CPU On-Die Thermal Sensors> on cpu6
Jul  6 23:02:17 freenas est6: <Enhanced SpeedStep Frequency Control> on cpu6
Jul  6 23:02:17 freenas coretemp7: <CPU On-Die Thermal Sensors> on cpu7
Jul  6 23:02:17 freenas est7: <Enhanced SpeedStep Frequency Control> on cpu7
Jul  6 23:02:17 freenas ZFS filesystem version: 5
Jul  6 23:02:17 freenas ZFS storage pool version: features support (5000)
Jul  6 23:02:17 freenas Timecounters tick every 1.000 msec
Jul  6 23:02:17 freenas freenas_sysctl: adding account.
Jul  6 23:02:17 freenas freenas_sysctl: adding directoryservice.
Jul  6 23:02:17 freenas freenas_sysctl: adding middlewared.
Jul  6 23:02:17 freenas freenas_sysctl: adding network.
Jul  6 23:02:17 freenas freenas_sysctl: adding services.
Jul  6 23:02:17 freenas ipfw2 (+ipv6) initialized, divert enabled, nat enabled, default to accept, logging disabled
Jul  6 23:02:17 freenas ugen0.1: <Intel EHCI root HUB> at usbus0
Jul  6 23:02:17 freenas uhub0: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus0
Jul  6 23:02:17 freenas uhub0: 8 ports with 8 removable, self powered
Jul  6 23:02:17 freenas ugen0.2: <vendor 0x8087 product 0x07db> at usbus0
Jul  6 23:02:17 freenas uhub1 on uhub0
Jul  6 23:02:17 freenas uhub1: <vendor 0x8087 product 0x07db, class 9/0, rev 2.00/0.02, addr 2> on usbus0
Jul  6 23:02:17 freenas uhub1: 4 ports with 4 removable, self powered
Jul  6 23:02:17 freenas ugen0.3: <American Power Conversion Back-UPS RS 1300G FW863.L6 .D USB FWL6> at usbus0
Jul  6 23:02:17 freenas ugen0.4: <American Megatrends Inc. Virtual Hub> at usbus0
Jul  6 23:02:17 freenas uhub2 on uhub1
Jul  6 23:02:17 freenas uhub2: <7-port Hub> on usbus0
Jul  6 23:02:17 freenas uhub2: 5 ports with 5 removable, self powered
Jul  6 23:02:17 freenas ugen0.5: <American Megatrends Inc. Virtual Keyboard and Mouse> at usbus0
Jul  6 23:02:17 freenas ukbd0 on uhub2
Jul  6 23:02:17 freenas ukbd0: <Keyboard Interface> on usbus0
Jul  6 23:02:17 freenas kbd2 at ukbd0
Jul  6 23:02:17 freenas random: unblocking device.
Jul  6 23:02:17 freenas ada0 at ahcich3 bus 0 scbus3 target 0 lun 0
Jul  6 23:02:17 freenas ada0: <16GB SATA Flash Drive SFDE001A> ACS-2 ATA SATA 3.x device
Jul  6 23:02:17 freenas ada0: Serial Number E0215343400000000099
Jul  6 23:02:17 freenas ada0: 600.000MB/s transfers (SATA 3.x, UDMA5, PIO 512bytes)
Jul  6 23:02:17 freenas ada0: Command Queueing enabled
Jul  6 23:02:17 freenas ada0: 15272MB (31277232 512 byte sectors)
Jul  6 23:02:17 freenas ada1 at ahcich10 bus 0 scbus10 target 0 lun 0
Jul  6 23:02:17 freenas ada1: <WDC WD30EFRX-68EUZN0 82.00A82> ACS-2 ATA SATA 3.x device
Jul  6 23:02:17 freenas ada1: Serial Number WD-WMC4N0H6L092
Jul  6 23:02:17 freenas ada1: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
Jul  6 23:02:17 freenas ada1: Command Queueing enabled
Jul  6 23:02:17 freenas ada1: 2861588MB (5860533168 512 byte sectors)
Jul  6 23:02:17 freenas ada1: quirks=0x1<4K>
Jul  6 23:02:17 freenas ada2 at ahcich11 bus 0 scbus11 target 0 lun 0
Jul  6 23:02:17 freenas ada2: <WDC WD30EFRX-68EUZN0 82.00A82> ACS-2 ATA SATA 3.x device
Jul  6 23:02:17 freenas ada2: Serial Number WD-WMC4N0KATSV7
Jul  6 23:02:17 freenas ada2: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
Jul  6 23:02:17 freenas ada2: Command Queueing enabled
Jul  6 23:02:17 freenas ada2: 2861588MB (5860533168 512 byte sectors)
Jul  6 23:02:17 freenas ada2: quirks=0x1<4K>
Jul  6 23:02:17 freenas ada3 at ahcich12 bus 0 scbus12 target 0 lun 0
Jul  6 23:02:17 freenas ada3: <WDC WD30EFRX-68EUZN0 82.00A82> ACS-2 ATA SATA 3.x device
Jul  6 23:02:17 freenas ada3: Serial Number WD-WCC4N5SDA835
Jul  6 23:02:17 freenas ada3: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
Jul  6 23:02:17 freenas ada3: Command Queueing enabled
Jul  6 23:02:17 freenas ada3: 2861588MB (5860533168 512 byte sectors)
Jul  6 23:02:17 freenas ada3: quirks=0x1<4K>
Jul  6 23:02:17 freenas ada4 at ahcich13 bus 0 scbus13 target 0 lun 0
Jul  6 23:02:17 freenas ada4: <WDC WD30EFRX-68EUZN0 82.00A82> ACS-2 ATA SATA 3.x device
Jul  6 23:02:17 freenas ada4: Serial Number WD-WMC4N0K5Y6SC
Jul  6 23:02:17 freenas ada4: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
Jul  6 23:02:17 freenas ada4: Command Queueing enabled
Jul  6 23:02:17 freenas ada4: 2861588MB (5860533168 512 byte sectors)
Jul  6 23:02:17 freenas ada4: quirks=0x1<4K>
Jul  6 23:02:17 freenas pass1 at ahcich9 bus 0 scbus9 target 0 lun 0
Jul  6 23:02:17 freenas pass1: <Marvell Console 1.01> Removable Processor SCSI device
Jul  6 23:02:17 freenas pass1: Serial Number HKDP221516WL
Jul  6 23:02:17 freenas pass1: 150.000MB/s transfers (SATA 1.x, UDMA4, ATAPI 12bytes, PIO 8192bytes)
Jul  6 23:02:17 freenas Trying to mount root from zfs:freenas-boot/ROOT/11.1-U7 []...
Jul  6 23:02:17 freenas kernel: igb0: link state changed to UP
Jul  6 23:02:17 freenas kernel: igb0: link state changed to UP
Jul  6 23:02:17 freenas ipmi0: <IPMI System Interface> port 0xca2,0xca3 on acpi0
Jul  6 23:02:17 freenas ipmi0: KCS mode found at io 0xca2 on acpi
Jul  6 23:02:17 freenas ipmi0: IPMI device rev. 1, firmware rev. 0.35, version 2.0
Jul  6 23:02:17 freenas ipmi0: Number of channels 2
Jul  6 23:02:17 freenas ipmi0: Attached watchdog
Jul  6 23:02:17 freenas ichwd0: <Intel Avoton/Rangeley SoC watchdog timer> at port 0x430-0x437,0x460-0x47f on isa0
Jul  6 23:02:17 freenas ichwd0: ICH WDT present but disabled in BIOS or hardware
Jul  6 23:02:17 freenas device_attach: ichwd0 attach returned 6
Jul  6 23:02:17 freenas GEOM_RAID5: Module loaded, version 1.3.20140711.62 (rev f91e28e40bf7)
Jul  6 23:02:17 freenas GEOM_MIRROR: Device mirror/swap0 launched (2/2).
Jul  6 23:02:17 freenas GEOM_MIRROR: Device mirror/swap1 launched (2/2).
Jul  6 23:02:17 freenas GEOM_ELI: Device mirror/swap0.eli created.
Jul  6 23:02:17 freenas GEOM_ELI: Encryption: AES-XTS 128
Jul  6 23:02:17 freenas GEOM_ELI:     Crypto: hardware
Jul  6 23:02:17 freenas GEOM_ELI: Device mirror/swap1.eli created.
Jul  6 23:02:17 freenas GEOM_ELI: Encryption: AES-XTS 128
Jul  6 23:02:17 freenas GEOM_ELI:     Crypto: hardware
Jul  6 23:02:17 freenas hwpmc: SOFT/16/64/0x67<INT,USR,SYS,REA,WRI> TSC/1/64/0x20<REA> IAP/2/40/0x3ff<INT,USR,SYS,EDG,THR,REA,WRI,INV,QUA,PRC> IAF/3/40/0x67<INT,USR,SYS,REA,WRI>
Jul  6 23:02:17 freenas kernel: igb0: link state changed to DOWN
Jul  6 23:02:17 freenas kernel: igb0: link state changed to DOWN
Jul  6 23:02:17 freenas ums0 on uhub2
Jul  6 23:02:17 freenas ums0: <Mouse Interface> on usbus0
Jul  6 23:02:17 freenas ums0: 3 buttons and [Z] coordinates ID=0
Jul  6 23:02:17 freenas kernel: igb0: link state changed to UP
Jul  6 23:02:17 freenas kernel: igb0: link state changed to UP
Jul  6 23:02:19 freenas ntpd[2162]: ntpd 4.2.8p10-a (1): Starting
Jul  6 23:02:35 freenas bridge0: Ethernet address: 02:5f:0b:ea:f2:00
Jul  6 23:02:35 freenas kernel: igb0: promiscuous mode enabled
Jul  6 23:02:35 freenas kernel: bridge0: link state changed to UP
Jul  6 23:02:35 freenas kernel: bridge0: link state changed to UP
Jul  6 23:02:35 freenas epair0a: Ethernet address: 02:cb:90:00:05:0a
Jul  6 23:02:35 freenas epair0b: Ethernet address: 02:cb:e0:00:06:0b
Jul  6 23:02:35 freenas kernel: epair0a: link state changed to UP
Jul  6 23:02:35 freenas kernel: epair0a: link state changed to UP
Jul  6 23:02:35 freenas kernel: epair0b: link state changed to UP
Jul  6 23:02:35 freenas kernel: epair0b: link state changed to UP
Jul  6 23:02:35 freenas kernel: igb0: link state changed to DOWN
Jul  6 23:02:35 freenas kernel: igb0: link state changed to DOWN
Jul  6 23:02:35 freenas kernel: epair0a: promiscuous mode enabled
Jul  6 23:02:40 freenas kernel: igb0: link state changed to UP
Jul  6 23:02:40 freenas kernel: igb0: link state changed to UP


I'm not sure what to do next :|.
 

Kortex

Dabbler
Joined
Mar 2, 2015
Messages
48
Also, zpool status reports...

Code:
                                                                                                                                   
        NAME                                            STATE     READ WRITE CKSUM                                                 
        jvol                                            ONLINE       0     0     0                                                 
          raidz2-0                                      ONLINE       0     0     0                                                 
            gptid/f0cddc04-5470-11e7-b93e-d05099c09d02  ONLINE       0     0     0                                                 
            gptid/f1f6acdb-5470-11e7-b93e-d05099c09d02  ONLINE       0     0     0                                                 
            gptid/49ced6c5-6756-11e7-b171-d05099c09d02  ONLINE       0     0     0                                                 
            gptid/f43c8c79-5470-11e7-b93e-d05099c09d02  ONLINE       0     0    10                                                 
                                                                                                                                    
errors: No known data errors                                                                                                        
 

Kortex

Dabbler
Joined
Mar 2, 2015
Messages
48
OK. I replaced that drive and let it resilver. Now it's saying:

Code:
CRITICAL: July 10, 2020, 4:07 a.m. - Device: /dev/ada2, Temperature 41 Celsius reached critical limit of 40 Celsius (Min/Max 38/41!)
CRITICAL: July 10, 2020, 4:07 a.m. - Device: /dev/ada3, Temperature 41 Celsius reached critical limit of 40 Celsius (Min/Max 37/41!)
CRITICAL: July 10, 2020, 4:07 a.m. - Device: /dev/ada4, not capable of SMART self-check
CRITICAL: July 10, 2020, 5:37 a.m. - Device: /dev/ada4, ATA error count increased from 0 to 10
CRITICAL: July 10, 2020, 3:02 a.m. - The volume jvol state is ONLINE: One or more devices is currently being resilvered. The pool will continue to function, possibly in a degraded state.


I fixed the temp threshold. But the disk I just replaced now has an error count of 10??

Also...
Code:
Shell

[root@freenas ~]# zpool status                                                                                                   
  pool: freenas-boot                                                                                                             
state: ONLINE                                                                                                                   
  scan: scrub repaired 0 in 0 days 00:01:18 with 0 errors on Fri Jul 10 03:46:18 2020                                             
config:                                                                                                                           
                                                                                                                                  
        NAME        STATE     READ WRITE CKSUM                                                                                   
        freenas-boot  ONLINE       0     0     0                                                                                 
          ada0p2    ONLINE       0     0     0                                                                                   
                                                                                                                                  
errors: No known data errors                                                                                                     
                                                                                                                                  
  pool: jvol                                                                                                                     
state: ONLINE                                                                                                                   
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 Fri Jul 10 03:03:10 2020                                                                       
        3.20T scanned at 96.4M/s, 2.17T issued at 65.3M/s, 8.18T total                                                           
        538G resilvered, 26.50% done, 1 days 02:49:36 to go                                                                       
config:                                                                                                                           
                                                                                                                                  
        NAME                                            STATE     READ WRITE CKSUM                                               
        jvol                                            ONLINE       0     0     0                                               
          raidz2-0                                      ONLINE       0     0     0                                               
            gptid/f0cddc04-5470-11e7-b93e-d05099c09d02  ONLINE       0     0     0                                               
            gptid/f1f6acdb-5470-11e7-b93e-d05099c09d02  ONLINE       0     0     0                                               
            gptid/49ced6c5-6756-11e7-b171-d05099c09d02  ONLINE       0     0     0                                               
            gptid/4fc397e0-c27b-11ea-8f7c-d05099c09d02  ONLINE       0     0     0  (resilvering)                                 
                                                                                                                                  
errors: No known data errors


These errors are constant now.

Code:
Jul 10 12:46:06 freenas (ada4:ahcich13:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 00 50 6a 9d 40 4b 00 00 01 00 00
Jul 10 12:46:06 freenas (ada4:ahcich13:0:0:0): CAM status: ATA Status Error
Jul 10 12:46:06 freenas (ada4:ahcich13:0:0:0): ATA status: 41 (DRDY ERR), error: 10 (IDNF )
Jul 10 12:46:06 freenas (ada4:ahcich13:0:0:0): RES: 41 10 50 6a 9d 00 4b 00 00 00 00
Jul 10 12:46:06 freenas (ada4:ahcich13:0:0:0): Retrying command
Jul 10 12:46:21 freenas (ada4:ahcich13:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 00 c0 d1 a1 40 4b 00 00 01 00 00
Jul 10 12:46:21 freenas (ada4:ahcich13:0:0:0): CAM status: ATA Status Error
Jul 10 12:46:21 freenas (ada4:ahcich13:0:0:0): ATA status: 41 (DRDY ERR), error: 10 (IDNF )
Jul 10 12:46:21 freenas (ada4:ahcich13:0:0:0): RES: 41 10 c0 d1 a1 00 4b 00 00 00 00
Jul 10 12:46:21 freenas (ada4:ahcich13:0:0:0): Retrying command
Jul 10 12:46:29 freenas (ada4:ahcich13:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 00 90 89 a1 40 4b 00 00 01 00 00
Jul 10 12:46:29 freenas (ada4:ahcich13:0:0:0): CAM status: ATA Status Error
Jul 10 12:46:29 freenas (ada4:ahcich13:0:0:0): ATA status: 41 (DRDY ERR), error: 10 (IDNF )
Jul 10 12:46:29 freenas (ada4:ahcich13:0:0:0): RES: 41 10 90 89 a1 00 4b 00 00 00 00
Jul 10 12:46:29 freenas (ada4:ahcich13:0:0:0): Retrying command
Jul 10 12:46:47 freenas (ada4:ahcich13:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 00 10 ed a6 40 4b 00 00 01 00 00
Jul 10 12:46:47 freenas (ada4:ahcich13:0:0:0): CAM status: ATA Status Error
Jul 10 12:46:47 freenas (ada4:ahcich13:0:0:0): ATA status: 41 (DRDY ERR), error: 10 (IDNF )
Jul 10 12:46:47 freenas (ada4:ahcich13:0:0:0): RES: 41 10 10 ed a6 00 4b 00 00 00 00
Jul 10 12:46:47 freenas (ada4:ahcich13:0:0:0): Retrying command
Jul 10 12:46:54 freenas (ada4:ahcich13:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 80 70 d8 a6 40 4b 00 00 00 00 00
Jul 10 12:46:54 freenas (ada4:ahcich13:0:0:0): CAM status: ATA Status Error
Jul 10 12:46:54 freenas (ada4:ahcich13:0:0:0): ATA status: 41 (DRDY ERR), error: 10 (IDNF )
Jul 10 12:46:54 freenas (ada4:ahcich13:0:0:0): RES: 41 10 70 d8 a6 00 4b 00 00 00 00
Jul 10 12:46:54 freenas (ada4:ahcich13:0:0:0): Retrying command
Jul 10 12:47:11 freenas (ada4:ahcich13:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 00 10 a7 b0 40 4b 00 00 01 00 00
Jul 10 12:47:11 freenas (ada4:ahcich13:0:0:0): CAM status: ATA Status Error
Jul 10 12:47:11 freenas (ada4:ahcich13:0:0:0): ATA status: 41 (DRDY ERR), error: 10 (IDNF )
Jul 10 12:47:11 freenas (ada4:ahcich13:0:0:0): RES: 41 10 10 a7 b0 00 4b 00 00 00 00
Jul 10 12:47:11 freenas (ada4:ahcich13:0:0:0): Retrying command
 
Last edited:

Kortex

Dabbler
Joined
Mar 2, 2015
Messages
48
More information. It says the drive isn't smart capable. I ran a smart test 3 times. Twice it said the device wasn't capable and once it gave results. What the hell is going on? Bad cable possibly?
 

Samuel Tai

Never underestimate your own stupidity
Moderator
Joined
Apr 24, 2020
Messages
5,399
What model is the new drive? Those errors suggest you installed an SMR drive.
 

Kortex

Dabbler
Joined
Mar 2, 2015
Messages
48
It's "WD30EFAX" which apparently is an SMR drive. The old drive was "WD30EFRX" which is CMR.

However, why would those errors follow after replacement? I wish I could stop the resilver and change the SATA cable. These are the exact errors as before the replacement.
 
Last edited:

Samuel Tai

Never underestimate your own stupidity
Moderator
Joined
Apr 24, 2020
Messages
5,399
Because a SMR drive has abysmal write performance, and the IO buffer gets filled up during the resilver, preventing the controller from responding to the SMART requests. RMA the drive for a CMR drive.
 

Kortex

Dabbler
Joined
Mar 2, 2015
Messages
48
Because a SMR drive has abysmal write performance, and the IO buffer gets filled up during the resilver, preventing the controller from responding to the SMART requests. RMA the drive for a CMR drive.

Can I stop the resilver safely?
 

Samuel Tai

Never underestimate your own stupidity
Moderator
Joined
Apr 24, 2020
Messages
5,399

Kortex

Dabbler
Joined
Mar 2, 2015
Messages
48
Just pull the SATA cable to the drive, and the resilver will eventually fail.

OK I will. Thank you for all your help sir. Lastly, theory question. I have four new drives sitting here. I had planned on migrating to a new (larger) pool. Do you think I should replace the drive, let it resilver and then copy the data? Or, would it be safe to copy the data to a new pool with 3 of the 4 disks functioning? Looking for an honest opinion.
 

Samuel Tai

Never underestimate your own stupidity
Moderator
Joined
Apr 24, 2020
Messages
5,399
I'd build a new pool as a RAIDZ2, and migrate the data over.
 

Kortex

Dabbler
Joined
Mar 2, 2015
Messages
48
I'd build a new pool as a RAIDZ2, and migrate the data over.

The current pool of four disks is RAIDZ2. You'd do that without buying a new disk to replace this SMR one? The four I have sitting here (I just checked) are definitely CMR.
 

Samuel Tai

Never underestimate your own stupidity
Moderator
Joined
Apr 24, 2020
Messages
5,399
If you have the drive ports to create a new pool, that's better for data safety than trying to expand the current pool in place. You'd create the new pool, and then set up an on-box replication job to replicate from the old pool to the new pool.
 

Kortex

Dabbler
Joined
Mar 2, 2015
Messages
48
If you have the drive ports to create a new pool, that's better for data safety than trying to expand the current pool in place. You'd create the new pool, and then set up an on-box replication job to replicate from the old pool to the new pool.

I do have the ports but it still doesn't explain why I'm getting the same ATA STATUS error from before with a completely different drive. I'm pretty nervous to replicate it but I guess I don't have a choice :|.
 
Top