Bug 261130 - sysutils/beadm - cannot boot into newly created boot environment
Summary: sysutils/beadm - cannot boot into newly created boot environment
Status: New
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: amd64 Any
: --- Affects Only Me
Assignee: freebsd-ports-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-01-11 21:54 UTC by James B. Byrne
Modified: 2022-12-18 21:34 UTC (History)
1 user (show)

See Also:
bugzilla: maintainer-feedback? (vermaden)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description James B. Byrne 2022-01-11 21:54:49 UTC 
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.
Comment 1 James B. Byrne 2022-01-12 15:29:27 UTC 
Error is reported during boot process:  internal error failed to initialize ZFS library
Comment 2 James B. Byrne 2022-01-12 18:00:09 UTC 
f I create a BE using beadm; and I activate that BE; and I reboot the system; and I do not interact with the boot process; then the system boots.

If I reboot the system from that BE; and I interact with the boot process; and I select the original BE; then the system boots.

If I activate the original BE; and reboot the system; and I do not interact with the boot menu; then the system boots.

If I reboot the system; and I select the new BE from the boot menu; then the zfs error is reported and the system fails to boot.
Comment 3 Slawomir Wojciech Wojtczak 2022-01-12 18:21:49 UTC 
(In reply to James B. Byrne from comment #0)

I have jest done that:

# beadm create test
# reboot
// select 'test' by hand at FreeBSD boot menu (8).

... and system booted to 'test' BE as usual. Zero problems.

I can not reproduce your problem.

Can you record what are you doing with a phone and post that movie on some platform and link it here?

Regards.
Comment 4 James B. Byrne 2022-01-13 14:05:39 UTC 
(In reply to Slawomir Wojciech Wojtczak from comment #3)

To bring recording devices into the computer facility is not allowed.  I can probably get the point stretched to permit recording what I am doing on my workstation in my own office, which is where I perform the maintenance on the host via ssh.  But, recording the boot sequence on the system console inside the computer facility may prove difficult to accomplish.

I will try, but it is not likely to be permitted; and if it is then it will not be approved today.

On the other hand, I created a BE on the same host using bectl.  This BE does not exhibit this problem.  That BEs can be selected from the boot menu and the system starts without error.
Comment 5 Slawomir Wojciech Wojtczak 2022-04-05 09:30:28 UTC 
Should we close that one?
Comment 6 Slawomir Wojciech Wojtczak 2022-12-18 21:34:23 UTC 
Please close this one.