From owner-freebsd-stable Fri Mar 13 12:41:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA06526 for freebsd-stable-outgoing; Fri, 13 Mar 1998 12:41:28 -0800 (PST) (envelope-from owner-freebsd-stable@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 MAA06493 for ; Fri, 13 Mar 1998 12:41:20 -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 MAA00291 for ; Fri, 13 Mar 1998 12:39:48 -0800 (PST) (envelope-from bsampley@best.com) Date: Fri, 13 Mar 1998 12:39:42 -0800 (PST) From: Burton Sampley X-Sender: bsampley@bsampley.vip.best.com To: stable@FreeBSD.ORG Subject: More problems with new slice code Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk -----BEGIN PGP SIGNED MESSAGE----- Greetings, Has anyone else run into this problem: Some time ago, in a past life, I ran /dev/MAKEDEV all. The next time I rebooted the system it puked into single user mode because apparently all the slice info had been blown away. Now when I try to convert over the the new slice code (last cvsup'ed and make world as of 980312 for -stable) it dies on mounting root. Since I cvsup'ed 4 days after the commit I'm assuming I also have the necessary changes to mount. When my system boots under the new kernel with my original /etc/fstab file all the files systems appear to come up clean except for that nasty little note which says: /dev/sd0a on /: Specified device does not match mounted device KABOOM ---> single user mode /sbin/mount root_device on / (local, read-only) Here's my original /etc/fstab: bsampley(102)% cat /etc/fstab # Device Mountpoint FStype Options Dump Pass# /dev/sd0b none swap sw 0 0 /dev/sd0a / ufs rw 1 1 /dev/sd0g /usr ufs rw 2 2 /dev/sd0f /usr/obj ufs rw,noatime,async 2 2 /dev/sd0e /var ufs rw 2 2 /dev/sd1e /usr/src ufs rw,noatime,async 2 2 proc /proc procfs rw 0 0 /dev/cd0c /cdrom cd9660 ro,noauto 0 0 bsampley(103)% I also tried it with root pointing to /dev/sd0s1a and /dev/sd0s2a, both bombed out before checking the file systems. Please note, this is a NON dangerously dedicated disk. It shares with M$ (for games only) and Linux (just to goof around with). Any ideas? - --------------- Burton Sampley bsampley@best.com or bsampley@haywire.csuhayward.edu PGP key available at http://www.best.com/~bsampley/pgp.html -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNQmZlHt2O8KJtMdBAQGh4AQAnGl4zcNNUSxNVewQBe7n4g2Axk94zIsu 3y1TFd6qTwa49pgucUUFcxe2ynMVi1GVlGbQvJyf9vi4Or75R+x4tID3hGCS05Ip YvSo0QOHj9VPyz/LRaeAZ6ssrPgedq32POKfHgJ6qQizeeP9riSsYUIaIANuAr5J 9sh6w0RIwNE= =skE0 -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message