Messages in this thread | | | Subject | Re: Detecting I/O error and Halting System | From | Alan Cox <> | Date | Mon, 27 Mar 2006 17:55:56 +0100 |
| |
On Llu, 2006-03-27 at 16:55 +0200, zine el abidine Hamid wrote: > hda: status timeout: status=0xd0 { Busy } adapter > disque annonce un status busy du DMA
If I'm reading the translation right then your hard disk decided it was busy and then never came back
> Feb 12 04:46:23 porte_de_clignancourt_nds_b kernel: > ide0: reset: success
So the IDE layer tried to reset it
> Feb 12 10:22:38 porte_de_clignancourt_nds_b kernel: > hda: timeout waiting for DMA
Which didnt help
> Feb 12 10:24:47 porte_de_clignancourt_nds_b kernel: > ide0: reset: success
Still trying
> Feb 12 10:24:47 porte_de_clignancourt_nds_b kernel: > hda: irq timeout: status=0xd0 { Busy } > > Feb 12 10:24:47 porte_de_clignancourt_nds_b kernel: > hda: DMA disabled
We gave up on DMA to see if PIO would help > > > Feb 12 10:24:47 porte_de_clignancourt_nds_b kernel: > ide0: reset timed-out, status=0x80 > Feb 12 10:24:47 porte_de_clignancourt_nds_b kernel: > hda: status timeout: status=0x80 { Busy } > nouvel échec de reset > Feb 12 10:24:47 porte_de_clignancourt_nds_b kernel: > hda: drive not ready for command > Feb 12 10:24:47 porte_de_clignancourt_nds_b kernel: > ide0: reset: success
And reset..
> Feb 12 13:45:38 porte_de_clignancourt_nds_b kernel: > hda: status timeout: status=0x80 { Busy } > Feb 12 13:45:38 porte_de_clignancourt_nds_b kernel: > hda: drive not ready for command > Feb 12 13:45:38 porte_de_clignancourt_nds_b kernel: > ide0: reset timed-out, status=0x80 > Feb 12 13:45:38 porte_de_clignancourt_nds_b kernel: > end_request: I/O error, dev 03:02 (hda), sector 102263 > Feb 12 13:45:38 porte_de_clignancourt_nds_b syslogd: > /var/log/maillog: Input/output error > Feb 12 13:45:38 porte_de_clignancourt_nds_b kernel: > end_request: I/O error, dev 03:02 (hda), sector 110720 > Feb 12 13:45:38 porte_de_clignancourt_nds_b kernel: > end_request: I/O error, dev 03:02 (hda), sector 110728
Eventually we give up.
First thing to check would be the disk and the temperature, then the cabling. In particular make sure the *long* part of the cable is between the drive and the controller.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |