From owner-freebsd-questions Mon Jan 14 7:53:51 2002 Delivered-To: freebsd-questions@freebsd.org Received: from guru.mired.org (okc-65-31-201-166.mmcable.com [65.31.201.166]) by hub.freebsd.org (Postfix) with SMTP id 0A17237B404 for ; Mon, 14 Jan 2002 07:49:53 -0800 (PST) Received: (qmail 2310 invoked by uid 100); 14 Jan 2002 15:49:46 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15426.65050.225532.538913@guru.mired.org> Date: Mon, 14 Jan 2002 09:49:46 -0600 To: "Matthew Rudderham" Cc: questions@freebsd.org Subject: Re: Reapiring bad blocks w/ fschk In-Reply-To: <60693838@toto.iv> X-Mailer: VM 6.90 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ From: "Mike Meyer" X-Delivery-Agent: TMDA/0.44 (Python 2.2; freebsd-4.4-STABLE-i386) Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Matthew Rudderham types: > Hi, > On a box I have running 4.3-Release I have been getting these messages every > so often: > > Jan 11 20:47:11 cfxu /kernel: ad0s1a: hard error reading fsbn 58622143 of > 2162752-2162767 (ad0s1 bn 58622143; cn 37220 tn 10 sn 13) status=59 error=40 > > I assume a few bad sectors have developed on the disk. When trying to > install packages I'm often getting messages related to not being able to > write within /var/ such as mktemp /var/tmp failed and could not add to > /var/db/pkg/... Etc so I assume these are where the bad blocks have > developed. I was wondering how I can mark these blocks as unusable so I can > continue to use the system until I get a replacement drive. Also when > running fsck normally it does show a few blocks it could not read from. Any > help would be very appreciated, the fsck manual was not much help and the > archives of -questions seems to be out of order. Many Thanks. fsck can't do what you want. I don't know that anything can on FreeBSD. Modern drives tend to deal with bad blocks all by themselves, so if the kernel is seeing them, it means the drive is in sad shape, and should be replaced ASAP. http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message