Disque dur qui plante

Fermé
KunGu Messages postés 1169 Date d'inscription vendredi 7 septembre 2007 Statut Membre Dernière intervention 17 mars 2013 - 16 mars 2013 à 18:10
KunGu Messages postés 1169 Date d'inscription vendredi 7 septembre 2007 Statut Membre Dernière intervention 17 mars 2013 - 17 mars 2013 à 00:31
Bonjour tout le monde,

J'ai un PC sous ubuntu, dessus tourne un programme qui enregistre des images de caméras sur un disque.

Au bout d'un moment le programme plante, et je m'aperçois que je ne peux plus accéder au disque (monté dans /media) : "ls: lecture du répertoire /media/DD2Cameras/: Erreur d'entrée/sortie"

J'ai copié le dmesg, qui m'indique ceci :

[ 2366.894603] ata4.00: exception Emask 0x12 SAct 0x0 SErr 0x1f80501 action 0x6
[ 2366.895261] ata4.00: BMDMA stat 0x5
[ 2366.895564] ata4: SError: { RecovData UnrecovData Proto 10B8B Dispar BadCRC Handshk LinkSeq TrStaTrns }
[ 2366.896435] ata4.00: failed command: WRITE DMA EXT
[ 2366.896858] ata4.00: cmd 35/00:e0:df:fb:08/00:00:1a:00:00/e0 tag 0 dma 114688 out
[ 2366.896861]          res 51/84:e0:df:fb:08/84:00:1a:00:00/e0 Emask 0x12 (ATA bus error)
[ 2366.898224] ata4.00: status: { DRDY ERR }
[ 2366.898569] ata4.00: error: { ICRC ABRT }
[ 2366.898929] ata4: hard resetting link
[ 2367.216126] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 2367.232494] ata4.00: configured for UDMA/133
[ 2367.232534] ata4: EH complete
[ 2437.008122] ata4.00: exception Emask 0x12 SAct 0x0 SErr 0x1b80500 action 0x6 frozen
[ 2437.008830] ata4: SError: { UnrecovData Proto 10B8B Dispar BadCRC LinkSeq TrStaTrns }
[ 2437.009526] ata4.00: failed command: WRITE DMA EXT
[ 2437.009954] ata4.00: cmd 35/00:00:5f:18:09/00:02:1a:00:00/e0 tag 0 dma 262144 out
[ 2437.009957]          res 40/00:e0:df:fb:08/84:00:1a:00:00/e0 Emask 0x16 (ATA bus error)
[ 2437.011328] ata4.00: status: { DRDY }
[ 2437.011654] ata4: hard resetting link
[ 2437.328113] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 2437.362965] ata4.00: failed to IDENTIFY (I/O error, err_mask=0x2)
[ 2437.362975] ata4.00: revalidation failed (errno=-5)
[ 2442.328077] ata4: hard resetting link
[ 2442.648158] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 2442.672539] ata4.00: configured for UDMA/133
[ 2442.672587] ata4: EH complete
[ 2502.741435] ata4.00: exception Emask 0x12 SAct 0x0 SErr 0x1f80500 action 0x6
[ 2502.742083] ata4.00: BMDMA stat 0x5
[ 2502.742392] ata4: SError: { UnrecovData Proto 10B8B Dispar BadCRC Handshk LinkSeq TrStaTrns }
[ 2502.743152] ata4.00: failed command: WRITE DMA EXT
[ 2502.743574] ata4.00: cmd 35/00:20:97:45:09/00:01:1a:00:00/e0 tag 0 dma 147456 out
[ 2502.743577]          res 51/84:00:b7:45:09/84:01:1a:00:00/e0 Emask 0x12 (ATA bus error)
[ 2502.744986] ata4.00: status: { DRDY ERR }
[ 2502.745330] ata4.00: error: { ICRC ABRT }


Et j'ai bien l'impression que tout ca se répète en boucle ..


Un peu plus loin j'ai ce genre de choses :

