Date: Mon, 03 Aug 1998 11:35:16 -0700 (PDT) From: Jonathan Hanna <pangolin@rogers.wave.ca> To: Chris <chrisj@outcast.media-net.net> Cc: freebsd-stable@FreeBSD.ORG, Mike Smith <mike@smith.net.au> Subject: Re: WD errors Message-ID: <199808031835.LAA01901@pc-21490.bc.rogers.wave.ca> In-Reply-To: <199808031612.JAA14148@antipodes.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 03-Aug-98 Mike Smith wrote: >> ... >> follows. wd0s1f: wdstart: timeout waiting to give command reading fsbn >> 3148892 of 3148892-3148893 (wd0s1 bn 3689468; cn 229 tn 167 sn 62)wd0: >> status 80<busy> error 80<badblk>. after afew screens of that the message >> will turn to wd0: wdunwedge failed: >> > wd0: status 80<busy> error 80<badblk> >> > wd0s1f: wdstart: timeout waiting to give command reading fsbn 3148892 of >> 3148892-3148893 (wd0s1 bn 3689468; cn 229 tn 167 sn 62)wd0: status >> 80<busy> error 80<badblk>. the system will remain on-line (ie pingable) >> ... > > Your disk seems to be struggling with a bad block. The best thing to do > at this point is throw the disk out and get a new one, as with any > modern IDE disk you will only get to this point once all of the > available spare sectors have been used up. When you give up on reading the block, you might try writing it and then rereading. It may have been a bad write as opposed to a bad block. I think I have caused this type of error with bad power connections but am not really sure. Jonathan Hanna <pangolin@rogers.wave.ca> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199808031835.LAA01901>