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 26/01/2018, à 14:01

elekaj34

[resolu] Disque HS mais sans l'être ?

Bonjour,

Sur l'un de mes disques, lorsque je lance un exécutable, j'ai droit a un "crash" du disque. L'application plante (ou se fige) et le disque apparaît comme déconnecté. Il faut que je redémarre pour le voir de nouveau. A priori, copier des fichiers fonctionne.

Désolé pour la longueur du post, mais j'ai essayé de mettre pas mal de logs significatifs et surtout essayé d'être exhaustif !

Après plantage, je lorgne ce que me raconte dmesg :

[ 1109.515381] ata6: limiting SATA link speed to 1.5 Gbps
[ 1109.515383] ata6.00: exception Emask 0x10 SAct 0x40000001 SErr 0x280100 action 0x6 frozen
[ 1109.515385] ata6.00: irq_stat 0x08000000, interface fatal error
[ 1109.515387] ata6: SError: { UnrecovData 10B8B BadCRC }
[ 1109.515388] ata6.00: failed command: READ FPDMA QUEUED
[ 1109.515390] ata6.00: cmd 60/00:00:1f:2f:8c/01:00:24:00:00/40 tag 0 ncq dma 131072 in
                        res 40/00:f0:1f:2e:8c/00:00:24:00:00/40 Emask 0x10 (ATA bus error)
[ 1109.515391] ata6.00: status: { DRDY }
[ 1109.515392] ata6.00: failed command: READ FPDMA QUEUED
[ 1109.515394] ata6.00: cmd 60/00:f0:1f:2e:8c/01:00:24:00:00/40 tag 30 ncq dma 131072 in
                        res 40/00:f0:1f:2e:8c/00:00:24:00:00/40 Emask 0x10 (ATA bus error)
