From nobody Fri Aug 12 20:25:33 2022 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4M4FYP1F17z4Z6pg for ; Fri, 12 Aug 2022 20:25:45 +0000 (UTC) (envelope-from eduardo@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4M4FYN6r3Cz3sjC; Fri, 12 Aug 2022 20:25:44 +0000 (UTC) (envelope-from eduardo@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1660335945; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=MGJRZMFHsjgPu8PliGF5OdK5wEy2iS8xOqSP/ot0yBI=; b=io16mv26EAimJMN0vtXcQ3MFBjzZWTFA5o1mWARvp0lOlNH4ZhUR04KxHzC7nkOvwQy+CM 17df4RJvOGgbT8IvPkIK9YUNUQJXgcZWTchU59/RcsLnaLRo/xpa35H0tV+7UOTlwUhSQi JdFP6fA5K0VG7Eic7cKBixz7JadvVAInRtx8wH4UC584aFi7nvVNQ/yrUcB7ExdIv7Ov16 i0SiFZQaXmXBCSlnxZalDdSZOo5AxtXeMnJbE97EJ26Tbq1mkprlbC9HnKGWSMtTmEuH1+ ZmCAMOWw3jk1VBhDwfKuxUJuf7FTYeAr5pO086roG4KR9QlcRFkEpz7EoH4DaQ== Received: from mail-vs1-f49.google.com (mail-vs1-f49.google.com [209.85.217.49]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) (Authenticated sender: eduardo) by smtp.freebsd.org (Postfix) with ESMTPSA id 4M4FYN5RPsz1Qmk; Fri, 12 Aug 2022 20:25:44 +0000 (UTC) (envelope-from eduardo@freebsd.org) Received: by mail-vs1-f49.google.com with SMTP id 125so1888066vsd.5; Fri, 12 Aug 2022 13:25:44 -0700 (PDT) X-Gm-Message-State: ACgBeo1lDIEeVLDm+qgDpoO4cndQYEOOrvsWaNngM0EpF7p+oESH+GgP HMQR6ll3rPn7sMUlgfQ8XyMWsxcGxzvBKbwJ1tg= X-Google-Smtp-Source: AA6agR4kyOHtLR815+IMzdbfKnpgCSXozNBuDYMyGodIEzHYml/PBzBNOLMRsh7LMdBynn2XzZkFi7Od2NJp9QuM6VQ= X-Received: by 2002:a05:6102:2836:b0:386:91a5:a241 with SMTP id ba22-20020a056102283600b0038691a5a241mr2567477vsb.51.1660335944369; Fri, 12 Aug 2022 13:25:44 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: <20220813.015426.809710797578801280.yasu@FreeBSD.org> <20220813.024435.741655799390389695.yasu@FreeBSD.org> In-Reply-To: From: Nuno Teixeira Date: Fri, 12 Aug 2022 21:25:33 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Updating EFI boot loader results in boot hangup To: Larry Rosenman Cc: Yasuhiro Kimura , FreeBSD CURRENT Content-Type: multipart/alternative; boundary="0000000000002c0b6d05e6111699" ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1660335945; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=MGJRZMFHsjgPu8PliGF5OdK5wEy2iS8xOqSP/ot0yBI=; b=msE0hFPRwPeGe/Mw8qwYB4TjfScAc0UplCSMsNsyg09oj4o2WLbXjVrIAqmhTLurma8S2p IJvEOVaRNEz9vGgvANZTmKY46cjYL/MdBaDoHsvrGspaH3SSLgHld+KrEbdYM06XtzMhEg XUhitvobvSSDx+DDUl3j5tM/o0Y/ErNh4vi7fB+fP4QNovBIVB40C61t8EPqw1NHsK8uRL ftoYol0KXg4sKnv5GhEf8+Oi+f8AYynguvoM638bIJPiIgipwOKxIwGb9UtYnfjoZBE9U+ mt+E+cwUsKi7dISb18HAhvrmx6hfLkZ4Pyajxqp783AvLzHFDH7H9vbcTy8Kvg== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1660335945; a=rsa-sha256; cv=none; b=fvFiM7Uokl7pESoxawhtjvSV1sX3Egz/+aZ5+09Z4CV/Fo4GRmuvl5T1M0HcyD+/o+jOKF GPCs8mXev1iiaeTPvSc8cMcgnRldpDducRXU/SU6yBpTxda7w0sfreg4J17nRp7u3lYtCe 3Jj4LlA4DuJ+2K0H7UOB1lXAhyLGnTXBnPs7vd4uGCkvjTFCOjdmVxLBPnjcZrWIUN2AJW 7ygyfzKzSKop+XYbybvAomZo3rvnj6fYzNsscBvoEEi6zNuMcyyZE3ftcpGpvoRbai32TQ ZpicFHAipjEaT6lU1ga1BNnSpTLficS73ATz0WuXoF3wv9+cwLiBQljFA/TgKg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N --0000000000002c0b6d05e6111699 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable The problem is if boot is failing, how to mount and rename it? I'm looking for a way, if possible, to boot directly bkp boot64x in case of failure. I was hoping to find it in loader(8) or uefi(8)... Larry Rosenman escreveu no dia sexta, 12/08/2022 =C3=A0(s) 21:09: > I would assume just rename the bootx64.old to bootx64.efi > > and/or put it in a different directory that EFI can see > > > On 08/12/2022 3:03 pm, Nuno Teixeira wrote: > > I'm searching without success to load a bkp loader in case of boot failur= e. > > Upgrade process willl be like: > --- > mount -t msdosfs /dev/nvd0p1 /mnt > cp /mnt/efi/boot/bootx64.efi /mnt/efi/boot/bootx64.old > cp /boot/loader.efi /mnt/efi/boot/bootx64.efi > --- > > I can't find the right docs to load bootx64.old. > Could you tell me what you did to solve your boot? > > Thanks > > Yasuhiro Kimura escreveu no dia sexta, 12/08/2022 =C3= =A0(s) > 18:45: > > From: Nuno Teixeira > Subject: Re: Updating EFI boot loader results in boot hangup > Date: Fri, 12 Aug 2022 18:26:11 +0100 > > > Hello Yasu, > > > > Does it needes to update boot loader everytime that we upgrade current? > > No, you need not. > > > The only time that I updated was a month ago because of zfs upgrade and > I need to practice how to boot > > loader bkp file :) > > I update boot loader everytime because I'd like to do it :-). > And sometimes problem hits upon me like this time and I contribute to > debugging base system :-):-). > > --- > Yasuhiro Kimura > > > > -- > Nuno Teixeira > FreeBSD Committer (ports) > > > -- > Larry Rosenman http://www.lerctr.org/~ler > Phone: +1 214-642-9640 E-Mail: ler@lerctr.org > US Mail: 5708 Sabbia Dr, Round Rock, TX 78665-2106 > --=20 Nuno Teixeira FreeBSD Committer (ports) --0000000000002c0b6d05e6111699 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
The problem is if boot is failing, how to mount and r= ename it?

