From owner-freebsd-questions@FreeBSD.ORG Mon Aug 4 20:17:00 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A7D5A1065684 for ; Mon, 4 Aug 2008 20:17:00 +0000 (UTC) (envelope-from freebsd_user@guice.ath.cx) Received: from guice.ath.cx (cpe-72-225-169-69.nyc.res.rr.com [72.225.169.69]) by mx1.freebsd.org (Postfix) with ESMTP id 661C28FC20 for ; Mon, 4 Aug 2008 20:16:59 +0000 (UTC) (envelope-from freebsd_user@guice.ath.cx) Received: from [192.168.1.3] (cpe-72-225-169-69.nyc.res.rr.com [72.225.169.69]) (authenticated bits=0) by guice.ath.cx (8.13.1/8.12.9) with ESMTP id m74K1IWG042208 for ; Mon, 4 Aug 2008 16:01:29 -0400 (EDT) (envelope-from freebsd_user@guice.ath.cx) Message-ID: <48975FF8.6010207@guice.ath.cx> Date: Mon, 04 Aug 2008 16:00:56 -0400 From: freebsd_user@guice.ath.cx User-Agent: Thunderbird 2.0.0.16 (Windows/20080708) MIME-Version: 1.0 To: freebsd-questions@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: buildworld, buildkernel, installkernel, shutdow now, fsck -p -- NO WRITE ACCESS 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, 04 Aug 2008 20:17:00 -0000 I do not code in any way. With that being said, should you be able to help please do so with the knowledge that I can not code. I'm following the freebsd handbook when the following occurs. -- separate fresh 'dangerously dedicated' installs of both 7.0 and 6.3-RELEASE on the same machine, yield the following: In multi-user mode make buildworld, buildkernel and installkernel. Shutdown now -- fsck -p /dev/ad4s1a: NO WRITE ACCESS /dev/ad4s1a: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY This happens each and everytime no matter if I install from iso -or- ftp (passive). After numerous attempts the only way to get past this is 'fsck -y'. Could the fbsd handbook section I'm following need updating or is there another issue taking place here? 23.4.1 The Canonical Way to Update Your System 23.4.5 Drop to Single User Mode