eGospodarka.pl
eGospodarka.pl poleca

eGospodarka.plGrupypl.comp.pecet › Chyba padł mi dysk
Ilość wypowiedzi w tym wątku: 42

  • 1. Data: 2020-09-22 18:00:08
    Temat: Chyba padł mi dysk
    Od: Smok Eustachy <s...@w...pl>

    A tu wynik diagnostyki:
    Ktoś się zna na tym? Co się dzieje?

    smartctl 6.6 2017-11-05 r4594 [x86_64-linux-5.2.15-pclos1] (local build)
    Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org

    === START OF INFORMATION SECTION ===
    Model Family: Western Digital Caviar Green (AF)
    Device Model: WDC WD15EARS-60MVWB0
    Serial Number: WD-WCAZA6193000
    LU WWN Device Id: 5 0014ee 25b0c02e8
    Firmware Version: 51.0AB51
    User Capacity: 1 500 301 910 016 bytes [1,50 TB]
    Sector Sizes: 512 bytes logical, 4096 bytes physical
    Form Factor: 3.5 inches
    Device is: In smartctl database [for details use: -P show]
    ATA Version is: ATA8-ACS (minor revision not indicated)
    SATA Version is: SATA 2.6, 3.0 Gb/s
    Local Time is: Tue Sep 22 17:42:13 2020 CEST
    SMART support is: Available - device has SMART capability.
    SMART support is: Enabled
    AAM feature is: Unavailable
    APM feature is: Unavailable
    Rd look-ahead is: Enabled
    Write cache is: Enabled
    DSN feature is: Unavailable
    ATA Security is: Disabled, NOT FROZEN [SEC1]

    === 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: ( 121) The previous self-test completed
    having
    the read element of the test failed.
    Total time to complete Offline
    data collection: (37560) seconds.
    Offline data collection
    capabilities: (0x5b) SMART execute Offline immediate.
    Auto Offline data collection on/off support.
    Suspend Offline collection upon new
    command.
    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: ( 362) minutes.
    SCT capabilities: (0x303d) 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 FLAGS VALUE WORST THRESH FAIL RAW_VALUE
    1 Raw_Read_Error_Rate POSR-K 200 200 051 - 0
    3 Spin_Up_Time POS--K 253 248 021 - 1158
    4 Start_Stop_Count -O--CK 099 099 000 - 1323
    5 Reallocated_Sector_Ct PO--CK 200 200 140 - 0
    7 Seek_Error_Rate POSR-K 200 200 051 - 0
    9 Power_On_Hours -O--CK 096 096 000 - 3419
    10 Spin_Retry_Count PO--CK 100 100 051 - 0
    11 Calibration_Retry_Count -O--CK 100 100 000 - 0
    12 Power_Cycle_Count -O--CK 099 099 000 - 1308
    184 End-to-End_Error PO--CK 100 100 097 - 0
    187 Reported_Uncorrect -O--CK 009 009 000 - 91
    188 Command_Timeout -O--CK 018 018 000 - 82
    190 Airflow_Temperature_Cel -O---K 069 058 040 - 31 (Min/Max
    25/31)
    192 Power-Off_Retract_Count -O--CK 200 200 000 - 98
    193 Load_Cycle_Count -O--CK 200 200 000 - 1224
    196 Reallocated_Event_Count -O--CK 200 200 000 - 0
    197 Current_Pending_Sector -O--CK 200 200 000 - 5
    198 Offline_Uncorrectable ----CK 200 200 000 - 4
    199 UDMA_CRC_Error_Count -O--CK 200 200 000 - 0
    200 Multi_Zone_Error_Rate ---R-- 200 200 000 - 3
    ||||||_ 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 6 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
    0x80-0x9f GPL,SL R/W 16 Host vendor specific log
    0xa0-0xa7 GPL,SL VS 16 Device vendor specific log
    0xa8-0xb7 GPL,SL VS 1 Device vendor specific log
    0xc0 GPL,SL VS 1 Device vendor specific log
    0xc1 GPL VS 93 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 (6 sectors)
    Device Error Count: 91 (device log contains only the most recent 24 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 91 [18] occurred at disk power-on lifetime: 3419 hours (142 days +
    11 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 00 00 09 ae 40 00 Error: UNC at LBA =
    0x000009ae = 2478

    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 08 00 10 00 00 ae a8 67 30 40 08 00:05:50.382 READ FPDMA
    QUEUED
    60 00 02 00 08 00 00 00 00 09 ae 40 08 00:05:50.382 READ FPDMA
    QUEUED
    ef 00 10 00 02 00 00 00 00 00 00 a0 08 00:05:50.382 SET FEATURES
    [Enable SATA feature]
    ec 00 00 00 00 00 00 00 00 00 00 a0 08 00:05:50.377 IDENTIFY DEVICE
    ef 00 03 00 45 00 00 00 00 00 00 a0 08 00:05:50.377 SET FEATURES
    [Set transfer mode]

    Error 90 [17] occurred at disk power-on lifetime: 3419 hours (142 days +
    11 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 00 00 09 ac 40 00 Error: UNC at LBA =
    0x000009ac = 2476

    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 02 00 40 00 00 00 00 09 ae 40 08 00:05:47.481 READ FPDMA
    QUEUED
    60 00 02 00 38 00 00 00 00 09 ac 40 08 00:05:47.481 READ FPDMA
    QUEUED
    60 00 08 00 30 00 00 ae a8 67 30 40 08 00:05:47.481 READ FPDMA
    QUEUED
    ef 00 10 00 02 00 00 00 00 00 00 a0 08 00:05:47.481 SET FEATURES
    [Enable SATA feature]
    ec 00 00 00 00 00 00 00 00 00 00 a0 08 00:05:47.476 IDENTIFY DEVICE

    Error 89 [16] occurred at disk power-on lifetime: 3419 hours (142 days +
    11 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 00 00 09 aa 40 00 Error: UNC at LBA =
    0x000009aa = 2474

    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 08 00 e8 00 00 ae a8 67 30 40 08 00:05:44.594 READ FPDMA
    QUEUED
    60 00 02 00 e0 00 00 00 00 09 aa 40 08 00:05:44.594 READ FPDMA
    QUEUED
    60 00 02 00 d8 00 00 00 00 09 ac 40 08 00:05:44.594 READ FPDMA
    QUEUED
    60 00 02 00 d0 00 00 00 00 09 ae 40 08 00:05:44.594 READ FPDMA
    QUEUED
    ef 00 10 00 02 00 00 00 00 00 00 a0 08 00:05:44.594 SET FEATURES
    [Enable SATA feature]

    Error 88 [15] occurred at disk power-on lifetime: 3419 hours (142 days +
    11 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 00 00 09 a8 40 00 Error: UNC at LBA =
    0x000009a8 = 2472

    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 08 00 10 00 00 ae a8 67 30 40 08 00:05:41.672 READ FPDMA
    QUEUED
    60 00 02 00 b0 00 00 00 00 09 ae 40 08 00:05:41.646 READ FPDMA
    QUEUED
    60 00 02 00 a8 00 00 00 00 09 ac 40 08 00:05:41.646 READ FPDMA
    QUEUED
    60 00 02 00 a0 00 00 00 00 09 aa 40 08 00:05:41.646 READ FPDMA
    QUEUED
    60 00 02 00 98 00 00 00 00 09 a8 40 08 00:05:41.645 READ FPDMA
    QUEUED

    Error 87 [14] occurred at disk power-on lifetime: 3419 hours (142 days +
    11 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 00 00 09 ae 40 00 Error: UNC at LBA =
    0x000009ae = 2478

    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 02 00 a0 00 00 00 00 09 ae 40 08 00:05:38.755 READ FPDMA
    QUEUED
    ef 00 10 00 02 00 00 00 00 00 00 a0 08 00:05:38.755 SET FEATURES
    [Enable SATA feature]
    ec 00 00 00 00 00 00 00 00 00 00 a0 08 00:05:38.751 IDENTIFY DEVICE
    ef 00 03 00 45 00 00 00 00 00 00 a0 08 00:05:38.751 SET FEATURES
    [Set transfer mode]
    ef 00 10 00 02 00 00 00 00 00 00 a0 08 00:05:38.751 SET FEATURES
    [Enable SATA feature]

    Error 86 [13] occurred at disk power-on lifetime: 3419 hours (142 days +
    11 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 00 00 09 ac 40 00 Error: UNC at LBA =
    0x000009ac = 2476

    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 02 00 10 00 00 00 00 09 ae 40 08 00:05:35.876 READ FPDMA
    QUEUED
    60 00 02 00 08 00 00 00 00 09 ac 40 08 00:05:35.876 READ FPDMA
    QUEUED
    ef 00 10 00 02 00 00 00 00 00 00 a0 08 00:05:35.876 SET FEATURES
    [Enable SATA feature]
    ec 00 00 00 00 00 00 00 00 00 00 a0 08 00:05:35.871 IDENTIFY DEVICE
    ef 00 03 00 45 00 00 00 00 00 00 a0 08 00:05:35.871 SET FEATURES
    [Set transfer mode]

    Error 85 [12] occurred at disk power-on lifetime: 3419 hours (142 days +
    11 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 00 00 09 aa 40 00 Error: UNC at LBA =
    0x000009aa = 2474

    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 02 00 b0 00 00 00 00 09 aa 40 08 00:05:33.001 READ FPDMA
    QUEUED
    60 00 02 00 a8 00 00 00 00 09 ac 40 08 00:05:33.001 READ FPDMA
    QUEUED
    60 00 02 00 a0 00 00 00 00 09 ae 40 08 00:05:33.001 READ FPDMA
    QUEUED
    ef 00 10 00 02 00 00 00 00 00 00 a0 08 00:05:33.001 SET FEATURES
    [Enable SATA feature]
    ec 00 00 00 00 00 00 00 00 00 00 a0 08 00:05:32.996 IDENTIFY DEVICE

    Error 84 [11] occurred at disk power-on lifetime: 3419 hours (142 days +
    11 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 00 00 09 a8 40 00 Error: UNC at LBA =
    0x000009a8 = 2472

    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 02 00 10 00 00 00 00 09 ae 40 08 00:05:30.107 READ FPDMA
    QUEUED
    60 00 02 00 08 00 00 00 00 09 ac 40 08 00:05:30.107 READ FPDMA
    QUEUED
    60 00 02 00 00 00 00 00 00 09 aa 40 08 00:05:30.107 READ FPDMA
    QUEUED
    60 00 02 00 f0 00 00 00 00 09 a8 40 08 00:05:30.107 READ FPDMA
    QUEUED
    60 00 08 00 90 00 00 9f 6d 14 d0 40 08 00:05:30.106 READ FPDMA
    QUEUED

    Error 83 [10] occurred at disk power-on lifetime: 3419 hours (142 days +
    11 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 00 00 09 ae 40 00 Error: UNC at LBA =
    0x000009ae = 2478

    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 02 00 18 00 00 00 00 09 ae 40 08 00:05:27.162 READ FPDMA
    QUEUED
    60 00 08 00 10 00 00 9f 6d 14 c8 40 08 00:05:27.162 READ FPDMA
    QUEUED
    ef 00 10 00 02 00 00 00 00 00 00 a0 08 00:05:27.162 SET FEATURES
    [Enable SATA feature]
    ec 00 00 00 00 00 00 00 00 00 00 a0 08 00:05:27.158 IDENTIFY DEVICE
    ef 00 03 00 45 00 00 00 00 00 00 a0 08 00:05:27.158 SET FEATURES
    [Set transfer mode]

    Error 82 [9] occurred at disk power-on lifetime: 3419 hours (142 days +
    11 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 00 00 09 ac 40 00 Error: UNC at LBA =
    0x000009ac = 2476

    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 08 00 c0 00 00 9f 6d 14 c8 40 08 00:05:24.260 READ FPDMA
    QUEUED
    60 00 02 00 b8 00 00 00 00 09 ae 40 08 00:05:24.260 READ FPDMA
    QUEUED
    60 00 02 00 b0 00 00 00 00 09 ac 40 08 00:05:24.260 READ FPDMA
    QUEUED
    ef 00 10 00 02 00 00 00 00 00 00 a0 08 00:05:24.260 SET FEATURES
    [Enable SATA feature]
    ec 00 00 00 00 00 00 00 00 00 00 a0 08 00:05:24.255 IDENTIFY DEVICE

    Error 81 [8] occurred at disk power-on lifetime: 3419 hours (142 days +
    11 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 00 00 09 aa 40 00 Error: UNC at LBA =
    0x000009aa = 2474

    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 02 00 20 00 00 00 00 09 aa 40 08 00:05:21.361 READ FPDMA
    QUEUED
    60 00 02 00 18 00 00 00 00 09 ac 40 08 00:05:21.361 READ FPDMA
    QUEUED
    60 00 02 00 10 00 00 00 00 09 ae 40 08 00:05:21.361 READ FPDMA
    QUEUED
    60 00 08 00 08 00 00 9f 6d 14 c8 40 08 00:05:21.361 READ FPDMA
    QUEUED
    ef 00 10 00 02 00 00 00 00 00 00 a0 08 00:05:21.361 SET FEATURES
    [Enable SATA feature]

    Error 80 [7] occurred at disk power-on lifetime: 3419 hours (142 days +
    11 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 00 00 09 a8 40 00 Error: UNC at LBA =
    0x000009a8 = 2472

    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 08 00 b0 00 00 9f 6d 14 c8 40 08 00:05:18.443 READ FPDMA
    QUEUED
    60 00 02 00 a8 00 00 00 00 09 ae 40 08 00:05:18.411 READ FPDMA
    QUEUED
    60 00 02 00 a0 00 00 00 00 09 ac 40 08 00:05:18.411 READ FPDMA
    QUEUED
    60 00 02 00 98 00 00 00 00 09 aa 40 08 00:05:18.411 READ FPDMA
    QUEUED
    60 00 02 00 90 00 00 00 00 09 a8 40 08 00:05:18.411 READ FPDMA
    QUEUED

    Error 79 [6] occurred at disk power-on lifetime: 3419 hours (142 days +
    11 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 00 00 09 ae 40 00 Error: UNC at LBA =
    0x000009ae = 2478

    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 02 00 80 00 00 00 00 09 ae 40 08 00:05:15.514 READ FPDMA
    QUEUED
    60 00 08 00 78 00 00 9f 6d 14 00 40 08 00:05:15.514 READ FPDMA
    QUEUED
    ef 00 10 00 02 00 00 00 00 00 00 a0 08 00:05:15.514 SET FEATURES
    [Enable SATA feature]
    ec 00 00 00 00 00 00 00 00 00 00 a0 08 00:05:15.509 IDENTIFY DEVICE
    ef 00 03 00 45 00 00 00 00 00 00 a0 08 00:05:15.509 SET FEATURES
    [Set transfer mode]

    Error 78 [5] occurred at disk power-on lifetime: 3419 hours (142 days +
    11 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 00 00 09 ac 40 00 Error: UNC at LBA =
    0x000009ac = 2476

    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 08 00 58 00 00 9f 6d 14 00 40 08 00:05:12.610 READ FPDMA
    QUEUED
    60 00 02 00 50 00 00 00 00 09 ae 40 08 00:05:12.610 READ FPDMA
    QUEUED
    60 00 02 00 48 00 00 00 00 09 ac 40 08 00:05:12.610 READ FPDMA
    QUEUED
    ef 00 10 00 02 00 00 00 00 00 00 a0 08 00:05:12.610 SET FEATURES
    [Enable SATA feature]
    ec 00 00 00 00 00 00 00 00 00 00 a0 08 00:05:12.605 IDENTIFY DEVICE

    Error 77 [4] occurred at disk power-on lifetime: 3419 hours (142 days +
    11 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 00 00 09 aa 40 00 Error: UNC at LBA =
    0x000009aa = 2474

    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 02 00 30 00 00 00 00 09 aa 40 08 00:05:09.708 READ FPDMA
    QUEUED
    60 00 02 00 28 00 00 00 00 09 ac 40 08 00:05:09.708 READ FPDMA
    QUEUED
    60 00 02 00 20 00 00 00 00 09 ae 40 08 00:05:09.708 READ FPDMA
    QUEUED
    60 00 08 00 18 00 00 9f 6d 14 00 40 08 00:05:09.708 READ FPDMA
    QUEUED
    ef 00 10 00 02 00 00 00 00 00 00 a0 08 00:05:09.708 SET FEATURES
    [Enable SATA feature]

    Error 76 [3] occurred at disk power-on lifetime: 3419 hours (142 days +
    11 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 00 00 09 a8 40 00 Error: UNC at LBA =
    0x000009a8 = 2472

    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 02 00 e8 00 00 00 00 09 ae 40 08 00:05:06.841 READ FPDMA
    QUEUED
    60 00 02 00 e0 00 00 00 00 09 ac 40 08 00:05:06.841 READ FPDMA
    QUEUED
    60 00 02 00 d8 00 00 00 00 09 aa 40 08 00:05:06.829 READ FPDMA
    QUEUED
    60 00 02 00 d0 00 00 00 00 09 a8 40 08 00:05:06.829 READ FPDMA
    QUEUED
    60 00 02 00 c8 00 00 00 00 09 a6 40 08 00:05:06.828 READ FPDMA
    QUEUED

    Error 75 [2] occurred at disk power-on lifetime: 3419 hours (142 days +
    11 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 00 00 09 a8 40 00 Error: UNC at LBA =
    0x000009a8 = 2472

    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 01 80 00 40 00 00 00 00 08 80 40 08 00:05:03.937 READ FPDMA
    QUEUED
    60 00 38 00 38 00 00 00 00 08 40 40 08 00:05:03.937 READ FPDMA
    QUEUED
    60 00 18 00 30 00 00 00 00 08 20 40 08 00:05:03.937 READ FPDMA
    QUEUED
    60 00 08 00 28 00 00 00 00 08 10 40 08 00:05:03.937 READ FPDMA
    QUEUED
    60 00 08 00 20 00 00 00 00 08 78 40 08 00:05:03.936 READ FPDMA
    QUEUED

    Error 74 [1] occurred at disk power-on lifetime: 3419 hours (142 days +
    11 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 00 00 09 ae 40 00 Error: UNC at LBA =
    0x000009ae = 2478

    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 08 00 30 00 00 ae a8 67 30 40 08 00:02:54.421 READ FPDMA
    QUEUED
    60 00 02 00 28 00 00 00 00 09 ae 40 08 00:02:54.421 READ FPDMA
    QUEUED
    ef 00 10 00 02 00 00 00 00 00 00 a0 08 00:02:54.421 SET FEATURES
    [Enable SATA feature]
    ec 00 00 00 00 00 00 00 00 00 00 a0 08 00:02:54.416 IDENTIFY DEVICE
    ef 00 03 00 45 00 00 00 00 00 00 a0 08 00:02:54.416 SET FEATURES
    [Set transfer mode]

    Error 73 [0] occurred at disk power-on lifetime: 3419 hours (142 days +
    11 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 00 00 09 ac 40 00 Error: UNC at LBA =
    0x000009ac = 2476

    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 02 00 48 00 00 00 00 09 ae 40 08 00:02:51.520 READ FPDMA
    QUEUED
    60 00 02 00 40 00 00 00 00 09 ac 40 08 00:02:51.520 READ FPDMA
    QUEUED
    60 00 08 00 38 00 00 ae a8 67 30 40 08 00:02:51.520 READ FPDMA
    QUEUED
    ef 00 10 00 02 00 00 00 00 00 00 a0 08 00:02:51.520 SET FEATURES
    [Enable SATA feature]
    ec 00 00 00 00 00 00 00 00 00 00 a0 08 00:02:51.515 IDENTIFY DEVICE

    Error 72 [23] occurred at disk power-on lifetime: 3419 hours (142 days +
    11 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 00 00 09 aa 40 00 Error: UNC at LBA =
    0x000009aa = 2474

    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 02 00 18 00 00 00 00 09 aa 40 08 00:02:48.615 READ FPDMA
    QUEUED
    60 00 02 00 10 00 00 00 00 09 ac 40 08 00:02:48.615 READ FPDMA
    QUEUED
    60 00 02 00 08 00 00 00 00 09 ae 40 08 00:02:48.615 READ FPDMA
    QUEUED
    60 00 08 00 f0 00 00 ae a8 67 30 40 08 00:02:48.615 READ FPDMA
    QUEUED
    ef 00 10 00 02 00 00 00 00 00 00 a0 08 00:02:48.615 SET FEATURES
    [Enable SATA feature]

    Error 71 [22] occurred at disk power-on lifetime: 3419 hours (142 days +
    11 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 00 00 09 a8 40 00 Error: UNC at LBA =
    0x000009a8 = 2472

    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 08 00 d0 00 00 ae a8 67 30 40 08 00:02:45.688 READ FPDMA
    QUEUED
    60 00 02 00 c8 00 00 00 00 09 ae 40 08 00:02:45.651 READ FPDMA
    QUEUED
    60 00 02 00 c0 00 00 00 00 09 ac 40 08 00:02:45.651 READ FPDMA
    QUEUED
    60 00 02 00 b8 00 00 00 00 09 aa 40 08 00:02:45.651 READ FPDMA
    QUEUED
    60 00 02 00 b0 00 00 00 00 09 a8 40 08 00:02:45.651 READ FPDMA
    QUEUED

    Error 70 [21] occurred at disk power-on lifetime: 3419 hours (142 days +
    11 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 00 00 09 a8 40 00 Error: UNC at LBA =
    0x000009a8 = 2472

    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 08 00 b8 00 00 00 00 09 a8 40 08 00:02:42.747 READ FPDMA
    QUEUED
    60 00 08 00 78 00 00 ae a8 66 80 40 08 00:02:42.747 READ FPDMA
    QUEUED
    ef 00 10 00 02 00 00 00 00 00 00 a0 08 00:02:42.746 SET FEATURES
    [Enable SATA feature]
    ec 00 00 00 00 00 00 00 00 00 00 a0 08 00:02:42.743 IDENTIFY DEVICE
    ef 00 03 00 45 00 00 00 00 00 00 a0 08 00:02:42.741 SET FEATURES
    [Set transfer mode]

    Error 69 [20] occurred at disk power-on lifetime: 3419 hours (142 days +
    11 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 00 00 09 ae 40 00 Error: UNC at LBA =
    0x000009ae = 2478

    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 08 00 58 00 00 ae a8 66 80 40 08 00:02:39.845 READ FPDMA
    QUEUED
    60 00 02 00 50 00 00 00 00 09 ae 40 08 00:02:39.845 READ FPDMA
    QUEUED
    ef 00 10 00 02 00 00 00 00 00 00 a0 08 00:02:39.845 SET FEATURES
    [Enable SATA feature]
    ec 00 00 00 00 00 00 00 00 00 00 a0 08 00:02:39.841 IDENTIFY DEVICE
    ef 00 03 00 45 00 00 00 00 00 00 a0 08 00:02:39.841 SET FEATURES
    [Set transfer mode]

    Error 68 [19] occurred at disk power-on lifetime: 3419 hours (142 days +
    11 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 00 00 09 ac 40 00 Error: UNC at LBA =
    0x000009ac = 2476

    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 02 00 08 00 00 00 00 09 ac 40 08 00:02:36.944 READ FPDMA
    QUEUED
    60 00 08 00 00 00 00 ae a8 66 80 40 08 00:02:36.944 READ FPDMA
    QUEUED
    60 00 02 00 f8 00 00 00 00 09 ae 40 08 00:02:36.944 READ FPDMA
    QUEUED
    ef 00 10 00 02 00 00 00 00 00 00 a0 08 00:02:36.943 SET FEATURES
    [Enable SATA feature]
    ec 00 00 00 00 00 00 00 00 00 00 a0 08 00:02:36.940 IDENTIFY DEVICE

    SMART Extended Self-test Log Version: 1 (1 sectors)
    Num Test_Description Status Remaining
    LifeTime(hours) LBA_of_first_error
    # 1 Extended offline Completed: read failure 90% 3387
    135032280
    # 2 Extended offline Interrupted (host reset) 90% 2
    -

    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): 258 (0x0102)
    SCT Support Level: 1
    Device State: Active (0)
    Current Temperature: 31 Celsius
    Power Cycle Min/Max Temperature: 25/31 Celsius
    Lifetime Min/Max Temperature: 20/42 Celsius
    Under/Over Temperature Limit Count: 0/0

    SCT Temperature History Version: 2
    Temperature Sampling Period: 1 minute
    Temperature Logging Interval: 1 minute
    Min/Max recommended Temperature: 0/60 Celsius
    Min/Max Temperature Limit: -41/85 Celsius
    Temperature History Size (Index): 128 (17)

    Index Estimated Time Temperature Celsius
    18 2020-09-22 15:35 35 ****************
    ... ..( 28 skipped). .. ****************
    47 2020-09-22 16:04 35 ****************
    48 2020-09-22 16:05 34 ***************
    49 2020-09-22 16:06 35 ****************
    50 2020-09-22 16:07 34 ***************
    ... ..( 7 skipped). .. ***************
    58 2020-09-22 16:15 34 ***************
    59 2020-09-22 16:16 35 ****************
    60 2020-09-22 16:17 35 ****************
    61 2020-09-22 16:18 34 ***************
    ... ..( 2 skipped). .. ***************
    64 2020-09-22 16:21 34 ***************
    65 2020-09-22 16:22 35 ****************
    66 2020-09-22 16:23 34 ***************
    67 2020-09-22 16:24 ? -
    68 2020-09-22 16:25 21 **
    69 2020-09-22 16:26 21 **
    70 2020-09-22 16:27 ? -
    71 2020-09-22 16:28 22 ***
    72 2020-09-22 16:29 ? -
    73 2020-09-22 16:30 23 ****
    74 2020-09-22 16:31 ? -
    75 2020-09-22 16:32 23 ****
    76 2020-09-22 16:33 ? -
    77 2020-09-22 16:34 23 ****
    78 2020-09-22 16:35 23 ****
    79 2020-09-22 16:36 24 *****
    80 2020-09-22 16:37 24 *****
    81 2020-09-22 16:38 25 ******
    82 2020-09-22 16:39 25 ******
    83 2020-09-22 16:40 25 ******
    84 2020-09-22 16:41 26 *******
    ... ..( 2 skipped). .. *******
    87 2020-09-22 16:44 26 *******
    88 2020-09-22 16:45 27 ********
    89 2020-09-22 16:46 27 ********
    90 2020-09-22 16:47 27 ********
    91 2020-09-22 16:48 28 *********
    92 2020-09-22 16:49 28 *********
    93 2020-09-22 16:50 29 **********
    ... ..( 5 skipped). .. **********
    99 2020-09-22 16:56 29 **********
    100 2020-09-22 16:57 30 ***********
    101 2020-09-22 16:58 30 ***********
    102 2020-09-22 16:59 30 ***********
    103 2020-09-22 17:00 31 ************
    ... ..( 2 skipped). .. ************
    106 2020-09-22 17:03 31 ************
    107 2020-09-22 17:04 32 *************
    ... ..( 5 skipped). .. *************
    113 2020-09-22 17:10 32 *************
    114 2020-09-22 17:11 ? -
    115 2020-09-22 17:12 23 ****
    116 2020-09-22 17:13 ? -
    117 2020-09-22 17:14 23 ****
    118 2020-09-22 17:15 ? -
    119 2020-09-22 17:16 24 *****
    120 2020-09-22 17:17 ? -
    121 2020-09-22 17:18 24 *****
    122 2020-09-22 17:19 ? -
    123 2020-09-22 17:20 25 ******
    124 2020-09-22 17:21 ? -
    125 2020-09-22 17:22 25 ******
    126 2020-09-22 17:23 25 ******
    127 2020-09-22 17:24 26 *******
    ... ..( 2 skipped). .. *******
    2 2020-09-22 17:27 26 *******
    3 2020-09-22 17:28 27 ********
    4 2020-09-22 17:29 27 ********
    5 2020-09-22 17:30 28 *********
    6 2020-09-22 17:31 28 *********
    7 2020-09-22 17:32 28 *********
    8 2020-09-22 17:33 29 **********
    ... ..( 3 skipped). .. **********
    12 2020-09-22 17:37 29 **********
    13 2020-09-22 17:38 30 ***********
    14 2020-09-22 17:39 30 ***********
    15 2020-09-22 17:40 30 ***********
    16 2020-09-22 17:41 31 ************
    17 2020-09-22 17:42 31 ************

    SCT Error Recovery Control:
    Read: 85 (8,5 seconds)
    Write: 85 (8,5 seconds)

    Device Statistics (GP/SMART Log 0x04) not supported

    SATA Phy Event Counters (GP Log 0x11)
    ID Size Value Description
    0x0001 2 0 Command failed due to ICRC error
    0x0002 2 0 R_ERR response for data FIS
    0x0003 2 0 R_ERR response for device-to-host data FIS
    0x0004 2 0 R_ERR response for host-to-device data FIS
    0x0005 2 0 R_ERR response for non-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
    0x000a 2 1 Device-to-host register FISes sent due to a COMRESET
    0x000b 2 0 CRC errors within host-to-device FIS
    0x8000 4 1378 Vendor specific


  • 2. Data: 2020-09-22 18:11:18
    Temat: Re: Chyba padł mi dysk
    Od: _Master_ <M...@...pl>

    W dniu 2020-09-22 o 18:00, Smok Eustachy pisze:
    >     A tu wynik diagnostyki:
    > Ktoś się zna na tym? Co się dzieje?

    A widzisz jakieś objawy?


    I pytanie kontrolne:

    Robisz backupy czy będziesz robił backupy?


  • 3. Data: 2020-09-22 18:26:12
    Temat: Re: Chyba padł mi dysk
    Od: Olaf Frikiov Skiorvensen <B...@i...invalid>

    Wcale nie przypadkiem, dnia Tue, 22 Sep 2020 18:00:08 +0200
    doszła do mnie wiadomość <5f6a1f88$0$554$65785112@news.neostrada.pl>
    od Smok Eustachy <s...@w...pl> :
    > A tu wynik diagnostyki:
    >Ktoś się zna na tym? Co się dzieje?

    Jeszcze nie padł, ale jest na dobrej drodze:


    > 5 Reallocated_Sector_Ct PO--CK 200 200 140 - 0
    Zero sektorów reallokował.

    >187 Reported_Uncorrect -O--CK 009 009 000 - 91
    >188 Command_Timeout -O--CK 018 018 000 - 82
    Coś chciał robić, ale nie skończył w spodziewanym czasie

    >196 Reallocated_Event_Count -O--CK 200 200 000 - 0
    >197 Current_Pending_Sector -O--CK 200 200 000 - 5
    Pięć w kolejce do reallokacji

    >198 Offline_Uncorrectable ----CK 200 200 000 - 4
    >200 Multi_Zone_Error_Rate ---R-- 200 200 000 - 3
    To nie wygląda dobrze(głowica rozkalibrowana?).

    Generalnie to polecam MHDD lub Victoria for Windows(po uprzednim przeczytaniu
    tutoriali z
    sieci). Dysk sam nie poradzi sobie z reallokacją, można mu ją wymusić za pomocą ww
    programów, oczywiście ilość tych sektorów może rosnąć w czasie skanowania, tak czy
    inaczej po "naprawie" radzę zgrać dane na coś innego, a ten dysk kilka-kilkanaście
    razy
    nadpisać zerami i zobaczyć, czy jakaś z wymienionych pozycji SMART będzie rosnąć,
    jeśli
    będzie, to dysk na emeryturę.


    v
    --
    Gdyby się wysadziło ich planety, zburzyło miasta,
    spaliło księgi, a ich samych wytłukło do nogi,
    może udałoby się ocalić naukę miłości bliźniego. SL.


  • 4. Data: 2020-09-22 20:28:53
    Temat: Re: Chyba padł mi dysk
    Od: Smok Eustachy <s...@w...pl>

    W dniu 22.09.2020 o 18:11, _Master_ pisze:
    > W dniu 2020-09-22 o 18:00, Smok Eustachy pisze:
    >>      A tu wynik diagnostyki:
    >> Ktoś się zna na tym? Co się dzieje?
    >
    > A widzisz jakieś objawy?
    >
    >
    Nie ładuje mi się partycja moja kochana z danymi. System jej nie widzi.
    > I pytanie kontrolne:
    >
    > Robisz backupy czy będziesz robił backupy?

    Robię. Jak ten dysk mi padnie to musże nowy kupić.


  • 5. Data: 2020-09-22 20:30:04
    Temat: Re: Chyba padł mi dysk
    Od: Smok Eustachy <s...@w...pl>

    W dniu 22.09.2020 o 18:26, Olaf Frikiov Skiorvensen pisze:
    /..../
    > Generalnie to polecam MHDD lub Victoria for Windows(po uprzednim przeczytaniu
    tutoriali z
    > sieci). Dysk sam nie poradzi sobie z reallokacją, można mu ją wymusić za pomocą ww
    > programów, oczywiście ilość tych sektorów może rosnąć w czasie skanowania, tak czy
    > inaczej po "naprawie" radzę zgrać dane na coś innego, a ten dysk kilka-kilkanaście
    razy
    > nadpisać zerami i zobaczyć, czy jakaś z wymienionych pozycji SMART będzie rosnąć,
    jeśli
    > będzie, to dysk na emeryturę.
    >
    A ja ni mam Windowsa chyba.
    >
    > v
    >


  • 6. Data: 2020-09-22 21:12:27
    Temat: Re: Chyba padł mi dysk
    Od: _Master_ <M...@...pl>

    Jak czujesz niepokój to kup już.

    Żadne logi Ci nie zagwarantują że dysk jutro nie padnie.

    Szkoda życia ;-)

    HDD i zasilacze się psują. Trzeba się z tym pogodzić ;-)


  • 7. Data: 2020-09-22 21:39:24
    Temat: Re: Chyba padł mi dysk
    Od: pioruns <w...@w...com>

    On 22/09/2020 17:26, Olaf Frikiov Skiorvensen wrote:
    > Generalnie to polecam MHDD lub Victoria for Windows(po uprzednim przeczytaniu
    tutoriali z
    > sieci). Dysk sam nie poradzi sobie z reallokacją, można mu ją wymusić za pomocą ww
    > programów, oczywiście ilość tych sektorów może rosnąć w czasie skanowania, tak czy
    > inaczej po "naprawie" radzę zgrać dane na coś innego, a ten dysk kilka-kilkanaście
    razy
    > nadpisać zerami i zobaczyć, czy jakaś z wymienionych pozycji SMART będzie rosnąć,
    jeśli
    > będzie, to dysk na emeryturę.

    Do naprawy takich problemów tylko Spinrite od Steve'a Gibsona. Koszt
    $89. Mi naprawił już dziesiątki dysków. Ostatnie perełki to dwa 1TB
    Hitachi, które miały po 1500 realokowanych sektorów i uptime po 8 lat,
    aż w końcu przyszedł czas na wymianę na większe, tak to by pracowały
    dalej. Nie wyobrażam sobie dysku nie przejechanego Spinritem który by
    działał z taką ilością badów i nie miał żadnych problemów.

    --
    pozdrawiam, pioruns
    _,.-'~'-.,__,.-'~'-.,__,.-'~'-.,__,.
    Registered Linux User #454644


  • 8. Data: 2020-09-22 23:07:47
    Temat: Re: Chyba padł mi dysk
    Od: Animka <a...@t...ja.wp.pl>

    W dniu 2020-09-22 o 20:28, Smok Eustachy pisze:
    > Nie ładuje mi się partycja moja kochana z danymi. System jej nie widzi.

    Zaglądałeś we właściwości i uprawnienia tej partycji? Może coś zmieniłeś.
    A w Zarzšdzaniu komputerem dyski to co tam jest?




    --
    animka


  • 9. Data: 2020-09-22 23:09:52
    Temat: Re: Chyba padł mi dysk
    Od: Olaf Frikiov Skiorvensen <B...@i...invalid>

    Wcale nie przypadkiem, dnia Tue, 22 Sep 2020 20:30:04 +0200
    doszła do mnie wiadomość <5f6a42ac$0$17356$65785112@news.neostrada.pl>
    od Smok Eustachy <s...@w...pl> :
    >W dniu 22.09.2020 o 18:26, Olaf Frikiov Skiorvensen pisze:
    >/..../
    >> Generalnie to polecam MHDD lub Victoria for Windows(po uprzednim przeczytaniu
    tutoriali z
    >> sieci). Dysk sam nie poradzi sobie z reallokacją, można mu ją wymusić za pomocą ww
    >> programów, oczywiście ilość tych sektorów może rosnąć w czasie skanowania, tak czy
    >> inaczej po "naprawie" radzę zgrać dane na coś innego, a ten dysk kilka-kilkanaście
    razy
    >> nadpisać zerami i zobaczyć, czy jakaś z wymienionych pozycji SMART będzie rosnąć,
    jeśli
    >> będzie, to dysk na emeryturę.
    >>
    >A ja ni mam Windowsa chyba.

    MHDD jest na System Rescue CD, spokojnie odpalisz z pena.
    https://www.system-rescue.org/
    Pod Linuxem jest WHDD, ale nie wiem, czy to naprawi(nie sprawdzałem)
    Jeszcze HDAT2, jest w formie ISO
    https://www.hdat2.com/
    Piorunus proponuje SpinRite - potrai naprawić takie błędy, ale jest płatny.
    Ja proponuję MHDD z SystemRescueCD, oczywiście po przeczytaniu tutoriala.
    --
    Gdyby się wysadziło ich planety, zburzyło miasta,
    spaliło księgi, a ich samych wytłukło do nogi,
    może udałoby się ocalić naukę miłości bliźniego. SL.


  • 10. Data: 2020-09-22 23:22:11
    Temat: Re: Chyba padł mi dysk
    Od: Olaf Frikiov Skiorvensen <B...@i...invalid>

    Wcale nie przypadkiem, dnia Tue, 22 Sep 2020 20:39:24 +0100
    doszła do mnie wiadomość <rkdjtc$84g$1$pioruns@news.chmurka.net>
    od pioruns <w...@w...com> :
    >On 22/09/2020 17:26, Olaf Frikiov Skiorvensen wrote:
    >> Generalnie to polecam MHDD lub Victoria for Windows(po uprzednim przeczytaniu
    tutoriali z
    >> sieci). Dysk sam nie poradzi sobie z reallokacją, można mu ją wymusić za pomocą ww
    >> programów, oczywiście ilość tych sektorów może rosnąć w czasie skanowania, tak czy
    >> inaczej po "naprawie" radzę zgrać dane na coś innego, a ten dysk kilka-kilkanaście
    razy
    >> nadpisać zerami i zobaczyć, czy jakaś z wymienionych pozycji SMART będzie rosnąć,
    jeśli
    >> będzie, to dysk na emeryturę.
    >
    >Do naprawy takich problemów tylko Spinrite od Steve'a Gibsona. Koszt
    >$89. Mi naprawił już dziesiątki dysków. Ostatnie perełki to dwa 1TB
    >Hitachi, które miały po 1500 realokowanych sektorów i uptime po 8 lat,
    >aż w końcu przyszedł czas na wymianę na większe, tak to by pracowały
    >dalej. Nie wyobrażam sobie dysku nie przejechanego Spinritem który by
    >działał z taką ilością badów i nie miał żadnych problemów.

    SpinRite potrafi(oprócz testu odczytu i opdzyskiwania danych) robić test zapisu
    wcześniej
    kopiując dane sektora w inne miejsce(chwilowo), w zasadzie tylko tym się różni od
    pozostałych wymienionych programów, no i oczywiście jest płatny.
    Ostatnio naprawiałem znajomej dysk z laptopa za pomocą Victorii, początkowy stan jak
    u
    Smoka, końcowy - 2408 reallokowanych sektorów - dysk będzie do wymiany niebawem.
    --
    Gdyby się wysadziło ich planety, zburzyło miasta,
    spaliło księgi, a ich samych wytłukło do nogi,
    może udałoby się ocalić naukę miłości bliźniego. SL.

strony : [ 1 ] . 2 ... 5


Szukaj w grupach

Szukaj w grupach

Eksperci egospodarka.pl

1 1 1

Wpisz nazwę miasta, dla którego chcesz znaleźć jednostkę ZUS.

Wzory dokumentów

Bezpłatne wzory dokumentów i formularzy.
Wyszukaj i pobierz za darmo: