Contenu | Rechercher | Menus

Annonce

Si vous rencontrez des soucis à rester connecté sur le forum (ou si vous avez perdu votre mot de passe) déconnectez-vous et reconnectez-vous depuis cette page, en cochant la case "Me connecter automatiquement lors de mes prochaines visites".
Test de l'ISO d'Ubuntu francophone : nous avons besoin de testeurs pour la version francophone d'Ubuntu 14.04. Liens et informations ici.

#1 Le 05/09/2012, à 20:17

vanzetti44

Pb dique dur

Salut,

Je suis sous Precise et j'ai un pb avec l'un de mes disques.
Le système freeze et obligé de redémarrer.
C'est aléatoire mais de + en + récurrent.
J'ai testé mes disques (sea tools, gsmart), rien de detecté mais je suis quasi sur que c''est un des disques.
j'ai 3 disques sata de connecté
j'ai des erreurs dans le /var/log/syslog:

Sep  5 19:52:11 vanzetti44-desktop kernel: [ 2511.496061]          res 40/00:08:cf:58:81/00:00:03:00:00/40 Emask 0x10 (ATA bus error)
Sep  5 19:52:11 vanzetti44-desktop kernel: [ 2511.496063] ata2.00: status: { DRDY }
Sep  5 19:52:11 vanzetti44-desktop kernel: [ 2511.496066] ata2: hard resetting link
Sep  5 19:52:17 vanzetti44-desktop kernel: [ 2516.860058] ata2: link is slow to respond, please be patient (ready=0)
Sep  5 19:52:21 vanzetti44-desktop kernel: [ 2521.508078] ata2: COMRESET failed (errno=-16)
Sep  5 19:52:21 vanzetti44-desktop kernel: [ 2521.508089] ata2: hard resetting link
Sep  5 19:52:22 vanzetti44-desktop kernel: [ 2521.828059] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Sep  5 19:52:22 vanzetti44-desktop kernel: [ 2521.829516] ata2.00: configured for UDMA/100
Sep  5 19:52:22 vanzetti44-desktop kernel: [ 2521.829545] ata2: EH complete
Sep  5 20:08:43 vanzetti44-desktop kernel: [ 3502.891192] ata2.00: exception Emask 0x10 SAct 0x3 SErr 0x580000 action 0x6 frozen
Sep  5 20:08:43 vanzetti44-desktop kernel: [ 3502.891195] ata2.00: irq_stat 0x08000000, interface fatal error
Sep  5 20:08:43 vanzetti44-desktop kernel: [ 3502.891198] ata2: SError: { 10B8B Dispar Handshk }
Sep  5 20:08:43 vanzetti44-desktop kernel: [ 3502.891201] ata2.00: failed command: WRITE FPDMA QUEUED
Sep  5 20:08:43 vanzetti44-desktop kernel: [ 3502.891205] ata2.00: cmd 61/00:00:77:d6:b0/04:00:0e:00:00/40 tag 0 ncq 524288 out
Sep  5 20:08:43 vanzetti44-desktop kernel: [ 3502.891206]          res 40/00:00:77:d6:b0/00:00:0e:00:00/40 Emask 0x10 (ATA bus error)

donc c'est bien  disque, cad le ata2...
mais est-ce que ata2 correspond a /dev/sdb...
comment faire la correspondance ou avoir des logs + prévis

merci

Hors ligne

#2 Le 15/03/2014, à 09:21

fg79

Re : Pb dique dur

J'ai le même problème (les mêmes messages d'erreur), avec un disque dur tout neuf, que je soupçonne d'être défaillant.
Chez moi, ata2 correspond avec /dev/sdb.
Si quelqu'un en sait davantage, je suis intéressé.

Merci.

Hors ligne

#3 Le 15/03/2014, à 09:31

moko138

Re : Pb dique dur

S'il te plaît, ouvre ton propre fil, colles-y ton ou tes messages d'erreur, et mets ici le lien vers ton nouveau fil.
Merci !

Hors ligne

#4 Le 15/03/2014, à 12:10

fg79

Re : Pb dique dur

Je poste ici les message présents dans mon syslog car je ne comprends l'intérêt d'un nouveau fil pour un problème similaire fut-il ancien.

