Is This Drive Dying? Should it be replaced?

[n00b-beginnings]

I have this SeaGate Barracuda - ada5 -which has been "reporting" offline uncorrectable sectors. Currently the number is 1048 Offline Uncorrectable Sectors.

During a File Transfer Into the Server yesterday it climed over 2000 and then began to fall back down to its current level of 1048.

Here are the results of smartctl -x /dev/ada5

I'm just having a bit of confusion sorting it out.... thanks for your help.



smartctl 7.0 2018-12-30 r4883 [FreeBSD 11.3-RELEASE-p11 amd64] (local build)
Copyright (C) 2002-18, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family: Seagate Barracuda 7200.14 (AF)
Device Model: ST1000DM003-9YN162
Serial Number: S1D48MLX
LU WWN Device Id: 5 000c50 051da60a1
Firmware Version: CC4B
User Capacity: 1,000,204,886,016 bytes [1.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 7200 rpm
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA8-ACS T13/1699-D revision 4
SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Mon Oct 12 14:01:36 2020 CDT

==> WARNING: A firmware update for this drive may be available,
see the following Seagate web pages:

Firmware Updates for Seagate Products | Seagate ASEAN

Seagate currently has firmware updates for certain drive families. Check here to see if an update is available.

knowledge.seagate.com

Barracuda (1 TB/disk platform) Firmware Update | Seagate ASEAN

knowledge.seagate.com

SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is: Unavailable
APM feature is: Disabled
Rd look-ahead is: Enabled
Write cache is: Enabled
DSN feature is: Unavailable
ATA Security is: Disabled, frozen [SEC2]
Wt Cache Reorder: Unavailable

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
See vendor-specific Attribute list for marginal Attributes.

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: ( 121) The previous self-test completed having
the read element of the test failed.
Total time to complete Offline
data collection: ( 575) 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: ( 113) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x3085) SCT Status supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE
1 Raw_Read_Error_Rate POSR-- 110 078 006 - 28943440
3 Spin_Up_Time PO---- 098 097 000 - 0
4 Start_Stop_Count -O--CK 100 100 020 - 192
5 Reallocated_Sector_Ct PO--CK 076 076 036 - 32672
7 Seek_Error_Rate POSR-- 079 060 030 - 86318164
9 Power_On_Hours -O--CK 065 065 000 - 31173
10 Spin_Retry_Count PO--C- 100 100 097 - 0
12 Power_Cycle_Count -O--CK 100 100 020 - 189
183 Runtime_Bad_Block -O--CK 100 100 000 - 0
184 End-to-End_Error -O--CK 100 100 099 - 0
187 Reported_Uncorrect -O--CK 001 001 000 - 6277
188 Command_Timeout -O--CK 100 098 000 - 5 6 6
189 High_Fly_Writes -O-RCK 001 001 000 - 2990
190 Airflow_Temperature_Cel -O---K 062 043 045 Past 38 (Min/Max 38/49 #373)
191 G-Sense_Error_Rate -O--CK 100 100 000 - 0
192 Power-Off_Retract_Count -O--CK 100 100 000 - 134
193 Load_Cycle_Count -O--CK 001 001 000 - 411683
194 Temperature_Celsius -O---K 038 057 000 - 38 (0 21 0 0 0)
197 Current_Pending_Sector -O--C- 094 001 000 - 1048
198 Offline_Uncorrectable ----C- 094 001 000 - 1048
199 UDMA_CRC_Error_Count -OSRCK 200 200 000 - 0
240 Head_Flying_Hours ------ 100 253 000 - 28982h+37m+10.693s
241 Total_LBAs_Written ------ 100 253 000 - 19867594008778
242 Total_LBAs_Read ------ 100 253 000 - 229512760525437
||||||_ K auto-keep
|||||__ C event count
||||___ R error rate
|||____ S speed/performance
||_____ O updated online
|______ P prefailure warning

General Purpose Log Directory Version 1
SMART Log Directory Version 1 [multi-sector log support]
Address Access R/W Size Description
0x00 GPL,SL R/O 1 Log Directory
0x01 SL R/O 1 Summary SMART error log
0x02 SL R/O 5 Comprehensive SMART error log
0x03 GPL R/O 5 Ext. Comprehensive SMART error log
0x06 SL R/O 1 SMART self-test log
0x07 GPL R/O 1 Extended self-test log
0x09 SL R/W 1 Selective self-test log
0x10 GPL R/O 1 NCQ Command Error log
0x11 GPL R/O 1 SATA Phy Event Counters log
0x21 GPL R/O 1 Write stream error log
0x22 GPL R/O 1 Read stream error log
0x80-0x9f GPL,SL R/W 16 Host vendor specific log
0xa1 GPL,SL VS 20 Device vendor specific log
0xa2 GPL VS 4496 Device vendor specific log
0xa8 GPL,SL VS 20 Device vendor specific log
0xa9 GPL,SL VS 1 Device vendor specific log
0xab GPL VS 1 Device vendor specific log
0xb0 GPL VS 5067 Device vendor specific log
0xbd GPL VS 512 Device vendor specific log
0xbe-0xbf GPL VS 65535 Device vendor specific log
0xc0 GPL,SL VS 1 Device vendor specific log
0xe0 GPL,SL R/W 1 SCT Command/Status
0xe1 GPL,SL R/W 1 SCT Data Transfer

SMART Extended Comprehensive Error Log Version: 1 (5 sectors)
Device Error Count: 37 (device log contains only the most recent 20 errors)
CR = Command Register
FEATR = Features Register
COUNT = Count (was: Sector Count) Register
LBA_48 = Upper bytes of LBA High/Mid/Low Registers ] ATA-8
LH = LBA High (was: Cylinder High) Register ] LBA
LM = LBA Mid (was: Cylinder Low) Register ] Register
LL = LBA Low (was: Sector Number) Register ]
DV = Device (was: Device/Head) Register
DC = Device Control Register
ER = Error register
ST = Status register
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 37 [16] occurred at disk power-on lifetime: 31122 hours (1296 days + 18 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 73 16 bb 00 00 00 Error: UNC at LBA = 0x7316bb00 = 1930869504

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 00 01 00 00 00 73 16 b5 98 40 00 22:27:03.686 READ FPDMA QUEUED
60 00 00 01 00 00 00 73 16 ba 98 40 00 22:27:03.686 READ FPDMA QUEUED
2f 00 00 00 01 00 00 00 00 00 10 00 00 22:27:03.578 READ LOG EXT
60 00 00 01 00 00 00 73 16 b5 98 40 00 22:27:00.794 READ FPDMA QUEUED
60 00 00 01 00 00 00 73 16 ba 98 40 00 22:27:00.793 READ FPDMA QUEUED

Error 36 [15] occurred at disk power-on lifetime: 31122 hours (1296 days + 18 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 73 16 bb 00 00 00 Error: UNC at LBA = 0x7316bb00 = 1930869504

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 00 01 00 00 00 73 16 b5 98 40 00 22:27:00.794 READ FPDMA QUEUED
60 00 00 01 00 00 00 73 16 ba 98 40 00 22:27:00.793 READ FPDMA QUEUED
2f 00 00 00 01 00 00 00 00 00 10 00 00 22:27:00.694 READ LOG EXT
60 00 00 01 00 00 00 73 16 b5 98 40 00 22:26:57.836 READ FPDMA QUEUED
60 00 00 01 00 00 00 73 16 ba 98 40 00 22:26:57.836 READ FPDMA QUEUED

Error 35 [14] occurred at disk power-on lifetime: 31122 hours (1296 days + 18 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 73 16 bb 00 00 00 Error: UNC at LBA = 0x7316bb00 = 1930869504

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 00 01 00 00 00 73 16 b5 98 40 00 22:26:57.836 READ FPDMA QUEUED
60 00 00 01 00 00 00 73 16 ba 98 40 00 22:26:57.836 READ FPDMA QUEUED
2f 00 00 00 01 00 00 00 00 00 10 00 00 22:26:57.802 READ LOG EXT
60 00 00 01 00 00 00 73 16 b5 98 40 00 22:26:54.930 READ FPDMA QUEUED
60 00 00 01 00 00 00 73 16 bc 98 40 00 22:26:54.929 READ FPDMA QUEUED

Error 34 [13] occurred at disk power-on lifetime: 31122 hours (1296 days + 18 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 73 16 bb 00 00 00 Error: UNC at LBA = 0x7316bb00 = 1930869504

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 00 01 00 00 00 73 16 b5 98 40 00 22:26:54.930 READ FPDMA QUEUED
60 00 00 01 00 00 00 73 16 bc 98 40 00 22:26:54.929 READ FPDMA QUEUED
60 00 00 01 00 00 00 73 16 ba 98 40 00 22:26:54.929 READ FPDMA QUEUED
2f 00 00 00 01 00 00 00 00 00 10 00 00 22:26:54.885 READ LOG EXT
60 00 00 01 00 00 00 73 16 bc 98 40 00 22:26:52.124 READ FPDMA QUEUED

Error 33 [12] occurred at disk power-on lifetime: 31122 hours (1296 days + 18 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 73 16 bb 00 00 00 Error: UNC at LBA = 0x7316bb00 = 1930869504

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 00 01 00 00 00 73 16 bc 98 40 00 22:26:52.124 READ FPDMA QUEUED
60 00 00 01 00 00 00 73 16 b7 98 40 00 22:26:52.110 READ FPDMA QUEUED
60 00 00 01 00 00 00 73 16 b6 98 40 00 22:26:52.088 READ FPDMA QUEUED
60 00 00 01 00 00 00 73 16 bb 98 40 00 22:26:52.088 READ FPDMA QUEUED
61 00 00 00 10 00 00 00 40 02 90 40 00 22:26:52.087 WRITE FPDMA QUEUED

Error 32 [11] occurred at disk power-on lifetime: 31122 hours (1296 days + 18 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 73 16 bb 00 00 00 Error: UNC at LBA = 0x7316bb00 = 1930869504

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 00 01 00 00 00 73 16 c4 98 40 00 22:26:49.100 READ FPDMA QUEUED
60 00 00 01 00 00 00 73 16 c3 98 40 00 22:26:49.100 READ FPDMA QUEUED
60 00 00 01 00 00 00 73 16 c2 98 40 00 22:26:49.100 READ FPDMA QUEUED
60 00 00 01 00 00 00 73 16 c1 98 40 00 22:26:49.100 READ FPDMA QUEUED
60 00 00 01 00 00 00 73 16 c0 98 40 00 22:26:49.100 READ FPDMA QUEUED

Error 31 [10] occurred at disk power-on lifetime: 31122 hours (1296 days + 18 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 73 16 bb 00 00 00 Error: UNC at LBA = 0x7316bb00 = 1930869504

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 00 01 00 00 00 73 16 c4 98 40 00 22:26:46.216 READ FPDMA QUEUED
60 00 00 01 00 00 00 73 16 c3 98 40 00 22:26:46.216 READ FPDMA QUEUED
60 00 00 01 00 00 00 73 16 c2 98 40 00 22:26:46.216 READ FPDMA QUEUED
60 00 00 01 00 00 00 73 16 c1 98 40 00 22:26:46.216 READ FPDMA QUEUED
60 00 00 01 00 00 00 73 16 c0 98 40 00 22:26:46.216 READ FPDMA QUEUED

Error 30 [9] occurred at disk power-on lifetime: 31122 hours (1296 days + 18 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 73 16 bb 00 00 00 Error: UNC at LBA = 0x7316bb00 = 1930869504

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 00 01 00 00 00 73 16 c4 98 40 00 22:26:43.333 READ FPDMA QUEUED
60 00 00 01 00 00 00 73 16 c3 98 40 00 22:26:43.333 READ FPDMA QUEUED
60 00 00 01 00 00 00 73 16 c2 98 40 00 22:26:43.332 READ FPDMA QUEUED
60 00 00 01 00 00 00 73 16 c1 98 40 00 22:26:43.332 READ FPDMA QUEUED
60 00 00 01 00 00 00 73 16 c0 98 40 00 22:26:43.332 READ FPDMA QUEUED

SMART Extended Self-test Log Version: 1 (1 sectors)
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed: read failure 90% 31172 1930869504
# 2 Extended offline Completed: read failure 90% 31146 1930869504
# 3 Extended offline Completed: read failure 90% 31105 15031272

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.

SCT Status Version: 3
SCT Version (vendor specific): 522 (0x020a)
Device State: Active (0)
Current Temperature: 38 Celsius
Power Cycle Min/Max Temperature: 38/49 Celsius
Lifetime Min/Max Temperature: 21/57 Celsius
Under/Over Temperature Limit Count: 0/0

SCT Data Table command not supported

SCT Error Recovery Control command not supported

Device Statistics (GP/SMART Log 0x04) not supported

Pending Defects log (GP Log 0x0c) not supported

SATA Phy Event Counters (GP Log 0x11)
ID Size Value Description
0x000a 2 12 Device-to-host register FISes sent due to a COM

 

[Pitfrr]

Well, your drive is failing...

The attributes #5, #197 and #198 are a good indicators for that (should be at 0... some forum members have different pain threshold here, some would tolerate few, but certainly not thousands as in that case... :-O). And as you mentioned, the increasing of the offline uncorrectable counter should really sound a big alarm.
Also the results of the short and long SMART tests ended with an error, that's never good.
And in the error log there are some UNC errors as well.

I would replace the drive as soon as possible...
You could RMA the drive, but I guess it's not under warranty anymore.


By the way, it would be more comfortable to put the output of the smartctl in the code tags "code" to ease the reading...

 

[n00b-beginnings]

Well, your drive is failing...

The attributes #5, #197 and #198 are a good indicators for that (should be at 0... some forum members have different pain threshold here, some would tolerate few, but certainly not thousands as in that case... :-O). And as you mentioned, the increasing of the offline uncorrectable counter should really sound a big alarm.
Also the results of the short and long SMART tests ended with an error, that's never good.
And in the error log there are some UNC errors as well.

I would replace the drive as soon as possible...
You could RMA the drive, but I guess it's not under warranty anymore.


By the way, it would be more comfortable to put the output of the smartctl in the code tags "code" to ease the reading...

When you say "Should be at 0" to which value are you referring? RAW_VALUE? or..

ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE
1 Raw_Read_Error_Rate POSR-- 117 078 006 - 141248576

5 Reallocated_Sector_Ct PO--CK 075 075 036 - 33344

197 Current_Pending_Sector -O--C- 099 001 000 - 312

198 Offline_Uncorrectable ----C- 099 001 000 - 312

 

[n00b-beginnings]

Code:

Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAGS    VALUE WORST THRESH FAIL RAW_VALUE
  1 Raw_Read_Error_Rate     POSR--   117   078   006    -    141562424
  3 Spin_Up_Time            PO----   098   097   000    -    0
  4 Start_Stop_Count        -O--CK   100   100   020    -    192
  5 Reallocated_Sector_Ct   PO--CK   075   075   036    -    33344
  7 Seek_Error_Rate         POSR--   079   060   030    -    86357176
  9 Power_On_Hours          -O--CK   065   065   000    -    31176
 10 Spin_Retry_Count        PO--C-   100   100   097    -    0
 12 Power_Cycle_Count       -O--CK   100   100   020    -    189
183 Runtime_Bad_Block       -O--CK   100   100   000    -    0
184 End-to-End_Error        -O--CK   100   100   099    -    0
187 Reported_Uncorrect      -O--CK   001   001   000    -    6277
188 Command_Timeout         -O--CK   100   098   000    -    5 6 6
189 High_Fly_Writes         -O-RCK   001   001   000    -    2990
190 Airflow_Temperature_Cel -O---K   059   043   045    Past 41 (Min/Max 38/49 #373)
191 G-Sense_Error_Rate      -O--CK   100   100   000    -    0
192 Power-Off_Retract_Count -O--CK   100   100   000    -    134
193 Load_Cycle_Count        -O--CK   001   001   000    -    411683
194 Temperature_Celsius     -O---K   041   057   000    -    41 (0 21 0 0 0)
197 Current_Pending_Sector  -O--C-   099   001   000    -    312
198 Offline_Uncorrectable   ----C-   099   001   000    -    312
199 UDMA_CRC_Error_Count    -OSRCK   200   200   000    -    0
240 Head_Flying_Hours       ------   100   253   000    -    28985h+29m+37.403s
241 Total_LBAs_Written      ------   100   253   000    -    19884778701237
242 Total_LBAs_Read         ------   100   253   000    -    230863177337763

 

[Pitfrr]

Yes, you should be looking at the RAW_VALUE column.
Some attributes are difficult to interpret because depending on the vendor but for the "common" ones, it's not the case (by "common" I'd say: #4, #5, #9, #12, #192, #194, #197, #198; those are the ones you'll be keeping an eye on and consider #5, #197 and #198 as the most important/critical ones).

 

[Fredda]

SMART Extended Self-test Log Version: 1 (1 sectors)
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed: read failure 90% 31172 1930869504
# 2 Extended offline Completed: read failure 90% 31146 1930869504
# 3 Extended offline Completed: read failure 90% 31105 15031272

Failing SMART tests are also a good indication your drive is going to die.

Did you cut that output off or are there really just these 3 tests which you have run?

If the latter is the case, you should setup a SMART task for all your drives.
Run a short test once a day and a long test once a week.

 

[Tigersharke]

It is also entirely possible that a zpool status would also show checksum errors, but whether it does or not seems immaterial considering the advice aready given.

 

[n00b-beginnings]

Failing SMART tests are also a good indication your drive is going to die.

Did you cut that output off or are there really just these 3 tests which you have run?

If the latter is the case, you should setup a SMART task for all your drives.
Run a short test once a day and a long test once a week.

TBH I'm not sure

 

[n00b-beginnings]

cache

It is also entirely possible that a zpool status would also show checksum errors, but whether it does or not seems immaterial considering the advice aready given.

root@uifmfreenas:~ # zpool status
pool: Storage
state: ONLINE
status: One or more devices has experienced an error resulting in data
corruption. Applications may be affected.
action: Restore the file in question if possible. Otherwise restore the
entire pool from backup.
see: http://illumos.org/msg/ZFS-8000-8A
scan: scrub repaired 0 in 0 days 02:07:01 with 1 errors on Sat Oct 10 11:17:34 2020
config:

NAME STATE READ WRITE CKSUM
Storage ONLINE 0 0 0
gptid/c9144f13-75a2-11e8-87c4-3085a9a5fd13 ONLINE 0 0 0
gptid/caef56f1-75a2-11e8-87c4-3085a9a5fd13 ONLINE 0 0 0
gptid/cc850098-75a2-11e8-87c4-3085a9a5fd13 ONLINE 0 0 0
gptid/367c3764-a32c-11ea-8273-000acd335a2c ONLINE 0 0 0
gptid/36e338ee-a32c-11ea-8273-000acd335a2c ONLINE 0 0 0
cache
gptid/954eec83-932d-11ea-b401-000acd335a2c ONLINE 0 0 0

errors: 2 data errors, use '-v' for a list

the two errors related to two files in the pool were Permanent Errors detected in the following files

/File/Name/Omitted/For/Privacy/File1
/File/Name/Omitted/For/Privacy/File2

 

[Fredda]

TBH I'm not sure

Well. It should be easy for you to check.

 

[HoneyBadger]

As others have stated, 100% dying drive and very likely that your pool has permanent damage based on the output of zpool status showing no redundancy (drives are in stripe)

Back up critical data immediately to another location. You can replace the drive with another, but only once a new drive has arrived - but it is highly suggested that you instead back everything up and recreate your pool with some manner of redundancy (RAIDZ2, mirrors)