From owner-freebsd-questions Fri Nov 29 8:40:31 2002 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7AB2E37B401; Fri, 29 Nov 2002 08:40:29 -0800 (PST) Received: from tomts21-srv.bellnexxia.net (tomts21.bellnexxia.net [209.226.175.183]) by mx1.FreeBSD.org (Postfix) with ESMTP id D35E943E4A; Fri, 29 Nov 2002 08:40:22 -0800 (PST) (envelope-from matt@gsicomp.on.ca) Received: from xena.gsicomp.on.ca ([65.95.186.92]) by tomts21-srv.bellnexxia.net (InterMail vM.5.01.04.19 201-253-122-122-119-20020516) with ESMTP id <20021129164016.NZIW981.tomts21-srv.bellnexxia.net@xena.gsicomp.on.ca>; Fri, 29 Nov 2002 11:40:16 -0500 Received: from hermes (hermes.gsicomp.on.ca [192.168.0.18]) by xena.gsicomp.on.ca (8.11.3/8.11.3) with SMTP id gATGeDS23634; Fri, 29 Nov 2002 11:40:13 -0500 (EST) (envelope-from matt@gsicomp.on.ca) Message-ID: <00f701c297c5$fef425c0$1200a8c0@gsicomp.on.ca> From: "Matthew Emmerton" To: "Jason Hunt" , "Vinco Maldini" Cc: , References: <20021129111613.W84905-100000@lethargic.dyndns.org> Subject: Re: Unexpected Soft Update Inconsistency / Cannot Read: Blk Date: Fri, 29 Nov 2002 11:40:15 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300 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 > On Fri, 29 Nov 2002, Vinco Maldini wrote: > > > 1) What does the result below mean? (Is my drive failing? Why can't I > > clean the FS?) > > > [ ... snip ... ] > > CANNOT READ: BLK 152744928 > > UNEXPECTED SOFT UPDATE INCONSISTENCY > [ ... snip ... ] > > > > THE FOLLOWING DISK SECTORS COULD NOT BE READ: 152744946, > [ ... etc, etc, snip ... ] > > > > Were there any kernel messages displayed on the consoles (the bright white > text)? If you don't have console access, run the /sbin/dmesg command. If > you see any ad2 read errors from the console, then you likely have a bad > drive. On the other hand, if you don't see any errors being reported by > the kernel, then the "CANNOT READ" errors are probably just caused by > incompleted meta-data writes to the drive. However, "THE FOLLOWING DISK > SECTORS COULD NOT BE READ" makes me think it is a hardware problem. > > > > 2) Are there any BSD tools for reading the SMART data off the Hard Disk > > so that I can see whether it is about to fail or currently experiencing > > HW failure. Any other ways to check for bad sectors? > > I thought that someone asked this same questions a few days ago, but I > can't find it in the archives. I'm honestly not sure if anything like > that is available. Searching the FreeBSD site did not yield any results. > My best suggestions is to check google. Or check with sos@freebsd.org. If there was something like this out there, he'd know :) -- Matt Emmerton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message