Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Selecting a boot environment from the loader does not correctly switch where the rootfs is loaded from. #78

Closed
mremski opened this issue Feb 16, 2019 · 1 comment

Comments

Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
@mremski
Copy link

@mremski mremski commented Feb 16, 2019

Not sure if this is Trident/TrueOS or FreeBSD issue, but lua loader, when you select an alternate boot environment from the loader menu, the rootfs does not correctly follow.

To Reproduce
Freshly installed Trident 18.12-U3, updated to U4.
Stop in loader menu
Select Boot Environments
Select 2 Active BootEnvironments to switch from the current default to another one.
continue booting.
After booting:
beadm list shows the selected BE with N in active (as it should) but zfs list shows the mountpoint for / as the previous default (beadm list Active has R).
Retrying shows same behavior, option 3 (bootfs) under Boot Environments does not change to follow the newly selected BE.

Expected Behavior:
The rootfs should follow the selected BE. If it doesn't you can run into mismatch between versions of the kernel and modules.

@RodMyers
Copy link

@RodMyers RodMyers commented Mar 16, 2019

I'm thinking this is a trueos or freebsd issue. Was noted by the trueos dev team.

will close for now

@RodMyers RodMyers closed this Mar 16, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment