From owner-freebsd-questions@FreeBSD.ORG Fri Jun 13 08:43:54 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7305937B409 for ; Fri, 13 Jun 2003 08:43:54 -0700 (PDT) Received: from pa-plum1b-166.pit.adelphia.net (pa-plum1b-217.pit.adelphia.net [24.53.161.217]) by mx1.FreeBSD.org (Postfix) with ESMTP id A437D43FA3 for ; Fri, 13 Jun 2003 08:43:53 -0700 (PDT) (envelope-from wmoran@potentialtech.com) Received: from potentialtech.com (working [172.16.0.95]) h5DFhqOg002911; Fri, 13 Jun 2003 11:43:53 -0400 (EDT) (envelope-from wmoran@potentialtech.com) Message-ID: <3EE9F138.4030200@potentialtech.com> Date: Fri, 13 Jun 2003 11:43:52 -0400 From: Bill Moran User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3) Gecko/20030429 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Rohit References: <200306131011.47302.rohitvis@rogers.com> <3EE9DCDB.20607@potentialtech.com> <200306131035.51185.rohitvis@rogers.com> In-Reply-To: <200306131035.51185.rohitvis@rogers.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: questions@freebsd.org Subject: Re: Booting takes too long. Why? (/ was not properly dismounted) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jun 2003 15:43:54 -0000 Rohit wrote: > Here is the dmesg. However, I should tell you that this has been the case with > all my FreeBSD boxes. I have two PC's running FreeBSD and a Compaq laptop > running FreeBSd all have different types of harddrives. > > The main problem is that everytime I boot I get the message saying / was not > dismounted properly and then it goes through and fixes all the drive block > errors. (This is the case on all my computers) My mistake ... I misread your original post. > I shutdown using the shutdown -h now command > or reboot using reboot now How big is your / partition? During the halt/reboot sequence, does it give any errors? Are all the buffers flushed? I'm grasping at straws here ... Is there some daemon running that takes too long to shutdown or doesn't shutdown cleanly, thus preventing the system from flushing all its buffers and marking the fs clean? One thing to try: manually stop all processes that you can, then issue "sync" a few times, then (when disk activity has stopped) issue reboot. See if / is still dirty on reboot. Does fsck succeed during boot? Possibly boot into single-usr mode and issue "fsck -y" until the filesystems are all marked clean, then try your standard method of rebooting and see if the / partition is now clean. Many guesses here. Hopefully one of them will be helpful. -- Bill Moran Potential Technologies http://www.potentialtech.com