From owner-freebsd-questions@FreeBSD.ORG Sun Jul 28 20:57:47 2013 Return-Path: Delivered-To: questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 1D6D64DA for ; Sun, 28 Jul 2013 20:57:47 +0000 (UTC) (envelope-from brett@lariat.net) Received: from mail.lariat.net (mail.lariat.net [66.62.230.51]) by mx1.freebsd.org (Postfix) with ESMTP id B5E4B2A6C for ; Sun, 28 Jul 2013 20:57:46 +0000 (UTC) Received: from Toshi.lariat.net (IDENT:ppp1000.lariat.net@localhost [127.0.0.1]) by mail.lariat.net (8.9.3/8.9.3) with ESMTP id OAA22279 for ; Sun, 28 Jul 2013 14:36:23 -0600 (MDT) Message-Id: <201307282036.OAA22279@mail.lariat.net> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Sun, 28 Jul 2013 14:36:18 -0600 To: questions@freebsd.org From: Brett Glass Subject: Help! Cannot boot after freebsd-update update to 9.1-p5 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Jul 2013 20:57:47 -0000 Help! I just used freebsd-update to upgrade a system to FreeBSD 9.1-RELEASE-p5 to close the latest security holes. I then rebuilt my custom kernel and tried to reboot. I'm now getting the message Can't work out which disk we are booting from. Guessed BIOS device 0xffffffff not found by probes, defaulting to disk0: at boot time. The strange thing is that when I boot the system from a FreeBSD 9.1 (AMD64) USB key, I can mount and read the file system on the hard drive that will not boot. There doesn't seem to be any problem with it. I've tried copying /boot/loader over from the USB key; still can't boot. Tried moving the GENERIC kernel over from the USB key into /boot/kernel, just in case there was a problem with my custom one; still can't boot. Not sure what to try next. Any ideas would be much appreciated! --Brett Glass