Date: 29 Oct 2003 14:08:48 -0500 From: Lowell Gilbert <freebsd-questions-local@be-well.ilk.org> To: Jer <jer@multihaven.org> Cc: questions@freebsd.org Subject: Re: Surface scan for Freebsd Message-ID: <44vfq7dfpb.fsf@be-well.ilk.org> In-Reply-To: <6.0.0.22.0.20031028165105.01ba0298@computer.multihaven.org> References: <6.0.0.22.0.20031028165105.01ba0298@computer.multihaven.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Jer <jer@multihaven.org> writes: > I have a feeling one of my disks is going south > Oct 28 11:28:40 computer /kernel: ad1: WRITE command timeout tag=0 > serv=0 - > resetting > Oct 28 11:28:40 computer /kernel: ata0: resetting devices .. done > Oct 28 11:28:55 computer /kernel: ad1: WRITE command timeout tag=0 > serv=0 - > resetting > Oct 28 11:28:55 computer /kernel: ata0: resetting devices .. done > Oct 28 11:29:06 computer /kernel: ad1: WRITE command timeout tag=0 > serv=0 - > resetting > Oct 28 11:29:06 computer /kernel: ata0: resetting devices .. done Actually, this doesn't show any signs of problems with the disk surface itself. The firmware on the drive is failing to report back when the disk controller was execpecting it to. I think the drive cable is the most common problem when this occurs, although the drive or the controller can be reponsible too. I've been getting these messages on my -STABLE machine for the last couple of weeks or so whenever the disk is stressed. I haven't yet gotten around to trying a new drive cable. > how can i do a surgace scan of sorts so I can make them with badblock? Aside from the fact that you're treating the wrong problem, you can't do that within FreeBSD. Modern drives do such sophisticated bad-block mapping internally that it is no longer worthwhile to maintain such facilities in the OS.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44vfq7dfpb.fsf>