[ 2800.192036] Buffer I/O error on device sdc1, logical block 54603393
[ 2800.192036] Buffer I/O error on device sdc1, logical block 54603394
[ 2800.192036] Buffer I/O error on device sdc1, logical block 54603395
[ 2800.192036] Buffer I/O error on device sdc1, logical block 54603396
[ 2800.192036] Buffer I/O error on device sdc1, logical block 54603397
[ 2800.192036] Buffer I/O error on device sdc1, logical block 54603398
[ 2800.192036] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 13641390 (offset 0 size 24576 starting block 54603406)
[ 2800.231004] sd 3:0:0:0: rejecting I/O to offline device
[ 2800.256091] Aborting journal on device sdc1-8.
[ 2800.264096] sd 3:0:0:0: rejecting I/O to offline device
[ 2800.284194] sd 3:0:0:0: rejecting I/O to offline device
[ 2800.292125] sd 3:0:0:0: [sdc] READ CAPACITY(16) failed
[ 2800.292138] sd 3:0:0:0: [sdc]  Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[ 2800.292147] sd 3:0:0:0: [sdc] Sense not available.
[ 2800.292198] sd 3:0:0:0: rejecting I/O to offline device
[ 2800.303064] JBD2: I/O error detected when updating journal superblock for sdc1-8.
[ 2800.316106] sd 3:0:0:0: rejecting I/O to offline device
[ 2800.336194] JBD2: Detected IO errors while flushing file data on sdc1-8
[ 2800.340549] sd 3:0:0:0: rejecting I/O to offline device
[ 2800.356099] sd 3:0:0:0: [sdc] READ CAPACITY failed
[ 2800.356114] sd 3:0:0:0: [sdc]  Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[ 2800.356122] sd 3:0:0:0: [sdc] Sense not available.
[ 2800.356182] sd 3:0:0:0: rejecting I/O to offline device
[ 2800.372129] sd 3:0:0:0: rejecting I/O to offline device
[ 2800.388403] sd 3:0:0:0: rejecting I/O to offline device
[ 2800.404564] sd 3:0:0:0: rejecting I/O to offline device
[ 2800.412234] sd 3:0:0:0: rejecting I/O to offline device
[ 2800.424109] EXT4-fs error (device sdc1): ext4_journal_start_sb:327: Detected aborted journal
[ 2800.432547] EXT4-fs (sdc1): Remounting filesystem read-only
[ 2800.441024] EXT4-fs (sdc1): previous I/O error to superblock detected
[ 2800.460142] sd 3:0:0:0: [sdc] Asking for cache data failed
[ 2800.469306] sd 3:0:0:0: [sdc] Assuming drive cache: write through
[ 2800.478935] sd 3:0:0:0: rejecting I/O to offline device
[ 2800.492170] EXT4-fs (sdc1): ext4_da_writepages: jbd2_start: 1024 pages, ino 13641391; err -30
[ 2800.521239] sdc: detected capacity change from 1000204886016 to 0
[ 2800.521320] ata4.00: detaching (SCSI 3:0:0:0)
[ 2800.575790] journal commit I/O error
[ 2800.586843] journal commit I/O error
[ 2800.640727] journal commit I/O error
[ 2800.663107] journal commit I/O error
[ 2800.824879] journal commit I/O error
[ 2800.956726] journal commit I/O error
[ 2800.995310] journal commit I/O error
[ 2801.027795] sd 3:0:0:0: [sdc] Stopping disk
[ 2801.027888] sd 3:0:0:0: [sdc] START_STOP FAILED
[ 2801.027894] sd 3:0:0:0: [sdc]  Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[ 2810.368855] EXT4-fs error (device sdc1): ext4_find_entry:935: inode #13631489: comm zma: reading directory lblock 0
[ 2810.386059] EXT4-fs error (device sdc1): ext4_find_entry:935: inode #13631489: comm zma: reading directory lblock 0
[ 3700.642808] EXT4-fs error (device sdc1): ext4_find_entry:935: inode #2: comm zmaudit.pl: reading directory lblock 0



Voilà, merci pour votre aide :)



A voir également:

1 réponse

tu peux tenter la commande fsck pour réparer le disque.

voila un petit howto

http://wiki.debian-facile.org/commande:fsck
0
KunGu Messages postés 1169 Date d'inscription vendredi 7 septembre 2007 Statut Membre Dernière intervention 17 mars 2013 224
17 mars 2013 à 00:31
Mais le disque est neuf !! Comment se ferait-il qu'il soit déjà corrompu ? Bug système ??
Je vais essayer quand même
0