[SOLVED]Smartmontools - pomoc przy interpretacji wyników testu

Tylko tematy nie mieszczące się powyżej.
Awatar użytkownika
Kamuisan
Serdeczny Borsuk
Serdeczny Borsuk
Posty: 198
Rejestracja: 20 kwie 2008, 23:05
Płeć: Mężczyzna
Wersja Ubuntu: 16.04
Środowisko graficzne: Xfce
Architektura: x86
Lokalizacja: Olsztyn

[SOLVED]Smartmontools - pomoc przy interpretacji wyników testu

Post autor: Kamuisan » 18 gru 2018, 20:17

Witam!
Przeprowadziłem test starego dysku w laptopie, ale nie jestem w stanie wywnioskować czy jest źle czy dobrze i ewentualnie jak bardzo jest źle. Jeżeli ktoś miałby chwilę zerknąć na wyniki testów i powiedzieć jak to wygląda, będę wdzięczny.

Kod: Zaznacz cały

root@kamuisan:/home/kamuisan# smartctl -a /dev/sda
smartctl 6.6 2016-05-31 r4324 [i686-linux-4.18.0-12-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Fujitsu MHY BH
Device Model:     FUJITSU MHY2120BH
Serial Number:    K410T7B2HG45
LU WWN Device Id: 5 00000e 041324dde
Firmware Version: 890B
User Capacity:    120 034 123 776 bytes [120 GB]
Sector Size:      512 bytes logical/physical
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS T13/1699-D revision 3f
SATA Version is:  SATA 2.5, 1.5 Gb/s
Local Time is:    Tue Dec 18 20:07:39 2018 CET
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:                (  487) 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:        (  69) minutes.
SCT capabilities:              (0x003f) 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     0x000f   100   100   046    Pre-fail  Always       -       118999
  2 Throughput_Performance  0x0005   100   100   030    Pre-fail  Offline      -       27066368
  3 Spin_Up_Time            0x0003   100   100   025    Pre-fail  Always       -       1
  4 Start_Stop_Count        0x0032   097   097   000    Old_age   Always       -       10628
  5 Reallocated_Sector_Ct   0x0033   100   100   024    Pre-fail  Always       -       0 (2000 0)
  7 Seek_Error_Rate         0x000f   100   100   047    Pre-fail  Always       -       2406
  8 Seek_Time_Performance   0x0005   100   100   019    Pre-fail  Offline      -       0
  9 Power_On_Hours          0x0032   080   080   000    Old_age   Always       -       10286
 10 Spin_Retry_Count        0x0013   100   100   020    Pre-fail  Always       -       0
 11 Calibration_Retry_Count 0x0032   253   099   000    Old_age   Always       -       1
 12 Power_Cycle_Count       0x0032   099   099   000    Old_age   Always       -       7930
182 Erase_Fail_Count_Total  0x0032   100   100   000    Old_age   Always       -       0
184 End-to-End_Error        0x0033   253   253   097    Pre-fail  Always       -       0
185 Unknown_Attribute       0x0010   100   100   000    Old_age   Offline      -       2
186 Unknown_Attribute       0x0032   253   253   000    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   100   094   000    Old_age   Always       -       17922898526216
188 Command_Timeout         0x0032   100   099   000    Old_age   Always       -       6
189 High_Fly_Writes         0x003a   253   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   071   045   000    Old_age   Always       -       29 (Min/Max 25/31)
191 G-Sense_Error_Rate      0x0032   253   098   000    Old_age   Always       -       16580652
192 Power-Off_Retract_Count 0x0032   095   095   000    Old_age   Always       -       85984544
193 Load_Cycle_Count        0x0032   097   097   000    Old_age   Always       -       72505
195 Hardware_ECC_Recovered  0x001a   100   100   000    Old_age   Always       -       3108
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0 (0 5992)
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x003e   200   253   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x000f   100   100   060    Pre-fail  Always       -       21889
203 Run_Out_Cancel          0x0002   100   100   000    Old_age   Always       -       429605454645
240 Transfer_Error_Rate     0x003e   200   200   000    Old_age   Always       -       0

SMART Error Log Version: 1
ATA Error Count: 12 (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 12 occurred at disk power-on lifetime: 9095 hours (378 days + 23 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
  -- -- -- -- -- -- --
  01 51 3f 31 e5 b9 4d  Error: AMNF 63 sectors at LBA = 0x0db9e531 = 230286641

  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 40 30 e5 b9 4d 00      01:49:54.743  READ DMA
  c8 00 01 50 00 71 42 00      01:49:54.247  READ DMA
  c8 00 01 00 00 00 40 00      01:49:54.247  READ DMA
  c8 00 01 00 00 00 40 00      01:49:54.247  READ DMA
  c8 00 01 00 00 00 40 00      01:49:54.243  READ DMA

Error 11 occurred at disk power-on lifetime: 9095 hours (378 days + 23 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 3f 31 e5 b9 4d  Error: UNC 63 sectors at LBA = 0x0db9e531 = 230286641

  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 40 30 e5 b9 4d 00      01:49:49.638  READ DMA
  c8 00 40 f0 e4 b9 4d 00      01:49:49.637  READ DMA
  c8 00 40 b0 e4 b9 4d 00      01:49:49.635  READ DMA
  c8 00 40 70 e4 b9 4d 00      01:49:49.634  READ DMA
  c8 00 40 30 e4 b9 4d 00      01:49:49.633  READ DMA

Error 10 occurred at disk power-on lifetime: 9049 hours (377 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 07 31 e5 b9 ed  Error: UNC 7 sectors at LBA = 0x0db9e531 = 230286641

  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 30 e5 b9 ed 08      00:40:59.806  READ DMA
  c8 00 18 28 d0 b9 ed 08      00:40:59.806  READ DMA
  c8 00 20 e0 cc b9 ed 08      00:40:59.792  READ DMA
  c8 00 08 80 97 08 eb 08      00:40:59.792  READ DMA
  c8 00 08 58 97 08 eb 08      00:40:59.769  READ DMA

Error 9 occurred at disk power-on lifetime: 8841 hours (368 days + 9 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
  -- -- -- -- -- -- --
  84 51 00 0f 08 00 40  Error: ICRC, ABRT at LBA = 0x0000080f = 2063

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 03 10 00 08 00 40 00      00:00:03.129  READ DMA EXT
  25 03 01 02 00 00 40 00      00:00:02.895  READ DMA EXT
  25 03 04 07 00 00 40 00      00:00:02.893  READ DMA EXT
  25 03 01 c1 07 00 40 00      00:00:02.883  READ DMA EXT
  25 03 01 00 00 00 40 00      00:00:02.882  READ DMA EXT

Error 8 occurred at disk power-on lifetime: 6916 hours (288 days + 4 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
  -- -- -- -- -- -- --
  84 51 00 09 00 00 40  Error: ICRC, ABRT at LBA = 0x00000009 = 9

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 03 08 02 00 00 40 00      00:00:02.802  READ DMA EXT
  25 03 01 00 00 00 40 00      00:00:02.799  READ DMA EXT
  25 03 01 00 00 00 40 00      00:00:02.792  READ DMA EXT
  25 03 01 00 00 00 40 00      00:00:02.791  READ DMA EXT
  25 03 01 00 00 00 40 00      00:00:02.790  READ DMA EXT

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%      9094         230286641
# 2  Short offline       Aborted by host               90%      9094         -
# 3  Extended offline    Completed without error       00%      6384         -
# 4  Short offline       Completed without error       00%      6383         -
# 5  Short offline       Aborted by host               80%        26         -

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.

root@kamuisan:/home/kamuisan# smartctl -t short /dev/sda
smartctl 6.6 2016-05-31 r4324 [i686-linux-4.18.0-12-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF OFFLINE IMMEDIATE AND SELF-TEST SECTION ===
Sending command: "Execute SMART Short self-test routine immediately in off-line mode".
Drive command "Execute SMART Short self-test routine immediately in off-line mode" successful.
Testing has begun.
Please wait 2 minutes for test to complete.
Test will complete after Tue Dec 18 20:13:24 2018

Use smartctl -X to abort test.
root@kamuisan:/home/kamuisan# smartctl -l selftest
smartctl 6.6 2016-05-31 r4324 [i686-linux-4.18.0-12-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

ERROR: smartctl requires a device name as the final command-line argument.


Use smartctl -h to get a usage summary

Kod: Zaznacz cały

root@kamuisan:/home/kamuisan# smartctl -l selftest /dev/sda
smartctl 6.6 2016-05-31 r4324 [i686-linux-4.18.0-12-generic] (local build)
Copyright (C) 2002-16, 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  Short offline       Completed: read failure       90%      9094         230286641
# 2  Short offline       Aborted by host               90%      9094         -
# 3  Extended offline    Completed without error       00%      6384         -
# 4  Short offline       Completed without error       00%      6383         -
# 5  Short offline       Aborted by host               80%        26         -

Ostatnio zmieniony 22 gru 2018, 12:33 przez Kamuisan, łącznie zmieniany 1 raz.
Registered Linux user #498194
Awatar użytkownika
mario_7
Administrator
Administrator
Posty: 7678
Rejestracja: 30 sie 2006, 13:11
Płeć: Mężczyzna
Wersja Ubuntu: 18.04
Środowisko graficzne: GNOME
Architektura: x86_64

Re: Smartmontools - pomoc przy interpretacji wyników testu

Post autor: mario_7 » 21 gru 2018, 22:38

Jest dobrze. Brak złych sektorów, nie wykazuje problemów mechanicznych.
Jeśli chcesz zrozumieć co poszczególne pozycje znaczą, to zajrzyj tutaj: https://en.m.wikipedia.org/wiki/S.M.A.R ... attributes
Czytelnia - poczytaj, Google - poszukaj
Awatar użytkownika
jacekalex
Gibki Gibbon
Gibki Gibbon
Posty: 4108
Rejestracja: 17 cze 2007, 02:54
Płeć: Mężczyzna
Wersja Ubuntu: inny OS
Środowisko graficzne: MATE
Architektura: x86_64

Re: Smartmontools - pomoc przy interpretacji wyników testu

Post autor: jacekalex » 22 gru 2018, 01:39

Zainteresuj się tym skryptem:

Kod: Zaznacz cały

#!/bin/bash


SMARTCTL=`which smartctl 2>/dev/null`

if [ -z $SMARTCTL ] || [ ! -x $SMARTCTL ]; then
 echo "It seems you have no smartmontools installed. "
 echo "Invoke 'apt install smartmontools' and re-run script"
 exit 1
fi

function check {
tmp_parm=`mktemp`
tmp_name=`mktemp`
$SMARTCTL -A $1 | sed -r 's/^\s+//g' > $tmp_parm
$SMARTCTL -i $1| sed -r 's/^\s+//g' > $tmp_name

echo -e $1 - `egrep -m1 "Model " $tmp_name | awk '{$1="";$2=""; print  "Model:   "$0}'`
echo -e $1 - `egrep -m1 "Device " $tmp_name | awk '{$1="";$2=""; print "Symbol:  "$0}'`
echo -e $1 - `egrep -m1 "Serial " $tmp_name | awk '{$1="";$2=""; print "Seria:   "$0}'`

for val in 9 5 10 11 171 172 177 181 187 188 196 197 198 199 200 231 ; do
 print=`egrep "^$val " $tmp_parm | awk '{ print $2" = "$10 }'`
  if [ ! -z "$print" ]; then
   echo -n "$1: "
  if  [[ `echo $print | grep "Power_On_Hours" ` ]]; then
   echo -e "\033[36;2m$print\033[0m"
  elif [ `echo $print | awk '{ print $3 }'` != 0 ]; then
   echo -e "\033[31;2m$print\033[0m"
  else
   echo -e "\033[32;2m$print\033[0m"
  fi
 fi
done

echo


rm -f $tmp_parm
rm -r $tmp_name

}

if [ $# -gt 0 ]; then
 devices=$@
else
 devices=`ls /dev/sd[a-z] 2>/dev/null ; ls /dev/nvme[0-9]n[0-9] 2>/dev/null`
fi

echo
if [ -b /dev/twe0 ]; then
 check "-d 3ware,0 /dev/twe0"
 check "-d 3ware,1 /dev/twe0"
else
 for d in $devices; do
  check $d
 done
fi
Wyświetla najważniejsze parametry świadczące o chorobie dyzia w dużo czytelniejszej formie.

Przy okazji pamiętaj, że co producent dysku to inna specyfikacja danych smart, także dane z testu smartmontools mogą nie być zbyt nieomylne, zwłaszcza przy różnych dyskach SSD.

Dlatego lepiej być w grupie tych, co posiadają backup wszystkich istotnych i ważnych danych,
aniżeli w grupie tych, co będą taki backup posiadać w przyszłości. :twisted:


U mnie wynik wygląda tak:

Kod: Zaznacz cały

# G1 ###   sob gru 22 01:31:26  domek : ~ 
root ~> smartcheck

/dev/sda - Model: Seagate Barracuda ES
/dev/sda - Symbol: ST3400620NS
/dev/sda - Seria: 9QH0BX9K
/dev/sda: Power_On_Hours = 43422
/dev/sda: Reallocated_Sector_Ct = 0
/dev/sda: Spin_Retry_Count = 0
/dev/sda: Reported_Uncorrect = 0
/dev/sda: Current_Pending_Sector = 0
/dev/sda: Offline_Uncorrectable = 0
/dev/sda: UDMA_CRC_Error_Count = 0
/dev/sda: Multi_Zone_Error_Rate = 0

/dev/sdb -
/dev/sdb - Symbol: WDC WD1005FBYZ-01YCBB2
/dev/sdb - Seria: WD-WMC6M0J4VTSU
/dev/sdb: Power_On_Hours = 4529
/dev/sdb: Reallocated_Sector_Ct = 0
/dev/sdb: Spin_Retry_Count = 0
/dev/sdb: Calibration_Retry_Count = 0
/dev/sdb: Reallocated_Event_Count = 0
/dev/sdb: Current_Pending_Sector = 0
/dev/sdb: Offline_Uncorrectable = 0
/dev/sdb: UDMA_CRC_Error_Count = 0
/dev/sdb: Multi_Zone_Error_Rate = 0
Pozdro
:craz:
Problemy rozwiązujemy na forum nie na PW -> Niech inni na tym skorzystają.
Komputer jest jak klimatyzacja - gdy otworzysz okna, robi się bezużyteczny...
Linux User #499936
Inny OS: Gentoo Linux :)
ODPOWIEDZ

Wróć do „Inne”

Kto jest online

Użytkownicy przeglądający to forum: Obecnie na forum nie ma żadnego zarejestrowanego użytkownika i 6 gości