So normally zroot/ROOT/default is always ahead of all of the others. But... We sometimes do things which disrupt this nice plan out of necessity. Such as needing to boot back into a previous version Boot Environment. And then that BE will start to collect disk block usage as things copy-on-write in that life fork off the main trunk that is zroot/ROOT/default.

And if one upgrades more while on that fork then that BE can get ahead of default.

So I am just asking for a little description of what's happening because otherwise it's not possible to know.

But if you have a working Boot Environment and a broken zroot/ROOT/default then it is possible to promote the BE and replace the zroot/ROOT/default with it.

I /think/ the process would be to use bectl delete default and create a new boot environment default from the working BE. I haven't actually needed to do that flow yet but I think that would be the recipe.

ooooooooooo, ok so just use bectl to delete the default boot environment and then copy the current one over?

whats happening is: i am in 13.3 but i had to hit 8 and then 2 to go into the 13.3 snapshot. then booting there went fine without sending me to mountroot> prompt

in the boot environments menu, the bootfs is still zroot/ROOT/default but the active is set to the snap from the update. either way i am showing all 13.3... one sec :)

ohhh..... hmmmm.... ok i am gonna have to fix my freebsd-updates because they are not completing like i think they were.... freebsd-version shows 13.3-release-p5 but the kernel is on 13.3

if i see the thing about c++ string and tuple again im gonna extract the entire c++ folder like that bug report says

last update removed a bunch of stuff but i dont see the c++ folder in there so well see how it goes

grabbed fresh base and copied over the c++/v1 dir

hmmm, still seeing that error =\ Installing updates...install: ///usr/include/c++/v1/__string exists but is not a directory but i replaced the dir with the 13.3.txz?

oh, maybe its because the freebsd-update.sh is old????

remove it and extract it from base.txz

freebsd-update or the c++ include dirs? i already did c++ dirs. freebsd-update shows modified date as today, so it had me second guessing whether i had an old one

diffing the one i grabbed from main and the one in /usr/sbin shows a lot of differences so ill replace it :)

the c++ dirs

ah, guess i missed the part of you doing that

all good

looks like the updated freebsd-update is working well :)

ok so i think i have all the freebsd-update installs run now. should i do a "pkg bootstrap -f"?

hmmm, freebsd-update keeps saying i have a partially completed update after installing no problem without any errors or messages =\

fn a man i cant get it lmao

seems like im right there

if i load the boot env thats behind the one created by freebsd-update it shows im on the right version, 13.3. if i load the be created by the freebsd-update it is like i never installed the update and it just installs yet again lmao

on the 'just before' snap i try to run update again and it shows /usr/sbin/freebsd-update: config_=======: not found

feels like im never going to get this back on track =\

you're making progress keep it up

Huh, it seems like I have ipv6 working with vnet jails after all.

alver cool how's it work?

polyex: had to setup the host to use a bridge with cloned MAC, transfer ipv4 and ipv6 addresses to that, enable ip6 routing (but not ip4), plug vnets on the existing bridge and give them their own ip4 with external gateway but ip6 with the host as gateway

Oh, and use /etc/start_if.vnet to overwrite the MAC address to what the hoster expects

eh. i wonder if you could add to the freebsd wiki or smth to share the knowledge?

fixed pkg, wasnt working because this was set url: "pkg+http://pkg.FreeBSD.org/${ABI}/release_1"

i keep seeing this, but /etc/defaults/rc.conf is there???? /etc/defaults/rc.conf: =======: not found

permissions are root:wheel on it so im not sure its that? weird

ahhhhhhhhhhhhh its a leftover from the merge cleanup

and that was the problem with freebsd-update too!! ADSMASDMAISDMASIOMA were getting somewhere

wow, ok, i think i might have everything back in place!!! searching on how to promote or replace boot environment on zroot not going so well tho

polyex: yes, I will have to write it down. Especially knowing how much time I wasted on other setups that did appear to work, but went tits up once neighbour discovery expiration started to kick in

in bectl my default boot environment shows 4.45T used. if i destroy it am i going to destory the zpool???

wabkia: that /etc/defaults/rc.conf: prefix is saying, that /etc/defaults/rc.conf is complaining/has an error and that error is "=======: not found", so it is looking for ======= and can't find it

ty nimaje, i got it removed already :)

and found out that the freebsd-update error was for the same reason

now im just trying to figure out if i set my default boot environment to the current snapshot and move on or if i try to copy it to default? oi vey

guess im not the only one having problems lol. bsd.to is offline

wabkia: you made me google ADSMASDMAISDMASIOMA, hoping to find some super long abbreviation I didn't know yet. Am disappoint.

hahahah sorry bro, an expression of elation

wondering where samba went tho LOL

