Po wymianie dysku w laptopie pojawiły się błędy na sektorach

Mam taki problem wymieniłem dysk w laptopie na używany dysk i ten dysk trochę pochodził po czym zaczął szwankować raz się system operacyjny nie chciał uruchomić to pomogło polecenie fsck/dev/sda6 i trochę naprawiło ten dysk a w tym momencie polecenie

 

smartctl -a /dev/sda

Dostaje następujący komunikat

smartctl 6.4 2014-10-07 r4002 [x86_64-linux-3.16.0-4-amd64] (local build)

Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org



=== START OF INFORMATION SECTION ===

Model Family: SAMSUNG SpinPoint MP5

Device Model: SAMSUNG HM500JJ

Serial Number: S2AVJDNB100881

LU WWN Device Id: 5 0024e9 004915c50

Firmware Version: 2AK10001

User Capacity: 500,107,862,016 bytes [500 GB]

Sector Size: 512 bytes logical/physical

Rotation Rate: 7200 rpm

Form Factor: 2.5 inches

Device is: In smartctl database [for details use: -P show]

ATA Version is: ATA8-ACS T13/1699-D revision 6

SATA Version is: SATA 2.6, 3.0 Gb/s

Local Time is: Sat Jul 2 15:01:42 2016 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

See vendor-specific Attribute list for marginal Attributes.



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: ( 6120) seconds.

Offline data collection

capabilities: (0x51) SMART execute Offline immediate.

                                        No Auto Offline data collection support.

                                        Suspend Offline collection upon new

                                        command.                                                                                                                                               

                                        No 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: ( 102) 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 0x002f 100 100 051 Pre-fail Always - 15955

  2 Throughput_Performance 0x0027 252 252 000 Pre-fail Always - 0

  3 Spin_Up_Time 0x0023 090 086 025 Pre-fail Always - 3317

  4 Start_Stop_Count 0x0032 097 097 000 Old_age Always - 3535

  5 Reallocated_Sector_Ct 0x0033 252 252 010 Pre-fail Always - 0

  7 Seek_Error_Rate 0x002f 252 252 051 Pre-fail Always - 0

  8 Seek_Time_Performance 0x0025 252 252 015 Pre-fail Offline - 0

  9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 5544

 10 Spin_Retry_Count 0x0033 252 252 051 Pre-fail Always - 0

 11 Calibration_Retry_Count 0x0032 099 099 000 Old_age Always - 1279

 12 Power_Cycle_Count 0x0032 097 097 000 Old_age Always - 3578

183 Runtime_Bad_Block 0x0032 252 252 010 Old_age Always - 0

184 End-to-End_Error 0x0033 252 252 048 Pre-fail Always - 0

186 Unknown_Attribute 0x0032 252 252 000 Old_age Always - 0

187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 13025

188 Command_Timeout 0x0032 252 252 000 Old_age Always - 0

190 Airflow_Temperature_Cel 0x0002 043 039 040 Old_age Always In_the_past 57 (Min/Max 11/63)

191 G-Sense_Error_Rate 0x0022 095 095 000 Old_age Always - 58053

192 Power-Off_Retract_Count 0x0022 252 252 000 Old_age Always - 0

193 Load_Cycle_Count 0x0032 095 095 000 Old_age Always - 59788

194 Temperature_Celsius 0x0002 043 039 000 Old_age Always - 57 (Min/Max 11/63)

195 Hardware_ECC_Recovered 0x003a 100 100 000 Old_age Always - 0

196 Reallocated_Event_Count 0x0032 252 252 000 Old_age Always - 0

197 Current_Pending_Sector 0x0032 100 100 000 Old_age Always - 13

198 Offline_Uncorrectable 0x0030 252 252 000 Old_age Offline - 0

199 UDMA_CRC_Error_Count 0x0036 200 200 000 Old_age Always - 0

