From owner-freebsd-questions@FreeBSD.ORG Mon Sep 18 21:39:42 2006 Return-Path: X-Original-To: questions@freebsd.org 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 D181716A403 for ; Mon, 18 Sep 2006 21:39:42 +0000 (UTC) (envelope-from jeff.cross@averageadmins.com) Received: from S3.cableone.net (s3.cableone.net [24.116.0.229]) by mx1.FreeBSD.org (Postfix) with ESMTP id 67C7443D58 for ; Mon, 18 Sep 2006 21:39:42 +0000 (GMT) (envelope-from jeff.cross@averageadmins.com) Received: from [192.168.15.2] (unverified [24.117.124.174]) by S3.cableone.net (CableOne SMTP Service S3) with ESMTP id 74921469 for multiple; Mon, 18 Sep 2006 14:39:40 -0700 Message-ID: <450F1222.3080800@averageadmins.com> Date: Mon, 18 Sep 2006 16:39:46 -0500 From: Jeff Cross User-Agent: Thunderbird 1.5.0.7 (X11/20060914) MIME-Version: 1.0 To: Adam Martin References: <450F00C6.1060805@averageadmins.com> In-Reply-To: X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-IP-stats: Incoming Last 0, First 25, in=11, out=0, spam=0 X-External-IP: 24.117.124.174 X-Abuse-Info: Send abuse complaints to abuse@cableone.net Cc: questions@freebsd.org Subject: Re: Dell PE850 and FreeBSD 6.1-RELEASE - Boot Issues X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Sep 2006 21:39:42 -0000 Adam Martin wrote: > > On 2006 Sep 18 , at 16:25, Jeff Cross wrote: > >> I am trying to run FreeBSD 6.1-RELEASE on a Dell PowerEdge 850 with some >> booting issues. I have searched the archives and found someone having a >> problem with the machine "booting too fast" but my problem is a little >> different. My machine hangs up after the following line is displayed >> during boot: >> >> acd0: CDROM at ata0-master UDMA33 >> >> I have to poke the machine in the eye to get it back. The keyboard and >> everything locks up at that point. The only way I can get the machine >> to boot up successfully is to use option 5 from the boot menu, Verbose >> Logging. >> >> Is there a way around this? I know this is ghetto but just being able >> to make the machine use that boot menu option as the default would work >> fine I believe. It would ultimately be nice to not have this issue on >> boot but the verbose logging option seems to boot fine so that would >> work for the interim. >> >> I am attaching my dmesg output from the verbose boot. I can't seem to >> get anything in messages or dmesg from one of the failed boot attempts. > > I do not know what's causing this, but for the meantime, if you edit > /boot/defaults/loader.conf and copy the line that reads: > > verbose_loading="NO" > > Paste this line into /boot/loader.conf, (or /boot/loader.conf.local, > depending upon your setup...) and change NO to YES. This will force > verbose loading, always. I don't know if this will do everything > IDENTICAL to boot option 5, however, when looking at the Forth code for > it, it appears that it will, on first glance (but I'm a bit rusty on > that...) > >> Any help is greatly appreciated. If more information is required to >> troubleshoot this further, please let me know. > > Good luck. I hope that people still read this thread, to help > diagnose your dmesg, and find your problem. This is really just a > temporary fix. > > > [dmesg trimmed for brevity] > > Cheers, > > -- > ADAM David Alan Martin > > > -- > Adam David Alan Martin > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "freebsd-questions-unsubscribe@freebsd.org" > > > Thanks for the reply, Adam. I actually tried the verbose_logging="YES" in my /boot/loader.conf file prior to posting but it still hangs after the CD-ROM line for some reason. It appears the only way the machine will boot up properly is if I hit 5 on the boot menu. This obviously doesn't make remote reboots very "admin friendly"! Thanks again for your reply! Jeff Cross http://www.averageadmins.com/