Date: Wed, 21 Aug 2019 22:34:21 +0300 From: Toomas Soome <tsoome@me.com> To: "O. Hartmann" <ohartmann@walstatt.org> Cc: freebsd-current <freebsd-current@freebsd.org> Subject: Re: HELP: UEFI/ZFS Boot failure: Ignoring Boot000A: Only one DP found Message-ID: <480F8DE0-A38F-4BCA-9F36-0D812CDB7DD8@me.com> In-Reply-To: <20190821213052.25d61cb4@thor.intern.walstatt.dynvpn.de> References: <20190821195847.577a165b@thor.intern.walstatt.dynvpn.de> <48D9A1D1-5A54-4FED-8DC8-40C9A5C9BE3A@me.com> <20190821213052.25d61cb4@thor.intern.walstatt.dynvpn.de>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 21 Aug 2019, at 22:30, O. Hartmann <ohartmann@walstatt.org> wrote:
>=20
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>=20
> Am Wed, 21 Aug 2019 22:14:46 +0300
> Toomas Soome <tsoome@me.com <mailto:tsoome@me.com>> schrieb:
>=20
>> If you drop into efi shell, can you start efi/boot/bootx64.efi =
manually? you should have
>> fs0: or like for ESP.
>>=20
>> rgds,
>> toomas
>=20
> Hello,
>=20
> I can't even stop to gain access to the shell; there is no timeframe =
to hit any key to stop by
> and access the efi shell.=20
>=20
> Kind regards,
> oh
hm? efi shell should be available from boot device menu, so you mean, =
you can not even get into firmware setup?
rgds,
toomas
>=20
>>=20
>>> On 21 Aug 2019, at 20:58, O. Hartmann <ohartmann@walstatt.org> =
wrote:
>>>=20
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA256
>>>=20
>>> I ran into serious trouble booting several boxes off UEFI. On modern =
hardware,
>>> the ESP is around 200 - 300 MB in size and usually I install
>>> /efi/freebsd/loader.efi, loader.efi taken from /boot/loader.efi. On =
some older
>>> hardware, specifically on a Lenovo E540 with latest available =
firmware (2.28),
>>> which uses 12-STABLE and a ZFS-only installation, there seems no =
working loader
>>> anymore!
>>> The installation of the Laptop has been performed using =
12.0-PRERELEASE on an
>>> Samsung EVO 860 500GB SSD. The ESP is 200M in size and contained
>>> /efi/boot/BOOTx64.efi and /efi/boot/startup.nsh.
>>>=20
>>> The ESP has been destroyed by accident. Now I tried to solve the =
problem by
>>> installing a new ESP and the proper loader, assuming that =
/boot/loader.efi
>>> (taken from a FreeBSD-13-CURRENT or from 12-STABLE of the same =
revision and
>>> sompiled on the same platform (Intel Haswell) as the lost laptop's =
revison of
>>> the OS is at. But I fail doing so. Somehow Lenovo's firmware is =
setting up a
>>> lot of UEFI boot numbers as provided via "efibootmgr -b 000X", X =
some Hex
>>> numer. -b 000A is usually denoted/labeld with "ATA HDD0".
>>>=20
>>> Installing the proper boot/loader.efi loader file from 12-STABLE =
(r351108) and
>>> setting the EFI variable according the following steps:
>>>=20
>>> mount -t msdosfs /dev/ada0p1 /mnt (ESP is on GPT partition 1, 0p2 is =
zroot)
>>> Install then loader.efi either as BOOTx64.efi or loader.efi under
>>> /mnt/efi/boot/ or /mnt/efi/freebsd/ and then set the boot =
environment
>>> accordingly via
>>>=20
>>> delete 000A first:
>>> efibootmgr -B -b 000A
>>>=20
>>> create the new efi boot var:
>>> efibootmgr -a -b 000A -c -l =
/mnt/efi/{freebsd|boot}/{loader.efi|BOOTx64.efi} -L
>>> FreeBSD
>>>=20
>>> The result is a non booting system, the Lenovo firmware jumps =
immediately into
>>> the menu for selecting a proper boot media.
>>>=20
>>> The same happens with /boot/boot1.efi installed as loader.efi or =
BOOTx64.efi
>>> shown above.
>>>=20
>>> In case I just brute-force flash the ESP with /boot/boot1.efifat, dd
>>> if=3Dboot1.efifat of=3D/dev/ada0p1 (ESP) (taken from the propper =
12-STABLE system I
>>> spoeke of above), then booting fails again, but this time with an =
error I watch
>>> on so many boxes recently:
>>>=20
>>> [...]
>>> Ignoring Boot000a: Only one DP found
>>> Trying ZFS pool
>>> Setting currdev to zfs:zroot/ROOT/default:
>>>=20
>>> Then the console freezes at that point and only RESET or POWER OFF =
is capable
>>> of a revive.
>>>=20
>>> What is wrong here? What am I missing?
>>>=20
>>> Thanks in advance,
>>>=20
>>> oh
>>>=20
>>>=20
>>> - --=20
>>> O. Hartmann
>>>=20
>>> Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten =
f=C3=BCr
>>> Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 =
28 Abs. 4 BDSG).
>>> -----BEGIN PGP SIGNATURE-----
>>>=20
>>> iHUEARYIAB0WIQSy8IBxAPDkqVBaTJ44N1ZZPba5RwUCXV2GbQAKCRA4N1ZZPba5
>>> R8nBAP9GBNJGQV+Q6BD2BlMYDX1Toxu9ybQZc2uahniHNER6cAEA5TmHBDTu94eE
>>> fX+hTk4vDUkf8ga4EsrUDZflage6LAk=3D
>>> =3D3img
>>> -----END PGP SIGNATURE-----
>>> _______________________________________________
>>> freebsd-current@freebsd.org mailing list
>>> https://lists.freebsd.org/mailman/listinfo/freebsd-current
>>> To unsubscribe, send any mail to =
"freebsd-current-unsubscribe@freebsd.org" =20
>>=20
>> _______________________________________________
>> freebsd-current@freebsd.org <mailto:freebsd-current@freebsd.org> =
mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-current =
<https://lists.freebsd.org/mailman/listinfo/freebsd-current>;
>> To unsubscribe, send any mail to =
"freebsd-current-unsubscribe@freebsd.org =
<mailto:freebsd-current-unsubscribe@freebsd.org>"
>=20
>=20
>=20
> - --=20
> O. Hartmann
>=20
> Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3=BC=
r
> Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 28 =
Abs. 4 BDSG).
> -----BEGIN PGP SIGNATURE-----
>=20
> iHQEARYIAB0WIQSy8IBxAPDkqVBaTJ44N1ZZPba5RwUCXV2b/AAKCRA4N1ZZPba5
> R+DDAP9LN8SDMDm/0ybGw+TBqczvS+m51n0DMYEqMZxTsikIFgD46rrBkm4zpKH5
> BDk3pkVT+h7MH8ghESa7XfhFGg3pCg=3D=3D
> =3D/Hm2
> -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?480F8DE0-A38F-4BCA-9F36-0D812CDB7DD8>