00:33:41 mvanbaak: just hope you don't get shock and awed :p 01:15:39 Speaking of wireguard running too slow, I had a fun one the other day. Turns out my home ISP was running a v4 over v6 tunnel or something that was adding extra overhead for every packet. The standard wg MTU adjustment wasn't enough, so I was getting packet fragmentation like crazy. Dropped the MTU and tunnel was back to normal speeds again. 01:16:25 o\ 02:24:30 is vm-bhyve still the go-to for running bhyve guests? 05:18:03 yes 05:19:50 thanks 08:01:26 i have optiplex 3050 micro running 15.1 and can't get any audio from the front panel minijack 08:01:47 sndstat shows: Installed devices: 08:01:48 pcm0: (play) default 08:01:48 pcm1: (play) 08:01:48 No devices installed from userspace. 08:02:29 it's unmuted in mixer 12:48:40 has anyone tried to use: https://github.com/FreeBSDFoundation/pkgbasify to transition their freebsd 15 from "traditional" upgrades to the pkgbase? I was thinking of doing in a jail.. and seeing if anyone had an experience good or bad using this? 12:58:05 voy4g3r2: I didn't do it on a jail specifically. I ran it on a regular host though. No issues (beyond one of my own making and failing to read the 15.1 upgrade notes in full and skipping the ports kmods update before rebooting haha). 12:59:17 For my jails, they are treated as disposable (managed using AppJail; easy to recreate). After the upgrade, I switched all of them over to pkgbase too (created a new pkgbase jail base, which AppJail can automate now, and rebuilt the jails off that). 14:30:08 ohhh interesting take on the appjail and base idea.. thank you ianthetechie 14:47:21 Sure thing voy4g3r2! If you wont to take a look, my whole setup is open source. Nothing about the AppJail setup itself (the docs are good and the maintainer is GREAT), but maybe some inspiration for how to set up the services: https://codeberg.org/ianthetechie/appjails 16:52:23 Currently it seems my rsync, on 14.4-RELEASE-p6, requires libcrypto.so.111, which I don't have... This seems to usually be a ports-related thing from reading, but I didn't compile rsync from ports 16:54:06 am fully upgraded and freebsd-version -kru shows 14.4 for everything, as far as I can tell 16:58:05 nvm, had missed a freebsd-update fetch 17:01:12 mewt: ldd `which rsync` 17:07:30 yes, did 17:08:23 And the result was...? 17:56:57 dch, ping 17:57:01 dch, it's not smooth sailing after all 17:57:20 dch, did the thing, took out the other old disk too (only booting from one now). the system is booting but then I get: 17:57:31 ZFS WARNING: Unable to open $dev for writing (error=1) 17:57:42 it lists that message both for the new drive and the now disconnected other old drive 17:58:17 if I have both the new drive and one of the old ones plugged in, the machine boots happily and zpool status looks good. 17:58:29 what does `zpool status -v` and `zpool list -v` show? output of `gpart show -l` is probably also useful 18:01:35 dch, https://paste.jvnv.net/view/36cX2 18:02:09 looks good to me. not sure why gpart backup|restore created the -free- (3.0K) section on the new disk tho. 18:04:07 difference on the new disk (ada1) between `gpart show` and `gpart show -l` tho: https://paste.jvnv.net/view/8eM7D 18:05:45 ah, that's just labels, never mind. 18:08:16 jbo: from a zfs side other than having the raw device name ada0p4 instead of gpt/disk0_zfs or whatever zfs seems happy 18:08:27 partitions look 4k aligned so this seems all good 18:09:17 dch, both old disks in the mirror didn't use GPT labels yet. I added the new one with a label. 18:09:22 that shouldn't break things, right? 18:09:27 no 18:09:43 even if the device names get renumbered for some reason zfs will figure it out 18:09:44 ada0p4 is the one I want to replace next but first I need to be able to boot from the new one and that's where things go wrong 18:09:54 it just looks nicer with gpt ones 18:11:32 I assume this is both rebootable at will and close at hand 18:11:55 yep 18:12:05 jbo: if you only have the new ada1 present, does it boot? and if not how far does it get? 18:12:36 ada1p1 should be an EFI partition, with msdosfs type 18:12:39 dch, that's where things are going wrong. if I only have new ada1 plugged in, it starts booting, but then eventually fails with the "ZFS WARNING: Unable to open $dev for writing (error=1) 18:13:06 so you get as far as the beastie boot loader? 18:13:10 yeah 18:13:14 not an EFI problem 18:13:29 and then it manages to load the kernel? but then fails? 18:13:30 I just repeated the experiment for a 4th time but this time I first detached ada0 from the zpool and now it seems happy... 18:13:47 which is concerning because if the drive would physically fail the machine wouldn't be able to boot from the other, good drive?! 18:13:53 * dch sprinkles holy water on ada0 18:13:58 :D 18:14:48 are you sure it ever booted from the other drive? 18:15:15 yeah 18:15:34 either you only have EFI partition set up on 1 drive, or your firmware isn't set up to boot from the 2nd device 18:15:53 I guarantee it booted fine from either of the old disks 1 hour ago before I started dicking around 18:16:05 ok thats good 18:16:10 the ZFS WARNING which prevents booting is concerning 18:24:36 so this looks like a hybrid boot system, bios+gpt layout 18:24:55 I think the error is coming from geom tasting 18:27:39 dch, after manually detaching the old drive from the pool everything seems to be fine... 18:27:45 jbo: so make sure all the partitions are labelled, and initialised, the bios boot sectors are written, and the efi partition is mountable as msdos, and has the correct bits present 18:27:53 now both are new disks and it boots happily from either without the ZFS write issue 18:48:03 ddr5 unbuffered ecc ram 18:48:32 sorry wrong channel 19:35:29 DDR5 is only quasi-ECC isn't it? 19:36:30 e.g. https://www.corsair.com/us/en/explorer/diy-builder/memory/is-ddr5-ecc-memory/ 20:01:16 You can buy real ECC with DDR5. 20:02:06 The decaf default ECC is worthless. 20:06:09 haha 20:26:53 the built-in ECC is cuz they run at such a high frequency, they'd fail without it 20:27:10 it is basically dishonest when manufacturers use it to sell the sticks 20:58:31 i ignore on-die ecc as a feature 20:59:16 it's on-die ECC 20:59:44 I never spent as long as with DDR5 to source proper ECC given that everything is marketed as ECC now 23:29:42 "Everything" is marketed as ECC?