From owner-freebsd-stable Tue May 26 15:59:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA13998 for freebsd-stable-outgoing; Tue, 26 May 1998 15:59:08 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA13942 for ; Tue, 26 May 1998 15:58:56 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id QAA23813; Tue, 26 May 1998 16:58:45 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id QAA09021; Tue, 26 May 1998 16:58:27 -0600 Date: Tue, 26 May 1998 16:58:27 -0600 Message-Id: <199805262258.QAA09021@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Mike Smith Cc: Nate Williams , Michael Robinson , freebsd-stable@FreeBSD.ORG Subject: Re: Bug in wd driver In-Reply-To: <199805262146.OAA01571@dingo.cdrom.com> References: <199805261502.JAA05071@mt.sri.com> <199805262146.OAA01571@dingo.cdrom.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > > Having a bad spot on a disk shouldn't make the disk *totally* unusable, > > as every other 'significant' OS can deal with fine. > > This isn't a "bad spot" in the traditional sense - this is the disk > firmware failing. No, this is a bad spot on the disk. > A "bad spot" gives you a recognisable, and recoverable, error. Only if the bad spot can be remapped 'magically' behind the scenes, or the spot is 'recoverable. When your bad-sector table is filled, the hard-disk is saying 'I can't read this anymore, so quit trying'. The FreeBSD driver says 'Please, try again', and again, and again, and again... > Note that DOS-derived operating systems will often dump their cookies in > a similar fashion under the same circumstances (exact results seem to > vary, and I don't have a drive I can test this with anymore, having > consigned my last one to the dump before moving). Not in my case. Win95/DOS was able to recognize this and map it out. > > This is also why I was w/out a laptop for 5 months, since our driver > > couldn't get past the bad sector on the boot partition when it went bad > > and everytime fsck tried to read it it locked up the computer. :( > > So don't fsck it; I talked you through solving that problem, and you > ignored me. 8) I couldn't *NOT* fsck it since init was were the bad-blocks was located. (I think it was the inode). All attempts to fix it or workaround it didn't work, so I punted on it. By the time I got DOS to remap it, I gave up on using FreeBSD on it, since I figured it was only a matter of time before another bad-spot showed up and I'd be in the same boat. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message