Date: Thu, 24 Mar 2022 03:30:30 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 262708] Root on ZFS - GEOM_LABEL issues Message-ID: <bug-262708-227-nn1tjwFWas@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-262708-227@https.bugs.freebsd.org/bugzilla/> References: <bug-262708-227@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=3D262708 --- Comment #2 from eu9gu4@gmail.com --- Graham, Sorry I can't answer your questions: I reorganized that SSD, deleted all partitions and re-installed only Gentoo Linux for now. FreeBSD and Windows = will follow later. Anyway, I don't know what a "boot environment is". And, as I mentioned, I u= sed FreeBSD for 2 days after the update. Only the 3rd day it failed to boot. I remember that the day before I let the Windows OS do its usual update and= it was a pretty consistent one. I also remember that a similar thing happened last year on another machine, where a FreeBSD system installed on UFS failed to boot after a Windows upda= te. This makes me think that maybe sometimes Microsoft screws up one way or ano= ther its partition. What I fail to understand is why FreeBSD CAM and ZFS/UFS filesystems fail to boot when changes occur on a different partition. When I will install the new FreeBSD soon, it will go on its own dedicated d= isk, with a whole disk ZFS pool. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-262708-227-nn1tjwFWas>