wabkia: boot environments are created by creating a snapshot and cloning that, as the snapshot has clones, you can't remove it and zfs counts its space to its dataset, if you remove old boot enviromnents bectl will remove the snapshot too and the space goes down

hmmm, so removing the "boot environment" at zroot/ROOT/default will delete the entire dataset and thats why it shows as 4.5T? or am i way off

installed samba, it was already set as enabled, conf was still there, started samba_server, working juuuuust fine :D

with the last snapshot from freebsd-update boot environment set as active it reboots without intervention ><

phhew what a day

Alver tyvm for adding that knowledge to the wiki. either ipv6 or jail section i guess

g'night

wabkia: no you shouldn't remove the default boot environment

look at bectl list and remove old boot environments you no longer need, as those were cloned from snapshots of zroot/ROOT/default their size also counts in some way to USED of zroot/ROOT/default

hmmm, when it boots from default, it gives me a mountroot> prompt

idk =\

did you maybe forget some more merge conflicts?

Heh, registering on the FreeBSD wiki is done by *mailing* a *physical person* who will then *manually* create the account. :D

Oldskool.

Don't forget to put a stamped and addressed return envelope in there for your wiki sticker

oOoo. I like stickers

nimaje no, the mountroot> problem i was having before i updated from 12.2

hi, I would like to burn an ISO image (archive.org/details/ntwks-351-upd) to a cd. I see that I can use cdrtool as per Chapter 20 of the Handbook. I do not have too many spare blank CDs so I would like to do it right. Could someone help me to understand if I have to use -b flag or not and what would be the name of the device? that is not clear to me after having read the handbook thanks a lot

it has been agers since I did this so any help is welcomed

uskerine: Well you could use the -dummy option while playing around that should be a safe bet.

Just realised that it must also be over 2 years since I last burnt a disc. :-D

Hi there

A lot of times I have an issue with external storage with ZFS file system

once connection failed or somehow power to the drive is disconnected the system become unstable

there is no way even to reboot remotely

the commands is just hangs

export, import, online, ... doesn't seems to have any effect other then just stuck without completion

the pool is in "suspended" state, even if drive is available

nerozero, By external storage do you mean USB? I have used USB storage over the years and it always freaks out periodically. It's never been reliable for me.

On the other hand USB network adaptors have been reliable and solid without any trouble for me. So strange that one can be very good and the other quite bad.

rwp usb also, external sata - same effect

<rwp> nerozero, By external storage do you mean USB? I have used USB storage over the years and it always freaks out periodically. It's never been reliable for me.

sorry wrong clipboard

^^^^

If zfs drops below the minimum number of devices it will go into "SUSPENDED" mode. If you jiggle everything and the storage providers are back then you can "zpool clear zroot" (or whatever pool name) and zfs will either return to ONLINE or if everything is okay. Or if it still does not have all providers it will become DEGRADED with providers in the removed state. Or it will remain SUSPENDED if it is still below the minimum number.

this is the best fun rsyncing the whole rootfs under a running system from another one xD

i guess that implies ufs, and not zfs

Yes after you start the rsync better you dont stop it as all tools like cat bin ps ls will be Bad system call (core dumped)

I have an rpi with freebsd 14.1. attached to it via USB is an external harddrive with a zpool on it. If I try to boot it with that drive attached it gets stuck in uboot with this message: i.imgur.com/ogyISRM.jpeg

feel free to ping if you have any input, I lurk :D

yourfate: it may no longer be relevant since I haven't worked with rpis since the 2nd version came out, but one of mine was so tight wrt power draw that if I connected a rotating-rust USB drive, it also faceplanted during boot because the system boot power reqs left just not enough juice for the USB drive to spin up reliably, causing all kinds of weirdness.

I swapped the HDD out for one with a split cable for power and data, and all was well after, afaicr

Alver: the external HDD has its own power adapter

can someone tell me if 13.whatever still is using python39 packages or has 311 at this time?

rtprio: ports isn't freebsd release specific and has switched to 311

i know this, but it specifies how packages are built

no idea if there is some builder that didn't do a rebuild since that change (probably not as the default is 311 for some while and full rebuilds should happen every two weeks and incremental rebuilds in between) or some mirror that didn't sync since that change

it's only been default since may 29

so more then a month, if nothing went completly wrong, there were two complete rebuilds of the pkg repos in between

I see the following in /var/log/messages from ntpd: leapsecond file ('/var/db/ntpd.leap-seconds.list'): expired 14 days ago

how do I resolve this?

mns: service ntpd fetch

Shouldn't periodic be auto fetching that?

mns, Put this in your /etc/rc.conf file: sysrc ntp_leapfile_sources="data.iana.org/time-zones/tzdb/leap-seconds.list"

The previous source that we used for years has decided to stop providing it. That's the new location of the data.

where can we watch the asiabsdcon 2023 and 2024 vids?