EFI, UEFI, PXE: FreeBSD-12.1-RELEASE-amd64-bootonly.iso boot from SAN device failed, error 0x7f22208e
vas at sibptus.ru
Fri Dec 25 04:35:31 UTC 2020
Graham Perrin wrote:
> On 24/12/2020 13:44, Victor Sudakov wrote:
> > The network installation of 12.1 also fails, albeit slightly differently.
> > For FreeBSD-12.1-RELEASE-amd64-bootonly.iso I have even filmed the
> > process:http://admin.sibptus.ru/~/vas/VID_20201224_202519.mp4 (36 seconds)
> Thanks. From the tail of the recording: <https://i.imgur.com/6NfzmZ4.jpg>
> efipart_readwrite: rw=1, blk=0 size=8 status=16
> efipart_readwrite: rw=1, blk=32 size=68 status=16
> efipart_readwrite: rw=1, blk=15 size=65 status=16
> Failed to find bootable partition
> Boot from SAN device 0x80 failed: Error 0x7f22208e
> Unregistered SAN device 0x80
> Could not boot: Error 0x7f22208e (http://ipxe.org/7f22208e)
> FreeBSD aside,
Why "FreeBSD aside"? It's completely FreeBSD-related.
> for a moment:
> >> My guess is that your SAN disk does not have a structure that is
> compatible with EFI booting.
Exactly so! And as the SAN disk in this case is the disk image
(loaded over HTTP) this means that
FreeBSD-12.1-RELEASE-amd64-mini-memstick.img does not have a structure
that is compatible with EFI booting.
That's the problem I'm talking about. It is in the disk image structure.
> >> It is the firmware of the machine that returns errors to iPXE that it
> tries to do it's best to inform you about.
If you are thinking that the "SAN disk" here is something other than
the disk image fetched by HTTP, you are mistaken.
> For the issue with 12.1, you might like to join this discussion:
> Fail to install FreeBSD via PXE UEFI firmware | The FreeBSD Forums
I don't particularly like web fora but thanks for the link, I'll
Victor Sudakov, VAS4-RIPE, VAS47-RIPN
2:5005/49 at fidonet http://vas.tomsk.ru/
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 455 bytes
Desc: not available
More information about the freebsd-questions