02:39:26 hi everyone, I'm having trouble with booting 12.4 release on sparc 02:39:40 basically getting the same results as here: https://forums.freebsd.org/threads/booting-freebsd-8-1-on-sun-fire-280r.17649/ 02:39:42 Title: booting FreeBSD 8.1 on sun fire 280R | The FreeBSD Forums 02:40:01 my machine is sun fire v100 (also known as netra X1) 02:40:13 symptoms are the same: The file just loaded does not appear to be executable. 02:40:35 I can boot Debian and Gentoo, but not FreeBSD. NetBSD gives the same error 02:41:16 I've burned 4 different images and changed cdrom drive, so that's out of the question... I burn at 8x and verify iso after, no errors 02:41:45 it seems like some openfirmware peculiarity, but I'm really puzzled at this point 02:58:46 That's goingto be a tough one to solve in the 3 weeks before 12.4 goes EOL. 04:17:26 I don't know that we actually have anyone all tht familiar with the sparc64 boot process anymore 04:21:00 I used to be. 04:21:11 Ran NetBSD on them. But it's been a while. 04:21:25 (Netbooted, too. I loved that platform.) 04:37:00 <_zip100> ok I don't know what was that 04:37:10 <_zip100> but apparently :f in the end of device name is mandatory 04:37:22 <_zip100> so full command is boot /pci@1f,0/ide@d/cdrom:f 04:42:46 _zip100: With that, you boot? 04:43:41 out of curiosity, what do you guys use for basic file distribution (http) outside of a script that modifies an index.html or something? 04:44:17 Apache httpd's AutoIndex feature? 04:48:59 _zip100: that's funkadelic, but glad you got it going 04:49:09 you're now the channel's resident expert 04:51:02 <_zip100> :D 04:51:13 <_zip100> yes, it boots successfully and I got into installer 04:52:07 nice 04:52:20 vdamewood: thx, will check it out 04:52:23 I miss having all the funky hardware, PMAX the most. (DECstation 5000/200) 04:53:00 I miss my SparcStation IPX. 04:53:20 It was the first computer I ever replaced a single IC on. 04:53:27 I have an IPC and an IPX. Got rid of all of it when I had kids, not realizing I was a year away from a house with enough room that I'd have a dedicated machine room in the cellar. 04:53:36 Had* Had* sadly past-tense. 04:53:46 The IPC had 4.3BSD 04:53:53 <_zip100> wow nice 04:53:57 No. 4.1? Something old. 04:54:11 Got rid of it all, except for my first two computers. 04:54:35 In my case, I had to put it in a storage unit that was rented by my mother, and guess who didn''t pay the bill 04:55:31 doh 04:56:27 ouch =( 04:57:49 _zip100: Even if you default to disk on that, it'd be well worth it to get a tftp and rarpd on your network for experimental stuff. 04:58:52 <_zip100> mason: I've spent two full days trying to netboot NetBSD from Linux. Now I know that both OpenBSD and NetBSD use network bootloader which supports only NFSv2 04:59:19 _zip100: Oh, hm. You should be able to snag a miniroot and go to anything from that. 04:59:45 Same idea as a Linux initramfs. 04:59:53 <_zip100> I thought so as well, but in practice bootloader cannot speak tftp 05:00:02 <_zip100> it can be loaded via tftp, yes 05:00:11 <_zip100> but then it goes full NFSv2 mode after 05:00:13 hrm, hrm. 05:00:37 <_zip100> so either a dedicated machine just for netbooting, because Linux has long since remove 2nd version of NFS 05:00:48 <_zip100> or putting kernel on disk and then mounting root via NFS 05:01:22 <_zip100> third option: add NFSv3 support to the bootloader :D 05:01:34 <_zip100> which would solve all problems actually 05:01:40 <_zip100> but it's quite a task 05:09:04 Seems worthwhile, fun. 06:30:54 How do i see what fs a usb drive has ? gpart show has it as mbr gpart list shows it da0s1 what else can i find ? 06:43:08 file -s 06:56:55 try df -T 06:59:48 thanks richard_ 07:49:19 Does FreeBSD support UASP? 08:38:28 endrift: AFAIK, no does it not. 08:39:30 i got a bin running with daemon and i need to see errors in /var/log/messages but they're not coming. the daemon line is daemon -P -f -m 3 -l local5 -s debug -T... is that not the right way? 08:39:51 if i run the bin's command directly it exits with an error so i know it makes them 09:00:05 is it possible to 'tail -f' everything going to syslog without making a new file config? 09:04:33 hm wow took all of those args out and just passed -S to daemon and it suppressed terminal output and instead now it's showing up in /var/log/messages like i want 09:13:44 is the -f the problem in your daemon command? 09:16:58 not sure. put it back in behavior was the same. then took -S out and behavior was the same 09:17:26 not sure why -f seems optional 09:20:05 any way to configure top's poll rate to be faster systemwide? 09:20:09 like in a /etc file 09:39:10 if a bin generates files that other system services and bins use, where should those files go? 10:13:11 :D hi 10:13:41 how do i fix "stale file handle" error when i try mounting nfs share hosted on fbsd from a linux client? 10:16:46 nevermind got it <3 :D 10:16:57 <3 10:18:17 welcome to /usr/home/wsky/nfs running on freebsd settled on a m2 mac running on utm :D 10:18:24 https://vlepy.com/~wsky/diabelek1/ 10:18:25 Title: Index of /~wsky/diabelek1 10:20:18 whoa 10:20:21 i don't know why i did that :F too much free time this morning 10:20:30 it fast? 10:20:49 what's fast? 10:20:52 hm makes me wonder, freebsd got drivers for AI accelerator hardware? 10:25:36 https://vlepy.com/~wsky/diabelek1/Zrzut%20ekranu%202023-12-10%20o%2011.24.09.png 10:35:51 that using hypervisorkit? 10:37:13 the bsd is running on utm 10:38:00 what's utm 10:38:25 it's a vm solution for apple silicon macs 10:38:38 cool 10:38:43 using bhyve? 10:40:58 nope 10:41:06 not that i know of 10:48:26 UTM uses Qemu 10:48:40 Hi all, I'm trying to upgrade 13.2-RELEASE to 14.0-RELEASE and for some reason after installing both kernel and word (tried both via source and binary upgrade) the system still boots into 13.2 kernel. I also started this thread on FreeBSD forums so far to no avail: https://forums.freebsd.org/threads/upgrading-13-2-14-0-from-source-is-not-successful.91263/. Any help is appreciated. 12:00:57 bolik: please check that you're booting into the right boot environment using bectl(8) 12:05:26 i want my bsd to stop getting dns from dhcp, i want static dns servers 12:05:29 how wouldi. do that? 12:07:53 mane: something like 'ignore domain-name-servers;' in /etc/dhclient.conf should work (although i haven't tested it, i just read the manpage). or you could use 'supersede domain-name-servers ...' to specify your own 12:08:25 see dhclient.conf(5) 12:08:51 thanks you! :D 12:09:36 I'd _completely_ forgotten about dhclient.conf and was looking at resolv.conf(5) and rc.conf(5) :) 12:14:58 debdrup: the latter might have something to prevent local_unbound setup haha 12:15:14 the resolv.conf import I mean 12:15:40 Remilia: only to enable it, I think. 12:15:53 hmm 12:15:55 true 12:16:25 Still, dhclient.conf(5) was completely paged out of my memory. 12:17:57 morg 12:18:19 morn* 12:18:41 Bitflip in between brain and keyboard? :D 12:19:01 he wanted to say "borg" but it's a secret 12:20:10 computer boots up faster than brain into the hivemind 12:20:54 :D 12:22:53 NVMe drives will do that :D 12:23:47 debdrup: evidently :) 12:24:37 That's assuming you reboot for anything other than kernel upgrades, of course - there's really no need for anything else. 12:26:43 * deacon426 agrees 12:27:16 the borg is sending instruction to retrieve fresh coffee 12:27:26 and upload 12:30:38 'morg' is transliterated Russian for morgue 12:30:54 could have at least made it Morgen instead 12:32:19 Remilia: I do feel somewhat dead atm so not far off 12:34:35 * deacon426 zombie-walks to the coffee machine 12:38:03 debdrup: I switched from a dedicated server to a VPS with guaranteed dedicated resources and post-update reboots are absolutely mind-blowing 12:38:21 on the old server major version upgrade meant like 20 minutes of downtime 12:38:34 because the BIOS took 7-8 minutes 12:38:47 'sea of sensors' my arse 12:39:41 plus it had hardware RAID1 with spinning rust on an E3-1240, while now it is 10 cores of an EPYC with NVMe SSD RAID 12:39:57 ≈4 seconds from connection lost to SSH up 12:41:11 Remilia: please stop intriguing me, i need coffee.. The BORG sais so 12:41:13 *us 12:41:24 *we 12:43:11 the only issue with the new server is that the provider's network keeps getting blocked by MS mail relays 12:57:18 @debdrup: bectl boots the environment created in 2021 (it states: BE:default, Active:NR, Mointpoint:/). Can I test whether the environment is able to boot before actually defining an untested BE as the one to be booted? 13:06:37 uploading coffee 40% complete--we ar one 13:12:26 Remilia: sounds like they have to call MS and get whitelisted, unless they're known spammers? Or for some whacky political reason 13:13:16 MS does not do whitelisting :| 13:13:44 you can ask to be delisted when they block you but they'll re-block if someone *on the same network* does the thing 13:13:46 scoundrels! 13:14:18 and the problem here that my server's IP is marked 'normal' by MS and only the provider can ask for a delisting 13:21:24 yeah, i feel like my new Arm64 VPS @ Hetzner boot exec 13:21:45 *even faster than the amd64 VPS 14:06:18 _xor: SIGABRT is generally the result of an explicit abort() call; various libraries and runtime environments do that when unable to proceed 14:06:49 e.g. c++ unhandled exceptions, memory corruptions detected by malloc, assertion failure in assert builds, etc. 14:18:16 bolik: you can test by using the -t flag for the activate, which enables the bootonce functionality; if it doesn't come up as you expect it to, simply reboot the machine by any means expedient (even a hard reset will work, and that's how I use it along with watchdogd(8) to enable unattended upgrades, the idea for which I have to credit Allan) 14:18:25 for the activate subcommand* 14:22:12 Good afternoon 14:24:44 any way to configure top's poll rate to be faster systemwide? like in a /etc file. 14:26:21 polyex: set the TOP environment variable using login classes in login.conf(5) 14:26:37 It's documented in top(1) ;) 14:26:46 no config file route? 14:27:06 I'm confused, what do you mean? 14:27:20 @debgrup: I will try that, however, so far, when trying to change the boot environment during the startup (playing with boot options) I only see BE´s of 13.2-RELEASE and none 14.0-RELEASE, even though bectl list does show 2 BE´s 14.0-RELEASE. 14:27:26 like a /etc/top.conf where i can set a global poll rate 14:27:33 If you set the TOP envionment variable via login classes using login.conf, all users in that class will inherit that environment variable. 14:27:43 ya i know 14:28:32 You're free to modify top to be able to read /etc/top.conf, but I doubt it's going to be accepted upstream because it seems incredibly installation-specific. 14:28:50 Especially when you can already accomplish what you want another way. 14:29:11 Similarly, tools like less also support the LESS variable. 14:29:59 It might be useful to add the various base system utility environment variables to environ(7).. 14:44:06 greerings dear FreeBSD people 14:44:11 greetings* even 14:44:19 today is a day of typos, apparently 14:44:24 oh yes! 14:44:49 what's the commonly accepted method for upgrading jails after a base system upgrade to 14.0-RELEASE? 14:44:55 bolik: huh, I'm not sure what the difference would be.. 14:45:12 my jails are ZFS clones of a 13.2-RELEASE snapshot template 14:46:28 veg: freebsd-update using -j and optionally --currently-running if that's appropriate 14:54:10 Neat, https://freshbsd.org/freebsd/src/commit/231eee17d2905 and https://freshbsd.org/freebsd/src/commit/e3b4fe645e50b adds software breakpoints and singlestepping to AMD CPUs for bhyve 14:54:11 Title: FreeBSD / src / 231eee1 / vmm: enable software breakpoints for AMD CPUs - FreshBSD 15:02:07 wow 15:02:40 if freebsd has tier 1 driver support for accelerated AI hardware maybe it takes the throne back from linux 15:02:52 that's the next datacenter trends 15:07:27 debgrup: tried to set the BE with bectl -t to 14.0-RELEASE but it still boots the old 13.2-RELEASE 15:09:10 All stocastic parrot acceleration hardware seems entirely proprietary, so I wouldn't hold my breath for it. 15:09:46 bolik: sorry, I've no clue; did you follow instructions on https://docs.freebsd.org/en/books/handbook/cutting-edge/#updating-upgrading-freebsdupdate ? 15:09:47 Title: Chapter 26. Updating and Upgrading FreeBSD | FreeBSD Documentation Portal 15:11:07 debdrup: Yes, i did. Thank you for your time. 15:12:44 does the bectl list output show the 14.0 as the currently active one? 15:15:22 even the proprietary AI hardware options seem limited: NVidia doesn't provide FreeBSD drivers for theirs, from what i can see 15:17:03 Remilia: No, it has a ¨T¨ flag next to it. 15:20:20 T is temporary hmm 15:20:55 Yes, i did bectl activate -t 15:21:12 so it´ll only boot once to check if itś working 15:26:51 bolik: I just tried -t with my poudriere VM and it worked as expected :\ 15:27:33 specified the 14.0-RELEASE-p1 as temporary, `shutdown -r now`, booted into that, did another `shutdown -r now` and got 14.0-RELEASE-p2 again 15:32:32 Remilia: thank you for trying. I have tried to search what could be the issue and ran across this possibility: https://serverfault.com/questions/602231/conflicting-information-about-the-running-kernel-version-in-freebsd/602263#602263 however, I´m not sure how to act upon it (but then again, it´s just a guess that I face similar issue).. 15:32:33 Title: Conflicting information about the running kernel version in FreeBSD - Server Fault 15:38:32 is there any way to get remaining lifetime information from an SD card? it doesn't support SMART, i already tried that. mmcsd0: 16GB at mmc1 50.0MHz/4bit/65535-block 15:40:49 any Ocaml people in here? 15:43:54 better to just ask your question and when someone can answer they will probably answer 15:44:35 okey. any known issues/limitation I should be aware of while working with OCaml in FreeBSD 15:45:05 * drobban about to learn about OCaml. 16:18:41 <_xor> I run into this every so often and it still manages to both amaze me and crack me up lol... 16:18:41 <_xor> https://stackoverflow.com/a/4583502 16:18:42 Title: c++ - Printing 1 to 1000 without loop or conditionals - Stack Overflow 16:19:23 <_xor> 5 lines, not including the headers of course, and without conditionals. 16:20:01 <_xor> 4 lines. Apparently my brain isn't tail-call optimized heh. 16:31:50 is it normal for pf to keep state information for dropped packets ? 16:32:20 I have this IP that keeps on badgering me : it's blocked but PF now has 25000 entries in the state table for it 17:01:17 unixwitch: for non-volatile flash like that found in SD cards and USB flash devices, it's best to treat it as WORM media and not assume you can write to it more than once - because often they simply have not enough sectors to move things around if a cell gets damaged and you've also rewritten data 17:02:42 drobban: I know of people who use ocaml on freebsd, so I assume that it works 17:03:45 unixwitch: interestingly enough, the above position isn't even one only held by IT people; any photographer, professional or amateur, will usually tell you that they treat SD cards like they're film roll 17:04:20 I have a sneaking suspicion that photographers use SD cards more than just about anyone else, so it' a pretty safe bet they know what they're talking about. 17:05:17 debdrup: considering the SD card is this system's root filesystem, that's not really an option 17:07:52 unixwitch: I assume it's necessary to boot, but can you reroot (reboot -r) onto _slightly_ more trustworthy storage? 17:08:21 That way you can keep the SD card read-only unless you're upgrading, which saves on whatever limited amount of spare cells it has. 17:09:29 does anyone have the link to the source code that shows the exact changes between minor p version releases ? like p1 vs p2 vs p3, etc 17:09:41 the changes aren't listed on : https://www.freebsd.org/releases/12.4R/errata/ for example 17:09:43 Title: FreeBSD 12.4-RELEASE Errata | The FreeBSD Project 17:09:49 i'm aware of the limitations of SD cards, i'm not looking to replace the SD card right now. i'm just curious about querying its state. 17:10:30 unixwitch: camcontrol might be able to tell you something, I'm not sure. 17:10:58 I don't know that there's an official API for it; if there is, I'm not sure it's in FreeBSDs base system. Have you looked in ports? 17:11:54 last1: check the releng branch for the m ajor version you're interested in. 17:13:02 https://cgit.freebsd.org/src/log/?h=releng/12.4 if I remember the URI scheme right 17:13:06 Title: src - FreeBSD source tree 17:13:10 that's typed from memory, so it might not work 17:13:45 I found the github tree as well 17:13:56 https://github.com/freebsd/freebsd-src/commits/releng/12.4/ 17:13:57 Title: Commits · freebsd/freebsd-src · GitHub 17:14:27 cgit.freebsd.org is the repo of record, github is just a mirror 17:14:47 ok, I'm confused about something 17:14:57 I wanted to get the openzfs fix with the dirty dnode issue 17:15:00 same, but about a lot :D 17:15:13 I did freebsd-update fetch on Dec 2nd, and it upgraded me to 12.4-p6 17:15:22 now I see that the fix didn't happen until p8 17:15:30 even though it was released on Dec 1st 17:15:52 check freebsd-version -kru 17:16:07 kernel and userland can be out of sync 17:16:52 freebsd-version -kru 12.4-RELEASE-p6 12.4-RELEASE-p6 12.4-RELEASE-p8 17:16:55 what does that mean ? lol 17:17:44 freebsd-version without args just prints: 12.4-RELEASE-p8 and uname -a shows 12.4-RELEASE-p6 FreeBSD 12.4-RELEASE-p6 17:17:59 if you check the manual page for freebsd-version, you'll see that it lists the kernel, running and userland versions 17:18:10 uname -a derives its value from a sysctl(8) which is tied to the kernel 17:18:52 I'm hella confused. which version am I on ? I did fetch, install, reboot, install 17:19:16 you can be on multiple point versions at the same time 17:19:35 if freebsd-update is telling you that you're up to date, you are 17:20:06 it's an artifact of how updating works in freebsd, and you're not the only one that finds it confuusing :) 17:20:09 I was affected by that zfs bug, I updated, the bug has now gone away but when I saw that I'm on p6 it made me think I didn't update 17:20:29 I just want to make sure I did update - because it's got me doubting myself now 17:20:36 how can I get all versions to match ? 17:20:41 you can't 17:21:21 the userland can have a higher number than the kernel, without it causing issues 17:21:34 last1: check the modification time on /boot/kernel/kernel and /boot/kernel/zfs.ko ... it might be only the updated module is shipped, not the kernel itself 17:21:47 that's a good way of putting it 17:21:51 yeah, zfs.ko has a proper modification time of dec 2nd 17:22:05 also confirmed by me seeing the bug has gone away 17:22:21 but now I have another machine that just updated to p9, I saw this one on p6 and it confused the hell out of me 17:22:27 since p6 doesn't have the fix. 17:22:42 so p6 has the p8 fix 17:22:45 crazy 17:23:08 no, the zfs kernel module is from p8, but that doesn't affect the kernel binary 17:23:57 it's a bit of a trip when you learn about this, but it all _does_ actually make sense 17:24:17 it's not that p6 has the fix, but the kernel version that uname prints is stored in /boot/kernel/kernel. so you have the /boot/kernel/kernel from p6 and /boot/kernel/zfs.ko from p8. there is no p8 version of /boot/kernel/kernel because the kernel itself didn't require an update. (yes, this is strange and confusing and i don't really like it.) 17:25:21 more importantly, it has a practical upshot - if there's ever a patch for the userland (ie. utilities or libraries), which doesn't update the kernel, you can simply update freebsd without rebooting (though you'll probably need to use sysutils/checkrestart to make sure you've restarted everything that needs it 17:25:46 s/$/)/ 17:26:03 shame that modules apparently don't have sccsid tags, or you could use `what /boot/kernel/zfs.ko` to confirm the fixed version is installed 17:27:40 yeah that'd be handy in situations like this where a module has been fixed by a point release - but those don't happen super rarely 17:28:12 I didn't realize we still don't have a driver for BCM4360. That's a real bummer. 17:29:04 rafe: Broadcom hasn't exactly been forthcoming with documentation for a BSD licensed driver 17:29:05 but p9 did update the kernel 17:30:03 debdup: Totally understand that problem, but the OpenBSD port has been around for awhile, no? 17:30:26 *debdrup 17:36:39 rafe: someone still needs to do the work, and that'd only make that one NIC work - bz@ is working on a different solution whereby the LKPI doesn't just work for GPUs, but also for WiFi devices, so that Linux drivers can be put in ports (since they're GPL, they can't be in the base system) and can be added that way. 17:37:36 Sounds like an even better solution; I hope it progresses soon. Is there a targeted release? 17:54:01 rafe, IIRC, some of it is already in 14.0. See https://people.freebsd.org/%7Ebz/wireless/ and https://www.freebsd.org/status/report-2022-10-2022-12/#_wireless_updates . 17:54:02 Title: Wireless Work In Progress 17:58:55 is perform-actual-lookups is enabled in nscd.conf, does that mean the cache is shared for all users, rather than being per-user? the behaviour for nscd -i/-I seems to imply this but doesn't actually say so 18:03:50 A lot of the utility of a nameserver cache would go away if it was per-user. 18:04:41 Being able to invalidate per-user has _some_ use, for rootcausing, but beyond that the best results are typically achieved by having everyone share the same nameserver cache. 18:05:04 i agree, that's why i'm wondering if this option makes the cache shared, instead of per-user like it is by default 18:06:35 Oh, huh, you're right - I completely missed that. 18:06:48 Take whatever I said and put it in the bin, please. 18:07:23 I guess -I is just for the convenience of not having to do -i for every user then. 18:10:20 this seems to suggest the cache is shared when nscd is doing lookups: https://cgit.freebsd.org/src/tree/usr.sbin/nscd/query.c?h=releng/14.0#n693 18:10:21 Title: query.c « nscd « usr.sbin - src - FreeBSD source tree 18:12:10 the code is rather lightly commented though... 18:13:05 Presumably nscd can't poison itself, which is the reason for the per-user caching - so it seems fine on first blush? 18:13:23 If someone can casue nscd to cache poison itself, you've got bigger problems. :D 18:14:24 that's why i would assume it works this way, but... i can't actually find anything that says so. maybe i should test it 18:26:02 There are few better way than diving in and finding out. 18:40:45 random weirdness of the day: LDAP's groupOfNames can't be empty (because the 'member' attribute is required)... so if you want to remove the last member from a group you have to delete the entire group, i guess? what an odd restriction. 18:41:39 rather annoying combined with rfc2307bis because posixGroup is an auxilliary objectClass there, so you can't (easily) have an empty POSIX group which is sometimes actually useful if the group only has primary members 18:49:23 Hey! ZFS-question. I put a new drive in and replaced one disk and removed two others (i only got one drive in total). After resilvering the first disk and evacutation for the other disks with all the data to the new drive can I physically remove the drives and change sata port for the new drive and boot the system? I installed boot code etc on the new drive. 18:49:55 gendish: only if you also remembered to put the boot sectors on the new drive 18:50:26 Unfortunately, ZFS can't manage boot sectors, so you have to do it via gpart - with the wrinkle, that it'll depend on your system setup. 18:50:41 debdrup: yeah i did that :) 18:50:46 gendish: moving a disk to a new port is fine since zfs doesn't use the physical port to identify the disk. removing the old disks is also fine as long as they're not listed in 'zpool status' anymore. as debdrup said check bootcode etc... 18:52:26 thanks. one thing i haven't understand yet is if i got legacy boot (no uefi) can i still boot a drive with zfsbootcode bigger then 2TB in freebsd? 18:52:52 gptzfsboot is your friend 18:53:11 my zroot pool is larger then 2TB 18:53:19 and? 18:53:20 hey Remilia :) 18:53:27 sorry I do not get it 18:53:52 how is that related to installing the GPT-aware ZFS boot loader in the first sector 18:53:59 i think the question is about issues with large disks and the BIOS interface that the CSM loader uses... i don't know the answer though 18:54:14 unixwitch: yeah thats correct 18:54:19 BIOS does not care, it will see the MBR shim 18:54:43 but loader uses the BIOS interface to read from the zpool, doesn't it? i mean, it doesn't contain hardware drivers for storage devices, so it must do 18:54:56 Remilia: ok, that was my question yesterday. thanks for answering 18:55:02 MBR is limited to ~2TB for disks, but GPT supports what's called a pMBR. 18:55:20 i f*cking love your nerds 18:55:26 you* 18:55:33 see gptzfsboot(8) 18:56:30 Remilia: I did but im too stupid to understand maybe. But my guess was that it would function like you said 18:56:38 unixwitch: the issue with 2 TB+ is that you cannot have an MBR partition that exceeds that size 18:56:39 boot(8) does have a note about this in the DIAGNOSTICS section which presumably also applies to gptzfsboot 18:56:57 NOTE: On older machines, or otherwise where EDD support (disk packet interface support) is not available, all boot-related files and structures (including the NOTE: On older machines, or otherwise where EDD support (disk packet interface support) is not available, all boot-related files and structures (including the NOTE: On older machines, or otherwise where EDD support (disk packet interface support) is not available, all boot-related files and st 18:56:59 the BIOS calls are not limited to 2 TB 18:57:03 whoops, bad paste 18:58:05 So when restarting my server after removing the old disks that been running for 8.5 years the server should both on one single 12TB drive with boot-codes installed! 18:58:21 EDD is apparently over 20 years old so this hopefully isn't an issue on any system still in use (at least one that's running ZFS) 18:59:53 point is, gptzfsboot does not care about MBR limits and hands off control to the loader in the pool it finds 19:00:08 which means 2 TB limit does not matter to it 19:00:19 the issue isn't MBR limits, it's that some (very old) BIOS call interfaces simply don't support large disks at all, so there's no way to read such data. 19:00:55 those 'very old' interfaces do not support disks larger than 4 GB 19:01:14 ok. I understand! Thanks for the info. It's just a waiting game now: Evacuation of /dev/ada1p3 in progress since Sun Dec 10 19:32:27 2023 231G copied out of 2.35T at 145M/s, 9.60% done, 4h15m to go 19:02:31 gendish: fwiw, if this is a long term change, you might be better off creating a new pool on the disk you want to use and copying the data over, instead of using zfs remove, to avoid the (admittedly fairly small) memory overhead 19:04:26 unixwitch: yeah, but this is the path I choosed :P 19:05:12 I do love my old x58 system with a intel 980x extreme edition. I want to keep it alive for as long as possible 19:05:48 gendish: oh, the power consumption of those older i7s… 19:06:02 thanks again all. is there anything to do if i want to verify that the boot-code is really there on the new drive? 19:06:08 130 W TDP 19:06:27 Remilia: got decent electricity prices 19:06:33 but yeah i know 19:06:38 gendish: 19:06:41 err, mistype 19:07:46 gendish: I find it funny that R9 7900 has 12C/24T at half the TDP of your 980 19:08:21 got a 3700x laying around... 19:09:03 Remilia: dont give me anxiety over electricity bills now (: 19:09:24 3700X has 65W TDP iirc 19:09:30 when upgrading from 12.4-p3 to p9, I did fetch / install / reboot then I issued another install 19:09:36 and it said: No updates are available to install. Run '/usr/sbin/freebsd-update fetch' first. 19:09:39 in fact, I am using a 3700X right now 19:09:56 is that to be expected on such minor updates ? 19:09:58 last1: you only need to install twice for major upgrades 19:10:04 13 to 14 19:10:16 it is related to ABI 19:10:44 basically read what freebsd-update install tells you 19:11:15 for 2-stage it will say something like 'kernel updates have been installed. reboot the system and continue with freebsd-update install' 19:11:52 Remilia: yeah i know. but need to buy a new mobo, memory etc 19:12:14 for the 3700x 19:18:02 last1, I have been confused by the three different versions of freebsd-version too. Let me try to help "unconfuse" things. 19:18:09 The kernel is a specific part and has its own kernel version. There is a version for the kernel that has been last installed on disk and a version of the kernel that is running. These will be different if a kernel has been installed but not yet rebooted to it. 19:18:20 Then there is a version for all of the non-kernel userland parts of the base system. freebsd-version without options reports the userland version. With -k it reports the installed kernel. With -r it reports the running kernel, the same as uname -r report. With -u it reports the userland version. 19:18:28 "freebsd-version -kru" seems most useful and reports all three versions. The userland version is often different from the kernel version since they are two independent parts of the system. 19:20:18 When freebsd-update install says "No updates are available to install. Run '/usr/sbin/freebsd-update fetch' first." it means there are no pending updates to apply. Running fetch *may* or *may not* find a new update from the distribution servers. If you are fully updated then there won't be any pending updates to apply. 19:21:06 The next freebsd-update fetch will say "No updates needed to update system to 13.2-RELEASE-p7." (at this moment) and no updates are pending. 19:21:29 On my updated system freebsd-version -kru reports 13.2-RELEASE-p4, 13.2-RELEASE-p4, 13.2-RELEASE-p7 19:22:06 And none of this above mentions the ports which are individually versioned and installed in /usr/local separately. 19:22:10 Hope this helps! 19:34:44 rwp: I do not think that was the question, they were just wondering why they did not need to do the 2-stage install 19:37:48 I think they had already done the full installation. 19:39:05 If I over-explained it then that's my bad. But it seemed at least some of the confusion was why freebsd-version reported something different from the kernel. 19:40:41 Also "freebsd-update install" always says to run "freebsd-update fetch" even though one already ran that earlier in order to get something to install. This makes sense in the grand scheme of things. Because on the first pass fetch will say there is something to install but on the second pass it will say that no updates are needed and break things out of the loop. 19:41:57 rwp: you would be neither the first nor the last to overexplain :3 19:43:26 Until I got comfortable with the design of the system I know this caught me a few times. And actually I am chagrinned to admit that just a couple of weeks ago you might remember that I hadn't had enough sleep and got snagged again just recently! 22:49:58 I would like a command to be executed prior nut starts. Where would it be the preferred place? I need to detach a kernel driver for a usb device -the ups- if I don't run it before I get "Can't claim USB device [0001:0000]@0/0: Other error" 23:16:06 is it possible for traffic to leak while pf is reloading? like service pf reload 23:22:22 Uh... I can't find how to install python-bcrypt on freebsd 23:22:56 and the pip install bcrypt requires rust compiler. I don't want a rust compiler for a damn python module just to hash things 23:25:00 gendish: how is the idle power draw of your cpu? 23:26:19 Ok I solved it