From owner-freebsd-questions@FreeBSD.ORG Mon Jun 20 05:13:10 2011 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 04C86106564A for ; Mon, 20 Jun 2011 05:13:10 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (agora.rdrop.com [IPv6:2607:f678:1010::34]) by mx1.freebsd.org (Postfix) with ESMTP id B78998FC16 for ; Mon, 20 Jun 2011 05:13:09 +0000 (UTC) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id p5K5D7GD047700 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 19 Jun 2011 22:13:07 -0700 (PDT) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.12.9/Submit) with UUCP id p5K5D7SV047699; Sun, 19 Jun 2011 22:13:07 -0700 (PDT) Received: from fbsd61 by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA15565; Sun, 19 Jun 11 22:01:26 PDT Date: Sun, 19 Jun 2011 22:01:01 -0700 From: perryh@pluto.rain.com To: wblock@wonkity.com Message-Id: <4dfed40d.idBPTDCVernU+B1C%perryh@pluto.rain.com> References: <4dfd563d.IqfwMUCBOY6OTPc3%perryh@pluto.rain.com> In-Reply-To: User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: upgrading the root FS to read-write 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, 20 Jun 2011 05:13:10 -0000 Warren Block wrote: > On Sat, 18 Jun 2011, perryh@pluto.rain.com wrote: > > > After booting 8.1-RELEASE single-user, what must I do to upgrade > > the root FS mount from read-only to read-write? I have tried: > > > > # mount -u / > > That's what I use. Try running fsck on it first. I didn't try fsck -- it's a gjournal, so shouldn't need it, and had definitely been unmounted cleanly anyway -- but I did try -f which should have forced the upgrade even if it had needed a fsck. Still no upgrade, and no messages. What finally worked was to reboot, and do the upgrade before anything else (still without fsck, confirming that that was not the problem). There is pretty clearly some kind of bug involved. Perhaps there was a legitimate reason for the upgrade to fail, but it surely should not have failed _silently_.