From owner-freebsd-current@FreeBSD.ORG Mon Jun 14 18:56:34 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7A27916A4CE for ; Mon, 14 Jun 2004 18:56:34 +0000 (GMT) Received: from bumble.loughton.me.uk (bumble.loughton.me.uk [81.2.68.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0350C43D39 for ; Mon, 14 Jun 2004 18:56:34 +0000 (GMT) (envelope-from spam_if_you_want_to@yahoo.co.uk) Received: from bumble.loughton.me.uk (bumble.loughton.me.uk [81.2.68.146]) by bumble.loughton.me.uk (Postfix) with ESMTP id 047F19A092 for ; Mon, 14 Jun 2004 19:56:43 +0100 (BST) Date: Mon, 14 Jun 2004 19:56:42 +0100 (BST) From: Richard Smith To: freebsd-current@freebsd.org Message-ID: X-The-Matrix: has you MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: unattended install of FreeBSD 5.2.1 does not umount disk properly X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jun 2004 18:56:34 -0000 I'm trying to do an unattended install of FreeBSD 5.2.1. If I don't include the 'shutdown' command at the end of the install.cfg file, the install works fine, but I have to manually reboot the machine after the install, which is no good for an unattended install. If I do include 'shutdown', then it appears that the disk does not unmount properly before the reboot. The console displays "syncing disks, buffers remaining". Normally I would expect a few numbers to be printed, followed by a reboot a second later. This what happens if the reboot is performed manually from the sysinstall menu. But when the reboot is performed automatically, after "syncing disks" it says: "WARNING - WRITE_DMA interrupt was seen but timeout fired LBA" and then prints the same number (e.g. 161) over and over again for several lines. After about 5 seconds the system reboots, but the new installation has errors on the filesystem and requires me to manually run fsck. This is no good for an unattended installation. Is there anyway to reboot the system from the install.cfg file and have it unmount cleanly? -- Richard