From owner-freebsd-questions Thu Apr 25 14: 6: 1 2002 Delivered-To: freebsd-questions@freebsd.org Received: from infinity.aesredfish.net (ns1.aesredfish.net [65.168.0.12]) by hub.freebsd.org (Postfix) with ESMTP id 9F87E37B405 for ; Thu, 25 Apr 2002 14:05:47 -0700 (PDT) Received: from potentialtech.com (mhope-dhcp-65-168-1-181.dashfast.com [65.168.1.181]) by infinity.aesredfish.net (8.11.6/8.11.0) with ESMTP id g3PL3qm20596; Thu, 25 Apr 2002 17:03:52 -0400 Message-ID: <3CC87069.9020304@potentialtech.com> Date: Thu, 25 Apr 2002 17:08:57 -0400 From: Bill Moran Organization: Potential Technologies User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:0.9.3) Gecko/20010914 X-Accept-Language: en-us MIME-Version: 1.0 To: Vinod Cc: freebsd-questions@freebsd.org Subject: Re: boot at night References: <20020425205415.12704.qmail@web21103.mail.yahoo.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Vinod wrote: > i had this question a month ago but didnt get any > solutions yet.my dual boot(fbsd 4.5 release and win2k) > dell dimension 4300,strangely boots at around 3:20 am > everyday.the /var/log/messages shows it up just as a > normal boot.nothing unusual.its not a power problem > too as the boot problem doesnt occur if its loaded up > and kept with win2k. Does /var/log/messages show "/ was not proprely dismounted"? If so, that indicates that a panic may have occurred, you could set the various settings to capture a crash dump in rc.conf and see where it's crashing from. However, if my memory serves correctly, 4.5-RELEASE had an elusive filesystem bug in it that affected just enough people to be annoying, but too few to be diagnosed and fixed quickly. 3:30 AM is about when certain automatic system maintenance should be running, and that's probably running the disk rather hard, causing the panic. The filesystem problem has been fixed, read the handbook and upgrade your system to 4.5-STABLE. I'd be willing to bet the problem will go away. If it doesn't, configure the system to collect crash dumps and see if you can collect enough information to file a problem report. Actually, it's a good idea to have your system configed for crash dumps no matter what. -- Bill Moran Potential Technology http://www.potentialtech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message