From owner-freebsd-questions Fri Mar 13 10:21:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA13666 for freebsd-questions-outgoing; Fri, 13 Mar 1998 10:21:44 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from bsampley.vip.best.com (bsampley.vip.best.com [206.184.160.196]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA13576 for ; Fri, 13 Mar 1998 10:21:14 -0800 (PST) (envelope-from bsampley@best.com) Received: from localhost (localhost [127.0.0.1]) by bsampley.vip.best.com (8.8.8/8.8.7) with SMTP id KAA00429; Fri, 13 Mar 1998 10:19:37 -0800 (PST) (envelope-from bsampley@best.com) Date: Fri, 13 Mar 1998 10:19:00 -0800 (PST) From: Burton Sampley X-Sender: bsampley@bsampley.vip.best.com To: freebsd-questions@FreeBSD.ORG cc: Kent Vander Velden Subject: Re: root filesystem and -current In-Reply-To: <19980313133514.09198@freebie.lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- I just cvsup'ed to -stable yesterday (980312) from -stable as of 980219. I have a similar problem as noted below. I also tried changing /etc/fstab to have root mounted on /dev/sd0s1a but that bombed worse than the other. My 1st try with my original fstab was at least able fsck all filesystems in my /etc/fstab BEFORE not being able to mount the kernel and throwing me into single user mode. I had to dust off my boot.flp and use fixit to back in to send this message. Basically, what's the fix? - -burton- - --------------- Burton Sampley bsampley@best.com or bsampley@haywire.csuhayward.edu PGP key available at http://www.best.com/~bsampley/pgp.html On Fri, 13 Mar 1998, Greg Lehey wrote: > > On Thu, 12 March 1998 at 18:24:28 -0600, Kent Vander Velden wrote: > > > > Hos something changed in -current during the past two weeks that would > > affect how the root filesystem is mounted? ^-current^-stable (for csh users) > Yes. For a more constructive use of limited banwidth, Greg's flame has be removed. > > The problem that I am seeing at the moment is with a new -current > > kernel, the root file system will fail to mount on boot. Running > > mount with no arguments shows that / has the device 'root_device' > > mounted on it and not '/dev/sd0a' as I would aspect. When I try to > > mount '/dev/sd0a' on / mount gives the error: "Specified device does > > not match mounted device.\n". I will try recompiling mount in a > > moment. Any other suggestions? ditto here under -stable > What has happened is relatively complicated: they've eliminated the > "compatibility slice", so you will no longer be able to mount > /dev/sd0a. Use /dev/sd0s1a instead (in /etc/fstab). Don't be put off > by the fact that it will then claim to mount /dev/sd0s2a; that's a > known bug. If that didn't work, any other solutions/suggestions? -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNQl4mnt2O8KJtMdBAQFAkwQAq6KR4fgU6ePu5DtTfI8v1zd2qVMTPTWx YV5dINjGEAoffYdHBxjN8qWX8rMB+IpYsf/+zAx1lCeqLfmAZ64s01BUNEMVGNTb IDkaI4AoWJZLg0iphRKX9nofOI/7H8BBRskSbSWFvdDSf+FZS5STu27U4KTnUIq7 ziuzbG9a+Mw= =g2By -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message