From owner-freebsd-newbies Fri Nov 29 18:28:23 2002 Delivered-To: freebsd-newbies@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DA56837B401 for ; Fri, 29 Nov 2002 18:28:20 -0800 (PST) Received: from pineapple.theshop.net (pineapple.theshop.net [66.210.104.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0699443ED1 for ; Fri, 29 Nov 2002 18:28:20 -0800 (PST) (envelope-from scott@bsdprophet.org) Received: from bsdprophet.org (40558f5dae34996ab98c2333e7e30efc@[66.210.107.47]) by pineapple.theshop.net (8.12.0/8.12.0) with ESMTP id gAU2Ym21029583; Fri, 29 Nov 2002 20:34:49 -0600 (CST) Message-ID: <3DE82232.80005@bsdprophet.org> Date: Fri, 29 Nov 2002 20:28:02 -0600 From: Scott Corey User-Agent: Mozilla/5.0 (X11; U; Linux i386; en-US; rv:1.2b) Gecko/20021016 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Andrew Cutler Cc: freebsd-newbies@freebsd.org Subject: Re: Unexpected Soft Update Inconsistency / Cannot Read: Blk References: <1038452975.1000.2.camel@blue.home> In-Reply-To: <1038452975.1000.2.camel@blue.home> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-newbies@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org You might want to try questions@freebsd.org. Andrew Cutler wrote: > I recently built a FreeBSD 4.7 Release file server that has a brand new > 80GB Wester Digital 7200RPM drive in it. Yesterday the box suffered two > power outages and a possible powersurge. > > > Today I decided that it would be a good idea to check on the state of > the file system and the result is attached below. I was unable to clean > the file system. > > I've got just two questions that hopefully someone can help with: > > 1) What does the result below mean? (Is my drive failing? Why can't I > clean the FS?) > > 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 sheck for bad sectors? > > TIA > > Andrew Cutler > > > > --------- START SCREEN SNIPPET -------------------- > > > mojo# fsck /dev/ad2s1e > ** /dev/ad2s1e > ** Last Mounted on /data > ** Phase 1 - Check Blocks and Sizes > > CANNOT READ: BLK 152744928 > UNEXPECTED SOFT UPDATE INCONSISTENCY > > CONTINUE? [yn] y > > THE FOLLOWING DISK SECTORS COULD NOT BE READ: 152744946, > > CANNOT READ: BLK 152745312 > UNEXPECTED SOFT UPDATE INCONSISTENCY > > CONTINUE? [yn] y > > THE FOLLOWING DISK SECTORS COULD NOT BE READ: 152745393, > > CANNOT READ: BLK 152746208 > UNEXPECTED SOFT UPDATE INCONSISTENCY > > CONTINUE? [yn] y > > THE FOLLOWING DISK SECTORS COULD NOT BE READ: 152746289, > > CANNOT READ: BLK 152747104 > UNEXPECTED SOFT UPDATE INCONSISTENCY > > CONTINUE? [yn] y > > THE FOLLOWING DISK SECTORS COULD NOT BE READ: 152747184, > > CANNOT READ: BLK 152748128 > UNEXPECTED SOFT UPDATE INCONSISTENCY > > CONTINUE? [yn] y > > THE FOLLOWING DISK SECTORS COULD NOT BE READ: 152748173, > > CANNOT READ: BLK 152748512 > UNEXPECTED SOFT UPDATE INCONSISTENCY > > CONTINUE? [yn] y > > THE FOLLOWING DISK SECTORS COULD NOT BE READ: 152748621, > > CANNOT READ: BLK 152749024 > UNEXPECTED SOFT UPDATE INCONSISTENCY > > CONTINUE? [yn] y > > THE FOLLOWING DISK SECTORS COULD NOT BE READ: 152749068, > > CANNOT READ: BLK 152749408 > UNEXPECTED SOFT UPDATE INCONSISTENCY > > CONTINUE? [yn] y > > THE FOLLOWING DISK SECTORS COULD NOT BE READ: 152749516, > ** Phase 2 - Check Pathnames > ** Phase 3 - Check Connectivity > ** Phase 4 - Check Reference Counts > ** Phase 5 - Check Cyl groups > 33755 files, 16020305 used, 22442867 free (12539 frags, 2803791 blocks, > 0.0% fragmentation) > > ***** FILE SYSTEM MARKED DIRTY ***** > > ***** PLEASE RERUN FSCK ***** > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-newbies" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-newbies" in the body of the message