Frage zu SMART-Werten

Zeiss

BIOS-Overclocker(in)
Moin zusammen,

ich habe mal wieder mein CrystalDiskInfo angeschmissen und etwas (für mich) beunruhigendes gesehen:

st3000dm001-1er166-png.1017772


Was heißt es jetzt? Ist sie langsam am Abnippeln?
 

Anhänge

  • ST3000DM001-1ER166.png
    ST3000DM001-1ER166.png
    122,3 KB · Aufrufe: 157
Es gibt schwebende und unkorrigierbare Sektoren. Das bedeutet in aller Regel nicht, dass die Platte jetzt morgen tot umfällt, spätestens jetzt sollte man aber seine Daten backuppen und langsam über einen Ersatz der Platte nachdenken.
 
Die 8 Sektoren hätte ich einfach beobachtet und gut wär's aber mir fällt eher noch BB negativ auf.
Wenn sich ein Aktueller Wert Richtung Grenzwert bewegt, ist das nicht so gut und wenn die Fehlerkorrektur nicht klappt, sicherlich auch nicht.


C6 hat bei denen AFAIK immer den Wert von C5.
 
typisch seagate würd platte tauschen und auf keinen fall mehr diese serie von seagate kauffen die sind müll spreche aus erfahrung meine hat sich auch so verabschidet hatte gleichen smartwerte und paar wochen später war die platte weg nicht mehr erkannt tod war sie
 
Die 8 Sektoren hätte ich einfach beobachtet und gut wär's aber mir fällt eher noch BB negativ auf.
Wenn sich ein Aktueller Wert Richtung Grenzwert bewegt, ist das nicht so gut und wenn die Fehlerkorrektur nicht klappt, sicherlich auch nicht.

Du meinst den einen unkorrigierbaren Fehler?

