From nobody Sat Aug 13 07:24:07 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 4M4X9H5FcFz4Z3LC for ; Sat, 13 Aug 2022 07:24:19 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from www121.sakura.ne.jp (www121.sakura.ne.jp [153.125.133.21]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4M4X9G2tHKz47XT; Sat, 13 Aug 2022 07:24:17 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from kalamity.joker.local (123-1-85-147.area1b.commufa.jp [123.1.85.147]) (authenticated bits=0) by www121.sakura.ne.jp (8.16.1/8.16.1/[SAKURA-WEB]/20201212) with ESMTPA id 27D7O7MC064705; Sat, 13 Aug 2022 16:24:08 +0900 (JST) (envelope-from junchoon@dec.sakura.ne.jp) Date: Sat, 13 Aug 2022 16:24:07 +0900 From: Tomoaki AOKI To: Larry Rosenman Cc: Nuno Teixeira , Yasuhiro Kimura , FreeBSD CURRENT Subject: Re: Updating EFI boot loader results in boot hangup Message-Id: <20220813162407.82d8bf7adf51da52cba13e4d@dec.sakura.ne.jp> In-Reply-To: <78c22181179d9c7f9fcea829002095eb@lerctr.org> References: <20220813.015426.809710797578801280.yasu@FreeBSD.org> <20220813.024435.741655799390389695.yasu@FreeBSD.org> <78c22181179d9c7f9fcea829002095eb@lerctr.org> Organization: Junchoon corps X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd13.0) 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 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 4M4X9G2tHKz47XT X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of junchoon@dec.sakura.ne.jp has no SPF policy when checking 153.125.133.21) smtp.mailfrom=junchoon@dec.sakura.ne.jp X-Spamd-Result: default: False [-1.60 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; AUTH_NA(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.999]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[text/plain]; FROM_EQ_ENVFROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; ASN(0.00)[asn:7684, ipnet:153.125.128.0/18, country:JP]; R_SPF_NA(0.00)[no SPF record]; MIME_TRACE(0.00)[0:+]; R_DKIM_NA(0.00)[]; RCVD_TLS_LAST(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; DMARC_NA(0.00)[sakura.ne.jp]; RCPT_COUNT_THREE(0.00)[4]; HAS_ORG_HEADER(0.00)[]; MID_RHS_MATCH_FROM(0.00)[] X-ThisMailContainsUnwantedMimeParts: N Or multiple installation in the same computer. For me, main and stable/13 are installed in different drive. So I can boot into healthy installation, mount problematic ESP, and alter broken bootx64.efi with known-to-work one. Usually, to boot into healthy installation, choose boot drive on UEFI menu. On Fri, 12 Aug 2022 15:26:08 -0500 Larry Rosenman wrote: > > > boot off a memstick? > > On 08/12/2022 3:25 pm, Nuno Teixeira wrote: > > > 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 à(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 > > failure. > > > > 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 > > à(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 > > -- > > 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 -- Tomoaki AOKI