Date: Thu, 17 Jun 2004 14:49:34 GMT From: Richard Smith <spam_if_you_want_to@yahoo.co.uk> To: freebsd-gnats-submit@FreeBSD.org Subject: misc/68047: unattended install of FreeBSD 5.2.1 does not umount disk properly Message-ID: <200406171449.i5HEnYRd008935@www.freebsd.org> Resent-Message-ID: <200406171450.i5HEoKgD007036@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 68047 >Category: misc >Synopsis: unattended install of FreeBSD 5.2.1 does not umount disk properly >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Jun 17 14:50:20 GMT 2004 >Closed-Date: >Last-Modified: >Originator: Richard Smith >Release: 5.2.1 >Organization: >Environment: >Description: 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. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200406171449.i5HEnYRd008935>