From owner-freebsd-current Mon Mar 23 13:01:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA07077 for freebsd-current-outgoing; Mon, 23 Mar 1998 13:01:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dean.pc.sas.com (sas90162.sas.com [192.58.190.162]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA07047 for ; Mon, 23 Mar 1998 13:00:53 -0800 (PST) (envelope-from brdean@dean.pc.sas.com) Received: (from brdean@localhost) by dean.pc.sas.com (8.8.8/8.8.8) id PAA03049; Mon, 23 Mar 1998 15:59:57 -0500 (EST) (envelope-from brdean) Message-Id: <199803232059.PAA03049@dean.pc.sas.com> From: "Brian Dean" Subject: sysinstall problem - umount /dist To: freebsd-current@FreeBSD.ORG Date: Mon, 23 Mar 1998 15:59:57 -0500 (EST) Reply-To: brdean@unx.sas.com X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm using a scripted installation to install FreeBSD and find that when the system boots for the first time after the install, 'fsck' complains that the disks have not be unmounted cleanly and begins repairs. In several cases, my system's name and IP address had not been flushed out to 'rc.conf'. This has been happening for several weeks now. I'm 99% sure that it did not occur with the 2/23 SNAP, but I can't narrow it down any more than that. What appears to happen is that the system reboots (without a panic or other message) before completing the umount of /dist. If I to the shell prompt at the main menu after the install completes, but before reboot, and issue 'umount /dist' before exiting, however, all is fine. Has anyone else seen this behavior, and is there a fix? Thanks, -Brian -- Brian Dean brdean@unx.sas.com Process Engineering The SAS Institute Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message