Date: Mon, 20 Jun 2005 15:46:20 +0100 From: Jayton Garnett <jay@codegurus.org> To: freebsd-stable@freebsd.org Subject: Re: ATA_DMA errors (and fs corruption!) (JM) Message-ID: <42B6D6BC.4000208@codegurus.org> In-Reply-To: <20050620120030.6818B16A420@hub.freebsd.org> References: <20050620120030.6818B16A420@hub.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
I had a similar problem and i changed system cases where i was getting a ICRC error and FreeBSD refused to load or even mount the root fs, it was also giving errors with something to do with the ATA something or other, it turned out to be the cable i used after rebuilding the system in the new case, i used a normal EIDE cable instead of a ATA cable :-/ hope that helps(probably not) Jay > >Tony Byrne wrote: > > > >>Hello Bob, >> >> >> >> >> >> >>>>can be hardware reasons for timeouts such as a dying disk or cable, >>>>but I think we've eliminated these in our case. [etc] >>>> >>>> >>>> >>>> >>BB> Don't ignore the possibility of failing controller hardware. We had >>BB> comparable mysterious problems on a client system, causing a lot of >>BB> head-scratching. Eventually the failure went hard and we had to replace the >>BB> motherboard. >> >>I hear ya! However, moving back to an older kernel changes the >>severity of the problem from a timeout every 2 to three minutes during >>heavy activity to about 4 or 5 in a 24 hour period. That doesn't >>sound like hardware to me. >> >>Regards, >> >>Tony. >> >> >> >> >> >i have these same errors on my VIA 823x series chipset. however, the >problem is only with the secondary device (acd0 in this case), and might >be stemming from some other problem. > > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?42B6D6BC.4000208>