From owner-freebsd-questions@FreeBSD.ORG Tue Nov 4 23:07:50 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 3EC81106564A for ; Tue, 4 Nov 2008 23:07:50 +0000 (UTC) (envelope-from popofnewslists@gmail.com) Received: from fk-out-0910.google.com (fk-out-0910.google.com [209.85.128.185]) by mx1.freebsd.org (Postfix) with ESMTP id B63C88FC1D for ; Tue, 4 Nov 2008 23:07:49 +0000 (UTC) (envelope-from popofnewslists@gmail.com) Received: by fk-out-0910.google.com with SMTP id k31so4020774fkk.11 for ; Tue, 04 Nov 2008 15:07:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:in-reply-to:mime-version:content-type:references :x-google-sender-auth; bh=8gDqMbU0Fb2iawWc3eAUuwYKjpp2kca7WfuUSczgwAw=; b=M4vrInUdfyZyPV7u/7tSJPkLFpe3TFZA/BlQ3gCIW0OKTrz7iZG7jWGzM4uzS5ZMSb HRcJD0BXAHQTzPUyd/mO8jb34zNjjd6V/fzXdUTrOdelSod2IhvxccGRjJU0F0CVDX4c vu1mQ3ghFR7M64Rl0FKT0gEfiCFIbghJ+41l0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:in-reply-to:mime-version :content-type:references:x-google-sender-auth; b=AWrBNoFDRrgPXryNy8AFWzA2ssXMaSIqttvk8Ml3lQCgbQz2o8eJ7jwfyBwiA2bIf7 8+PkFKp/vezunDb8eb84cHxNOyWV14FQPND1F1/fd2xXZ06RYW0Ym1ss7QuzJMFMEpVh DaPUzS3MdEP7kQ6IgoxNNQjVnvZB0rV1/0wzA= Received: by 10.181.139.10 with SMTP id r10mr51764bkn.64.1225840068441; Tue, 04 Nov 2008 15:07:48 -0800 (PST) Received: by 10.181.219.10 with HTTP; Tue, 4 Nov 2008 15:07:48 -0800 (PST) Message-ID: <9196e72b0811041507l1714614fw7b4bc8c2b901c763@mail.gmail.com> Date: Wed, 5 Nov 2008 00:07:48 +0100 From: "Popof Popof" Sender: popofnewslists@gmail.com To: "FreeBSD Questions" In-Reply-To: <584820.36562.qm@web56807.mail.re3.yahoo.com> MIME-Version: 1.0 References: <9196e72b0811041057m7d33e3fap9a15246def6eb3a2@mail.gmail.com> <584820.36562.qm@web56807.mail.re3.yahoo.com> X-Google-Sender-Auth: 90649b6cf1cf2360 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: Unable to mount / in read - write mode 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: Tue, 04 Nov 2008 23:07:50 -0000 The kernel used is a GENERIC one from 6.0. / is mounted but in read-only mode and I can use it in single user mode. The mount command has been created on October 26 2008 and I hadn't start my laptop since one year so I'm sure that this comes from my update. Using mount command manually failed: > #mount -w /dev/ad0s2a / > mount option is unknown > mount: /dev/ad0s2a My fstab file contains /dev/ad0s2a / ufs rw 1 1 > but ad0s2a is in ro mode as show mount output /dev/ados2a on / (ufs, local, read-only) > 2008/11/4 mdh > --- On Tue, 11/4/08, Popof Popof wrote: > > From: Popof Popof > > Subject: Unable to mount / in read - write mode > > To: "FreeBSD Questions" > > Date: Tuesday, November 4, 2008, 1:57 PM > > Hi, > > I recently tried to update my FreeBSD 6.0 to FreeBSD 7.0. > > I don't know where but I made a mistake and I am always > > booting on the 6.0 > > kernel. > > The problem is that I have an error during boot process: > > > > mount option is unknown > > > mount: /dev/ad0s2a : Invalid argument > > > Mounting root filesystem rw failed, startup aborted > > > Boot interrupted > > > > > > Its seems that tools have correctly upgraded (man mount let > > me see that I > > use the FreeBSD 7 version of mount) but not the kernel. > > > > Does someone has an idea to allow me to use my filesystem > > in read write mode > > ? > > This seems to be a problem with the mount command. Why do you feel the > kernel may be at fault? If the kernel can get to mount, then it has > obviously already mounted / (though possibly in read-only mode, which is > something you should let us know...) > There is also not necessarily a corrolation between a man page and the > actual binary. Check the binary's modification time and such for better > detail here. Beyond that, try running the mount command manually from the > command line after booting from a CD or in single-user mode, if single-user > mode works. > > - mdh > > > > >