Date: Sat, 23 Apr 2005 12:16:21 +0100 From: Alex Zbyslaw <xfb52@dial.pipex.com> To: Chris Zumbrunn <chris@czv.com> Cc: questions@freebsd.org Subject: Re: Stuck in bootstrapping hell - how do I troubleshoot? Message-ID: <426A2E85.3060100@dial.pipex.com> In-Reply-To: <42f9671b54b3016c2501bfebb7e97ddb@czv.com> References: <5af4153cc97abfa75d403f30eb8e9963@czv.com> <f428b0f5d245cc46f5236416ba2b145c@czv.com> <4268E78D.6030009@dial.pipex.com> <a321c5840470646276c71827aa75bbb9@czv.com> <42692350.3080102@dial.pipex.com> <42f9671b54b3016c2501bfebb7e97ddb@czv.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?426A2E85.3060100>