From owner-freebsd-stable@freebsd.org Wed Nov 18 19:14:08 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 37D3DA328BB for ; Wed, 18 Nov 2015 19:14:08 +0000 (UTC) (envelope-from rainer@ultra-secure.de) Received: from mail.ultra-secure.de (mail.ultra-secure.de [88.198.178.88]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A0E6D13E0 for ; Wed, 18 Nov 2015 19:14:07 +0000 (UTC) (envelope-from rainer@ultra-secure.de) Received: (qmail 61621 invoked by uid 89); 18 Nov 2015 19:10:31 -0000 Received: from unknown (HELO ?192.168.1.200?) (rainer@ultra-secure.de@217.71.83.52) by mail.ultra-secure.de with ESMTPA; 18 Nov 2015 19:10:31 -0000 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\)) Subject: Re: After BIOS-Upgrade, I can't (UEFI-) boot anymore From: Rainer Duffner In-Reply-To: <81C9CF72068BAA4C85C4FA6FF062C7B367809725@MFRSEXCH-HQ.merseyfire.gov.uk> Date: Wed, 18 Nov 2015 20:10:30 +0100 Cc: freebsd-stable , "freebsd-proliant@freebsd.org" Content-Transfer-Encoding: quoted-printable Message-Id: References: <9A4A45D3-AED0-4312-AA05-47F24BE9D24F@ultra-secure.de> <81C9CF72068BAA4C85C4FA6FF062C7B367809725@MFRSEXCH-HQ.merseyfire.gov.uk> To: "O'Connor, Kevin" X-Mailer: Apple Mail (2.3096.5) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Nov 2015 19:14:08 -0000 > Am 18.11.2015 um 14:33 schrieb O'Connor, Kevin = : >=20 >=20 >=20 > =46rom the wiki >=20 > The boot process proceeds as follows: >=20 > UEFI firmware runs at power up and searches for an OS loader in the = EFI system partition. The path to the loader may be set by an EFI = environment variable, with a default of /EFI/BOOT/BOOTX64.EFI. >=20 > For FreeBSD, boot1.efi is installed as /EFI/BOOT/BOOTX64.EFI. > boot1.efifat is an image of such a FAT filesystem for use by = bsdinstall=20 > boot1.efi locates the first partition with a type of freebsd-ufs, = and from it loads loader.efi. (This may be a different disk than the one = holding the EFI system partition.) > loader.efi loads and boots the kernel, as described in loader(8). >=20 > So my best guess is that something has been changed by the upgrades = and boot1.efi no longer knows the correct location of /boot/loader.efi >=20 > You'll have to go digging in the EFI system partition to work out what = has changed. (I assume you have done an automated install of the HP = support DVD and upgraded the array controller and the HDD microcode = etc.) >=20 > Kevin >=20 I=E2=80=99ve figured it out already (after sleeping a few hours and = looking at it all morning. The system contains an additional controller (H240, in JBOD mode) that = hosts another 8 disks. The first of these disks previously (and briefly) housed another FreeBSD = installation, with the GPT etc. that comes with it. Even though it was now part of a zpool, the labels etc. persisted. I had = forgotten about this... Upon the BIOS upgrade, the system suddenly started looking at this disk, = too and tried to boot from it. I had to offline the disk, remove the partitions and the GPT and online = the disk again - and then it would boot again.