Harddisk: přežije nebo vyměnit?

[rado3105]

Toto je vystup, zaujima ci uz disk treba vymenit alebo to este prezije alebo ako este nieco dotestovat?

smartctl -a /dev/sda
smartctl 5.40 2010-07-12 r3124 [i686-pc-linux-gnu] (local build)
Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital AV-GP family
Device Model:     WDC WD15EVDS-68V9B0
Serial Number:    WD-WMAVU0931943
Firmware Version: 01.00A01
User Capacity:    1,500,300,828,160 bytes
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   8
ATA Standard is:  Exact ATA specification draft version not indicated
Local Time is:    Wed Aug 22 12:47:08 2012 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:  (0x82)   Offline data collection activity
               was completed without error.
               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:        (35700) 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:     (   2) minutes.
Extended self-test routine
recommended polling time:     ( 255) minutes.
Conveyance self-test routine
recommended polling time:     (   5) minutes.
SCT capabilities:           (0x303f)   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     0x002f   200   200   051    Pre-fail  Always       -       1700
  3 Spin_Up_Time            0x0027   189   180   021    Pre-fail  Always       -       5508
  4 Start_Stop_Count        0x0032   080   080   000    Old_age   Always       -       20552
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   200   200   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   071   071   000    Old_age   Always       -       21616
 10 Spin_Retry_Count        0x0032   100   100   000    Old_age   Always       -       0
 11 Calibration_Retry_Count 0x0032   100   100   000    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   080   080   000    Old_age   Always       -       20550
192 Power-Off_Retract_Count 0x0032   173   173   000    Old_age   Always       -       20541
193 Load_Cycle_Count        0x0032   156   156   000    Old_age   Always       -       132092
194 Temperature_Celsius     0x0022   115   103   000    Old_age   Always       -       35
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   199   199   000    Old_age   Always       -       330
198 Offline_Uncorrectable   0x0030   199   199   000    Old_age   Offline      -       255
199 UDMA_CRC_Error_Count    0x0032   200   199   000    Old_age   Always       -       4931
200 Multi_Zone_Error_Rate   0x0008   198   198   000    Old_age   Offline      -       410

