From owner-freebsd-questions Wed Jun 30 13: 3:19 1999 Delivered-To: freebsd-questions@freebsd.org Received: from ucsu.Colorado.EDU (ucsu.Colorado.EDU [128.138.129.83]) by hub.freebsd.org (Postfix) with ESMTP id 20D9715656 for ; Wed, 30 Jun 1999 13:03:15 -0700 (PDT) (envelope-from doranj@ucsu.Colorado.EDU) Received: (from doranj@localhost) by ucsu.Colorado.EDU (8.9.3/8.9.3/ITS-5.0/standard) id OAA05983 for freebsd-questions@freebsd.org; Wed, 30 Jun 1999 14:03:14 -0600 (MDT) From: Jonathon Doran Message-Id: <199906302003.OAA05983@ucsu.Colorado.EDU> Subject: Re: hard disk Corrupted? To: freebsd-questions@freebsd.org Date: Wed, 30 Jun 1999 14:03:14 -0600 (MDT) In-Reply-To: <3.0.6.32.19990630135226.00c47560@intranet.com.mx> from "Jorge Biquez" at Jun 30, 99 01:52:26 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 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