Ironwolf 10TB failure

C

craigdt

Explorer
Joined
Mar 10, 2014
Messages
74
Hey all,

About 1.5 years ago, I bought 6x 10TB Ironwolf drives, recently one of them started reporting errors via both smart tests and TrueNAS zfs.

The odd thing is the SMART overall-health self-assessment test result: PASSED

Here is the full SMART output of the drive:
smartctl 7.2 2020-12-30 r5155 [FreeBSD 12.2-RELEASE-p14 amd64] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family: Seagate IronWolf
Device Model: ST10000VN0008-2JJ101
LU WWN Device Id: 5 000c50 0c6ad1fd4
Firmware Version: SC60
User Capacity: 10,000,831,348,736 bytes [10.0 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 7200 rpm
Form Factor: 3.5 inches
Device is: In smartctl database [for details use: -P show]
ATA Version is: ACS-4 (minor revision not indicated)
SATA Version is: SATA 3.3, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Sat Aug 20 18:34:11 2022 AEST
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: ( 118) The previous self-test completed having
the read element of the test failed.
Total time to complete Offline
data collection: ( 567) 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: ( 971) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x50bd) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 081 064 044 Pre-fail Always - 131301136
3 Spin_Up_Time 0x0003 087 087 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 122
5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 168
7 Seek_Error_Rate 0x000f 084 060 045 Pre-fail Always - 244743117
9 Power_On_Hours 0x0032 095 095 000 Old_age Always - 4735
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 122
18 Head_Health 0x000b 100 100 050 Pre-fail Always - 0
187 Reported_Uncorrect 0x0032 099 099 000 Old_age Always - 1
188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0
190 Airflow_Temperature_Cel 0x0022 075 045 040 Old_age Always - 25 (Min/Max 16/26)
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 117
193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 591
194 Temperature_Celsius 0x0022 025 040 000 Old_age Always - 25 (0 10 0 0 0)
195 Hardware_ECC_Recovered 0x001a 081 064 000 Old_age Always - 131301136
197 Current_Pending_Sector 0x0012 096 096 000 Old_age Always - 2112
198 Offline_Uncorrectable 0x0010 096 096 000 Old_age Offline - 2112
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0
200 Pressure_Limit 0x0023 100 100 001 Pre-fail Always - 0
240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 4663 (62 4 0)
241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 75168824178
242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 92030427365

