From owner-freebsd-questions Wed Jun 30 13: 9:49 1999 Delivered-To: freebsd-questions@freebsd.org Received: from mail2.uunet.ca (mail2.uunet.ca [142.77.1.15]) by hub.freebsd.org (Postfix) with ESMTP id 9F26314CA8 for ; Wed, 30 Jun 1999 13:09:46 -0700 (PDT) (envelope-from ponnamp@tradeit.com) Received: from tradeit.com ([199.45.117.40]) by mail2.uunet.ca with SMTP id <50544-2450>; Wed, 30 Jun 1999 16:09:42 -0400 Received: from anandhapc ([192.9.211.106]) by tradeit.com (4.1/SMI-4.1) id AA15430; Wed, 30 Jun 99 16:10:15 EDT From: "Anandha Ponnampalam" To: "Jonathon Doran" , Subject: RE: hard disk Corrupted? Date: Wed, 30 Jun 1999 16:10:20 -0400 Message-Id: <003001bec334$94435930$6ad309c0@anandhapc.vtidev.ca> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-Msmail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 X-Mimeole: Produced By Microsoft MimeOLE V4.72.3612.1700 In-Reply-To: <199906302003.OAA05983@ucsu.Colorado.EDU> Importance: Normal Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG does fsck also check for bad sectors? . -----Original Message----- . From: owner-freebsd-questions@FreeBSD.ORG . [mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of Jonathon Doran . Sent: Wednesday, June 30, 1999 4:03 PM . To: freebsd-questions@freebsd.org . Subject: Re: hard disk Corrupted? . . . > I just installed version 3.1 . It is running fine. . > I had a problem with the no break connected to that machine and . the machine . > wents down when the energy fail. The system restarted without . trouble and I . > run a FSCK . . > ***** PLEASE RERUN FSCK ***** . > ** /dev/rwd0s1e . > ** Last Mounted on /var . > ** Phase 1 - Check Blocks and Sizes . > ** Phase 2 - Check Pathnames . > ** Phase 3 - Check Connectivity . > ** Phase 4 - Check Reference Counts . > ** Phase 5 - Check Cyl groups . > 381 files, 3211 used, 26540 free (52 frags, 3311 blocks, 0.2% . fragmentation) . > . > ***** FILE SYSTEM STILL DIRTY ***** . . . . This probably isn't too bad. Anytime the system goes down . without a proper . unmount, you run the risk of having inconsistent file system info. What . you need to do is to boot the machine and unmount these filesystems. Then . run fsck against the raw device (/dev/rwd0s1e). You may want to boot . in single user mode (boot -s at the prompt), when doing this. . . Jon Doran . . . To Unsubscribe: send mail to majordomo@FreeBSD.org . with "unsubscribe freebsd-questions" in the body of the message . To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message