From owner-freebsd-questions Wed Mar 6 18: 1:23 2002 Delivered-To: freebsd-questions@freebsd.org Received: from rutger.owt.com (rutger.owt.com [204.118.6.16]) by hub.freebsd.org (Postfix) with ESMTP id 7A50337B41B for ; Wed, 6 Mar 2002 18:01:19 -0800 (PST) Received: from owt.com (owt-207-41-94-232.owt.com [207.41.94.232]) by rutger.owt.com (8.9.3/8.9.3) with ESMTP id SAA07395; Wed, 6 Mar 2002 18:01:13 -0800 Message-ID: <3C86C9E7.30405@owt.com> Date: Wed, 06 Mar 2002 18:01:11 -0800 From: Kent Stewart User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011128 Netscape6/6.2.1 X-Accept-Language: en-us, es-mx MIME-Version: 1.0 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 References: <3C853C4C.B0437102@uber.com.br> <3C855FEE.7090509@owt.com> <3C86AD9A.67BD8766@uber.com.br> Content-Type: text/plain; charset=ISO-8859-1; format=flowed 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 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? I would try mount -u / If that doesn't work, use the command that is in /etc/fstab but do it for your current slice arrangement. Kent > > >>>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 > > > > > . > > -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://users.owt.com/kstewart/index.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message