From owner-freebsd-newbies Fri Nov 29 15:22:16 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 E64B537B401 for ; Fri, 29 Nov 2002 15:22:13 -0800 (PST) Received: from fry.serversaint.com (fry.serversaint.com [162.42.131.156]) by mx1.FreeBSD.org (Postfix) with ESMTP id 61D2943EB2 for ; Fri, 29 Nov 2002 15:22:13 -0800 (PST) (envelope-from andrew@dnaml.com) Received: from cpe-144-132-174-149.nsw.bigpond.net.au ([144.132.174.149] helo=[192.168.0.106]) by fry.serversaint.com with esmtp (Exim 3.36 #1) id 18HF3S-0005AC-00 for freebsd-newbies@freebsd.org; Thu, 28 Nov 2002 03:09:31 +0000 Subject: Unexpected Soft Update Inconsistency / Cannot Read: Blk From: Andrew Cutler To: freebsd-newbies@freebsd.org Content-Type: text/plain Organization: Message-Id: <1038452975.1000.2.camel@blue.home> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.0 Date: 28 Nov 2002 14:09:36 +1100 Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - fry.serversaint.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [0 0] X-AntiAbuse: Sender Address Domain - dnaml.com 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 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