Date: Fri, 25 Dec 2020 11:35:27 +0700 From: Victor Sudakov <vas@sibptus.ru> To: freebsd-questions@freebsd.org Subject: Re: EFI, UEFI, PXE: FreeBSD-12.1-RELEASE-amd64-bootonly.iso boot from SAN device failed, error 0x7f22208e Message-ID: <20201225043527.GA52325@admin.sibptus.ru> In-Reply-To: <a24b96bd-a446-383d-11b7-601b5b96539a@gmail.com> References: <20201223025406.GA25600@admin.sibptus.ru> <af710389-3e9a-6f0d-98e4-d69aab875fed@gmail.com> <20201223104459.GA36737@admin.sibptus.ru> <6cbaa416-0262-c85f-8e74-19a8ac95605d@gmail.com> <20201224134403.GB13527@admin.sibptus.ru> <a24b96bd-a446-383d-11b7-601b5b96539a@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--7AUc2qLy4jB3hD7Z Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Graham Perrin wrote: > On 24/12/2020 13:44, Victor Sudakov wrote: >=20 > > The network installation of 12.1 also fails, albeit slightly differentl= y. > >=20 > > For FreeBSD-12.1-RELEASE-amd64-bootonly.iso I have even filmed the > > process:http://admin.sibptus.ru/~/vas/VID_20201224_202519.mp4 (36 seco= nds) >=20 >=20 > Thanks. From the tail of the recording: <https://i.imgur.com/6NfzmZ4.jpg>; >=20 > =E2=80=A6 > efipart_readwrite: rw=3D1, blk=3D0 size=3D8 status=3D16 > efipart_readwrite: rw=3D1, blk=3D32 size=3D68 status=3D16 > efipart_readwrite: rw=3D1, blk=3D15 size=3D65 status=3D16 > Failed to find bootable partition > Boot from SAN device 0x80 failed: Error 0x7f22208e > (http://ipxe.org/7f22208e) > Unregistered SAN device 0x80 > Could not boot: Error 0x7f22208e (http://ipxe.org/7f22208e) >=20 > ---- >=20 > FreeBSD aside,=20 Why "FreeBSD aside"? It's completely FreeBSD-related. > for a moment: > <https://forums346.rssing.com/browser.php?indx=3D7254081&item=3D1122>; >=20 > >> 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 http://192.168.170.5/tftpboot/FreeBSD-12.1-RELEASE-amd64-mini-memstick.img (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. >=20 > For the issue with 12.1, you might like to join this discussion: >=20 > Fail to install FreeBSD via PXE UEFI firmware | The FreeBSD Forums > <https://forums.freebsd.org/threads/fail-to-install-freebsd-via-pxe-uefi-= firmware.73069/> I don't particularly like web fora but thanks for the link, I'll probably join. --=20 Victor Sudakov, VAS4-RIPE, VAS47-RIPN 2:5005/49@fidonet http://vas.tomsk.ru/ --7AUc2qLy4jB3hD7Z Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEcBAEBAgAGBQJf5WwPAAoJEA2k8lmbXsY0vH8H/3WsKwhaNw9kiNpVe1+iq9SK RLSwcfV9G/XzKAzvzEaXP9qYsRRrBAoiWGCLjQjCxsKcp+5Rvivgf5DCHOe7vrnq W1iP/xs2eRXlj2pSu0ji5VdbOWkTqf+uboBvbhpiqWgjBxIozcyo559dRp2EYQdb gFflEfOmkFfwxHP84/ENLwl5008m4ITBMW1giFYGjY7Qh71T5vbaNmf81gRwYrNi Nubzt1R9+Ba6QWlC3/PnKWX29rMdz5bgqNx7uCbIliikRMywlQO4eHWGqCyFVvc7 8SH7fu4vJ2klVzIR2XXz+ahuvFVLOrniDFVWEUPp5lnQQGt7LfyfrI7xCZGzLkM= =YSYR -----END PGP SIGNATURE----- --7AUc2qLy4jB3hD7Z--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20201225043527.GA52325>