From owner-freebsd-questions Mon May 21 20: 3: 8 2001 Delivered-To: freebsd-questions@freebsd.org Received: from itouch.co.nz (itouch.co.nz [203.99.66.188]) by hub.freebsd.org (Postfix) with ESMTP id AC5EA37B422 for ; Mon, 21 May 2001 20:03:04 -0700 (PDT) (envelope-from jonc@itouch.co.nz) Received: (from jonc@localhost) by itouch.co.nz (8.11.3/8.11.1) id f4M32ip41416; Tue, 22 May 2001 15:02:44 +1200 (NZST) (envelope-from jonc) Date: Tue, 22 May 2001 15:02:44 +1200 From: Jonathan Chen To: Pete Christie Cc: "questions@FreeBSD.ORG" Subject: Re: (newbie)/usr file system has UNEXPECTED INCONSISTANICES Message-ID: <20010522150243.A40939@itouchnz.itouch> References: <3B09CF4B.6DEE4BED@idsi.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3B09CF4B.6DEE4BED@idsi.net>; from christie@idsi.net on Mon, May 21, 2001 at 10:30:36PM -0400 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 On Mon, May 21, 2001 at 10:30:36PM -0400, Pete Christie wrote: [...] > I was mucking around with Gnome (and enlightenment) (nothing to deep, > just poking around the typical 'user' stuff, I wasn't messing with any > .conf files or anything) on a relatively new install of v4.2 and when I > tried to exit and the system locked up, I tried the Ctrl-Alt-BackSpace, > but the machine rebooted and now I get an error message that /usr can't > be mounted because of 'UNEXPECTED INCONSISTENCIES'. While I'd like to > get to the root (ha! my first -nix humor) of the lockup, I'm gonna need > to have /usr back if at all possible. Now I understand I'm supposed to > include some log files and such, but at this point I could spend a few > evenings just figuring out how to get this info over to my Win98 machine > to include it in this message, so please forgive me . . . See if you can boot single user. This is done by hitting the spacebar when the countdown to boot begins; and then enter boot -s This should bring you to single user mode. Accept the default /bin/sh as your root shell. After you're in, try fsck'ing /usr # fsck -y /usr Depending on how bad the damage is, it may ask you to redo this again. If all goes well, you may be able to go multiuser with a repaired /usr. To exit single-user mode, a Control-D or # exit will start the multiuser boot process. -- Jonathan Chen ---------------------------------------------------------------------- "You can get farther with a kind word and a gun than you can with a kind word alone" - Al Capone To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message