From owner-freebsd-questions@FreeBSD.ORG Sat Apr 23 11:16:24 2005 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 7D3EA16A4CE for ; Sat, 23 Apr 2005 11:16:24 +0000 (GMT) Received: from smtp-out3.blueyonder.co.uk (smtp-out3.blueyonder.co.uk [195.188.213.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 323B543D5D for ; Sat, 23 Apr 2005 11:16:23 +0000 (GMT) (envelope-from xfb52@dial.pipex.com) Received: from [82.41.37.55] ([82.41.37.55]) by smtp-out3.blueyonder.co.uk with Microsoft SMTPSVC(5.0.2195.6713); Sat, 23 Apr 2005 12:17:00 +0100 Message-ID: <426A2E85.3060100@dial.pipex.com> Date: Sat, 23 Apr 2005 12:16:21 +0100 From: Alex Zbyslaw User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-GB; rv:1.7) Gecko/20040627 X-Accept-Language: en, en-us MIME-Version: 1.0 To: Chris Zumbrunn References: <5af4153cc97abfa75d403f30eb8e9963@czv.com> <4268E78D.6030009@dial.pipex.com> <42692350.3080102@dial.pipex.com> <42f9671b54b3016c2501bfebb7e97ddb@czv.com> In-Reply-To: <42f9671b54b3016c2501bfebb7e97ddb@czv.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 23 Apr 2005 11:17:00.0710 (UTC) FILETIME=[F83AF460:01C547F5] cc: questions@freebsd.org Subject: Re: Stuck in bootstrapping hell - how do I troubleshoot? 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: Sat, 23 Apr 2005 11:16:24 -0000 Chris Zumbrunn wrote: > Yes, I'm just waiting until someone has to go by there anyway in the > next days. No big deal, but it's not urgent enough to justify the trip > just for that. In the meantime, it is annoying to know that ultimately > I just have this problem because I'm doing something wrong! ...where > am I screwing up the setup? :-) The only other thing to occur to me was that the machine might actually be booting, but getting stuck somewhere maybe probing devices. I'm no expert on the bootup procedure, but I would doubt that /var/log/messages was being updated during device probes. The stuff is probably buffered somewhere and then written. One final thing I might try in your position is to copy a GENERIC kernel to the disk and see what happens when you reboot. Or even try a very pared down kernel with nothing but disks, ethernet card and whatever else is mandatory. I guess also compare the stuff in /boot with the machine that works. --Alex