From owner-freebsd-questions@FreeBSD.ORG Mon Apr 23 20:31:52 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AD9BE16A400 for ; Mon, 23 Apr 2007 20:31:52 +0000 (UTC) (envelope-from youshi10@u.washington.edu) Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mx1.freebsd.org (Postfix) with ESMTP id 8ECA413C45A for ; Mon, 23 Apr 2007 20:31:52 +0000 (UTC) (envelope-from youshi10@u.washington.edu) Received: from hymn03.u.washington.edu (hymn03.u.washington.edu [140.142.12.169]) by mxout1.cac.washington.edu (8.13.7+UW06.06/8.13.7+UW07.03) with ESMTP id l3NKVqT7031372 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 23 Apr 2007 13:31:52 -0700 Received: from localhost (localhost [127.0.0.1]) by hymn03.u.washington.edu (8.13.7+UW06.06/8.13.7+UW07.03) with ESMTP id l3NKVph5022498 for ; Mon, 23 Apr 2007 13:31:51 -0700 X-Auth-Received: from [192.55.52.1] by hymn03.u.washington.edu via HTTP; Mon, 23 Apr 2007 13:31:51 PDT Date: Mon, 23 Apr 2007 13:31:51 -0700 (PDT) From: youshi10@u.washington.edu To: freebsd-questions@freebsd.org In-Reply-To: <644792.46664.qm@web58104.mail.re3.yahoo.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-PMX-Version: 5.3.1.294258, Antispam-Engine: 2.5.1.298604, Antispam-Data: 2007.4.23.131934 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='SUPERLONG_LINE 0.05, NO_REAL_NAME 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __RUS_SUBJ_ALL_UCASE_1251 0, __RUS_SUBJ_ALL_UCASE_KOI8R 0, __SANE_MSGID 0' Subject: Re: UNEXPECTED SOFT UPDATE INCONSISTENCY X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Apr 2007 20:31:52 -0000 On Mon, 23 Apr 2007, L Goodwin wrote: [...] > I assume I'll have to run fsck on /usr, but have 2 questions: > 1) Is this problem caused by yesterday's accidental power-off? Yes, most likely. > 2) What prompts should I expect from fsck, and how should I reply to each in order to resolve this problem correctly? Just say yes to all the prompts, but backup any important data first. Or if you're afraid of any issues, reinstall. If this problem persists (near every time you reboot), it's time to get a new drive because it got toasted during a write phase. I wouldn't say that though until you install from scratch though and verify that that is or is not the case. -Garrett