From owner-freebsd-hackers Tue Feb 3 04:40:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA17542 for hackers-outgoing; Tue, 3 Feb 1998 04:40:59 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from word.smith.net.au (ppp8.portal.net.au [202.12.71.108]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA17534 for ; Tue, 3 Feb 1998 04:40:54 -0800 (PST) (envelope-from mike@word.smith.net.au) Received: from word (localhost [127.0.0.1]) by word.smith.net.au (8.8.8/8.8.5) with ESMTP id XAA03576; Tue, 3 Feb 1998 23:03:35 +1030 (CST) Message-Id: <199802031233.XAA03576@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Jim Carroll cc: freebsd-hackers@FreeBSD.ORG Subject: Re: wd0s1e hard errors In-reply-to: Your message of "Mon, 02 Feb 1998 21:54:35 CDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 03 Feb 1998 23:03:35 +1030 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe hackers" > > wd0s1e: hard error reading fsbn 721266 of 721264-721279 (wd0s1 bn 1057138; cn 262 tn 11 sn 61)wd0: status 59 error 40 > > wd0s1e: hard error reading fsbn 721266 of 721264-721279 (wd0s1 bn 1057138; cn 262 tn 11 sn 61)wd0: status 59 error 40 > > wd0s1e: hard error reading fsbn 721266 of 721264-721279 (wd0s1 bn 1057138; cn 262 tn 11 sn 61)wd0: status 59 error 40 > > wd0s1e: hard error reading fsbn 721266 of 721264-721279 (wd0s1 bn 1057138; cn 262 tn 11 sn 61)wd0: status 59 error 40 > > > Can someone point me towards a man page, FAQ, book or other reference that > would describe what I can do about the above sort of error? Replace the disk ASAP. If you are seeing hard errors, the disk has run out of spare (forwarding) sectors, and it's on the way out. You can mount a disk forced, readonly, under these circumstances in order to copy stuff off it. > I have looked over the bad144 docs, but it appears this software is > considered obsolete. Unfortuantely, I cannot figure out what is it's > contemporary replacement. Bad sector management has moved largely into the drive logic, where it can be performed transparently. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\