Mar 15 06:32:25 intranet kernel: [   95.840033] ata2.00: exception Emask 0x0 SAct 0x7f800001 SErr 0x0 action 0x6 frozen
Mar 15 06:32:25 intranet kernel: [   95.840164] ata2.00: failed command: WRITE FPDMA QUEUED
Mar 15 06:32:25 intranet kernel: [   95.843931] ata2.00: cmd 61/50:00:08:0e:04/00:00:3a:00:00/40 tag 0 ncq 40960 out
Mar 15 06:32:25 intranet kernel: [   95.843932]          res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Mar 15 06:32:25 intranet kernel: [   95.851945] ata2.00: status: { DRDY }
Mar 15 06:32:25 intranet kernel: [   95.856017] ata2.00: failed command: WRITE FPDMA QUEUED
Mar 15 06:32:25 intranet kernel: [   95.860154] ata2.00: cmd 61/00:b8:00:c4:14/04:00:00:00:00/40 tag 23 ncq 524288 out
Mar 15 06:32:25 intranet kernel: [   95.860155]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Mar 15 06:32:25 intranet kernel: [   95.868680] ata2.00: status: { DRDY }
Mar 15 06:32:25 intranet kernel: [   95.873020] ata2.00: failed command: WRITE FPDMA QUEUED
Mar 15 06:32:25 intranet kernel: [   95.877388] ata2.00: cmd 61/00:c0:00:c8:14/04:00:00:00:00/40 tag 24 ncq 524288 out
Mar 15 06:32:25 intranet kernel: [   95.877390]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Mar 15 06:32:25 intranet kernel: [   95.886465] ata2.00: status: { DRDY }
Mar 15 06:32:25 intranet kernel: [   95.891087] ata2.00: failed command: WRITE FPDMA QUEUED
Mar 15 06:32:25 intranet kernel: [   95.895766] ata2.00: cmd 61/00:c8:00:cc:14/04:00:00:00:00/40 tag 25 ncq 524288 out
Mar 15 06:32:25 intranet kernel: [   95.895767]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Mar 15 06:32:25 intranet kernel: [   95.905141] ata2.00: status: { DRDY }
Mar 15 06:32:25 intranet kernel: [   95.909910] ata2.00: failed command: WRITE FPDMA QUEUED
Mar 15 06:32:25 intranet kernel: [   95.914680] ata2.00: cmd 61/00:d0:00:d0:14/04:00:00:00:00/40 tag 26 ncq 524288 out
Mar 15 06:32:25 intranet kernel: [   95.914682]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Mar 15 06:32:25 intranet kernel: [   95.924627] ata2.00: status: { DRDY }
Mar 15 06:32:25 intranet kernel: [   95.929492] ata2.00: failed command: WRITE FPDMA QUEUED
Mar 15 06:32:25 intranet kernel: [   95.934369] ata2.00: cmd 61/00:d8:00:d4:14/04:00:00:00:00/40 tag 27 ncq 524288 out
Mar 15 06:32:25 intranet kernel: [   95.934370]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Mar 15 06:32:25 intranet kernel: [   95.944244] ata2.00: status: { DRDY }
Mar 15 06:32:25 intranet kernel: [   95.949314] ata2.00: failed command: WRITE FPDMA QUEUED
Mar 15 06:32:25 intranet kernel: [   95.954407] ata2.00: cmd 61/00:e0:00:d8:14/04:00:00:00:00/40 tag 28 ncq 524288 out
Mar 15 06:32:25 intranet kernel: [   95.954408]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Mar 15 06:32:25 intranet kernel: [   95.964619] ata2.00: status: { DRDY }
Mar 15 06:32:25 intranet kernel: [   95.969762] ata2.00: failed command: WRITE FPDMA QUEUED
Mar 15 06:32:25 intranet kernel: [   95.974961] ata2.00: cmd 61/00:e8:00:dc:14/04:00:00:00:00/40 tag 29 ncq 524288 out
Mar 15 06:32:25 intranet kernel: [   95.974963]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Mar 15 06:32:25 intranet kernel: [   95.985531] ata2.00: status: { DRDY }
Mar 15 06:32:25 intranet kernel: [   95.990910] ata2.00: failed command: WRITE FPDMA QUEUED
Mar 15 06:32:25 intranet kernel: [   95.996309] ata2.00: cmd 61/00:f0:00:e0:14/04:00:00:00:00/40 tag 30 ncq 524288 out
Mar 15 06:32:25 intranet kernel: [   95.996311]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Mar 15 06:32:25 intranet kernel: [   96.007316] ata2.00: status: { DRDY }
Mar 15 06:32:25 intranet kernel: [   96.007322] ata2: hard resetting link
Mar 15 06:32:25 intranet kernel: [   96.496018] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Mar 15 06:32:25 intranet kernel: [   96.497781] ata2.00: configured for UDMA/133
Mar 15 06:32:25 intranet kernel: [   96.497787] ata2.00: device reported invalid CHS sector 0
Mar 15 06:32:25 intranet kernel: [   96.497791] ata2.00: device reported invalid CHS sector 0
Mar 15 06:32:25 intranet kernel: [   96.497794] ata2.00: device reported invalid CHS sector 0
Mar 15 06:32:25 intranet kernel: [   96.497797] ata2.00: device reported invalid CHS sector 0
Mar 15 06:32:25 intranet kernel: [   96.497800] ata2.00: device reported invalid CHS sector 0
Mar 15 06:32:25 intranet kernel: [   96.497803] ata2.00: device reported invalid CHS sector 0
Mar 15 06:32:25 intranet kernel: [   96.497806] ata2.00: device reported invalid CHS sector 0
Mar 15 06:32:25 intranet kernel: [   96.497809] ata2.00: device reported invalid CHS sector 0
Mar 15 06:32:25 intranet kernel: [   96.497818] ata2: EH complete
Mar 15 06:33:38 intranet kernel: [  168.832030] ata2.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x6 frozen
Mar 15 06:33:38 intranet kernel: [  168.832153] ata2.00: failed command: WRITE FPDMA QUEUED
Mar 15 06:33:38 intranet kernel: [  168.835899] ata2.00: cmd 61/00:00:00:04:63/04:00:00:00:00/40 tag 0 ncq 524288 out
Mar 15 06:33:38 intranet kernel: [  168.835901]          res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Mar 15 06:33:38 intranet kernel: [  168.843788] ata2.00: status: { DRDY }
Mar 15 06:33:38 intranet kernel: [  168.847822] ata2.00: failed command: READ FPDMA QUEUED
Mar 15 06:33:38 intranet kernel: [  168.851888] ata2.00: cmd 60/08:08:48:08:40/00:00:00:00:00/40 tag 1 ncq 4096 in
Mar 15 06:33:38 intranet kernel: [  168.851891]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Mar 15 06:33:38 intranet kernel: [  168.860262] ata2.00: status: { DRDY }
Mar 15 06:33:38 intranet kernel: [  168.864562] ata2: hard resetting link
Mar 15 06:33:38 intranet kernel: [  169.356026] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Mar 15 06:33:38 intranet kernel: [  169.357805] ata2.00: configured for UDMA/133
Mar 15 06:33:38 intranet kernel: [  169.357810] ata2.00: device reported invalid CHS sector 0
Mar 15 06:33:38 intranet kernel: [  169.357818] ata2: EH complete
Mar 15 06:34:56 intranet kernel: [  246.816030] ata2.00: exception Emask 0x0 SAct 0x20000010 SErr 0x0 action 0x6 frozen
Mar 15 06:34:56 intranet kernel: [  246.816159] ata2.00: failed command: WRITE FPDMA QUEUED
Mar 15 06:34:56 intranet kernel: [  246.816245] ata2.00: cmd 61/00:20:f0:73:87/04:00:3a:00:00/40 tag 4 ncq 524288 out
Mar 15 06:34:56 intranet kernel: [  246.816247]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Mar 15 06:34:56 intranet kernel: [  246.816510] ata2.00: status: { DRDY }
Mar 15 06:34:56 intranet kernel: [  246.816567] ata2.00: failed command: WRITE FPDMA QUEUED
Mar 15 06:34:56 intranet kernel: [  246.816652] ata2.00: cmd 61/b8:e8:98:17:04/00:00:3a:00:00/40 tag 29 ncq 94208 out
Mar 15 06:34:56 intranet kernel: [  246.816653]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Mar 15 06:34:56 intranet kernel: [  246.816884] ata2.00: status: { DRDY }
Mar 15 06:34:56 intranet kernel: [  246.816942] ata2: hard resetting link
Mar 15 06:34:56 intranet kernel: [  247.308014] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Mar 15 06:34:56 intranet kernel: [  247.309768] ata2.00: configured for UDMA/133
Mar 15 06:34:56 intranet kernel: [  247.309773] ata2.00: device reported invalid CHS sector 0
Mar 15 06:34:56 intranet kernel: [  247.309777] ata2.00: device reported invalid CHS sector 0
Mar 15 06:34:56 intranet kernel: [  247.309783] ata2: EH complete
Mar 15 06:35:55 intranet kernel: [  305.888023] ata2.00: NCQ disabled due to excessive errors
Mar 15 06:35:55 intranet kernel: [  305.888028] ata2.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x6 frozen
Mar 15 06:35:55 intranet kernel: [  305.888148] ata2.00: failed command: WRITE FPDMA QUEUED
Mar 15 06:35:55 intranet kernel: [  305.894909] ata2.00: cmd 61/00:00:a8:e8:bf/04:00:3a:00:00/40 tag 0 ncq 524288 out
Mar 15 06:35:55 intranet kernel: [  305.894911]          res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Mar 15 06:35:55 intranet kernel: [  305.908555] ata2.00: status: { DRDY }
Mar 15 06:35:55 intranet kernel: [  305.915425] ata2.00: failed command: READ FPDMA QUEUED
Mar 15 06:35:55 intranet kernel: [  305.922243] ata2.00: cmd 60/08:08:00:08:c0/00:00:3a:00:00/40 tag 1 ncq 4096 in
Mar 15 06:35:55 intranet kernel: [  305.922244]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Mar 15 06:35:55 intranet kernel: [  305.935837] ata2.00: status: { DRDY }
Mar 15 06:35:55 intranet kernel: [  305.942637] ata2: hard resetting link
Mar 15 06:35:55 intranet kernel: [  306.432022] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Mar 15 06:35:55 intranet kernel: [  306.434102] ata2.00: configured for UDMA/133
Mar 15 06:35:55 intranet kernel: [  306.434109] ata2.00: device reported invalid CHS sector 0
Mar 15 06:35:55 intranet kernel: [  306.434117] ata2: EH complete

Je précise que cette série d'erreur ne s'est pas reproduite et que le disque semble bien fonctionner depuis.
Je suis en train de faire une vérification des blocs défectueux, et à 25% d'avancement, aucune erreur n'a été détectée.
Reste à savoir s'il s'agit à priori d'une défaillance du disque ou bien d'une défaillance du contrôleur.

Hors ligne

Haut de page ↑