SMART Error Log Version: 1
ATA Error Count: 699 (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 699 occurred at disk power-on lifetime: 21615 hours (900 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 08 39 40 e3  Error: UNC at LBA = 0x03403908 = 54540552

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 00 ff 38 40 e3 08      14:06:15.378  READ DMA
  ec 00 00 00 00 00 a0 08      14:06:15.371  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 08      14:06:15.371  SET FEATURES [Set transfer mode]

Error 698 occurred at disk power-on lifetime: 21615 hours (900 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 08 39 40 e3  Error: UNC at LBA = 0x03403908 = 54540552

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 00 ff 38 40 e3 08      14:06:12.690  READ DMA
  ec 00 00 00 00 00 a0 08      14:06:12.682  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 08      14:06:12.682  SET FEATURES [Set transfer mode]

Error 697 occurred at disk power-on lifetime: 21615 hours (900 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 08 39 40 e3  Error: UNC at LBA = 0x03403908 = 54540552

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 00 ff 38 40 e3 08      14:06:10.017  READ DMA
  ec 00 00 00 00 00 a0 08      14:06:10.009  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 08      14:06:10.009  SET FEATURES [Set transfer mode]

Error 696 occurred at disk power-on lifetime: 21615 hours (900 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 08 39 40 e3  Error: UNC at LBA = 0x03403908 = 54540552

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 00 ff 38 40 e3 08      14:06:07.344  READ DMA
  ec 00 00 00 00 00 a0 08      14:06:07.336  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 08      14:06:07.336  SET FEATURES [Set transfer mode]

Error 695 occurred at disk power-on lifetime: 21615 hours (900 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 08 39 40 e3  Error: UNC at LBA = 0x03403908 = 54540552

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 00 ff 38 40 e3 08      14:06:04.671  READ DMA
  ec 00 00 00 00 00 a0 08      14:06:04.663  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 08      14:06:04.663  SET FEATURES [Set transfer mode]

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.

[Reklama]

[Pavel 'TIGER' Růžička]

No pokud je to nějaký serverový disk, či dosk s velmi důležitými daty, tak bych ho už asi vyměnil. Jinak pokud používáte GUI, tak je skvělá utilita palimpsest, která řekne srozumitelnou formou, jak na tom disk je.

[trubicoid2]

no postup je takovyto:

1. zalohuj vse v pripade, ze disk je kaput
2. smartctl -t short /dev/sda; pockat 2 minuty; smartctl -a /dev/sda; kouknout se, ze tam je "Short offline ... Completed without error"
3. smartctl -t long /dev/sda; pockat 255 minut; smartctl -a /dev/sda; kouknout se, ze tam je "Extended offline ... Completed without error"

Jestli jeden z testu nedopadne dobre, mas vadny bloky a ukaze se, kde je prvni (LBA).

To se da jeste zvratit, nebo reklamovat, to je na tobe.

Pokus o opravu: na disku pustis destruktivni! badblocks -svw /dev/sda a uvidis, jestli se nahodou ty vadny sektory nerealokujou; po poslednim kroku (jede to velmi, velmi dlouho) by melo byt "0 bad sectors found".

Pak udelas znova bod 3. pro kontrolu a mozna to dopadne dobre. (Misto destruktivniho prepisu jde pustit neco jako mmhd, ktery sektor precte a zapise, cimz si taky realokaci vynuti, ale ja bych veril vic badblocks a pak obnovil zalohu)

Pak budes mit vetsi cislo v Realocated_sectors_count a Realocated_events_count. Je treba mit na pameti, ze tyto hodnoty se jednou vycerpaji.

[trubicoid2]

jo, to jsem zjistil nedavno, ze badblocks jede rychleji, kdyz se zvysi defaultni -b nebo -c alespon 4x; stejne to trva dlouho, ale dobry neco

takze

Kód: [Vybrat]

badblocks -svw -c 512 /dev/sda

[Pavel 'TIGER' Růžička]

Ano, v tomto směru je větší důvěra v badblocks oproti MHDD na místě. Alespoň z mé praxe.

[Reklama]

[rado3105]

Kratky test ukazal toto:
SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed: read failure       90%     21617         485393

[trubicoid2]

dlouhy nemusis delat, mas vadnej blok; reklamace asi neprichazi do uvahy, tak zaloha a badblocks a zkusit ho prealokovat?

zalohu asi pres ddrescue, snad mas po ruce stejny nebo o neco vetsi disk

jestli je to /, tak nabootovat nejakou live distribuci, napr. linuxrescuecd, ta ma ddrescue

[Rhinox]

Disk je v poradku a nevidim duvod na vymenu. Nevim jestli ma smysl tady psat nakej dlouhej rozbor kdyz jak koukam se to tady hemzi odborniky, tak jenom strucne:

Mas tam nekolik krat chybu pri cteni. To je naprosto bezna vec, od toho je CRC. Trvale reseni je premapovani sektoru, to se u disku bohuzel aktivuje jenom pri zapisu. Chyba pri cteni tudiz nema za nasledek premapovani weak-sektoru na jeden z rezervnich, disk s tim ceka az na chvili, kdy budes chtit zapisovat zrovna na tento slabej sektor. Proto kazde dalsi cteni tohoto sektoru spusobi danou chybu. Neni to ovsem nic kritickeho.

Jestli te to opravdu stve a nechces cekat az se sektor pri zapisu premapuje, muzes skusit natvrdo neco jako "hdparm --write-sector CHS /dev/???", podle mne je to ovsem naprosto zbytecne. Co by sis mel vsimnout je "SMART overall-health self-assessment test result: PASSED"...

[rado3105]

Vdaka Rhinox, vyzera ze vies o com hovoris. Este som sa chcel spytat, ked spustim prikaz: hdparm --write-sector CHS /dev/??? je tam riziko straty dat?

[Rhinox]

Samozrejme ze riziko straty dat tam je! To je prikaz kterej nizkourovnove zapisuje presne na danej sektor, tudiz o data ktera jsou ulozeny na nem prides! To sem asi mel napsat hned...
:-)

[rado3105]

Vdaka...mam objednany 2 tyzdne WD RED a stale nic...tak pockam kym pride zalohujem a obnovim a budu tam tie data ulozene duplicitne...vdaka este raz...vsetkym

[trubicoid2]

no nerad se hadam, ale podle rhinoxa bych to teda nedelal. ja uz taky par disku opravil a ty co nesly opravit vyhodil.

von teda ma pravdu, ze by to jakoze stacilo vynulovat ten vadnej sektor, ale on nebude asi jen jeden a smartctl -t ti rekne, kde je ten prvni.

Navic nulovat sektor, aniz bys ho zkusil predtim precist pomoci ddrescue (nekdy se to podari, zkousi to nekolikrat), tim zarucene prijdes o data, co v nem byly.

No a man hdparm rika:
 --write-sector
              Writes zeros to the specified sector number.  VERY DANGEROUS.  The sector number must be given (base10) after this option.  hdparm will issue a low-level write (completely bypassing the usual block layer read/write mechanisms) to the specified sector.  This can be used to force a drive to  repair  a  bad  sector
              (media error).

Takze bych tam radeji psal pomoci dd.

Nu a jestli a jak je to nebezpecny a jestli disk menit prave zalezi na tom, kolik tech vadnych sektoru bude. Mam disk s 6 a uz nekolik let se tam novy neobjevil. Zase na jinem disku pribyvali exponencialne, az za tyden uplne zdechnul. Takze asi tak.

[Olaf]

Disk je v poradku a nevidim duvod na vymenu...

Já bych takový optimista nebyl. "SMART overall-health self-assessment test result: PASSED" zas tak moc neznamená.

Podle následujících atributů je vidět, že se nejedná o jeden, ale víc sektorů:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
197 Current_Pending_Sector  0x0032   199   199   000    Old_age   Always       -       330
198 Offline_Uncorrectable   0x0030   199   199   000    Old_age   Offline      -       255

Měl jsem v ruce disk, který taky "prošel" (SMART overall-health self-assessment test result: PASSED; 1 Raw_Read_Error_Rate = 620; 196 Reallocated_Event_Count = 0; 197 Current_Pending_Sector = 270;198 Offline_Uncorrectable = 0) a při pokusu o backup byl disk po několika hodinách KO. Nepřečetl jsem z něj už nic (ani SMART).

Takže se připojím k názoru:

... Nu a jestli a jak je to nebezpecny a jestli disk menit prave zalezi na tom, kolik tech vadnych sektoru bude. Mam disk s 6 a uz nekolik let se tam novy neobjevil. Zase na jinem disku pribyvali exponencialne, az za tyden uplne zdechnul. Takze asi tak.

Můžete sem (jen tak pro zajímavost) šoupnout výstup smartctl -a /dev/sda po tom krátkém testu?:

Kratky test ukazal toto:
SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed: read failure       90%     21617         485393

[rado3105]

# smartctl -a /dev/sda
smartctl 5.40 2010-07-12 r3124 [i686-pc-linux-gnu] (local build)
Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital AV-GP family
Device Model:     WDC WD15EVDS-68V9B0
Serial Number:    WD-WMAVU0931943
Firmware Version: 01.00A01
User Capacity:    1,500,300,828,160 bytes
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   8
ATA Standard is:  Exact ATA specification draft version not indicated
Local Time is:    Wed Aug 22 20:45:23 2012 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:      ( 121)   The previous self-test completed having
               the read element of the test failed.
Total time to complete Offline
data collection:        (35700) 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:     (   2) minutes.
Extended self-test routine
recommended polling time:     ( 255) minutes.
Conveyance self-test routine
recommended polling time:     (   5) minutes.
SCT capabilities:           (0x303f)   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     0x002f   200   200   051    Pre-fail  Always       -       1700
  3 Spin_Up_Time            0x0027   189   180   021    Pre-fail  Always       -       5508
  4 Start_Stop_Count        0x0032   080   080   000    Old_age   Always       -       20552
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   200   200   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   071   071   000    Old_age   Always       -       21623
 10 Spin_Retry_Count        0x0032   100   100   000    Old_age   Always       -       0
 11 Calibration_Retry_Count 0x0032   100   100   000    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   080   080   000    Old_age   Always       -       20550
192 Power-Off_Retract_Count 0x0032   173   173   000    Old_age   Always       -       20541
193 Load_Cycle_Count        0x0032   156   156   000    Old_age   Always       -       132097
194 Temperature_Celsius     0x0022   106   103   000    Old_age   Always       -       44
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   199   199   000    Old_age   Always       -       330
198 Offline_Uncorrectable   0x0030   199   199   000    Old_age   Offline      -       255
199 UDMA_CRC_Error_Count    0x0032   200   199   000    Old_age   Always       -       4931
200 Multi_Zone_Error_Rate   0x0008   198   198   000    Old_age   Offline      -       410

SMART Error Log Version: 1
ATA Error Count: 699 (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 699 occurred at disk power-on lifetime: 21615 hours (900 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 08 39 40 e3  Error: UNC at LBA = 0x03403908 = 54540552

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 00 ff 38 40 e3 08      14:06:15.378  READ DMA
  ec 00 00 00 00 00 a0 08      14:06:15.371  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 08      14:06:15.371  SET FEATURES [Set transfer mode]

Error 698 occurred at disk power-on lifetime: 21615 hours (900 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 08 39 40 e3  Error: UNC at LBA = 0x03403908 = 54540552

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 00 ff 38 40 e3 08      14:06:12.690  READ DMA
  ec 00 00 00 00 00 a0 08      14:06:12.682  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 08      14:06:12.682  SET FEATURES [Set transfer mode]

Error 697 occurred at disk power-on lifetime: 21615 hours (900 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 08 39 40 e3  Error: UNC at LBA = 0x03403908 = 54540552

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 00 ff 38 40 e3 08      14:06:10.017  READ DMA
  ec 00 00 00 00 00 a0 08      14:06:10.009  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 08      14:06:10.009  SET FEATURES [Set transfer mode]

Error 696 occurred at disk power-on lifetime: 21615 hours (900 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 08 39 40 e3  Error: UNC at LBA = 0x03403908 = 54540552

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 00 ff 38 40 e3 08      14:06:07.344  READ DMA
  ec 00 00 00 00 00 a0 08      14:06:07.336  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 08      14:06:07.336  SET FEATURES [Set transfer mode]

Error 695 occurred at disk power-on lifetime: 21615 hours (900 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 08 39 40 e3  Error: UNC at LBA = 0x03403908 = 54540552

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 00 ff 38 40 e3 08      14:06:04.671  READ DMA
  ec 00 00 00 00 00 a0 08      14:06:04.663  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 08      14:06:04.663  SET FEATURES [Set transfer mode]

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed: read failure       90%     21617         485393

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.

[trubicoid2]

no po tom testu se moc statistika nezmeni, protoze on se zastavi na prvni chybe. zajimavejsi by bylo se podivat na vysledek po dobehnuti ddrescue nebo badblocks.
nicmene je nejmin 330 pending sectors (mozna vic, protoze jsi asi nezkousel cist vsechny sektory), to uz je docela hodne. mozna to i tak pujde opravit, ale nevim, pak sem napis, jak jsi dopad

a je pravda, ze "SMART overall-health self-assessment test result: PASSED" nic neznamena. to kontroluje snad jen bios, pokud to mas zapnuty. spousta disku hlasila PASSED do posledni sekundy pred smrti