Can't mount a boot environment (says doesn't exist)

loveydovey

loveydovey

When I run bectl list, it shows me all the BEs from previous patch updates. When I do bectl mount 14.3-RELEASE_2026_02_28_182803, it tells me that specified boot environment does not exist. I'm stumped.
 
Strangely, mounting a BE ZFS dataset doesn't work either (dataset not found even though it shows in the list):
zfs list -r -o name,mountpoint,canmount | grep /ROOT shows the list.
zfs mount -o mountpoint=/tmp/some_mount zroot/ROOT/14.3-RELEASE-p8_2026_02_28_182803 says dataset does not exist even though it shows up in the list. The dataset is not active at the time.
 
Oh my god, never mind. I was using underscores where there were dashes.

Now, this is horrible. 🙋‍♂️ Can we talk about this?

When freebsd-update (upgrade) auto create a BE, the naming convention uses literally almost 50% underscores and 50% dashes. Like, seriously? Can there be either dashes or underscores? We are not writing a beautiful poem line, we are trying to make sure no one spends time decoding and messing up separators.

Fix it please. 🪗
 
I deactivated the automatic creation of BE by freebsd-update on all the systems I use because these names are far too long to type and also to avoid getting ton of BEs.

I remained old-fashion in this matter: create a BE before update/upgrade or whatever I may fear. Each time I create a new one, I delete the oldest. On most of my machines, there are only two BE at a time, no more.
 
I hear ya. I mean, there's utility in dating auto-created BEs, but it's just too wordy and too motley in terms of symbols. It needs to be clever.
 
You must log in or register to reply here.
Back
Top