[ 1109.515394] ata6.00: status: { DRDY }
[ 1109.515396] ata6: hard resetting link
[ 1109.829598] ata6: SATA link down (SStatus 0 SControl 310)
[ 1115.003269] ata6: hard resetting link
[ 1115.317509] ata6: SATA link down (SStatus 0 SControl 310)
[ 1120.379169] ata6: hard resetting link
[ 1120.693401] ata6: SATA link down (SStatus 0 SControl 310)
[ 1120.693405] ata6.00: disabled
[ 1120.693417] sd 5:0:0:0: [sde] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 1120.693419] sd 5:0:0:0: [sde] tag#0 Sense Key : Not Ready [current] 
[ 1120.693420] sd 5:0:0:0: [sde] tag#0 Add. Sense: Logical unit not ready, hard reset required
[ 1120.693421] sd 5:0:0:0: [sde] tag#0 CDB: Read(10) 28 00 24 8c 2f 1f 00 01 00 00
[ 1120.693422] blk_update_request: I/O error, dev sde, sector 613166879
[ 1120.693430] sd 5:0:0:0: rejecting I/O to offline device
[ 1120.693432] sd 5:0:0:0: [sde] killing request
[ 1120.693435] sd 5:0:0:0: [sde] tag#30 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 1120.693436] sd 5:0:0:0: [sde] tag#30 Sense Key : Not Ready [current] 
[ 1120.693436] sd 5:0:0:0: [sde] tag#30 Add. Sense: Logical unit not ready, hard reset required
[ 1120.693437] sd 5:0:0:0: [sde] tag#30 CDB: Read(10) 28 00 24 8c 2e 1f 00 01 00 00
[ 1120.693437] blk_update_request: I/O error, dev sde, sector 613166623
[ 1120.693442] ata6: EH complete
[ 1120.693448] sd 5:0:0:0: [sde] FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[ 1120.693448] sd 5:0:0:0: [sde] CDB: Write(10) 2a 00 1d 04 02 5f 00 00 30 00
[ 1120.693449] blk_update_request: I/O error, dev sde, sector 486802015
[ 1120.693457] ata6.00: detaching (SCSI 5:0:0:0)
[ 1120.693469] Aborting journal on device sde1-8.
[ 1120.693476] JBD2: Error -5 detected when updating journal superblock for sde1-8.
[ 1120.693653] EXT4-fs error (device sde1): ext4_journal_check_start:56: Detected aborted journal
[ 1120.693655] EXT4-fs (sde1): Remounting filesystem read-only
[ 1120.693656] EXT4-fs (sde1): previous I/O error to superblock detected
[ 1120.693669] EXT4-fs (sde1): ext4_writepages: jbd2_start: 9223372036854775807 pages, ino 664064; err -30
[ 1120.693695] blk_update_request: I/O error, dev sde, sector 0
[ 1120.701743] EXT4-fs error (device sde1): ext4_find_entry:1463: inode #6702693: comm X-Plane-x86_64: reading directory lblock 0
[ 1120.701748] EXT4-fs (sde1): previous I/O error to superblock detected
[ 1120.701779] EXT4-fs error (device sde1): ext4_find_entry:1463: inode #7617107: comm X-Plane-x86_64: reading directory lblock 0
[ 1120.701780] EXT4-fs (sde1): previous I/O error to superblock detected
[ 1120.701804] EXT4-fs error (device sde1): ext4_find_entry:1463: inode #6303953: comm X-Plane-x86_64: reading directory lblock 0
[ 1120.701805] EXT4-fs (sde1): previous I/O error to superblock detected
[ 1120.701828] EXT4-fs error (device sde1): ext4_find_entry:1463: inode #6181869: comm X-Plane-x86_64: reading directory lblock 0
[ 1120.701830] EXT4-fs (sde1): previous I/O error to superblock detected
[ 1120.701854] EXT4-fs error (device sde1): ext4_find_entry:1463: inode #17869185: comm X-Plane-x86_64: reading directory lblock 0
[ 1120.701856] EXT4-fs (sde1): previous I/O error to superblock detected
[ 1120.701881] EXT4-fs error (device sde1): ext4_find_entry:1463: inode #7486008: comm X-Plane-x86_64: reading directory lblock 0
[ 1120.701883] EXT4-fs (sde1): previous I/O error to superblock detected
[ 1120.701905] EXT4-fs error (device sde1): ext4_find_entry:1463: inode #9193441: comm X-Plane-x86_64: reading directory lblock 0
[ 1120.701907] EXT4-fs (sde1): previous I/O error to superblock detected
[ 1120.701935] EXT4-fs error (device sde1): ext4_find_entry:1463: inode #4732529: comm X-Plane-x86_64: reading directory lblock 0
[ 1120.701960] EXT4-fs error (device sde1): ext4_find_entry:1463: inode #5516794: comm X-Plane-x86_64: reading directory lblock 0
[ 1120.701983] EXT4-fs error (device sde1): ext4_find_entry:1463: inode #6182176: comm X-Plane-x86_64: reading directory lblock 0
[ 1120.702093] EXT4-fs warning (device sde1): dx_probe:742: inode #4730484: lblock 0: comm X-Plane-x86_64: error -5 reading directory block
[ 1120.702496] EXT4-fs warning (device sde1): dx_probe:742: inode #4596481: lblock 0: comm X-Plane-x86_64: error -5 reading directory block
[ 1120.703621] EXT4-fs warning (device sde1): dx_probe:742: inode #5519483: lblock 0: comm X-Plane-x86_64: error -5 reading directory block
[ 1120.703999] EXT4-fs warning (device sde1): ext4_dx_find_entry:1532: inode #787999: lblock 1: comm X-Plane-x86_64: error -5 reading directory block
[ 1120.704014] EXT4-fs warning (device sde1): ext4_dx_find_entry:1532: inode #787999: lblock 1: comm X-Plane-x86_64: error -5 reading directory block
[ 1120.704027] EXT4-fs warning (device sde1): ext4_dx_find_entry:1532: inode #787999: lblock 1: comm X-Plane-x86_64: error -5 reading directory block
[ 1120.704040] EXT4-fs warning (device sde1): ext4_dx_find_entry:1532: inode #787999: lblock 1: comm X-Plane-x86_64: error -5 reading directory block
[ 1120.704053] EXT4-fs warning (device sde1): ext4_dx_find_entry:1532: inode #787999: lblock 1: comm X-Plane-x86_64: error -5 reading directory block
[ 1120.704067] EXT4-fs warning (device sde1): ext4_dx_find_entry:1532: inode #787999: lblock 1: comm X-Plane-x86_64: error -5 reading directory block
[ 1120.704081] EXT4-fs warning (device sde1): ext4_dx_find_entry:1532: inode #787999: lblock 1: comm X-Plane-x86_64: error -5 reading directory block
[ 1120.705708] sd 5:0:0:0: [sde] Synchronizing SCSI cache
[ 1120.705726] sd 5:0:0:0: [sde] Synchronize Cache(10) failed: Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[ 1120.705727] sd 5:0:0:0: [sde] Stopping disk
[ 1120.705728] sd 5:0:0:0: [sde] Start/Stop Unit failed: Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK

Là je me dis que çà sent pas bon et je lance un  smartctl -a /dev/sde avec le retour suivant :

