Date: Sun, 04 Dec 2022 18:49:58 +0000 From: bugzilla-noreply@freebsd.org To: doc@FreeBSD.org Subject: [Bug 268100] 13.1's loader.efi is not able to find a ZFS pool if it was checkpointed on 12.3 Message-ID: <bug-268100-9-5i4EkBoX21@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-268100-9@https.bugs.freebsd.org/bugzilla/> References: <bug-268100-9@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D268100 --- Comment #2 from ml@netfence.it --- (In reply to Warner Losh from comment #1) First off, there are no "characteristics of the ZFS snapshot": we are talki= ng about "zpool checkpoint", not "zfs snap". I have no idea on why loader.efi can't boot from a checkpointed ZFS pool:=20 I only saw the message above ("can not read checkpoint data"). I don't have the original problematic pool anymore: it was a production ser= ver and I needed to boot it ASAP, so I just issued "zpool checkpoint -d" (that = is, as soon as I relized what the problem was). I guess, in order to recreate the situation, procedure would be: install 12= .3 UEFI+ZFS, checkpoint, upgrade to 13.1 (maybe upgrading boot loader is enoug= h). The only thing I could add is it was a zraid5 pool (3 disks); not sure it matters. Importance is "less than bulk" to me: it would have saved me three hours of spreading panic if I had known; now I'll simply check if a checkpoint exists before upgrading (or, if I forget, boot from an USB key and remove it later= ). My only goal was to let other people know, so maybe they won't be hit so ha= rd by this. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-268100-9-5i4EkBoX21>