"Popof Popof" <[EMAIL PROTECTED]> writes: > 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.
Yes, you do seem to have made a mess of your system, all right. If you hadn't used the machine lately anyway, you might find it easier to start from "scratch" (wipe out the installation and start over). But hopefully not. > Using mount command manually failed: > > >> #mount -w /dev/ad0s2a / >> mount option <update> 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) At least the device names seem to be the same. This might be something silly and minor. You can boot from CD (or floppy, flash drive, etc.) to edit the file, and try to edit the file. Remember that you need a newline at the end of the fstab file, and strange characters can confuse it. > > 2008/11/4 mdh <[EMAIL PROTECTED]> > >> --- On Tue, 11/4/08, Popof Popof <[EMAIL PROTECTED]> wrote: >> > From: Popof Popof <[EMAIL PROTECTED]> >> > Subject: Unable to mount / in read - write mode >> > To: "FreeBSD Questions" <firstname.lastname@example.org> >> > 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 <rw> 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 >> >> >> >> >> > _______________________________________________ > email@example.com mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ _______________________________________________ firstname.lastname@example.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"