Viper780
Er ist tot, Jim!
|
Mein NAS hat mir heute ein paar sehr verzweifelte Mails geschickt. Fehlermeldung: Device: /dev/ada4, 1 Currently unreadable (pending) sectors
ganze Mail: Device info:
TOSHIBA MG09ACA18TE, S/N:72********, WWN:5-000039-*******, FW:0105, 18.0 TB
For details see host's SYSLOG.
You can also use the smartctl utility for further investigation.
No additional messages about this problem will be sent. smartctl 7.3 2022-02-28 r5338 [FreeBSD 13.2-RELEASE-p8 amd64] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, [url]www.smartmontools.org[/url]
=== START OF INFORMATION SECTION ===
Model Family: Toshiba MG09ACA... Enterprise Capacity HDD
Device Model: TOSHIBA MG09ACA18TE
Serial Number: 72********
LU WWN Device Id: 5 000039 *******
Firmware Version: 0105
User Capacity: 18,000,207,937,536 bytes [18.0 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 7200 rpm
Form Factor: 3.5 inches
Device is: In smartctl database 7.3/5319
ATA Version is: ACS-4 T13/BSR INCITS 529 revision 5
SATA Version is: SATA 3.3, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Wed Apr 3 15:38:28 2024 CEST
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: (0x84) Offline data collection activity
was suspended by an interrupting command from host.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 120) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: (1484) minutes.
SCT capabilities: (0x003d) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0
2 Throughput_Performance 0x0005 100 100 050 Pre-fail Offline - 0
3 Spin_Up_Time 0x0027 100 100 001 Pre-fail Always - 8508
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 5184
5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 30
7 Seek_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0
8 Seek_Time_Performance 0x0005 100 100 050 Pre-fail Offline - 0
9 Power_On_Hours 0x0032 082 082 000 Old_age Always - 7398
10 Spin_Retry_Count 0x0033 100 100 030 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 284
23 Helium_Condition_Lower 0x0023 100 100 075 Pre-fail Always - 0
24 Helium_Condition_Upper 0x0023 100 100 075 Pre-fail Always - 0
27 MAMR_Health_Monitor 0x0023 100 100 030 Pre-fail Always - 525918
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 184
193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 5188
194 Temperature_Celsius 0x0022 100 100 000 Old_age Always - 42 (Min/Max 17/45)
196 Reallocated_Event_Count 0x0033 100 100 010 Pre-fail Always - 17
197 Current_Pending_Sector 0x0032 100 100 000 Old_age Always - 1
198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0
220 Disk_Shift 0x0002 100 100 000 Old_age Always - 102891523
222 Loaded_Hours 0x0032 095 095 000 Old_age Always - 2390
223 Load_Retry_Count 0x0032 100 100 000 Old_age Always - 0
224 Load_Friction 0x0022 100 100 000 Old_age Always - 0
226 Load-in_Time 0x0026 100 100 000 Old_age Always - 646
240 Head_Flying_Hours 0x0001 100 100 001 Pre-fail Offline - 0
241 Total_LBAs_Written 0x0032 100 100 000 Old_age Always - 63676561537
242 Total_LBAs_Read 0x0032 100 100 000 Old_age Always - 594034263254
SMART Error Log Version: 1
ATA Error Count: 15 (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 15 occurred at disk power-on lifetime: 7398 hours (308 days + 6 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 43 c0 88 3a c8 40 Error: UNC at LBA = 0x00c83a88 = 13122184
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 40 28 a0 9c de 40 00 1d+17:06:05.249 READ FPDMA QUEUED
60 c0 20 e0 9b de 40 00 1d+17:06:05.249 READ FPDMA QUEUED
60 80 18 60 94 de 40 00 1d+17:06:05.249 READ FPDMA QUEUED
60 40 10 20 91 de 40 00 1d+17:06:05.249 READ FPDMA QUEUED
60 40 08 e0 90 de 40 00 1d+17:06:05.249 READ FPDMA QUEUED
Error 14 occurred at disk power-on lifetime: 7398 hours (308 days + 6 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 43 38 88 3a c8 40 Error: UNC at LBA = 0x00c83a88 = 13122184
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 40 b0 a0 9c de 40 00 1d+17:06:02.098 READ FPDMA QUEUED
60 c0 a8 e0 9b de 40 00 1d+17:06:02.098 READ FPDMA QUEUED
60 80 a0 60 94 de 40 00 1d+17:06:02.098 READ FPDMA QUEUED
60 40 98 20 91 de 40 00 1d+17:06:02.098 READ FPDMA QUEUED
60 40 90 e0 90 de 40 00 1d+17:06:02.098 READ FPDMA QUEUED
Error 13 occurred at disk power-on lifetime: 7398 hours (308 days + 6 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 43 a8 88 3a c8 40 Error: UNC at LBA = 0x00c83a88 = 13122184
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 40 28 a0 9c de 40 00 1d+17:05:59.284 READ FPDMA QUEUED
60 c0 20 e0 9b de 40 00 1d+17:05:58.924 READ FPDMA QUEUED
60 80 18 60 94 de 40 00 1d+17:05:58.924 READ FPDMA QUEUED
60 40 10 20 91 de 40 00 1d+17:05:58.924 READ FPDMA QUEUED
60 40 08 e0 90 de 40 00 1d+17:05:58.924 READ FPDMA QUEUED
Error 12 occurred at disk power-on lifetime: 7398 hours (308 days + 6 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 43 18 88 3a c8 40 Error: UNC at LBA = 0x00c83a88 = 13122184
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 c0 98 e0 9b de 40 00 1d+17:05:56.081 READ FPDMA QUEUED
60 80 90 60 94 de 40 00 1d+17:05:55.696 READ FPDMA QUEUED
60 40 88 20 91 de 40 00 1d+17:05:55.696 READ FPDMA QUEUED
60 40 80 e0 90 de 40 00 1d+17:05:55.696 READ FPDMA QUEUED
60 40 78 a0 90 de 40 00 1d+17:05:55.696 READ FPDMA QUEUED
Error 11 occurred at disk power-on lifetime: 7398 hours (308 days + 6 hours)
When the command that caused the error occurred, the device was in standby mode.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 43 c8 88 3a c8 40 Error: UNC at LBA = 0x00c83a88 = 13122184
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 80 08 60 94 de 40 00 1d+17:05:55.001 READ FPDMA QUEUED
60 40 00 20 91 de 40 00 1d+17:05:52.853 READ FPDMA QUEUED
60 40 f8 e0 90 de 40 00 1d+17:05:52.852 READ FPDMA QUEUED
60 40 f0 a0 90 de 40 00 1d+17:05:52.844 READ FPDMA QUEUED
60 40 e8 60 90 de 40 00 1d+17:05:52.840 READ FPDMA QUEUED
SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]
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.
Muss ich mir jetzt eine neue HDD kaufen oder kanns auch an was anderem liegen?
|
Rogaahl
Super Moderatorinterrupt
|
Ich würde sagen, ja. 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 30
196 Reallocated_Event_Count 0x0033 100 100 010 Pre-fail Always - 17
Es kann bereits Datenkorruption vorhanden sein!
|
Jedimaster
Here to stay
|
Yep, die HDD ist nicht mehr vertrauenswürdig.
|
Viper780
Er ist tot, Jim!
|
Es kann bereits Datenkorruption vorhanden sein! Mit RaidZ1 unwahrscheinlich. Vielen Dank für euer Feedback und habs leider befürchtet. Na dann eine 18TB HDD kaufen und RMA anstoßen
|
Jedimaster
Here to stay
|
Hmmm ich bin jetzt nicht wirklich Experte bezüglich ZFS, aber die mögliche Korruption liegt hier ein Level unter dem Dateisystem.
'Reallocated Sector Count' bedeutet das HEX 30 - also so um die 45 Sektoren als 'Defekt' markiert wurden (in HEX 17, also 23 Schreib/Lesevorgängen) weil sie Schreib/Lesefehler hatten. Es wurden also Daten auf die 'Reserveblöcke' kopiert. Dies kann potentiell zu 100.0% funktionieren, kann aber auch bereits das eine oder andere umgefallene Bit beinhalten.
Wie groß die Auswirkung dann bei ZFS ist wie gesagt kann ich nicht feststellen, bei einem klassischen Raid-1 würde das Raid feststellen das die Platte nicht synchron ist und das Raid würde 'degraded' ausspucken - und ein Rebuild angestoßen - und - wie schon öfters gesehen dies solange wiederholen bis die defekte HDD gar nicht mehr ansprechbar ist.
Wenn die NAS grad ein Mail geschickt hat ist es offenbar noch nicht so 'Dramatisch', aber die Tage/Stunden/Minuten der Platte sind jedenfalls gezählt.
|
Philipp
Here to stay
|
aber die Tage/Stunden/Minuten der Platte sind jedenfalls gezählt. Es kann durchaus sein, dass die Platte auch noch in 2-3 Jahren funktioniert. Wenn man so eine Platte nicht tauschen möchte oder kann, sollte man allerdings die Reallocated_Sector_Ct im Auge behalten. Wenn dieser Wert weiter nach oben geht, dürfte ein Ausfall sehr wahrscheinlich werden.
|
Viper780
Er ist tot, Jim!
|
RaidZ-1 entspricht grob einem Raid 5 und laut Info von ZFS scheinen die Fehler korrigiert worden zu sein.
2,6MB an Daten waren betroffen.
|
Jedimaster
Here to stay
|
Wie gesagt, bin kein ZFS-Experte  Ich wollts nur anmerken das das Problem ein Level darunter angesiedelt ist und etwas Information weitergeben wieso man die Platte nicht weiter verwenden sollte 'solangs noch geht'
|
Anmeldung