00:01:15 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. 00:01:38 And if one upgrades more while on that fork then that BE can get ahead of default. 00:01:56 So I am just asking for a little description of what's happening because otherwise it's not possible to know. 00:02:30 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. 00:03:49 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. 00:22:19 ooooooooooo, ok so just use bectl to delete the default boot environment and then copy the current one over? 00:23:48 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 00:26:46 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 :) 00:27:55 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 00:29:25 if i see the thing about c++ string and tuple again im gonna extract the entire c++ folder like that bug report says 00:29:42 last update removed a bunch of stuff but i dont see the c++ folder in there so well see how it goes 00:40:13 grabbed fresh base and copied over the c++/v1 dir 00:52:12 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? 00:57:04 oh, maybe its because the freebsd-update.sh is old???? 01:01:36 remove it and extract it from base.txz 01:09:16 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 01:10:28 diffing the one i grabbed from main and the one in /usr/sbin shows a lot of differences so ill replace it :) 01:11:44 the c++ dirs 01:12:11 ah, guess i missed the part of you doing that 01:14:00 all good 01:31:39 looks like the updated freebsd-update is working well :) 02:35:21 ok so i think i have all the freebsd-update installs run now. should i do a "pkg bootstrap -f"? 02:39:10 hmmm, freebsd-update keeps saying i have a partially completed update after installing no problem without any errors or messages =\ 05:24:37 fn a man i cant get it lmao 05:24:41 seems like im right there 05:26:26 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 05:26:42 on the 'just before' snap i try to run update again and it shows /usr/sbin/freebsd-update: config_=======: not found 07:32:07 feels like im never going to get this back on track =\ 07:34:28 you're making progress keep it up 07:36:58 Huh, it seems like I have ipv6 working with vnet jails after all. 07:37:17 * Alver should write down how or he'll forget again 07:39:06 alver cool how's it work? 07:47:58 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 07:48:33 Oh, and use /etc/start_if.vnet to overwrite the MAC address to what the hoster expects 07:48:58 eh. i wonder if you could add to the freebsd wiki or smth to share the knowledge? 07:59:32 fixed pkg, wasnt working because this was set url: "pkg+http://pkg.FreeBSD.org/${ABI}/release_1" 08:00:06 i keep seeing this, but /etc/defaults/rc.conf is there???? /etc/defaults/rc.conf: =======: not found 08:01:47 permissions are root:wheel on it so im not sure its that? weird 08:02:47 ahhhhhhhhhhhhh its a leftover from the merge cleanup 08:06:04 and that was the problem with freebsd-update too!! ADSMASDMAISDMASIOMA were getting somewhere 08:12:52 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 08:17:34 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 08:21:00 in bectl my default boot environment shows 4.45T used. if i destroy it am i going to destory the zpool??? 08:21:02 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 08:21:18 ty nimaje, i got it removed already :) 08:21:34 and found out that the freebsd-update error was for the same reason 08:22:35 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 08:26:37 guess im not the only one having problems lol. bsd.to is offline 08:30:57 wabkia: you made me google ADSMASDMAISDMASIOMA, hoping to find some super long abbreviation I didn't know yet. Am disappoint. 08:34:51 hahahah sorry bro, an expression of elation 08:35:01 wondering where samba went tho LOL 08:37:01 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 08:39:23 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 08:40:04 installed samba, it was already set as enabled, conf was still there, started samba_server, working juuuuust fine :D 08:40:34 with the last snapshot from freebsd-update boot environment set as active it reboots without intervention >< 08:40:37 phhew what a day 08:50:38 Alver tyvm for adding that knowledge to the wiki. either ipv6 or jail section i guess 08:50:41 g'night 08:50:53 wabkia: no you shouldn't remove the default boot environment 08:53:01 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 09:01:52 hmmm, when it boots from default, it gives me a mountroot> prompt 09:01:53 idk =\ 09:08:19 did you maybe forget some more merge conflicts? 09:09:03 Heh, registering on the FreeBSD wiki is done by *mailing* a *physical person* who will then *manually* create the account. :D 09:09:06 Oldskool. 09:09:59 Don't forget to put a stamped and addressed return envelope in there for your wiki sticker 09:10:51 oOoo. I like stickers 09:11:15 * Alver is happy as a clam with the jails finally working 09:37:18 nimaje no, the mountroot> problem i was having before i updated from 12.2 10:57:29 hi, I would like to burn an ISO image (https://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 10:58:18 https://bpa.st/SF5Q 10:58:42 it has been agers since I did this so any help is welcomed 12:05:03 uskerine: Well you could use the -dummy option while playing around that should be a safe bet. 12:06:08 Just realised that it must also be over 2 years since I last burnt a disc. :-D 14:42:44 Hi there 14:43:07 A lot of times I have an issue with external storage with ZFS file system 14:43:33 once connection failed or somehow power to the drive is disconnected the system become unstable 14:43:46 there is no way even to reboot remotely 14:43:54 the commands is just hangs 14:44:43 export, import, online, ... doesn't seems to have any effect other then just stuck without completion 14:45:11 the pool is in "suspended" state, even if drive is available 14:55:51 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. 14:56:19 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. 14:56:20 rwp usb also, external sata - same effect 14:56:27 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. 14:56:37 sorry wrong clipboard 14:56:38 https://github.com/openzfs/zfs/pull/11082 14:56:41 ^^^^ 14:59:34 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. 14:59:44 * rwp has a meeting now ttfn 17:21:34 this is the best fun rsyncing the whole rootfs under a running system from another one xD 17:25:59 i guess that implies ufs, and not zfs 17:30:05 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) 20:33:27 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: https://i.imgur.com/ogyISRM.jpeg 20:37:21 feel free to ping if you have any input, I lurk :D 20:47:30 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. 20:48:14 I swapped the HDD out for one with a split cable for power and data, and all was well after, afaicr 20:54:58 Alver: the external HDD has its own power adapter 21:14:27 can someone tell me if 13.whatever still is using python39 packages or has 311 at this time? 21:16:57 rtprio: ports isn't freebsd release specific and has switched to 311 21:17:22 i know this, but it specifies how packages are built 21:25:39 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 21:38:22 it's only been default since may 29 21:41:54 so more then a month, if nothing went completly wrong, there were two complete rebuilds of the pkg repos in between 21:49:01 I see the following in /var/log/messages from ntpd: leapsecond file ('/var/db/ntpd.leap-seconds.list'): expired 14 days ago 21:49:07 how do I resolve this? 22:49:23 mns: service ntpd fetch 23:12:28 Shouldn't periodic be auto fetching that? 23:34:34 mns, Put this in your /etc/rc.conf file: sysrc ntp_leapfile_sources="https://data.iana.org/time-zones/tzdb/leap-seconds.list" 23:35:40 The previous source that we used for years has decided to stop providing it. That's the new location of the data. 23:40:23 where can we watch the asiabsdcon 2023 and 2024 vids?