From owner-freebsd-questions Wed Mar 6 15:59:42 2002 Delivered-To: freebsd-questions@freebsd.org Received: from dot.uber.com.br (ctbcnetsuper-146.xdsl-fixo.ctbcnetsuper.com.br [200.225.201.146]) by hub.freebsd.org (Postfix) with SMTP id 3745137B404 for ; Wed, 6 Mar 2002 15:59:36 -0800 (PST) Received: (qmail 28727 invoked from network); 6 Mar 2002 20:57:59 -0000 Received: from ctbcnetsuper-204.xdsl-dinamico.ctbcnetsuper.com.br (HELO uber.com.br) (200.225.205.204) by 0 with SMTP; 6 Mar 2002 20:57:59 -0000 Message-ID: <3C86AD9A.67BD8766@uber.com.br> Date: Wed, 06 Mar 2002 21:00:26 -0300 From: =?iso-8859-1?Q?Jos=E9?= Romildo Malaquias Organization: UFOP X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.4.18 i686) X-Accept-Language: en MIME-Version: 1.0 To: Kent Stewart Cc: freebsd-questions@FreeBSD.ORG Subject: Re: FreeBSD installed slice was renamead by Windows XP installer References: <3C853C4C.B0437102@uber.com.br> <3C855FEE.7090509@owt.com> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit 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 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? > > Any clues? Romildo -- Prof. José Romildo Malaquias Departamento de Computação http://iceb.ufop.br/~romildo Universidade Federal de Ouro Preto romildo@iceb.ufop.br Brasil romildo@uber.com.br To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message