Date: Thu, 22 Jul 2004 12:01:33 +0200 From: Stijn Hoop <stijn@win.tue.nl> To: George Barnett <george@alink.co.za> Cc: stable@freebsd.org Subject: Re: ATA errors Message-ID: <20040722100132.GO18553@pcwin002.win.tue.nl> In-Reply-To: <40FF89A4.4030508@alink.co.za> References: <40FF89A4.4030508@alink.co.za>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On Thu, Jul 22, 2004 at 10:32:20AM +0100, George Barnett wrote: > Hi All, > > I'm having a few issues and I could use another brain on this. I have a > machine which is throwing up ata errors like this: > > Jul 22 00:16:16 <kern.crit> mail /kernel: ad2s1e: soft error (ECC > corrected) reading fsbn 77465920 of 38732960-38733087 (ad2s1 bn > 77465920; cn 461106 tn 18 sn 4)ad2s1e: hard error reading fsbn 77465920 > of 38732960-38733087 (ad2s1 bn 77465920; cn 461106 tn 18 sn 4)ad2: > timeout waiting for cmd=ef s=00 e=7f > Jul 22 00:16:16 <kern.crit> mail /kernel: trying PIO mode > Jul 22 00:16:18 <kern.crit> mail /kernel: ad2s1e: soft error (ECC > corrected) reading fsbn 77465920 of 38732960-38733087 (ad2s1 bn > 77465920; cn 461106 tn 18 sn 4)ad2s1e: hard error reading fsbn 77465920 > of 38732960-38733087 (ad2s1 bn 77465920; cn 461106 tn 18 sn 4) status=7f > error=7f > Jul 22 00:16:18 <kern.crit> mail /kernel: ad2: timeout waiting for DRQ - > resetting > Jul 22 00:16:18 <kern.crit> mail /kernel: ata1: resetting devices .. > Jul 22 00:16:18 <kern.crit> mail /kernel: ad2: removed from configuration > Jul 22 00:16:18 <kern.crit> mail /kernel: done > > It was doing this a few weeks ago, so I swapped the disk out and it was > happy for a bit. Now it's coming back and doing it on the new disk > (which is in the same place as the old one (sec-master)). Did you check the failed disk using Maxtor's utility, and did it report any errors? I have about the same situation -- 4.10-STABLE reporting a read error every few days, each time on a different disk, but every time it turned out that the disk really was good according to Maxtor's tests :( > I figure this means the controller has gone bork? That's also a possibility, but I've seen it happen on 3 different controllers already, which imho is too much coincidence for it to really be a controller failure. I'm still in the dark as to what it really is though. It could very well still be a hardware error in my case (heat and memory not yet ruled out). --Stijn -- "Linux has many different distributions, meaning that you can probably find one that is exactly what you want (I even found one that looked like a Unix system)." -- Mike Meyer, from a posting at questions@freebsd.org [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFA/5B8Y3r/tLQmfWcRAgfUAJwLumY7vKL/KJftyNXCdWT7d3T+1gCfZ6N5 q0USr8akXl7A/M3pLa/1Azo= =qYMD -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040722100132.GO18553>