200 Multi_Zone_Error_Rate 0x002a 001 001 000 Old_age Always - 36547



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: 4982 hours (207 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 SC SN CL CH DH

  -- -- -- -- -- -- --

  40 51 08 a0 05 ed e0 Error: UNC 8 sectors at LBA = 0x00ed05a0 = 15533472



  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 08 a0 05 ed e0 00 00:00:00.018 READ DMA

  c8 00 08 a0 05 ed e0 00 00:00:00.016 READ DMA

  c8 00 08 a0 05 ed e0 00 00:00:00.015 READ DMA

  c8 00 02 5a d1 61 e0 00 00:00:00.015 READ DMA

  c8 00 08 00 d1 55 e0 00 00:00:00.015 READ DMA



Error 5 occurred at disk power-on lifetime: 4982 hours (207 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 SC SN CL CH DH

  -- -- -- -- -- -- --

  40 51 08 a0 05 ed e0 Error: UNC 8 sectors at LBA = 0x00ed05a0 = 15533472



  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 08 a0 05 ed e0 00 00:00:00.016 READ DMA

  c8 00 08 a0 05 ed e0 00 00:00:00.015 READ DMA

  c8 00 02 5a d1 61 e0 00 00:00:00.015 READ DMA

  c8 00 08 00 d1 55 e0 00 00:00:00.015 READ DMA

  c8 00 18 90 53 ec e0 00 00:00:00.015 READ DMA



Error 4 occurred at disk power-on lifetime: 4982 hours (207 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 SC SN CL CH DH

  -- -- -- -- -- -- --

  40 51 08 a0 05 ed e0 Error: UNC 8 sectors at LBA = 0x00ed05a0 = 15533472



  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 08 a0 05 ed e0 00 00:00:00.015 READ DMA

  c8 00 02 5a d1 61 e0 00 00:00:00.015 READ DMA

  c8 00 08 00 d1 55 e0 00 00:00:00.015 READ DMA

  c8 00 18 90 53 ec e0 00 00:00:00.015 READ DMA

  c8 00 10 70 53 ec e0 00 00:00:00.015 READ DMA



Error 3 occurred at disk power-on lifetime: 4982 hours (207 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 SC SN CL CH DH

  -- -- -- -- -- -- --

  40 51 08 a0 05 ed e0 Error: UNC 8 sectors at LBA = 0x00ed05a0 = 15533472



  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 08 a0 05 ed e0 00 00:00:00.013 READ DMA

  c8 00 08 a0 05 ed e0 00 00:00:00.011 READ DMA

  c8 00 08 a0 05 ed e0 00 00:00:00.010 READ DMA

  c8 00 02 5a d1 61 e0 00 00:00:00.010 READ DMA

  c8 00 10 60 09 00 e0 00 00:00:00.010 READ DMA



Error 2 occurred at disk power-on lifetime: 4982 hours (207 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 SC SN CL CH DH

  -- -- -- -- -- -- --

  40 51 08 a0 05 ed e0 Error: UNC 8 sectors at LBA = 0x00ed05a0 = 15533472



  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 08 a0 05 ed e0 00 00:00:00.011 READ DMA

  c8 00 08 a0 05 ed e0 00 00:00:00.010 READ DMA

  c8 00 02 5a d1 61 e0 00 00:00:00.010 READ DMA

  c8 00 10 60 09 00 e0 00 00:00:00.010 READ DMA

  c8 00 02 0a 08 60 e0 00 00:00:00.010 READ DMA



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 0

Note: revision number not 1 implies that no selective self-test has ever been run

 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS

    1 0 0 Completed [00% left] (0-65535)

    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.

 

Zgłasza mi błędy na dysku są jakieś uszkodzone sektory i teraz się zastanawiam czy wystarczy tylko na nowo przeczyszczenie tych sektorów programem fsck czy wymiana dysku czy może nawet płyty głównej bo słyszałem, że może być nawet płyta główna uszkodzona ?

Atrybut 187 i 200 mówią niby o problemach z samą powierzchnią - problem z zapisem.

Ale 11 to raczej problem z mechanniką dysku. Nie hałasuje, nie stuka nic?

Do tego 191, czyli lakonicznie mówiąc, ilość wstrząsów jest wysoki. Może po prostu każdy ruch rejestruje w SMART, a może jednak pracował w ciężkich warunkach, spadał itd?

 

Gdyby płyta była uszkodzona, czy kabel SATA lub zasilacz to atrybut 183  miałby jakąś wartość, a tutaj masz 0.

Jako root jescze uruchom to

smartctl -l selftest /dev/sda

smartctl -l selftest /dev/sda

 

smartctl 6.4 2014-10-07 r4002 [x86_64-linux-3.16.0-4-amd64] (local build)

Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org



=== START OF READ SMART DATA SECTION ===

SMART Self-test log structure revision number 1

No self-tests have been logged. [To run self-tests, use: smartctl -t]

 

Jako root:

smartctl -t long /dev/sdb
 

Pojawi się informacja np.

Test will complete after Tue Jul  5 23:21:20 2016

 

Następnie możesz wykonać polecenie z mojego poprzedniego posta. Do czasu zakończenia testu poużywaj go trochę w grach, instalacji czegoś, aktualizacji systemu, jakiegoś backupu, archiwizacji.

Zrobiłem tak jak pisałeś i w tym momencie po wykonaniu polecenia

smartctl -l selftest /dev/sda

Wyświetla mi uszkodzone sektory

 

smartctl 6.4 2014-10-07 r4002 [x86_64-linux-3.16.0-4-amd64] (local build)

Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org



=== START OF READ SMART DATA SECTION ===

SMART Self-test log structure revision number 1

Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error

# 1 Extended offline Interrupted (host reset) 90% 5600 -

# 2 Extended offline Completed: read failure 90% 5599 15442584

# 3 Extended offline Completed: read failure 90% 5595 15442581

# 4 Extended offline Completed: read failure 90% 5592 15442581

# 5 Extended offline Completed: read failure 90% 5592 15442581

# 6 Extended offline Completed: read failure 90% 5589 15442581

i teraz jak je naprawić bo chyba było jakieś polecenie. I czy teraz te polecenia będę musiał wykonywać do tej pory jak w

197 Current_Pending_Sector  0x0032   100   100   000    Old_age   Always       -       16

będzie wartość 0

Można to naprawić przez e2fsck lub fsck, ewentualnie w trybie “rescue” przez badblocks.

Ale to, że wyłączy jakieś sektory, to nie znaczy, że po 5 minutach się nie pojawią nowe.

Wg mnie dysk po prostu się kończy.

W SMART wartości się nie zerują.