I'm looking for a way, if possible, to boot= directly bkp boot64x in case of failure.
I was hoping to find it= in loader(8) or uefi(8)...

<= div dir=3D"ltr" class=3D"gmail_attr">Larry Rosenman <ler@lerctr.org> escreveu no dia sexta, 12/08/2022 =C3= =A0(s) 21:09:

I would assume just rename the bootx64.old to bootx64.efi

and/or put it in a different directory that EFI can see=C2=A0


On 08/12/2022 3:03 pm, Nu= no Teixeira wrote:

I'm searching without success to load a bkp loader in case of boot= failure.
=C2=A0
Upgrade process willl be like:
---
mount -t msdosfs /dev/nvd0p1 /mnt
cp /mnt/efi/boot/bootx64.e= fi /mnt/efi/boot/bootx64.old
cp /boot/loader.efi /mnt/efi/boot/bootx64.e= fi
---
=C2=A0
I can't find the right docs to load bootx64.old.
Could you tell me what you did to solve your boot?
=C2=A0
Thanks



--
Nuno Teixeira
Fr= eeBSD Committer (ports)


--=C2=A0<= br>Larry Rosenman =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0ht= tp://www.lerctr.org/~ler
Phone: +1 214-642-9640 =C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0E-Mail: ler@lerctr.o= rg
US Mail: 5708 Sabbia Dr, Round Rock, TX 78665-2106


--
Nun= o Teixeira
FreeBSD Committer (ports)
--0000000000002c0b6d05e6111699--