logo elektroda
logo elektroda
X
logo elektroda
Adblock/uBlockOrigin/AdGuard mogą powodować znikanie niektórych postów z powodu nowej reguły.

Seagate/Momentus/7200.4 - Prawdopodobnie uszkodzony dysk.

arragorn 12 Lip 2014 23:18 1911 7
  • #1 13791563
    arragorn
    Poziom 2  
    Posty: 4
    Witajcie,
    Bardzo proszę o pomoc w zdiagnozowaniu problemu z dyskiem.
    Dziekuje i pozdrawiam, AR

    smartctl 6.0 2012-10-10 r3643 [i686-linux-3.5.6-pmagic] (local build)


    === START OF INFORMATION SECTION ===
    Model Family: Seagate Momentus 7200.4
    Device Model: ST9500420AS
    Serial Number: 5VJASZYB
    LU WWN Device Id: 5 000c50 02fa8e9ca
    Firmware Version: 0003LVM1
    User Capacity: 500,107,862,016 bytes [500 GB]
    Sector Size: 512 bytes logical/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 2.6, 3.0 Gb/s (current: 3.0 Gb/s)
    Local Time is: Sat Jul 12 22:48:25 2014 UTC
    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: ( 121) The previous self-test completed having
    the read element of the test failed.
    Total time to complete Offline
    data collection: ( 0) 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: ( 110) minutes.
    Conveyance self-test routine
    recommended polling time: ( 2) minutes.
    SCT capabilities: (0x103b) SCT Status supported.
    SCT Error Recovery Control supported.
    SCT Feature Control supported.
    SCT Data Table 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 091 086 034 Pre-fail Always - 48688806
    3 Spin_Up_Time 0x0003 100 100 000 Pre-fail Always - 0
    4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 201
    5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0
    7 Seek_Error_Rate 0x000f 063 060 030 Pre-fail Always - 2463486
    9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 49 (237 57 0)
    10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
    12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 201
    184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0
    187 Reported_Uncorrect 0x0032 001 001 000 Old_age Always - 468
    188 Command_Timeout 0x0032 100 100 000 Old_age Always - 2
    189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0
    190 Airflow_Temperature_Cel 0x0022 060 053 045 Old_age Always - 40 (Min/Max 38/40)
    191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 10
    192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 481
    193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 1043
    194 Temperature_Celsius 0x0022 040 047 000 Old_age Always - 40 (0 11 0 0 0)
    195 Hardware_ECC_Recovered 0x001a 046 039 000 Old_age Always - 48688806
    196 Reallocated_Event_Count 0x000f 100 100 030 Pre-fail Always - 35 (47720 0)
    197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 2
    198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 2
    199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0
    254 Free_Fall_Sensor 0x0032 100 100 000 Old_age Always - 0

    SMART Error Log Version: 1
    ATA Error Count: 465 (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 465 occurred at disk power-on lifetime: 49 hours (2 days + 1 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 1e c6 56 00 Error: UNC at LBA = 0x0056c61e = 5686814

    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 40 e6 bf 56 40 00 00:08:26.479 READ FPDMA QUEUED
    60 00 40 66 66 55 40 00 00:08:25.986 READ FPDMA QUEUED
    60 00 40 26 66 55 40 00 00:08:25.979 READ FPDMA QUEUED
    60 00 40 e6 65 55 40 00 00:08:25.978 READ FPDMA QUEUED
    60 00 40 47 bd 45 40 00 00:08:20.986 READ FPDMA QUEUED

    Error 464 occurred at disk power-on lifetime: 49 hours (2 days + 1 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 1e c6 56 00 Error: UNC at LBA = 0x0056c61e = 5686814

    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 00 c0 56 40 00 00:05:38.345 READ FPDMA QUEUED
    60 00 00 00 a4 53 40 00 00:05:36.180 READ FPDMA QUEUED
    60 00 00 00 a3 53 40 00 00:05:36.171 READ FPDMA QUEUED
    60 00 00 00 fa 43 40 00 00:05:31.178 READ FPDMA QUEUED
    60 00 00 00 f9 43 40 00 00:05:31.170 READ FPDMA QUEUED

    Error 463 occurred at disk power-on lifetime: 48 hours (2 days + 0 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 6e b9 9d 00 Error: UNC at LBA = 0x009db96e = 10336622

    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 08 88 d5 87 40 00 00:16:48.866 READ FPDMA QUEUED
    60 00 06 fe 66 33 40 00 00:16:48.865 READ FPDMA QUEUED
    60 00 01 fb 66 33 40 00 00:16:48.865 READ FPDMA QUEUED
    60 00 29 d2 66 33 40 00 00:16:48.865 READ FPDMA QUEUED
    60 00 20 8f 30 38 40 00 00:16:48.864 READ FPDMA QUEUED

    Error 462 occurred at disk power-on lifetime: 48 hours (2 days + 0 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 6e b9 9d 00 Error: UNC at LBA = 0x009db96e = 10336622

    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 08 88 d5 87 40 00 00:16:46.247 READ FPDMA QUEUED
    60 00 06 fe 66 33 40 00 00:16:46.246 READ FPDMA QUEUED
    60 00 01 fb 66 33 40 00 00:16:46.246 READ FPDMA QUEUED
    60 00 29 d2 66 33 40 00 00:16:46.246 READ FPDMA QUEUED
    60 00 20 8f 30 38 40 00 00:16:46.245 READ FPDMA QUEUED

    Error 461 occurred at disk power-on lifetime: 48 hours (2 days + 0 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 6e b9 9d 00 Error: UNC at LBA = 0x009db96e = 10336622

    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 08 88 d5 87 40 00 00:16:43.593 READ FPDMA QUEUED
    60 00 06 fe 66 33 40 00 00:16:43.593 READ FPDMA QUEUED
    60 00 01 fb 66 33 40 00 00:16:43.593 READ FPDMA QUEUED
    60 00 29 d2 66 33 40 00 00:16:43.592 READ FPDMA QUEUED
    60 00 20 8f 30 38 40 00 00:16:43.592 READ FPDMA QUEUED

    SMART Self-test log structure revision number 1
    Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
    # 1 Conveyance offline Completed: read failure 90% 49 10336622
    # 2 Short offline Completed: read failure 90% 49 10336622
    # 3 Vendor (0x50) Completed without error 00% 0 -

    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.
  • Pomocny post
    #2 13791613
    mbo
    VIP Zasłużony dla elektroda
    Posty: 19691
    Pomógł: 2333
    Ocena: 845
    Dysk na procedurę naprawczą - ma niestabilne sektory.
    Obchodź się z nim delikatniej - są zarejestrowane przeciążenia podczas pracy.
  • #3 13791688
    arragorn
    Poziom 2  
    Posty: 4
    Co to znaczy? niestety nie jest już na gwarancji...
  • #5 13792376
    arragorn
    Poziom 2  
    Posty: 4
    Dzieki, dzis zabieram sie za naprawe...
    ...
  • #6 13794677
    arragorn
    Poziom 2  
    Posty: 4
    Niestety nie udalo sie, i nie wiem o co chodzi... czy ktos moze pomoc?:

    root@PartedMagic:~# ddrescue --force /dev/zero /dev/sda


    GNU ddrescue 1.16
    Press Ctrl-C to interrupt
    rescued: 500107 MB, errsize: 0 B, current rate: 484 GB/s
    ipos: 500107 MB, errors: 0, average rate: 3379 MB/s
    opos: 500107 MB, time since last successful read: 0 s
    Copying non-tried blocks...
    ddrescue: write error: No space left on device
  • #7 13794690
    mbo
    VIP Zasłużony dla elektroda
    Posty: 19691
    Pomógł: 2333
    Ocena: 845
    Użyj do zerowania i remap MHDD zgodnie z opisem procedury na forum.
  • #8 13817520
    anu
    Poziom 17  
    Posty: 307
    Pomógł: 19
    Ocena: 32
    arragorn napisał:
    Niestety nie udalo sie, i nie wiem o co chodzi... czy ktos moze pomoc?:

    root@PartedMagic:~# ddrescue --force /dev/zero /dev/sda


    GNU ddrescue 1.16
    Press Ctrl-C to interrupt
    rescued: 500107 MB, errsize: 0 B, current rate: 484 GB/s
    ipos: 500107 MB, errors: 0, average rate: 3379 MB/s
    opos: 500107 MB, time since last successful read: 0 s
    Copying non-tried blocks...
    ddrescue: write error: No space left on device


    Jeśli już Linux, to proponuję zamiast ddrescue w tym samym momencie dać:
    dd if=/dev/zero of=/dev/sda
    przy czym /dev/sda to MUSI być oznaczenie uszkodzonego dysku!
    Komenda KASUJE zawartość /dev/sda !!!

    Po tej komendzie należy oczytać smart w szczególności Reallocated i Pending. Pending powinien się wyzerować. Jeśli nie, to MHDD z tym remapem co wyżej. Jeśli dalej nie, to użycie fragmentu dysku (ale to często denerwujące doświadczenie) lub kosz.

    Jeśli Pending i Reallocated będą na 0, to używać wedle kieszeni, ale z backupem.

Podsumowanie tematu

LABEL_AI_GENERATED
Dysk Seagate Momentus 7200.4 (model ST9500420AS) wykazuje problemy z niestabilnymi sektorami, co sugeruje uszkodzenie. Użytkownik został poinformowany o konieczności delikatnego obchodzenia się z dyskiem oraz o wykonaniu zerowania po skopiowaniu danych. Wskazano na możliwość użycia narzędzi takich jak MHDD do remapowania oraz komendy dd w systemie Linux do zerowania dysku. Po wykonaniu tych operacji, ważne jest sprawdzenie wartości SMART, szczególnie parametrów Reallocated i Pending. W przypadku dalszych problemów, zaleca się rozważenie użycia fragmentu dysku lub wymiany urządzenia.
Podsumowanie AI na podstawie dyskusji. Może zawierać błędy.
REKLAMA