Contenu | Rechercher | Menus

Annonce

Si vous avez des soucis pour rester connecté, déconnectez-vous puis reconnectez-vous depuis ce lien en cochant la case
Me connecter automatiquement lors de mes prochaines visites.

À propos de l'équipe du forum.

#1 Le 03/03/2021, à 17:07

yayou

Test état Hdd avec smartmontools

J'ai remarqué des anomalie en branchant un de mes Hdd. J'ai donc choisi de faire une vérification son état avec smartmontools. Ca a donné ça:

smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.4.0-66-generic] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF READ SMART DATA SECTION ===
SMART Error Log Version: 1
ATA Error Count: 393 (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 393 occurred at disk power-on lifetime: 272 hours (11 days + 8 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 06 89 00 40 e8  Error: UNC 6 sectors at LBA = 0x08400089 = 138412169

  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 00 06 89 00 40 e0 00      01:04:26.202  READ DMA EXT
  ef 03 45 00 00 00 a0 00      01:04:26.201  SET FEATURES [Set transfer mode]
  ff ff ff ff ff ff ff 0c      01:04:26.190  [VENDOR SPECIFIC]
  25 00 02 87 00 40 e0 00      01:04:25.369  READ DMA EXT
  ef 03 45 00 00 00 a0 00      01:04:25.368  SET FEATURES [Set transfer mode]

Error 392 occurred at disk power-on lifetime: 272 hours (11 days + 8 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 01 88 00 40 e8  Error: UNC 1 sectors at LBA = 0x08400088 = 138412168

  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 00 02 87 00 40 e0 00      01:04:25.369  READ DMA EXT
  ef 03 45 00 00 00 a0 00      01:04:25.368  SET FEATURES [Set transfer mode]
  ff ff ff ff ff ff ff 0c      01:04:25.357  [VENDOR SPECIFIC]
  25 00 06 89 00 40 e0 00      01:04:25.091  READ DMA EXT
  ef 03 45 00 00 00 a0 00      01:04:25.090  SET FEATURES [Set transfer mode]

Error 391 occurred at disk power-on lifetime: 272 hours (11 days + 8 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 06 89 00 40 e8  Error: UNC 6 sectors at LBA = 0x08400089 = 138412169

  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 00 06 89 00 40 e0 00      01:04:25.091  READ DMA EXT
  ef 03 45 00 00 00 a0 00      01:04:25.090  SET FEATURES [Set transfer mode]
  ff ff ff ff ff ff ff 0c      01:04:25.079  [VENDOR SPECIFIC]
  25 00 02 87 00 40 e0 00      01:04:24.829  READ DMA EXT
  25 00 06 81 00 40 e0 00      01:04:24.829  READ DMA EXT

Error 390 occurred at disk power-on lifetime: 272 hours (11 days + 8 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 01 88 00 40 e8  Error: UNC 1 sectors at LBA = 0x08400088 = 138412168

  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 00 02 87 00 40 e0 00      01:04:24.829  READ DMA EXT
  25 00 06 81 00 40 e0 00      01:04:24.829  READ DMA EXT
  25 00 02 7f 00 40 e0 00      01:04:24.828  READ DMA EXT
  25 00 06 79 00 40 e0 00      01:04:24.828  READ DMA EXT
  25 00 02 77 00 40 e0 00      01:04:24.806  READ DMA EXT

Error 389 occurred at disk power-on lifetime: 272 hours (11 days + 8 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 80 3f 00 80 ec  Error: UNC 128 sectors at LBA = 0x0c80003f = 209715263

  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 00 80 3f 00 80 e0 00      01:04:17.357  READ DMA EXT
  25 00 80 3f 00 40 e0 00      01:04:17.343  READ DMA EXT
  25 00 80 3f 00 00 e0 00      01:04:17.332  READ DMA EXT
  25 00 80 3f 00 c0 e0 00      01:04:17.317  READ DMA EXT
  25 00 80 3f 00 80 e0 00      01:04:17.296  READ DMA EXT

Est ce grave docteur?

Hors ligne

#2 Le 03/03/2021, à 21:52

Nuliel

Re : Test état Hdd avec smartmontools

Il manque la moitié du rapport smart. Je te laisse donner la première partie avec

sudo smartctl -a /dev/sdX

en remplaçant /dev/sdX par le bon disque

Hors ligne