> -----Original Message-----
> From: owner-freebsd-proliant at freebsd.org [mailto:owner-freebsd-
> proliant at freebsd.org] On Behalf Of Rainer Duffner
> Sent: 17 November 2015 23:13
> To: freebsd-stable <freebsd-stable at freebsd.org>
> Cc: freebsd-proliant at freebsd.org
> Subject: After BIOS-Upgrade, I can't (UEFI-) boot anymore
>
> Hi,
>
> I have a HP DL380 G9, that I boot from an internal SmartArray Controller
> provided RAID1 into FreeBSD 10.1 amd64.
>
> I have upgraded the BIOS to the 2015-10 release and on reboot, I now get a
> message that
>
> /boot/loader.efi
>
> can?t be found.
>
> I can legacy boot it into mfsbsd and the file is there.
>
> How can I fix this?
> Or how can I debug this and why is this failing in the first place?
From the wiki
The boot process proceeds as follows:
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.
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
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).
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
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.)
Kevin
>
>
> Rainer
>
> _______________________________________________
> freebsd-proliant at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-proliant
> To unsubscribe, send any mail to "freebsd-proliant-
> unsubscribe at freebsd.org"
This e-mail and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed.
If you have received this e-mail in error please notify the originator of the
message.
Any views expressed in this message are those of the individual sender, except
where the sender specifies and with authority, states them to be the views of
Merseyside Fire & Rescue Service, (MFRS).
Incoming and outgoing emails may be monitored in line with current legislation.
Steps have been taken to ensure that this email and attachments are free from
any virus. In keeping with good computing practice the recipient should ensure
they are actually virus free.
http://www.merseyfire.gov.uk/