S.M.A.R.T Error? ja oder nein

|RaBtEr|

Lieutenant
Registriert
März 2008
Beiträge
651
Hallo

Ich nutze nas4free auf meinem NAS.
Die Festplatten sind schon relativ alt (ca. 5-8Jahre) und ich weiß, dass ich in naher Zukunft neue brauche...
Muss ich mich jetzt allerdings beeilen?

Folgende Email habe ich von meinem NAS erhalten. Ich kann leider nicht so viel damit anfangen. Für ein geübtes Auge sind es vielleicht nur ein paar Sekunden.

Betreff: SMART error (CurrentPendingSector) detected on host: nas4free

This message was generated by the smartd daemon running on:

host name: nas4free
DNS domain: local

The following warning/error was logged by the smartd daemon:

Device: /dev/ada2, 64 Currently unreadable (pending) sectors

Device info:
ST3000DM001-9YN166, S/N:W1F17W3Z, WWN:5-000c50-0538564fc, FW:CC4B, 3.00 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 6.5 2016-05-07 r4318 [FreeBSD 10.3-RELEASE-p7 amd64] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family: Seagate Barracuda 7200.14 (AF)
Device Model: ST3000DM001-9YN166
Serial Number: W1F17W3Z
LU WWN Device Id: 5 000c50 0538564fc
Firmware Version: CC4B
User Capacity: 3,000,592,982,016 bytes [3.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: 3.0 Gb/s)
Local Time is: Fri May 12 16:13:03 2017 UTC

==> WARNING: A firmware update for this drive may be available, see the following Seagate web pages:
http://knowledge.seagate.com/articles/en_US/FAQ/207931en
http://knowledge.seagate.com/articles/en_US/FAQ/223651en

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: ( 592) seconds.
Offline data collection
capabilities: (0x73) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
No 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: ( 345) 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 FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 118 099 006 Pre-fail Always - 172880336
3 Spin_Up_Time 0x0003 092 092 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 989
5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0
7 Seek_Error_Rate 0x000f 082 060 030 Pre-fail Always - 175604466
9 Power_On_Hours 0x0032 059 059 000 Old_age Always - 36685
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 43
183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0
184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0
187 Reported_Uncorrect 0x0032 001 001 000 Old_age Always - 115
188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 0 0
189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0
190 Airflow_Temperature_Cel 0x0022 067 061 045 Old_age Always - 33 (Min/Max 17/38)
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 - 33
193 Load_Cycle_Count 0x0032 051 051 000 Old_age Always - 99230
194 Temperature_Celsius 0x0022 033 040 000 Old_age Always - 33 (0 17 0 0 0)
197 Current_Pending_Sector 0x0012 100 098 000 Old_age Always - 64
198 Offline_Uncorrectable 0x0010 100 098 000 Old_age Offline - 64
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0
240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 5463h+09m+21.254s
241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 62546925726830
242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 117115010897563