Ka wie brauchbar die Informationen von CrystalDiskInfo bzgl. Seagate Platten sind, aber generell sollte bekannt sein das die Smartwerte von Seagate anders dargestellt werden/bzw in der Regel unbrauchbar (smartmontools) sind. Am besten Herstellertool aka (https://www.seagate.com/de/de/support/downloads/seatools/) drueber laufen lassen.

Seagate SER, RRER & HEC

Habe ich getan, SeaTools melden alles grün, SMART-Test grün und auch ein erweiterter Test auch, hmmm.

typisch seagate würd platte tauschen und auf keinen fall mehr diese serie von seagate kauffen die sind müll spreche aus erfahrung meine hat sich auch so verabschidet hatte gleichen smartwerte und paar wochen später war die platte weg nicht mehr erkannt tod war sie

Ich nutze seit 22 Jahren fast nur Seagate Platten und keine Probleme bis jetzt gehabt...
 
Darum geht es aber nicht!

@Topic: Habe gerade einen "einfachen Langzeittest" gestartet, mal schauen.
 
Check mal mit Gsmart control - GSmartControl :: Home & News nach, zu welchen Ergebnis der InterneHelathcheck (extended) kommt.
(Reiter - Self_tests ---> Test Type --> Extended Self-Test)
Schau dir auch noch die anderen Reiter durch wie zb Error Log, ob dort etwas abgelegt wurde.
 
8 Sektoren können nicht gelesen werden (ID-C5), die wurden bei Plattenselbsttests gefunden (ID-C6), es gab 3 Schreibfehler (ID-BD) da waren die Schreibköpfe ausserhalb ihrer vorgesehenen Position. 391 mal konnte die Fehlerkorrektur nicht korrigieren (ID-BB), da aber keine Lesefehler verzeichnet sind (erste 16 Bit/4 Stellen des 48 Bit/12 Stelligen Rohwertes von ID-01) konnte in einem/mehreren wiederholten Versuch doch noch gelesen werden.

Solange die Daten gesichert sind kann man gelassen der Dinge harren die noch folgen mögen.
 
Hmm, ist wohl wirklich hin:

attachment.php

Was gibt gsmart control aus?
Wenn ein Fehler diagnostiziert wird, wird das abgespeichert.

Was man machen kann, Daten backupen und die Festplatte einfach formatieren. Danach diese vollschreiben lassen mit Daten und den Vorgang wiederholen. Schauen wie sich die Smartwerte verhalten (Schwebende Sektoren & Wiederzugewiesene Sektoren)

Ich nehme WD.
Alle die bei uns abgeraucht sind waren Seagate (OEM).

Es gibts Serien vom Hersteller X die anfällig für Ausfälle sind. Klassiker Seagate 3tb Baracuda - Die 4TB sind jedoch recht Ok, haben zwei davon im Betrieb und nach knapp 5k Stunden noch keine Probleme erkannt/aufgefallen.
Mein absoluter Dauerläufer ist eine alte Hitachi - 2Tb mit 25k Stunden und 1a Smartwerten. Bei den Wds habe ich bis jetzt nur postives - bei den Goldenen erlebt.Die Blues sind mir bis jetzt alles gestorben - technisches Ko weil ihnen die Reservesektoren ausgegenagen sind
Festplatten sind einfach verschleißteile.....
 
Zuletzt bearbeitet:
Die ausgefallenen Seagate waren 2,5" Platten.

Wobei die Reservesektoren nur weniger werden, wenn es Wiederzuweisungsereignisse gibt. Meine WD Blue im 2. PC hat schon 18k Stunden und keinerlei Wiederzuweisungen.
Wie viele Stunden die WD Black und Red im 1. PC haben, kan ich am Wochenende mal schauen.
 
@razzor1984: Habe Dir die Ausgabe vom gsmart angehängt.

smartctl 6.6 2017-11-05 r4594 [x86_64-w64-mingw32-win7-sp1] (sf-6.6-1)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family: Seagate Barracuda 7200.14 (AF)
Device Model: ST3000DM001-1ER166
Serial Number: W500AFMG
LU WWN Device Id: 5 000c50 07c5d154a
Firmware Version: CC25
User Capacity: 3.000.592.982.016 bytes [3,00 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-2, ACS-3 T13/2161-D revision 3b
SATA Version is: SATA 3.1, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is: Fri Nov 02 20:12:20 2018 MZ
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is: Unavailable
APM level is: 128 (minimum power consumption without standby)
Rd look-ahead is: Enabled
Write cache is: Enabled
DSN feature is: Unavailable
ATA Security is: Disabled, frozen [SEC2]

=== 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: ( 121) The previous self-test completed having
the read element of the test failed.
Total time to complete Offline
data collection: ( 89) 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: ( 329) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x1085) 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-- 104 093 006 - 76488906
3 Spin_Up_Time PO---- 095 093 000 - 0
4 Start_Stop_Count -O--CK 098 098 020 - 2586
5 Reallocated_Sector_Ct PO--CK 100 100 010 - 0
7 Seek_Error_Rate POSR-- 071 060 030 - 12665990
9 Power_On_Hours -O--CK 089 089 000 - 10170
10 Spin_Retry_Count PO--C- 100 100 097 - 0
12 Power_Cycle_Count -O--CK 099 099 020 - 1065
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 - 401
188 Command_Timeout -O--CK 100 099 000 - 0 0 1
189 High_Fly_Writes -O-RCK 097 097 000 - 3
190 Airflow_Temperature_Cel -O---K 075 056 045 - 25 (Min/Max 23/31)
191 G-Sense_Error_Rate -O--CK 100 100 000 - 0
192 Power-Off_Retract_Count -O--CK 100 100 000 - 6
193 Load_Cycle_Count -O--CK 073 073 000 - 54733
194 Temperature_Celsius -O---K 025 044 000 - 25 (0 16 0 0 0)
197 Current_Pending_Sector -O--C- 100 100 000 - 8
198 Offline_Uncorrectable ----C- 100 100 000 - 8
199 UDMA_CRC_Error_Count -OSRCK 200 200 000 - 0
240 Head_Flying_Hours ------ 100 253 000 - 4730h+52m+29.034s
241 Total_LBAs_Written ------ 100 253 000 - 15871909738
242 Total_LBAs_Read ------ 100 253 000 - 63045506895
||||||_ 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
0x30 GPL,SL R/O 9 IDENTIFY DEVICE data 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 129 Device vendor specific log
0xa9 GPL,SL VS 1 Device vendor specific log
0xab GPL VS 1 Device vendor specific log
0xb0 GPL VS 5176 Device vendor specific log
0xbe-0xbf GPL VS 65535 Device vendor specific log
0xc0 GPL,SL VS 1 Device vendor specific log
0xc1 GPL,SL VS 10 Device vendor specific log
0xc3 GPL,SL VS 8 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: 401 (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 401 [0] occurred at disk power-on lifetime: 10142 hours (422 days + 14 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 f5 59 28 78 00 00 Error: UNC at LBA = 0xf5592878 = 4116260984

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 00 80 00 00 f5 59 28 00 40 00 1d+19:51:14.049 READ FPDMA QUEUED
ef 00 90 00 03 00 00 00 00 00 00 00 00 1d+19:51:14.049 SET FEATURES [Disable SATA feature]
ef 00 02 00 00 00 00 00 00 00 00 00 00 1d+19:51:14.012 SET FEATURES [Enable write cache]
00 00 00 00 00 00 00 00 00 00 00 00 ff 1d+19:51:13.934 NOP [Abort queued commands]
60 00 00 00 80 00 00 f5 59 28 00 40 00 1d+19:51:10.347 READ FPDMA QUEUED

Error 400 [19] occurred at disk power-on lifetime: 10142 hours (422 days + 14 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 f5 59 28 78 00 00 Error: UNC at LBA = 0xf5592878 = 4116260984

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 00 80 00 00 f5 59 28 00 40 00 1d+19:51:10.347 READ FPDMA QUEUED
ef 00 90 00 03 00 00 00 00 00 00 00 00 1d+19:51:10.346 SET FEATURES [Disable SATA feature]
ef 00 02 00 00 00 00 00 00 00 00 00 00 1d+19:51:10.346 SET FEATURES [Enable write cache]
00 00 00 00 00 00 00 00 00 00 00 00 ff 1d+19:51:10.291 NOP [Abort queued commands]
60 00 00 00 80 00 00 f5 59 28 00 40 00 1d+19:51:06.715 READ FPDMA QUEUED

Error 399 [18] occurred at disk power-on lifetime: 10142 hours (422 days + 14 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 f5 59 28 78 00 00 Error: UNC at LBA = 0xf5592878 = 4116260984

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 00 80 00 00 f5 59 28 00 40 00 1d+19:51:06.715 READ FPDMA QUEUED
ef 00 90 00 03 00 00 00 00 00 00 00 00 1d+19:51:06.714 SET FEATURES [Disable SATA feature]
ef 00 02 00 00 00 00 00 00 00 00 00 00 1d+19:51:06.680 SET FEATURES [Enable write cache]
00 00 00 00 00 00 00 00 00 00 00 00 ff 1d+19:51:06.599 NOP [Abort queued commands]
60 00 00 00 80 00 00 f5 59 28 00 40 00 1d+19:51:03.014 READ FPDMA QUEUED

Error 398 [17] occurred at disk power-on lifetime: 10142 hours (422 days + 14 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 f5 59 28 78 00 00 Error: UNC at LBA = 0xf5592878 = 4116260984

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 00 80 00 00 f5 59 28 00 40 00 1d+19:51:03.014 READ FPDMA QUEUED
ef 00 90 00 03 00 00 00 00 00 00 00 00 1d+19:51:03.014 SET FEATURES [Disable SATA feature]
ef 00 02 00 00 00 00 00 00 00 00 00 00 1d+19:51:03.014 SET FEATURES [Enable write cache]
00 00 00 00 00 00 00 00 00 00 00 00 ff 1d+19:51:02.965 NOP [Abort queued commands]
60 00 00 00 80 00 00 f5 59 28 00 40 00 1d+19:50:59.405 READ FPDMA QUEUED

Error 397 [16] occurred at disk power-on lifetime: 10142 hours (422 days + 14 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 f5 59 28 78 00 00 Error: UNC at LBA = 0xf5592878 = 4116260984

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 00 80 00 00 f5 59 28 00 40 00 1d+19:50:59.405 READ FPDMA QUEUED
ef 00 90 00 03 00 00 00 00 00 00 00 00 1d+19:50:59.405 SET FEATURES [Disable SATA feature]
ef 00 02 00 00 00 00 00 00 00 00 00 00 1d+19:50:59.379 SET FEATURES [Enable write cache]
00 00 00 00 00 00 00 00 00 00 00 00 ff 1d+19:50:59.289 NOP [Abort queued commands]
60 00 00 00 80 00 00 f5 59 28 00 40 00 1d+19:50:55.713 READ FPDMA QUEUED

Error 396 [15] occurred at disk power-on lifetime: 10142 hours (422 days + 14 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 f5 59 28 78 00 00 Error: UNC at LBA = 0xf5592878 = 4116260984

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 00 80 00 00 f5 59 28 00 40 00 1d+19:50:55.713 READ FPDMA QUEUED
ef 00 90 00 03 00 00 00 00 00 00 00 00 1d+19:50:55.713 SET FEATURES [Disable SATA feature]
ef 00 02 00 00 00 00 00 00 00 00 00 00 1d+19:50:55.712 SET FEATURES [Enable write cache]
00 00 00 00 00 00 00 00 00 00 00 00 ff 1d+19:50:55.663 NOP [Abort queued commands]
60 00 00 00 80 00 00 f5 59 28 00 40 00 1d+19:50:52.078 READ FPDMA QUEUED

Error 395 [14] occurred at disk power-on lifetime: 10142 hours (422 days + 14 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 f5 59 28 78 00 00 Error: UNC at LBA = 0xf5592878 = 4116260984

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 00 80 00 00 f5 59 28 00 40 00 1d+19:50:52.078 READ FPDMA QUEUED
ef 00 90 00 03 00 00 00 00 00 00 00 00 1d+19:50:52.078 SET FEATURES [Disable SATA feature]
ef 00 02 00 00 00 00 00 00 00 00 00 00 1d+19:50:52.046 SET FEATURES [Enable write cache]
00 00 00 00 00 00 00 00 00 00 00 00 ff 1d+19:50:51.954 NOP [Abort queued commands]
60 00 00 00 80 00 00 f5 59 28 00 40 00 1d+19:50:48.396 READ FPDMA QUEUED

Error 394 [13] occurred at disk power-on lifetime: 10142 hours (422 days + 14 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 f5 59 28 78 00 00 Error: UNC at LBA = 0xf5592878 = 4116260984

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 00 80 00 00 f5 59 28 00 40 00 1d+19:50:48.396 READ FPDMA QUEUED
ef 00 90 00 03 00 00 00 00 00 00 00 00 1d+19:50:48.396 SET FEATURES [Disable SATA feature]
ef 00 02 00 00 00 00 00 00 00 00 00 00 1d+19:50:48.396 SET FEATURES [Enable write cache]
ef 00 02 00 00 00 00 00 00 00 00 00 00 1d+19:50:48.396 SET FEATURES [Enable write cache]
00 00 00 00 00 00 00 00 00 00 00 00 ff 1d+19:50:48.345 NOP [Abort queued commands]

Error 393 [12] occurred at disk power-on lifetime: 10142 hours (422 days + 14 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 f5 59 28 78 00 00 Error: UNC at LBA = 0xf5592878 = 4116260984

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 00 80 00 00 f5 59 28 00 40 00 1d+19:50:44.749 READ FPDMA QUEUED
ef 00 90 00 03 00 00 00 00 00 00 00 00 1d+19:50:44.749 SET FEATURES [Disable SATA feature]
ef 00 02 00 00 00 00 00 00 00 00 00 00 1d+19:50:44.749 SET FEATURES [Enable write cache]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 1d+19:50:44.714 IDENTIFY DEVICE
00 00 00 00 00 00 00 00 00 00 00 00 ff 1d+19:50:44.594 NOP [Abort queued commands]

Error 392 [11] occurred at disk power-on lifetime: 10142 hours (422 days + 14 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 f5 59 28 78 00 00 Error: UNC at LBA = 0xf5592878 = 4116260984

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 00 80 00 00 f5 23 58 00 40 00 1d+19:50:29.269 READ FPDMA QUEUED
60 00 00 00 80 00 00 f5 23 57 80 40 00 1d+19:50:29.262 READ FPDMA QUEUED
60 00 00 00 80 00 00 f5 23 57 00 40 00 1d+19:50:29.262 READ FPDMA QUEUED
60 00 00 00 80 00 00 f5 23 56 80 40 00 1d+19:50:29.261 READ FPDMA QUEUED
60 00 00 00 80 00 00 f5 23 56 00 40 00 1d+19:50:29.261 READ FPDMA QUEUED

Error 391 [10] occurred at disk power-on lifetime: 9069 hours (377 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 COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 f5 59 28 78 00 00 Error: UNC at LBA = 0xf5592878 = 4116260984

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 f5 59 4f 40 40 00 1d+03:33:54.420 READ FPDMA QUEUED
60 00 00 01 00 00 00 f5 59 4e 40 40 00 1d+03:33:54.420 READ FPDMA QUEUED
60 00 00 01 00 00 00 f5 59 4d 40 40 00 1d+03:33:54.420 READ FPDMA QUEUED
60 00 00 01 00 00 00 f5 59 4c 40 40 00 1d+03:33:54.420 READ FPDMA QUEUED
60 00 00 01 00 00 00 f5 59 4b 40 40 00 1d+03:33:54.420 READ FPDMA QUEUED

Error 390 [9] occurred at disk power-on lifetime: 9069 hours (377 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 COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 f5 59 28 78 00 00 Error: UNC at LBA = 0xf5592878 = 4116260984

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 f5 59 4f 40 40 00 1d+03:33:50.744 READ FPDMA QUEUED
60 00 00 01 00 00 00 f5 59 4e 40 40 00 1d+03:33:50.744 READ FPDMA QUEUED
60 00 00 01 00 00 00 f5 59 4d 40 40 00 1d+03:33:50.744 READ FPDMA QUEUED
60 00 00 01 00 00 00 f5 59 4c 40 40 00 1d+03:33:50.744 READ FPDMA QUEUED
60 00 00 01 00 00 00 f5 59 4b 40 40 00 1d+03:33:50.744 READ FPDMA QUEUED

Error 389 [8] occurred at disk power-on lifetime: 9069 hours (377 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 COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 f5 59 28 78 00 00 Error: UNC at LBA = 0xf5592878 = 4116260984

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 f5 59 4f 40 40 00 1d+03:33:47.016 READ FPDMA QUEUED
60 00 00 01 00 00 00 f5 59 4e 40 40 00 1d+03:33:47.016 READ FPDMA QUEUED
60 00 00 01 00 00 00 f5 59 4d 40 40 00 1d+03:33:47.016 READ FPDMA QUEUED
60 00 00 01 00 00 00 f5 59 4c 40 40 00 1d+03:33:47.016 READ FPDMA QUEUED
60 00 00 01 00 00 00 f5 59 4b 40 40 00 1d+03:33:47.016 READ FPDMA QUEUED

Error 388 [7] occurred at disk power-on lifetime: 9069 hours (377 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 COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 f5 59 28 78 00 00 Error: UNC at LBA = 0xf5592878 = 4116260984

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 f5 59 4f 40 40 00 1d+03:33:43.368 READ FPDMA QUEUED
60 00 00 01 00 00 00 f5 59 4e 40 40 00 1d+03:33:43.368 READ FPDMA QUEUED
60 00 00 01 00 00 00 f5 59 4d 40 40 00 1d+03:33:43.368 READ FPDMA QUEUED
60 00 00 01 00 00 00 f5 59 4c 40 40 00 1d+03:33:43.368 READ FPDMA QUEUED
60 00 00 01 00 00 00 f5 59 4b 40 40 00 1d+03:33:43.368 READ FPDMA QUEUED

Error 387 [6] occurred at disk power-on lifetime: 9069 hours (377 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 COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 f5 59 28 78 00 00 Error: UNC at LBA = 0xf5592878 = 4116260984

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 f5 59 4f 40 40 00 1d+03:33:39.651 READ FPDMA QUEUED
60 00 00 01 00 00 00 f5 59 4e 40 40 00 1d+03:33:39.651 READ FPDMA QUEUED
60 00 00 01 00 00 00 f5 59 4d 40 40 00 1d+03:33:39.651 READ FPDMA QUEUED
60 00 00 01 00 00 00 f5 59 4c 40 40 00 1d+03:33:39.651 READ FPDMA QUEUED
60 00 00 01 00 00 00 f5 59 4b 40 40 00 1d+03:33:39.651 READ FPDMA QUEUED

Error 386 [5] occurred at disk power-on lifetime: 9069 hours (377 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 COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 f5 59 28 78 00 00 Error: UNC at LBA = 0xf5592878 = 4116260984

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 f5 59 4f 40 40 00 1d+03:33:35.950 READ FPDMA QUEUED
60 00 00 01 00 00 00 f5 59 4e 40 40 00 1d+03:33:35.950 READ FPDMA QUEUED
60 00 00 01 00 00 00 f5 59 4d 40 40 00 1d+03:33:35.950 READ FPDMA QUEUED
60 00 00 01 00 00 00 f5 59 4c 40 40 00 1d+03:33:35.950 READ FPDMA QUEUED
60 00 00 01 00 00 00 f5 59 4b 40 40 00 1d+03:33:35.950 READ FPDMA QUEUED

Error 385 [4] occurred at disk power-on lifetime: 9069 hours (377 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 COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 f5 59 28 78 00 00 Error: UNC at LBA = 0xf5592878 = 4116260984

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 f5 59 4f 40 40 00 1d+03:33:32.242 READ FPDMA QUEUED
60 00 00 01 00 00 00 f5 59 4e 40 40 00 1d+03:33:32.242 READ FPDMA QUEUED
60 00 00 01 00 00 00 f5 59 4d 40 40 00 1d+03:33:32.242 READ FPDMA QUEUED
60 00 00 01 00 00 00 f5 59 4c 40 40 00 1d+03:33:32.242 READ FPDMA QUEUED
60 00 00 01 00 00 00 f5 59 4b 40 40 00 1d+03:33:32.242 READ FPDMA QUEUED

Error 384 [3] occurred at disk power-on lifetime: 9069 hours (377 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 COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 f5 59 28 78 00 00 Error: UNC at LBA = 0xf5592878 = 4116260984

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 f5 59 4f 40 40 00 1d+03:33:28.599 READ FPDMA QUEUED
60 00 00 01 00 00 00 f5 59 4e 40 40 00 1d+03:33:28.598 READ FPDMA QUEUED
60 00 00 01 00 00 00 f5 59 4d 40 40 00 1d+03:33:28.598 READ FPDMA QUEUED
60 00 00 01 00 00 00 f5 59 4c 40 40 00 1d+03:33:28.598 READ FPDMA QUEUED
60 00 00 01 00 00 00 f5 59 4b 40 40 00 1d+03:33:28.598 READ FPDMA QUEUED

Error 383 [2] occurred at disk power-on lifetime: 9069 hours (377 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 COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 f5 59 28 78 00 00 Error: UNC at LBA = 0xf5592878 = 4116260984

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 f5 59 4f 40 40 00 1d+03:33:24.910 READ FPDMA QUEUED
60 00 00 01 00 00 00 f5 59 4e 40 40 00 1d+03:33:24.910 READ FPDMA QUEUED
60 00 00 01 00 00 00 f5 59 4d 40 40 00 1d+03:33:24.910 READ FPDMA QUEUED
60 00 00 01 00 00 00 f5 59 4c 40 40 00 1d+03:33:24.910 READ FPDMA QUEUED
60 00 00 01 00 00 00 f5 59 4b 40 40 00 1d+03:33:24.910 READ FPDMA QUEUED

Error 382 [1] occurred at disk power-on lifetime: 9069 hours (377 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 COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 f5 59 28 78 00 00 Error: UNC at LBA = 0xf5592878 = 4116260984

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 00 40 00 00 f5 59 28 40 40 00 1d+03:33:21.258 READ FPDMA QUEUED
ef 00 90 00 03 00 00 00 00 00 00 00 00 1d+03:33:21.258 SET FEATURES [Disable SATA feature]
ef 00 02 00 00 00 00 00 00 00 00 00 00 1d+03:33:21.258 SET FEATURES [Enable write cache]
00 00 00 00 00 00 00 00 00 00 00 00 ff 1d+03:33:21.197 NOP [Abort queued commands]
60 00 00 00 40 00 00 f5 59 28 40 40 00 1d+03:33:17.604 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% 10170 4116260984
# 2 Short offline Completed without error 00% 10137 -

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)
SCT Support Level: 1
Device State: Active (0)
Current Temperature: 25 Celsius
Power Cycle Min/Max Temperature: 23/31 Celsius
Lifetime Min/Max Temperature: 16/44 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

SATA Phy Event Counters (GP Log 0x11)
ID Size Value Description
0x000a 2 21 Device-to-host register FISes sent due to a COMRESET
0x0001 2 0 Command failed due to ICRC error
0x0003 2 0 R_ERR response for device-to-host data FIS
0x0004 2 0 R_ERR response for host-to-device data FIS
0x0006 2 0 R_ERR response for device-to-host non-data FIS
0x0007 2 0 R_ERR response for host-to-device non-data FIS
 
Sehr schön, jetzt weist du das die letzten 20 Fehler (von 401 registrierten, also mittlerweile um 10 mehr) der Sektor 4116260984 war. Der ist wohl nicht nur für die Reported_Uncorrectables / unkorrigierbare Fehler sondern könnte auch für die 8 nicht lesbaren Sektoren verantwortlich sein (8 logische 512 Byte Sektoren = 1 physischer 4K Sektor).

Hier wird gezeigt wie ein Sektor gezielt beschrieben werden kann:
[Anleitung] Defekte Sektoren manuell neu zuweisen
 
Zurück