[Bug 229926] FreeBSD loader(8) - /boot/zfsloader - is unable to boot other then currently set BE
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Sat Jul 21 15:21:18 UTC 2018
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229926
Bug ID: 229926
Summary: FreeBSD loader(8) - /boot/zfsloader - is unable to
boot other then currently set BE
Product: Base System
Version: 11.2-RELEASE
Hardware: Any
OS: Any
Status: New
Severity: Affects Many People
Priority: ---
Component: kern
Assignee: bugs at FreeBSD.org
Reporter: vermaden at interia.pl
Created attachment 195335
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=195335&action=edit
zfsloader-beadm.png
Hi,
the title is probably misleading so let me try to explain the details.
You have two boot environments, currently booted one called 'safe' and you just
created new one as backup, lets call it 'test'.
# beadm list
BE Active Mountpoint Space Created
safe NR / 378.1M 2018-07-20 07:26
test - - 412.0K 2018-07-21 18:51
Now, lets create 'disaster', we will remove the /boot directory from the
currently used BE.
# rm -rf /boot
... and restart.
# reboot
Now the loader(8) does not even show us Boot Menu but only error message that
it is not able to locate the /boot/zfsloader from the currently set bootfs
option for zroot, as shown on the zfsloader-beadm.png image, and that is quite
OK, it waits at boot: prompt waiting for an option.
... but if I type zroot/ROOT/test:/boot/kernel/kernel there is stops with BTX
halted message.
The 'fix' for that is to boot from ISO or MEMSTICK with LiveCD option and set
bootfs manurally for zroot to zroot/ROOT/test value and reboot, as shown on the
zfsloader-zpool-bootfs.png image.
IMHO if we type zroot/ROOT/test:/boot/kernel/kernel at boot: prompt it should
not halt, but proove me wrong.
Regards,
vermaden
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-bugs
mailing list