From owner-freebsd-questions Thu Jul 19 10:31:35 2001 Delivered-To: freebsd-questions@freebsd.org Received: from gekko.i-clue.de (server.ms-agentur.de [62.153.134.194]) by hub.freebsd.org (Postfix) with ESMTP id 81EEB37B403 for ; Thu, 19 Jul 2001 10:31:28 -0700 (PDT) (envelope-from so@server.i-clue.de) Received: from i-clue.de (automatix.i-clue.de [192.168.0.112]) by gekko.i-clue.de (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id TAA31367; Thu, 19 Jul 2001 19:39:19 +0200 Message-ID: <3B5719F4.C7EE3B12@i-clue.de> Date: Thu, 19 Jul 2001 19:33:40 +0200 From: Christoph Sold Reply-To: so@server.i-clue.de X-Mailer: Mozilla 4.75 [de] (WinNT; U) X-Accept-Language: de MIME-Version: 1.0 To: Gram Wheeler Cc: questions@FreeBSD.ORG Subject: Re: Hard drive poked? References: <790FAC90BABB834AAE3719C94B9A1A9701C6CDA2@RED-MSG-11.redmond.corp.microsoft.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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 Gram Wheeler schrieb: > > Hi all > > When I last tried to cvsup, I get the following types of error messages > on > the screen: > > /kernel: ad0s2f: hard error reading fsbn 15273680 of 1999072-1999327 > (ad0s2 > bn 15273680 cn 1010 tn 39 sn 23) status=59 error=40 > > These keep repeating with different but similar values, and it sounds > like > the disk is having a hard time. > > Does this mean my disk is poked? Interestingly, 15273680 is out of the > range 1999072-1999327. Is it possibly some other form of corruption that > > has caused a logical inconsistency in the file system that fsck doesn't > detect? > > tx > Gram > > PS I left this running for a while, and eventually had a read error of > the cvsup file reported. I deleted the file, ran cvsup again, and this > time the cvsup completed. But I am still concerned about whether I have > just removed the symptom and not discovered the cause... Hard errors are a typical symptom of a hard disk in its death throws. For SCSI disks, the drive will be in a useable state for a while after the first hard error. IDE drives just go south soon after. I'd do 1) dump, 2) fsck, and 3) replace the disk. Note I do the dump before the fsck in case fsck causes the drive to goes belly up before you got the chance to fsck. Note: I assume that drive did it's job for at least a few months before. For new drives, or boxes with recent hardware changes, different rules apply. HTH -Christoph Sold To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message