smartctl 6.5 2016-01-24 r4214 [x86_64-linux-4.10.0-42-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Barracuda 7200.14 (AF)
Device Model:     ST500DM002-1BD142
Serial Number:    W2AK6MVC
LU WWN Device Id: 5 000c50 05c989dbf
Firmware Version: KC45
User Capacity:    500 107 862 016 bytes [500 GB]
Sector Sizes:     512 bytes logical, 4096 bytes 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 3.0, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is:    Fri Jan 26 11:49:19 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:  (0x82)	Offline data collection activity
					was completed without error.
					Auto Offline Data Collection: Enabled.
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: 		(  609) seconds.
Offline data collection
capabilities: 			 (0x7b) SMART execute Offline immediate.
					Auto Offline data collection on/off support.
					Suspend Offline collection upon new
					command.
					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: 	 (  83) minutes.
Conveyance self-test routine
recommended polling time: 	 (   2) minutes.
SCT capabilities: 	       (0x303f)	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   107   099   006    Pre-fail  Always       -       215120
  3 Spin_Up_Time            0x0003   100   097   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   099   099   020    Old_age   Always       -       1696
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   085   060   030    Pre-fail  Always       -       364740484
  9 Power_On_Hours          0x0032   079   079   000    Old_age   Always       -       18986
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   099   099   020    Old_age   Always       -       1667
183 Runtime_Bad_Block       0x0032   097   097   000    Old_age   Always       -       3
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
188 Command_Timeout         0x0032   100   098   000    Old_age   Always       -       32 32 105
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   067   052   045    Old_age   Always       -       33 (Min/Max 18/45)
194 Temperature_Celsius     0x0022   033   048   000    Old_age   Always       -       33 (0 13 0 0 0)
195 Hardware_ECC_Recovered  0x001a   039   021   000    Old_age   Always       -       215120
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   199   000    Old_age   Always       -       6194
240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       19008h+15m+35.035s
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       2766948400
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       2846364616

SMART Error Log Version: 1
No Errors Logged

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 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.

A priori, pas de secteurs défecteux et je tente une réparation de la partition :

# e2fsck -C0 -f -v /dev/sde1
e2fsck 1.42.13 (17-May-2015)
Passe 1 : vérification des i-noeuds, des blocs et des tailles
Passe 2 : vérification de la structure des répertoires                         
Passe 3 : vérification de la connectivité des répertoires                      
Passe 4 : vérification des compteurs de référence
Passe 5 : vérification de l'information du sommaire de groupe                  
                                                                               
      379847 i-noeuds utilisés (1.24%, sur 30583008)
        3356 fichiers non contigus (0.9%)
          85 répertoires non contigus (0.0%)
             nombre d'i-noeuds avec des blocs ind/dind/tind : 0/0/0
             Histogramme des profondeurs d'extents : 378872/17
    83806062 blocs utilisés (68.64%, sur 122093568)
           0 bloc défectueux
           1 fichier de grande taille

      365379 fichiers normaux
       13390 répertoires
           0 fichier de périphérique en mode caractère
           0 fichier de périphérique en mode bloc
           0 fifo
           0 lien
        1069 liens symboliques (950 liens symboliques rapides)
           0 socket
------------
      379838 fichiers

A priori, pas de problèmes rencontrés au check du disque.
Mais lancer une application stockée sur la partition /dev/sde1 plante toujours.

Bref j'en perds mon latin yikes et ne sait pas trop si mon disque est HS ou pas !

PS : Là je tente un backup de toutes les données sur un autre disque.

Dernière modification par elekaj34 (Le 26/01/2018, à 18:53)


Alain - Linux Ubuntu 18.04 LTS 64bits
Lumières d'Ici ... et d'Ailleurs

Hors ligne

#2 Le 26/01/2018, à 14:32

inbox

Re : [resolu] Disque HS mais sans l'être ?

Salut,

Il semble qu'il y ai un problème électromécanique. De plus ce disque à fonctionné environ 19000 heures.

Je dirais qu'il est plutôt usé.

Tu peux tout de même vérifier que la connectique est OK. S'il t'est possible essaye avec un autre câble Sata.

A+


Un problème résolu ? Indiquez le en modifiant le titre du sujet.

Hors ligne

#3 Le 26/01/2018, à 18:53

elekaj34

Re : [resolu] Disque HS mais sans l'être ?

Bonsoir,

Merci pour l'idée du câble big_smile parce-que çà vient bien de çà en effet yikes
Bizarrement, je n'ai pas touché l'intérieur de mon PC depuis des mois  et j'avoue que j'ai du mal à comprendre qu'un câble puisse "s'user" sans le manipuler !

inbox a écrit :

Salut,
De plus ce disque à fonctionné environ 19000 heures.
Je dirais qu'il est plutôt usé.

Alors tu va t'affoler pour le second disque (/dev/sdb) qui a 89600 heures au compteur (j'aimerais bien savoir s'il va passer les 100 000 heures) wink


Alain - Linux Ubuntu 18.04 LTS 64bits
Lumières d'Ici ... et d'Ailleurs

Hors ligne