From nobody Tue Nov 22 18:42:36 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 4NGtRZ11pxz4jHGh for ; Tue, 22 Nov 2022 18:42:50 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-vs1-f41.google.com (mail-vs1-f41.google.com [209.85.217.41]) (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)) by mx1.freebsd.org (Postfix) with ESMTPS id 4NGtRY0VD5z3r1L; Tue, 22 Nov 2022 18:42:49 +0000 (UTC) (envelope-from asomers@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of asomers@gmail.com designates 209.85.217.41 as permitted sender) smtp.mailfrom=asomers@gmail.com; dmarc=none Received: by mail-vs1-f41.google.com with SMTP id t14so15315328vsr.9; Tue, 22 Nov 2022 10:42:49 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=DRrViaMGJZhKEEWmxHV7ZiqiIv44uiLOWmGiCo9Jmak=; b=3p9dm+h0A/CITF1loJLWhT4YDZSKViaXsnCfMPuwFeszFxWJT4y+Mzkne5Y1aHNu3A OovrHmcfkW25dhBvKusED03v+MvDUUT9u6yjYIU0Z8fhv+sKuPD3j98yL12Kv6TxgFLF UxrG1hof9wxzkAxYT2/uuETfFde4HFQtWcQRiYbGIBT+I92J8jdzYwsJt7IIYd0hbYEP evmkjm6G6hJVhyWzz1NjWqfwx5OirbDR2Hyvt7/btWgFCFTbWS/iJcfRosj4/58oEn0T DimVxOhlttnGF0RIOAk/3Gw7iRX2Yhdg9lozm/KWkA/CRz6mpGBMtYNYJ6/6oflH22lB Jg8w== X-Gm-Message-State: ANoB5pn9QW13ugUJIHoTx18vcyP+QXzK3fVsTR00Oeip7SNWTsnp8Rx2 zbmYtpvbMiEGkmMdKdsLCTm3d4Jk+VxTeO26EsY= X-Google-Smtp-Source: AA0mqf7NMv/UnIeC0TuzM74f88SzIZtypOtz05bJOhQ60k2GE0ZZeTtgCZV4hUUc60Fe390BVzwzi4WYnPr6xOWpx+4= X-Received: by 2002:a05:6102:3911:b0:3af:b08c:9bbe with SMTP id e17-20020a056102391100b003afb08c9bbemr14450581vsu.76.1669142567941; Tue, 22 Nov 2022 10:42:47 -0800 (PST) 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 References: <20220531123221.n7ubs365ceeqo2d4@x1> In-Reply-To: From: Alan Somers Date: Tue, 22 Nov 2022 11:42:36 -0700 Message-ID: Subject: Re: UEFI question To: John Kennedy Cc: freebsd-fs@freebsd.org, Nathan Whitehorn Content-Type: text/plain; charset="UTF-8" X-Spamd-Result: default: False [-1.17 / 15.00]; NEURAL_HAM_SHORT(-0.99)[-0.989]; NEURAL_HAM_MEDIUM(-0.98)[-0.980]; NEURAL_SPAM_LONG(0.80)[0.802]; FORGED_SENDER(0.30)[asomers@freebsd.org,asomers@gmail.com]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; MIME_GOOD(-0.10)[text/plain]; MLMMJ_DEST(0.00)[freebsd-fs@freebsd.org]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; R_DKIM_NA(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[209.85.217.41:from]; FREEMAIL_ENVFROM(0.00)[gmail.com]; MIME_TRACE(0.00)[0:+]; RWL_MAILSPIKE_POSSIBLE(0.00)[209.85.217.41:from]; RCVD_TLS_LAST(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; FREEFALL_USER(0.00)[asomers]; ARC_NA(0.00)[]; FROM_NEQ_ENVFROM(0.00)[asomers@freebsd.org,asomers@gmail.com]; RCPT_COUNT_THREE(0.00)[3]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; DMARC_NA(0.00)[freebsd.org]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Queue-Id: 4NGtRY0VD5z3r1L X-Spamd-Bar: - X-ThisMailContainsUnwantedMimeParts: N On Tue, May 31, 2022 at 9:27 AM John Kennedy wrote: > > 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. I just noticed the same problem. For mirrored installs, the 13.1-RELEASE installer only formats the efi partition on one hard disk. Shouldn't it do both?