From nobody Tue May 31 15:25:34 2022 X-Original-To: freebsd-fs@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 DB8981B617FD for ; Tue, 31 May 2022 15:27:06 +0000 (UTC) (envelope-from warlock@phouka1.phouka.net) Received: from phouka1.phouka.net (phouka1.phouka.net [107.170.196.116]) (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 (2048 bits) client-digest SHA256) (Client CN "phouka.net", Issuer "Go Daddy Secure Certificate Authority - G2" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4LCGNV0cLlz4bdw for ; Tue, 31 May 2022 15:27:06 +0000 (UTC) (envelope-from warlock@phouka1.phouka.net) Received: from phouka1.phouka.net (localhost [127.0.0.1]) by phouka1.phouka.net (8.16.1/8.16.1) with ESMTPS id 24VFPY28028301 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for ; Tue, 31 May 2022 08:25:34 -0700 (PDT) (envelope-from warlock@phouka1.phouka.net) Received: (from warlock@localhost) by phouka1.phouka.net (8.16.1/8.16.1/Submit) id 24VFPYKm028300 for freebsd-fs@freebsd.org; Tue, 31 May 2022 08:25:34 -0700 (PDT) (envelope-from warlock) Date: Tue, 31 May 2022 08:25:34 -0700 From: John Kennedy To: freebsd-fs@freebsd.org Subject: Re: UEFI question Message-ID: References: <20220531123221.n7ubs365ceeqo2d4@x1> List-Id: Filesystems List-Archive: https://lists.freebsd.org/archives/freebsd-fs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-fs@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220531123221.n7ubs365ceeqo2d4@x1> X-Rspamd-Queue-Id: 4LCGNV0cLlz4bdw X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of warlock@phouka1.phouka.net has no SPF policy when checking 107.170.196.116) smtp.mailfrom=warlock@phouka1.phouka.net X-Spamd-Result: default: False [-0.03 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.81)[-0.812]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-fs@freebsd.org]; TO_DN_NONE(0.00)[]; AUTH_NA(1.00)[]; RCPT_COUNT_ONE(0.00)[1]; MID_RHS_MATCH_FROMTLD(0.00)[]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_SPAM_LONG(0.59)[0.585]; DMARC_NA(0.00)[phouka.net]; MLMMJ_DEST(0.00)[freebsd-fs]; FORGED_SENDER(0.30)[warlock@phouka.net,warlock@phouka1.phouka.net]; R_SPF_NA(0.00)[no SPF record]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:14061, ipnet:107.170.192.0/18, country:US]; FROM_NEQ_ENVFROM(0.00)[warlock@phouka.net,warlock@phouka1.phouka.net]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-ThisMailContainsUnwantedMimeParts: N On Tue, May 31, 2022 at 02:32:21PM +0200, Julien Cigar wrote: > I have a Dell R340 server on which installed a 13.0-RELEASE and then > upgraded to 13.1-RELEASE (through freebsd-update). ZFS is used (raidz2). > > The system has the following partitions: https://gist.github.com/silenius/2defdd5480c5c1bc9ba2ff8940756466 > Some things regarding UEFI are not clear to me: > - as you can see in the partition list, the installer created an EFI > partition on all 4 drives, however it looks like only the first one has > has been populated (an mounted): https://gist.github.com/silenius/1220c953f905d868c1615fd0e7122bbf .. why ? > - if I understand well if my da0 disk dies the system becomes > unbootable (https://gist.github.com/silenius/51d202053295270eaaeb2c02316165ee).. correct? > - what's the correct way to fix this? should I newfs_msdos on each EFI > partition and copy /boot/loader.efi as /EFI/BOOT/BOOTX64.EFI? or > should I use efibootmgr? > > Thanks for enlightening me :) I use UEFI to multi-boot a lot myself, but not through efibootmgr (vs picking it via UEFI/BIOS on boot manually). I'm multi-booting windows and FreeBSD, so I'm being (justifiably) paranoid, but not based on being burnt in recent memory. Depending on how your system works (drives are enumerated at startup), in theory any of your disks could be da0. If you've only got a working EFI partition on one, that is probably hedging your bets a bit but yes, if that drive died, you'd probably be dead. In my dual-disk setups, I'd see an EFI and a freebsd-boot (BIOS) partition on both disks, I split my total swap between the two (not mirrored), and did ZFS "raiding" (mirroring-ish, usually) across the freebsd-zfs partitions. In my case, using the UEFI/BIOS from the motherboard, I could manually pick a disk to boot from which let me vet UEFI or ZFS bootblock changes for sanity before committing to both. But yes, I'd upgrade them both to the same thing once I was sure it would work.