[Bug 261130] sysutils/beadm - cannot boot into newly created boot environment
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 261130] sysutils/beadm - cannot boot into newly created boot environment"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 261130] sysutils/beadm - cannot boot into newly created boot environment"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 261130] sysutils/beadm - cannot boot into newly created boot environment"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 261130] sysutils/beadm - cannot boot into newly created boot environment"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 261130] sysutils/beadm - cannot boot into newly created boot environment"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 261130] sysutils/beadm - cannot boot into newly created boot environment"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 261130] sysutils/beadm - cannot boot into newly created boot environment"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Tue, 11 Jan 2022 21:54:49 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261130 Bug ID: 261130 Summary: sysutils/beadm - cannot boot into newly created boot environment Product: Ports & Packages Version: Latest Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: ports-bugs@FreeBSD.org Reporter: byrnejb@harte-lyne.ca CC: vermaden@interia.pl CC: vermaden@interia.pl Flags: maintainer-feedback?(vermaden@interia.pl) FreeBSD-12.2p12 - beadm-1.3.2 When booting into a newly created BE the system reports `internal error failed to initialize ZFS library` and hangs at the point of mounting the filesystems. Booting into the existing R BE proceeds normally. Steps to reproduce: 1. Create new BE using beadm (beadm create newbe). 2. Reboot (shutdown -r now). 3. Interrupt default boot at FreeBSD boot menu (8). 4. Select BE newbe (2). 5. Proceed to boot. Expected behaviour: System boots and login prompt appears at console. Observed behaviour: System hangs after displaying date and time on console. Console is non-responsive. System can be restarted using <ctrl><alt><del> from console keyboard. -- You are receiving this mail because: You are the assignee for the bug.