From owner-freebsd-questions Wed Mar 6 16: 6:16 2002 Delivered-To: freebsd-questions@freebsd.org Received: from topaz.mdcc.cx (topaz.mdcc.cx [212.204.230.141]) by hub.freebsd.org (Postfix) with ESMTP id 8302A37B427 for ; Wed, 6 Mar 2002 16:05:50 -0800 (PST) Received: from k7.mavetju.org (topaz.mdcc.cx [212.204.230.141]) by topaz.mdcc.cx (Postfix) with ESMTP id 76B212B671; Thu, 7 Mar 2002 01:05:47 +0100 (CET) Received: by k7.mavetju.org (Postfix, from userid 1001) id 1601A852; Thu, 7 Mar 2002 11:05:41 +1100 (EST) Date: Thu, 7 Mar 2002 11:05:41 +1100 From: Edwin Groothuis To: =?iso-8859-1?Q?Jos=E9_Romildo_Malaquias?= Cc: freebsd-questions@FreeBSD.ORG Subject: Re: FreeBSD installed slice was renamead by Windows XP installer Message-ID: <20020307110541.E503@k7.mavetju.org> Mail-Followup-To: Edwin Groothuis , =?iso-8859-1?Q?Jos=E9_Romildo_Malaquias?= , freebsd-questions@FreeBSD.ORG References: <3C853C4C.B0437102@uber.com.br> <3C855FEE.7090509@owt.com> <3C86AD9A.67BD8766@uber.com.br> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5.1i In-Reply-To: <3C86AD9A.67BD8766@uber.com.br>; from romildo@uber.com.br on Wed, Mar 06, 2002 at 09:00:26PM -0300 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 Wed, Mar 06, 2002 at 09:00:26PM -0300, José Romildo Malaquias wrote: > Kent Stewart wrote: > > > José Romildo Malaquias wrote: > > > > > I have installed FreeBSD 4.5 on my box in slice ad0s4. Another day > > > I have also installed Windows XP on my box in slice ad0s1. I do not > > > know why, but after Windows installation, slice numbering on my > > > disk was changed. Now the FreeBSD slice is ad0s3. And of course > > > I am unable to boot into FreeBSD successfuly. At boot time, the > > > root file system can not be mounted and I am asked what device > > > file to use in mounting it. Then I tell to mount it using /dev/ad0s3a. > > > It is then mounted in read only mode, but the other file systems also > > > fail mounting because of the same reason. I am presented > > > with a prompt for a shell to be used. In the shell I try to > > > mount the remainder files systems, but the system tells me > > > that the corresponding device does not exist. In fact, doing > > > an 'ls -l /dev/ad0s3*' command, I see that there is only the > > > /dev/ad0s3 device file. So I do not know how to proceed to > > > solve this problem. > > > > cd /dev > > sh MAKEDEV ad0s3h > > > > It will make everything. > > The root file system is being mounted in read only mode. Therefore > the device files can not be created. Also the /etc/fstab file can not > be edited to reflect the new partitions. > > How can I mount the root file system in read-write mode in this > situation? Go to single-user mode and just mount it. That will work, trust me :-) Edwin -- Edwin Groothuis | Personal website: http://www.MavEtJu.org edwin@mavetju.org | Interested in MUDs? Visit Fatal Dimensions: ------------------+ http://www.FatalDimensions.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message