Date: Mon, 25 Jan 1999 01:24:41 -0500 From: Chris Johnson <cjohnson@palomine.net> To: "Jason C. Wells" <jcwells@u.washington.edu> Cc: Steve Proctor <sproctor@calweb.com>, freebsd-questions@FreeBSD.ORG Subject: Re: Mount Failure! Message-ID: <19990125012441.A16471@palomine.net> In-Reply-To: <Pine.BSF.4.05.9901250505251.348-100000@s8-37-26.student.washington.edu>; from Jason C. Wells on Mon, Jan 25, 1999 at 05:11:26AM %2B0000 References: <Pine.BSF.4.02A.9901242034520.12510-100000@web1.calweb.com> <Pine.BSF.4.05.9901250505251.348-100000@s8-37-26.student.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jan 25, 1999 at 05:11:26AM +0000, Jason C. Wells wrote: > On Sun, 24 Jan 1999, Steve Proctor wrote: > > >"MOUNT: /dev/wd0s1a on /: specified device does not match mounted device > >Filesystem mount failed, startup aborted" > > I am a bit fuzzy on the precise details of this. The problem is with > compatibilty slice naming and mount. Some changes have been made and I am > not sure that I am fully up to snuff yet. > > YMMV!!! > > Try > 'boot -s' > 'fsck /dev/wd0a' or 'fsck /dev/wd0s1a'to make sure it's clean > 'mount /dev/wd0a /' or 'mount /dev/wd0s1a /' > 'mount -u /' > mount your /usr partition > 'vi /etc/fstab' > change your root partition to wd0a instead os wd0s1a > > I just did this ten minutes ago. Something seems fishy about the whole > thing but it is working for me. You'll probably have the same problem the next time you cvsup. I got bitten by this earlier today, and it looks like it was fixed later in the day. I re-cvsupped and things work like they did before-- /dev/wd0s1a is mounted on /, not /dev/wd0a. Chris 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?19990125012441.A16471>