SMART Error Log Version: 1
ATA Error Count: 115 (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 115 occurred at disk power-on lifetime: 33663 hours (1402 days + 15 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 00 ff ff ff 4f 00 1d+11:11:14.188 READ FPDMA QUEUED
60 00 00 ff ff ff 4f 00 1d+11:11:14.188 READ FPDMA QUEUED
2f 00 01 10 00 00 00 00 1d+11:11:14.088 READ LOG EXT
60 00 00 ff ff ff 4f 00 1d+11:11:11.296 READ FPDMA QUEUED
60 00 00 ff ff ff 4f 00 1d+11:11:11.296 READ FPDMA QUEUED

Error 114 occurred at disk power-on lifetime: 33663 hours (1402 days + 15 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 00 ff ff ff 4f 00 1d+11:11:11.296 READ FPDMA QUEUED
60 00 00 ff ff ff 4f 00 1d+11:11:11.296 READ FPDMA QUEUED
2f 00 01 10 00 00 00 00 1d+11:11:11.196 READ LOG EXT
60 00 00 ff ff ff 4f 00 1d+11:11:08.387 READ FPDMA QUEUED
60 00 00 ff ff ff 4f 00 1d+11:11:08.387 READ FPDMA QUEUED

Error 113 occurred at disk power-on lifetime: 33663 hours (1402 days + 15 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 00 ff ff ff 4f 00 1d+11:11:08.387 READ FPDMA QUEUED
60 00 00 ff ff ff 4f 00 1d+11:11:08.387 READ FPDMA QUEUED
2f 00 01 10 00 00 00 00 1d+11:11:08.287 READ LOG EXT
60 00 00 ff ff ff 4f 00 1d+11:11:05.484 READ FPDMA QUEUED
60 00 00 ff ff ff 4f 00 1d+11:11:05.484 READ FPDMA QUEUED

Error 112 occurred at disk power-on lifetime: 33663 hours (1402 days + 15 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 00 ff ff ff 4f 00 1d+11:11:05.484 READ FPDMA QUEUED
60 00 00 ff ff ff 4f 00 1d+11:11:05.484 READ FPDMA QUEUED
2f 00 01 10 00 00 00 00 1d+11:11:05.033 READ LOG EXT
61 00 00 ff ff ff 4f 00 1d+11:11:02.163 WRITE FPDMA QUEUED
61 00 10 ff ff ff 4f 00 1d+11:11:02.163 WRITE FPDMA QUEUED

Error 111 occurred at disk power-on lifetime: 33663 hours (1402 days + 15 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 00 ff ff ff 4f 00 1d+11:11:02.163 WRITE FPDMA QUEUED
61 00 10 ff ff ff 4f 00 1d+11:11:02.163 WRITE FPDMA QUEUED
61 00 10 ff ff ff 4f 00 1d+11:11:02.161 WRITE FPDMA QUEUED
60 00 00 ff ff ff 4f 00 1d+11:11:02.152 READ FPDMA QUEUED
60 00 00 ff ff ff 4f 00 1d+11:11:02.150 READ FPDMA QUEUED

SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed without error 00% 36672 -
# 2 Short offline Completed without error 00% 36648 -
# 3 Short offline Completed without error 00% 36624 -
# 4 Short offline Completed without error 00% 36600 -
# 5 Short offline Completed without error 00% 36576 -
# 6 Short offline Completed without error 00% 36553 -
# 7 Short offline Completed without error 00% 36528 -
# 8 Short offline Completed without error 00% 36504 -
# 9 Short offline Completed without error 00% 36480 -
#10 Short offline Completed without error 00% 36456 -
#11 Short offline Completed without error 00% 36431 -
#12 Extended offline Completed without error 00% 36414 -
#13 Short offline Completed without error 00% 36407 -
#14 Short offline Completed without error 00% 36385 -
#15 Short offline Completed without error 00% 36359 -
#16 Short offline Completed without error 00% 36335 -
#17 Short offline Completed without error 00% 36311 -
#18 Short offline Completed without error 00% 36287 -
#19 Short offline Completed without error 00% 36263 -
#20 Short offline Completed without error 00% 36239 -
#21 Short offline Completed without error 00% 36217 -

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.
 
Hi laut dem Protokoll sind es 64 "schwebende Sektoren" die noch nicht remappt werden konnten

Gefahr ist im Verzug!

Wenn dir die Daten wichtig sind mache SOFORT ein Backup der wichtigen Sachen
 
Danke für die schnelle Info und einschätzung!

In dem NAS sind zwei Festplatten verbaut, welche beide die gleichen Daten enthalten (quasi RAID)
Sind beide Platten schon beschädigt oder nur eine?
Es dauert ja etwas bis die neuen Platten da sind...
 
Model Family: Seagate Barracuda 7200.14 (AF)
Device Model: ST3000DM001-9YN166
Serial Number: W1F17W3Z

Anhand der Seriennummer sollte das einfach sein :)
 
Für eine ST3000DM001 hat diese mit 36685 Power-On Hours sehr lange gehalten, denn diese HDDs sind nur für bis zu 2400 Power-On Hours im Jahr gemacht, die hätte so viele Stunden erst nach über 15 Jahren bei dem bestimmungsgemäßen Gebrauch erreicht. Nimm als Ersatz NAS oder Surveillance HDDs, also die WD Red oder Purple oder von Seagate die Ironwolf oder Skyhawk.
 
Holt schrieb:
...diese HDDs sind nur für bis zu 2400 Power-On Hours im Jahr gemacht, die hätte so viele Stunden erst nach über 15 Jahren bei dem bestimmungsgemäßen Gebrauch erreicht...

@ |RaBtEr|
Wir versuchen durch unsere Forenpräsenz verstärkt auf genau dieses Thema aufmerksam zu machen!
Vielen Nutzern ist überhaupt nicht bewusst, dass es für verschiedene Szenarien unterschiedlich gebaute Festplattentypen gibt.
Wie von Holt angesprochen, ist die BarraCuda von uns nicht als NAS-HDD empfohlen. Sie hat also in Deinem Fall schon eine wirklich beachtliche Lauf- und Lebenszeit hinter sich.

Auch auf die Gefahr hin uns in verschiedenen Threads zu wiederholen, hier noch einmal eine kleine Übersichtstabelle:

overview.jpg

Für Deinen Zweck würden wir also in jedem Fall zu einer NAS-Platte (bei Seagate IronWolf) raten!
 
Zurück
Oben