From owner-freebsd-stable Sat Mar 14 11:04:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA19847 for freebsd-stable-outgoing; Sat, 14 Mar 1998 11:04:30 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from netcom1.netcom.com (mvh@netcom14.netcom.com [192.100.81.126]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA19835 for ; Sat, 14 Mar 1998 11:04:26 -0800 (PST) (envelope-from mvh@netcom.com) Received: (from mvh@localhost) by netcom1.netcom.com (8.8.8/8.8.8) id LAA26384; Sat, 14 Mar 1998 11:04:21 -0800 (PST) (envelope-from mvh) Date: Sat, 14 Mar 1998 11:04:21 -0800 (PST) Message-Id: <199803141904.LAA26384@netcom1.netcom.com> From: "Michael V. Harding" To: robert+freebsd@cyrus.watson.org CC: bsampley@best.com, stable@FreeBSD.ORG In-reply-to: (message from Robert Watson on Sat, 14 Mar 1998 13:06:23 -0500 (EST)) Subject: Re: More problems with new slice code References: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk I and everyone I know has been bitten by ./MAKEDEV deleting existing slices. This can make the system fail in a way that can take up to a day of headscratching to fix. And you can't even read the man pages. Could ./MAKEDEV make all slices by default, instead? Date: Sat, 14 Mar 1998 13:06:23 -0500 (EST) From: Robert Watson X-Sender: robert@trojanhorse.pr.watson.org Reply-To: Robert Watson cc: stable@FreeBSD.ORG Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-UIDL: 3006ebd6af756621c094b935215fb7ba On Sat, 14 Mar 1998, Burton Sampley wrote: > For anyone interested, I found a solution to the problem described below. > I just cd'ed in /dev/ and ran ./MAKEDEV for each slice being used. I then > modified /etc/fstab with the correct slices for each filesystem and booted > under the new kernel. Everything has gone perfect after. I had a similar nasty experience. It was made nastier by the fact that I did a MAKEDEV and then booted without changing fstab -- MAKEDEV deleted my wd0a /dev entries, putting me back in single user mode again! There seem to be some transaction problems with the current arrangement, but they largely have to do with slightly irregular slice configurations (such as my config with two slices, only the a partition on the first, and a failure to have the /dev entries). Robert N Watson Carnegie Mellon University http://www.cmu.edu/ SafePort Network Services http://www.safeport.com/ robert@fledge.watson.org http://www.watson.org/~robert/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message