Date: Thu, 07 Mar 2002 07:36:06 -0300 From: =?iso-8859-1?Q?Jos=E9?= Romildo Malaquias <romildo@uber.com.br> To: Kent Stewart <kstewart@owt.com> Cc: freebsd-questions@freebsd.org, romildo@uber.com.br Subject: Re: FreeBSD installed slice was renamead by Windows XP installer Message-ID: <3C874295.A03C5141@uber.com.br> References: <3C853C4C.B0437102@uber.com.br> <3C855FEE.7090509@owt.com> <3C86AD9A.67BD8766@uber.com.br> <20020307110541.E503@k7.mavetju.org> <3C872B69.589E062E@uber.com.br> <3C873539.1050008@owt.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Kent Stewart wrote: > José Romildo Malaquias wrote: > > > Edwin Groothuis wrote: > > > >>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 :-) > >> > > > > Unfortunatly it did not work. I have booted in single user mode (boot -s) > > and the system initialized correctly, although the root file system was > > mounted read only (as expected for single user mode booting). But > > remounting the root file system in read-write mode failed: > > > > # mount -u / > > mount: /dev/ad0s4a on /: specified device does not match mounted device > > This was kind of expected. > > > > > # mount -t ufs /dev/ad0s3a / > > mount: /dev/ad0s3a: No such file or directory > > > > Now I do not know what to do get my root file system mounted in > > read-write mode. If I do not specify the device file in the mount > > command, the system seems to consult the /etc/fstab file, which > > is wrong. If I instruct mount to use the correct device file, mounting > > files because the device file does not exist. > > If you do a df, what shows up? # df Filesystem 512-blocks Used Avail Capacity Mounted on /dev/ad0s3a 257980 82904 154440 35% / It is interesting how the root filesystem is mounted (read only) using the device file /dev/ad0s3a without a /dev/ad0s3a file. 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3C874295.A03C5141>