SMART Error Log Version: 1
ATA Error Count: 1
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 1 occurred at disk power-on lifetime: 4696 hours (195 days + 16 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
-- -- -- -- -- -- --
40 51 00 ff ff ff 0f Error: WP at LBA = 0x0fffffff = 268435455

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
61 00 08 ff ff ff 4f 00 41d+04:43:53.751 WRITE FPDMA QUEUED
61 00 08 ff ff ff 4f 00 41d+04:43:53.751 WRITE FPDMA QUEUED
61 00 08 ff ff ff 4f 00 41d+04:43:53.751 WRITE FPDMA QUEUED
61 00 18 ff ff ff 4f 00 41d+04:43:53.741 WRITE FPDMA QUEUED
61 00 08 ff ff ff 4f 00 41d+04:43:53.741 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: read failure 60% 4579 -
# 2 Extended offline Completed: read failure 60% 4296 -
# 3 Short offline Completed without error 00% 4261 -
# 4 Extended offline Completed without error 00% 2344 -
# 5 Short offline Completed without error 00% 2302 -
# 6 Extended offline Interrupted (host reset) 00% 1668 -
# 7 Short offline Completed without error 00% 1659 -
# 8 Extended offline Interrupted (host reset) 00% 1250 -
# 9 Short offline Completed without error 00% 1225 -
#10 Short offline Completed without error 00% 1225 -
#11 Extended offline Completed without error 00% 627 -
#12 Short offline Completed without error 00% 593 -
#13 Extended offline Aborted by host 90% 78 -
#14 Short offline Completed without error 00% 1 -

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.
Click to expand...

I currently have a scrub performing on the pool, but the current zpool status is:
root@mainnas:~ # zpool status Volume
pool: Volume
state: ONLINE
status: One or more devices has experienced an unrecoverable error. An
attempt was made to correct the error. Applications are unaffected.
action: Determine if the device needs to be replaced, and clear the errors
using 'zpool clear' or replace the device with 'zpool replace'.
see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-9P
scan: scrub in progress since Sat Aug 20 16:33:51 2022
10.2T scanned at 1.21G/s, 9.49T issued at 1.12G/s, 50.2T total
0B repaired, 18.91% done, 10:18:15 to go
config:

NAME STATE READ WRITE CKSUM
Volume ONLINE 0 0 0
raidz2-0 ONLINE 0 0 0
gptid/f81a58ad-530a-11eb-a2fa-002590f0cf92 ONLINE 0 0 0
gptid/5923e69a-5361-11eb-a2fa-002590f0cf92 ONLINE 0 0 0
gptid/ef4c370b-53b6-11eb-a2fa-002590f0cf92 ONLINE 0 0 0
gptid/f6a4b5f8-5403-11eb-a2fa-002590f0cf92 ONLINE 1 0 0
gptid/d7d639dd-5267-11eb-a2fa-002590f0cf92 ONLINE 0 0 0
gptid/79beb246-52bb-11eb-a2fa-002590f0cf92 ONLINE 0 0 0
raidz2-1 ONLINE 0 0 0
gptid/c30cdc67-55b2-11e7-8f32-002590f0cf92 ONLINE 0 0 0
gptid/0809c059-56cd-11e7-8a5c-002590f0cf92 ONLINE 0 0 0
gptid/71e5b94d-5667-11e7-a11e-002590f0cf92 ONLINE 0 0 0
gptid/003cde3e-47ff-11e7-8632-002590f0cf92 ONLINE 0 0 0
gptid/da4fde72-572b-11e7-88f6-002590f0cf92 ONLINE 0 0 0
gptid/d0eb580c-5803-11e7-adb2-002590f0cf92 ONLINE 0 0 0

errors: No known data errors
Click to expand...

The harddrive is still under the 3 year warranty for it, would you consider this harddrive failing enough to be covered under warranty, despite the PASS on the overall SMART health test ?
 
ChrisRJ

ChrisRJ

Wizard
Joined
Oct 23, 2020
Messages
1,919
I don't know how Seagate handles warranty for those drives. For my Exos 16 TB drives I have had 3 replacements under warranty so far. I honestly don't remember what exactly had been reported as error from SMART and/or ZFS. So I just triggered the RMA process and sent the drive in. Replacement came after 2 business days without any question.

Irrespective of the warranty situation, I would recommend to get a new drive asap and replace the faulty one with it. A spare drive is always a good idea and this way you get peace of mind.
 
Etorix

Etorix

Wizard
Joined
Dec 30, 2020
Messages
2,134
It didn't pass the last extended SMART tests, and has quite high numbers of reallocated and pending sectors—any non-zero value here should be a clear-cut case for return. Definitely replace and RMA.
 
C

craigdt

Explorer
Joined
Mar 10, 2014
Messages
74
ChrisRJ said:
I don't know how Seagate handles warranty for those drives. For my Exos 16 TB drives I have had 3 replacements under warranty so far. I honestly don't remember what exactly had been reported as error from SMART and/or ZFS. So I just triggered the RMA process and sent the drive in. Replacement came after 2 business days without any question.

Irrespective of the warranty situation, I would recommend to get a new drive asap and replace the faulty one with it. A spare drive is always a good idea and this way you get peace of mind.
Click to expand...
Etorix said:
It didn't pass the last extended SMART tests, and has quite high numbers of reallocated and pending sectors—any non-zero value here should be a clear-cut case for return. Definitely replace and RMA.
Click to expand...
Thanks guys,

I've ordered a new drive to replace it, should be available tomorrow to pick up so I will swap it out then and send the faulty drive back to be replaced which will become a spare.

The pool scrub finished and it faulted the hdd, too many errors.

Looking at smart report now, there are significant errors being reported:
smartctl 7.2 2020-12-30 r5155 [FreeBSD 12.2-RELEASE-p14 amd64] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family: Seagate IronWolf
Device Model: ST10000VN0008-2JJ101
Serial Number: ZL00ME5V
LU WWN Device Id: 5 000c50 0c6ad1fd4
Firmware Version: SC60
User Capacity: 10,000,831,348,736 bytes [10.0 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 7200 rpm
Form Factor: 3.5 inches
Device is: In smartctl database [for details use: -P show]
ATA Version is: ACS-4 (minor revision not indicated)
SATA Version is: SATA 3.3, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Sun Aug 21 13:52:48 2022 AEST
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: ( 118) The previous self-test completed having
the read element of the test failed.
Total time to complete Offline
data collection: ( 567) 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: ( 971) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x50bd) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 068 064 044 Pre-fail Always - 123319340
3 Spin_Up_Time 0x0003 087 087 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 122
5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 168
7 Seek_Error_Rate 0x000f 084 060 045 Pre-fail Always - 246009684
9 Power_On_Hours 0x0032 095 095 000 Old_age Always - 4755
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 122
18 Head_Health 0x000b 100 100 050 Pre-fail Always - 0
187 Reported_Uncorrect 0x0032 094 094 000 Old_age Always - 6
188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0
190 Airflow_Temperature_Cel 0x0022 079 045 040 Old_age Always - 21 (Min/Max 16/26)
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 117
193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 669
194 Temperature_Celsius 0x0022 021 040 000 Old_age Always - 21 (0 10 0 0 0)
195 Hardware_ECC_Recovered 0x001a 081 064 000 Old_age Always - 123319340
197 Current_Pending_Sector 0x0012 096 096 000 Old_age Always - 2128
198 Offline_Uncorrectable 0x0010 096 096 000 Old_age Offline - 2128
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0
200 Pressure_Limit 0x0023 100 100 001 Pre-fail Always - 0
240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 4669 (249 95 0)
241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 75175080226
242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 94459067577

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: 4741 hours (197 days + 13 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
-- -- -- -- -- -- --
40 51 00 ff ff ff 0f Error: WP at LBA = 0x0fffffff = 268435455

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
61 00 20 ff ff ff 4f 00 43d+02:23:33.355 WRITE FPDMA QUEUED
61 00 40 ff ff ff 4f 00 43d+02:23:27.562 WRITE FPDMA QUEUED
61 00 10 90 02 40 40 00 43d+02:23:27.559 WRITE FPDMA QUEUED
61 00 10 ff ff ff 4f 00 43d+02:23:27.542 WRITE FPDMA QUEUED
61 00 10 ff ff ff 4f 00 43d+02:23:27.505 WRITE FPDMA QUEUED

Error 5 occurred at disk power-on lifetime: 4741 hours (197 days + 13 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
-- -- -- -- -- -- --
40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 10 ff ff ff 4f 00 43d+02:23:22.130 READ FPDMA QUEUED
60 00 10 ff ff ff 4f 00 43d+02:23:22.130 READ FPDMA QUEUED
60 00 10 90 02 40 40 00 43d+02:23:22.130 READ FPDMA QUEUED
61 00 28 ff ff ff 4f 00 43d+02:23:22.088 WRITE FPDMA QUEUED
60 00 d0 ff ff ff 4f 00 43d+02:23:20.421 READ FPDMA QUEUED

Error 4 occurred at disk power-on lifetime: 4741 hours (197 days + 13 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
-- -- -- -- -- -- --
40 51 00 ff ff ff 0f Error: WP at LBA = 0x0fffffff = 268435455

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
61 00 20 ff ff ff 4f 00 43d+02:23:13.374 WRITE FPDMA QUEUED
60 00 d0 ff ff ff 4f 00 43d+02:23:13.374 READ FPDMA QUEUED
60 00 00 ff ff ff 4f 00 43d+02:23:13.374 READ FPDMA QUEUED
60 00 00 ff ff ff 4f 00 43d+02:23:13.374 READ FPDMA QUEUED
60 00 00 ff ff ff 4f 00 43d+02:23:13.374 READ FPDMA QUEUED

Error 3 occurred at disk power-on lifetime: 4741 hours (197 days + 13 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
-- -- -- -- -- -- --
40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 d0 ff ff ff 4f 00 43d+02:23:06.298 READ FPDMA QUEUED
60 00 00 ff ff ff 4f 00 43d+02:23:06.298 READ FPDMA QUEUED
60 00 00 ff ff ff 4f 00 43d+02:23:06.298 READ FPDMA QUEUED
60 00 00 ff ff ff 4f 00 43d+02:23:06.298 READ FPDMA QUEUED
60 00 00 ff ff ff 4f 00 43d+02:23:06.298 READ FPDMA QUEUED

Error 2 occurred at disk power-on lifetime: 4741 hours (197 days + 13 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
-- -- -- -- -- -- --
40 51 00 ff ff ff 0f Error: WP at LBA = 0x0fffffff = 268435455

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
61 00 20 ff ff ff 4f 00 43d+02:07:53.288 WRITE FPDMA QUEUED
60 00 00 ff ff ff 4f 00 43d+02:07:52.643 READ FPDMA QUEUED
60 00 00 ff ff ff 4f 00 43d+02:07:52.643 READ FPDMA QUEUED
60 00 00 ff ff ff 4f 00 43d+02:07:52.643 READ FPDMA QUEUED
60 00 00 ff ff ff 4f 00 43d+02:07:52.643 READ 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: read failure 60% 4579 -
# 2 Extended offline Completed: read failure 60% 4296 -
# 3 Short offline Completed without error 00% 4261 -
# 4 Extended offline Completed without error 00% 2344 -
# 5 Short offline Completed without error 00% 2302 -
# 6 Extended offline Interrupted (host reset) 00% 1668 -
# 7 Short offline Completed without error 00% 1659 -
# 8 Extended offline Interrupted (host reset) 00% 1250 -
# 9 Short offline Completed without error 00% 1225 -
#10 Short offline Completed without error 00% 1225 -
#11 Extended offline Completed without error 00% 627 -
#12 Short offline Completed without error 00% 593 -
#13 Extended offline Aborted by host 90% 78 -
#14 Short offline Completed without error 00% 1 -

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.
Click to expand...

I was reading that these same errors can also be caused by fault power or data cables as well, but then if that was the case, I would most likely be having an issue with more than one drive as its in a hot swap case that uses one cable for 4 drives..

Still I guess the errors will show their ugly head when I swap a new drive in if it is that... we shall see...

Glad I set my vdevs up as zraid2 and I have a full backup :smile:
 
Etorix

Etorix

Wizard
Joined
Dec 30, 2020
Messages
2,134
craigdt said:
I was reading that these same errors can also be caused by fault power or data cables as well, but then if that was the case, I would most likely be having an issue with more than one drive as its in a hot swap case that uses one cable for 4 drives..
Click to expand...
UDMA_CRC errors could be due to cables. Pending/Uncorrectable/Reallocated Sectors are hardware failures of the disk platters.

craigdt said:
Glad I set my vdevs up as zraid2 and I have a full backup :smile:
Click to expand...
Good points here!
 
You must log in or register to reply here.

Similar threads

R
zpool status READ errors
Replies
3
Views
4K
resill
R
L
"Critical error - ata2 error count increased from 0 to 1"
Replies
2
Views
766
Louis_Cyphre
L
2dfx
Dead HDD in ZFS pool...just making sure I have the procedure right...
Replies
1
Views
849
Samuel Tai
Samuel Tai
M
SOLVED Error "Device: /dev/ada0, Self-Test Log error count increased from 1 to 2."
Replies
3
Views
2K
Mat_Dum
M
H
Suddenly ATA error Count increast
Replies
2
Views
973
hardwarejunky009
H
Top