From owner-freebsd-questions Sun Dec 8 15:21:49 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 6580837B401 for ; Sun, 8 Dec 2002 15:21:45 -0800 (PST) Received: from fry.serversaint.com (fry.serversaint.com [162.42.131.156]) by mx1.FreeBSD.org (Postfix) with ESMTP id D56DF43EA9 for ; Sun, 8 Dec 2002 15:21:44 -0800 (PST) (envelope-from andrew@1stelement.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 18LAk5-0001SR-00; Sun, 08 Dec 2002 23:21:46 +0000 Subject: Re: Unexpected Soft Update Inconsistency / Cannot Read: Blk From: Andrew Cutler To: philipp Cc: freebsd-questions@freebsd.org In-Reply-To: <20021208231016.B3856@phrost.net> References: <1038402708.527.10.camel@blue.home> <20021208231016.B3856@phrost.net> Content-Type: text/plain Organization: Message-Id: <1039389699.261.6.camel@localhost> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.0 Date: 09 Dec 2002 10:21:39 +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 - 1stelement.com 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 Unfortunately the answer presented itself very soon after posting the message. I pulled the hard drive out of the box, and tried to format it in a Windows machine. It occurred to me that the drive had not been formated and therefore had not had data written to all parts of the disk. Half way through the format I got an 'Unsafe removal of device' message, and upon reboot the drive was TOTALLY dead. It would be nice if FreeBSD had a SMARTY utility - it would have allowed me to possibly detect this failure. I've been told that work is underway to write one and it might be ready for 5.0. Cheers, Andrew On Mon, 2002-12-09 at 09:10, philipp wrote: > hey, > > i just browsed through the freebsd-questions archive and found your > mail (see below). > i am just wondering if you found out what the problem was and/or how > to solve it since i am in the same situation > > on Thu, Nov 28, 2002 at 12:11:48AM +1100, 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. > > > > 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-questions" in the body of the message > > regards -- Andrew Cutler To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message