From owner-freebsd-questions Sun Mar 15 13:33:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA03131 for freebsd-questions-outgoing; Sun, 15 Mar 1998 13:33:37 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from set.spradley.tmi.net (set.spradley.tmi.net [207.170.107.99]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA02392; Sun, 15 Mar 1998 13:32:20 -0800 (PST) (envelope-from tsprad@set.spradley.tmi.net) Received: from localhost (set.spradley.tmi.net) [127.0.0.1] by set.spradley.tmi.net with esmtp (Exim 1.82 #2) id 0yEKyr-00053H-00; Sun, 15 Mar 1998 15:30:05 -0600 X-Mailer: exmh version 2.0zeta 7/24/97 To: Jim Hodges cc: Colin Eric Johnson , freebsd-stable@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG, Free Unix Users of New Mexico Subject: Re: Trouble with kernel from FreeBSD-stable (2.2.6-beta?) In-reply-to: Your message of "Sun, 15 Mar 1998 15:43:48 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 15 Mar 1998 15:30:04 -0600 From: Ted Spradley Message-Id: Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > On Sun, 15 Mar 1998, Colin Eric Johnson wrote: > > I'm using the same config file that I used with the 2.2.5-release source > > and that kernel works just fine. When I build the kernel and boot I get > > the following: > > > > the kernel is labeled: 2.2.6-beta #0 > > > > Rebuild the kernel before you reboot. A bit late for that advice now. But Mr. Johnson said he had built a kernel. He didn't say that he rebuilt /sbin/mount. Perhaps that's the problem. Generally, 'make world' before you make and boot a new (upgraded, not just reconfigured) kernel. > > > Once all of the devices have been found and checked this new kernel > > attempts to change the device that root is on: > > > > changing root device to: wd0s2a > > I am unclear why this is wd0s2a instead of wd0s1a if the latter is really > your root partition. There has been a great deal of discussion on this list in the last few days about this of-by-one error. It boils down to: a) the slice number is one greater than it should be. b) don't worry about it. c) it will be fixed soon, but it's not as easy as it might seem. > > it then mounts swap and then begins the fsck. at this point it give the > > following error > > > > /dev/wd0a on /: specified device does not match mounted device. > > > > The compatability slice wd0a is going away and the code to mount root on > the actual slice has been put in place. > > Filesystem 1K-blocks Used Avail Capacity Mounted on > > /dev/wd0a 180495 43910 122146 26% / > > /dev/wd1s1e 1205727 944425 164844 85% /usr > > /dev/wd0s1e 149279 4360 132977 3% /var This is the situation the new /sbin/mount can deal with but the old one can't. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message