[Bug 233657] bectl siliently fails on i386

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

[Bug 233657] bectl siliently fails on i386

bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233657

            Bug ID: 233657
           Summary: bectl siliently fails on i386
           Product: Base System
           Version: 12.0-RELEASE
          Hardware: i386
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: bin
          Assignee: [hidden email]
          Reporter: [hidden email]

bectl on i386 with root on zfs silently fails.

bectl list gives no output

bectl create gives no output

Same thing happens when root is ufs.

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

[Bug 233657] bectl siliently fails on i386

bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233657

Rob <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]

--- Comment #1 from Rob <[hidden email]> ---
(In reply to Philip Homburg from comment #0)

I wasn't able to reproduce this problem on a VM.

root@test:~ # uname -a
FreeBSD test 12.0-RELEASE FreeBSD 12.0-RELEASE r341666 GENERIC  i386

root@test:~ # bectl create bootenv
/* no output */

root@test:~ # bectl list
BE      Active Mountpoint Space Created
default NR     /          423M  2018-12-19 11:37
bootenv -      -          8K    2018-12-19 11:46

root@test:~ # gpart show
=>      40  33554352  vtbd0  GPT  (16G)
        40      1024      1  freebsd-boot  (512K)
      1064       984         - free -  (492K)
      2048   4194304      2  freebsd-swap  (2.0G)
   4196352  29356032      3  freebsd-zfs  (14G)
  33552384      2008         - free -  (1.0M)

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

[Bug 233657] bectl siliently fails on i386

bugzilla-noreply
In reply to this post by bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233657

--- Comment #2 from Philip Homburg <[hidden email]> ---
My laptop boots from BIOS and has MBR. Could that make a difference?

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

[Bug 233657] bectl siliently fails on i386

bugzilla-noreply
In reply to this post by bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233657

--- Comment #3 from Rob <[hidden email]> ---
(In reply to Philip Homburg from comment #2)

I don't know how it would.

Given that no error messages are produced, my hunch is bectl is failing to
initialize

'bectl' uses libbe(3) to initialize a boot environment to work from. The
following is a description about 'libbe_init()' from the libbe(3) man page:


     The libbe_init() function takes an optional BE root and initializes
     libbe, returning a libbe_handle_t * on success, or NULL on error.  If a
     BE root is supplied, libbe will only operate out of that pool and BE
     root.  An error may occur if:

     /boot and / are not on the same filesystem and device,
     libzfs fails to initialize,
     The system has not been properly booted with a ZFS boot environment,
     libbe fails to open the zpool the active boot environment resides on, or
     libbe fails to locate the boot environment that is currently mounted.


That may help you trouble-shoot the cause.

Another thing to try is, pass the root boot environment (i.e. zroot/ROOT) to
bectl explicitly. This is undocumented but, you can pass the '-r' flag before
any of the 'bectl' commands (create, list, destroy, etc.). Here's an example:

To create boot environment named 'bootenv' under the boot root zroot/ROOT
# bectl -r zroot/ROOT create bootenv

To list a boot environment under zroot/ROOT
# bectl -r zroot/ROOT list

I'm curious what you come up with.

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

[Bug 233657] bectl siliently fails on i386

bugzilla-noreply
In reply to this post by bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233657

Graham Perrin <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]

--- Comment #4 from Graham Perrin <[hidden email]> ---
(In reply to Philip Homburg from comment #0)

> bectl list gives no output

I may be mistaken but I vaguely recall that for me there was no output, no
listing, prior to my first use of a 'bectl create …' command.

At the moment I don't have a clean installation of FreeBSD with which to test.

----

Comparing for a moment with beadm,

[grahamperrin@ghostbsd-virtual] ~% date ; uname -v
Fri Jan  4 05:58:07 GMT 2019
FreeBSD 12.0-CURRENT #0 7ad4fada6(HEAD): Thu Aug  2 11:37:15 EDT 2018    
root@hydra:/usr/obj/root/jenkins/workspace/TrueOS_-_Stable_-_Complete/TrueOS_Stable/amd64.amd64/sys/GENERIC
[grahamperrin@ghostbsd-virtual] ~% beadm
usage:
  beadm activate <beName>
  beadm create [-e nonActiveBe | -e beName@snapshot] <beName>
  beadm create <beName@snapshot>
  beadm destroy [-F] <beName | beName@snapshot>
  beadm list [-a] [-s] [-D] [-H]
  beadm rename <origBeName> <newBeName>
  beadm mount <beName> [mountpoint]
  beadm { umount | unmount } [-f] <beName>
[grahamperrin@ghostbsd-virtual] ~% bectl
bectl: Command not found.
[grahamperrin@ghostbsd-virtual] ~% sudo pkg install bectl
Updating GhostBSD-base repository catalogue...
GhostBSD-base repository is up to date.
Updating GhostBSD-ports repository catalogue...
GhostBSD-ports repository is up to date.
All repositories are up to date.
pkg: No packages available to install matching 'bectl' have been found in the
repositories
[grahamperrin@ghostbsd-virtual] ~% beadm list
BE      Active Mountpoint  Space Created
initial NR     /            3.8G 2019-01-04 05:22
[grahamperrin@ghostbsd-virtual] ~% beadm list -s
BE/Dataset/Snapshot             Active Mountpoint  Space Created

initial
  ghostbsd-virtual/ROOT/initial NR     /            3.8G 2019-01-04 05:22
[grahamperrin@ghostbsd-virtual] ~%

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

[Bug 233657] bectl siliently fails on i386

bugzilla-noreply
In reply to this post by bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233657

Kyle Evans <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Assignee|[hidden email]            |[hidden email]
                 CC|                            |[hidden email]

--- Comment #5 from Kyle Evans <[hidden email]> ---
(In reply to Philip Homburg from comment #0)

If you can still reproduce this, can you post `zfs list` output, please?

Also, take now that I've become aware of this report.

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "[hidden email]"