Date: Fri, 18 Feb 2005 09:25:05 -0600 (CST) From: "Reid Linnemann" <lreid@cs.okstate.edu> To: cperciva@freebsd.org Cc: "freebsd-current@freebsd.org" <freebsd-current@freebsd.org> Subject: Re: ad WRITE_DMA timing out frequently Message-ID: <20050218152505.4B672A063E@csa.cs.okstate.edu> In-Reply-To: <42160556.5040106@freebsd.org>
index | next in thread | previous in thread | raw e-mail
On 2/18/2005, "Colin Percival" <cperciva@freebsd.org> wrote: >Reid Linnemann wrote: >> ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=2085599 >> ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=2085599 >> kernel: ad0: FAILURE - WRITE_DMA timed out >> kernel: g_vfs_done():ad0s1d[WRITE(offset=52772864, length=16384)]error = 5 > >Looks like a dying disk. > >> It seems to me that a sector on the disk might be dead in the ad0s1d >> slice (/var), but I want to be certain before I take further steps that >> the behavior I'm experiencing is positively unrelated to the migration >> to 6-CURRENT. > >Install sysutils/smartmontools from ports and use smartctl. Odds are that >the drive has logged hundreds of errors by now. > >Colin Percival >_______________________________________________ >freebsd-current@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-current >To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" smartctl doesn't report any logged errors. On a hunch, I also dd'ed a file large enough to fill /var, hoping that it would crater on writing to that sector. It didn't. I know that's not a very useful test, but it seems to hint to me that the disk isn't bad, but the driver is freaking out from some event.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050218152505.4B672A063E>