Latest activity

Short update for 15.0-RELEASE, I've just tested this with 15.0-BETA2: - jlduran@ has imported blocklist 2025/04-/28 in https://cgit.freebsd.org/ports/commit/?id=e2dcc9fc4 - upstream has renamed blacklistd -> blocklistd so we have followed suit...

I would still expect a power supply with a ten year warranty to last a good ten years, especially if it is reasonably over-provisioned and a brand name device. Also, I would expect such a device to fail "cleanly" instead of going haywire and kill...

Yes :) I will inspect the issue first. If it occurs again I will try to replace SATA cables. If that doesn't work different ports, etc. Power Supplies should be changed after 5-7 years I think. Mine is 3 years old now, and always running in eco...

Funny fact: for me it was an EVGA Platinum 1000W power supply that failed. Granted, it was ten years and a bit old, but it was a 10 year warranty power supply so it was still unexpected. But agreed, not very likely, so it is at the bottom of the...

My last HDD Raid also behaved similarly. Due to letting some drivers out, I guess.

1. Camcontrol devlist and smartctl clearly didn't show my HDDs correctly, now they are, after adding some options to my custom kernel I assume very highly that it is either option 2 or 3. More likely option 2 though as the SATA cables are very...

There's no logged bad sectors or pending sectors so i think your disk plates are good. The 8 errors that you see can be caused by bad SATA connection, power interrupts (disk reset) or bad connection between the controller and disk head. After...

As far as I know the NVidia drivers (and their DRM driver counterparts) aren't included in the kmods repository yet. But those shouldn't be needed anymore, as the repositories are now built for 14.3-RELEASE specifically. But due to various...

sysrc kld_list # to check what kernel modules are loaded if any sysrc kld_list+=nvidia-modeset # to load nvidia.ko & nvidia-modeset.ko on reboot kldload nvidia-modeset # for using it without rebooting # -- this may or may not work... Reboot...

Hmmm....it seems obvious to me that I should not have upgraded to 14.3 until after 14.2's EOL. Oh, well. It is a learning experience for me, at least. Ken Gordon

I pretty much agree with the ideas VladiBG said, so making a short list here of possible causes: Your driver mods might have been the issue, if this does not happen with a GENERIC kernel, you know what the problem was. Bad SATA Cable Bad...

Yeah. All my systems here at home use both. They boot off UFS while ZFS is for data. The reason: I clone them rather than install them from scratch. For example, when I cloned my old laptop to my new laptop I simply had to change a few settings...

After my 'experiences' with N95/N100/N150 systems ... I omit them in any way - they are FAR from 6W TDP like Intel 3150N were ... After my adventures with various Mini NAS systems: -...

ZFS does provide better data recovery. A minimum of three copies of metadata are written to disk. Each block is checksummed with a hash. You will almost always know when your data is corrupt with ZFS. UFS and old-school filesystems like it don't...

Also the one below? https://en.wikipedia.org/wiki/Casu_martzu

PkgBase offers besides individual packages, so called "package sets" (meta-packages, see freebsd-base(7) manual for details on PACKAGE SETS). One of them is FreeBSD-set-base. With that base meta package, you can install/maintain the base system...

Keep in mind the CD and DVD images are read-only, even if you 'burned' them to a memory stick. You won't be able to create that mount point there. You can use /tmp/altroot for example as /tmp is a writable tmpfs filesystem. The installer itself...

I would have actually preferred a MacBookPro for work, but it's not an option our team-lead was willing to go through with. We will see how well the P14 holds up. I need to show up in the office three times a week and when the weather is not...

That failed, because I have a custom kernel compiled, and left out some SCSI options out, which were apparently needed. So, the drivers were not loaded properly. After comparing my kernel against the GENERIC one, I fixed that problem.

Well going through the diagnostics, and inspecting carefully I will just replace the 2 sata cables for the HDDs tomorrow and see whether still errors will occur or not, before replacing stuff. Thank you for the recommendation :)

Try with replacing the cable with a new short sata cable.

Yes, so now, as in currently, at the present point in time, they're being built for 14.3-RELEASE. And have been doing so since the beginning of October.

Managed to solve the smartcl error not showing up my HDDs. Issuing smartcl -a /dev/ada0 shows me: smartctl 7.5 2025-04-30 r5714 [FreeBSD 14.3-RELEASE-p3 amd64] (local build) Copyright (C) 2002-25, Bruce Allen, Christian Franke...

Thanks for your answers ....

Try paying attention, repositories were built for 14.2 until it went EoL. There's a three month overlap.

Well, for starters I am always uncomfortable with external storage (USB and Thunniebolt). Cables and plugs are always trying to come apart. Even if my local PC is only a terminal I would like to hold physically local backups on it.

Apparently some people ran the GNU coreutils test suite against the Rust coreutils, which showed many failures and the Ubuntus went ahead anyway.

I dunno about Mini PCs. Somehow it always strikes me as combining the disadvantages of a desktop with those of a laptop.

Thanks to all of you! I'll the create my poudriere-packages first on a host at home for 14.3 and transfer the packages before the update to my host which should be updated. (That's the mimic, I used also in the past.) Thanks a lot!

Just did a test, this isn't the only file that gets in the way. You also need to rm /usr/include/c++/v1/__tuple And it seems the directory has to exist too, I was expecting it to create that directory if it didn't exist. install...

It's only one file, just rm /usr/include/c++/v1/__string before doing the upgrade.

https://www.freebsd.org/security/advisories/FreeBSD-EN-23:12.freebsd-update.asc This is not available in 13.1 or 13.0. Since #1 says 13.0, need to update freebsd-update first.

No need to be too afraid for minor version upgrades. I'm creating poudriere jails once per stable branch and regularly upgrade it on stable branch (recently switched from stable/14 to stable/15 when the branch was created), as even upgrades from...

For poudriere you should just create a new jail with the new version. Then start your poudriere-bulk on the new version jail. I don't even do minor version upgrades on my poudriere jails, only patch updates...

If you don't want pkg rebuilds all at once, installing misc/compat13x until you can take enough time for rebuilding. Poudriere wants rebuilding all installed ports when OSVERSION (comes from __FreeBSD_version defined in /usr/include/sys/param.h...

Update the host itself first. You can go from any 13.x version directly to 14.3-RELEASE, there's no need to do any of the intermediate minor version upgrades. Just make sure the 13.x has the latest patch level before doing the major version...

Dan is one of my favorite sources. He shows up here on the forums. I'm not going to speculate "why" but would guess "time and real life" may have been factors. This article is still the basis of all my ZFS configurations...

https://www.freebsddiary.org/ hasn't had an entry since 2012. Though, it with other software related topics has continued at https://dan.langille.org and is current. The status of The FreeBSD Diary hasn't been updated since. Interestingly, Dan...

NB: sadly, I will not be running FreeBSD, but AlmaLinux if I can. Worst case: Ubuntu :-(

We'll get P14s Gen5 soon. I could also have had a P16s Gen3 - but I hated the asymmetrical keyboard where you are either sitting in front of the keyboard or in front of the screen but never both. That's what the X9 Aura (which is what I assume...

Interesting. I built smartmontools from source. And tried some commands like: Input: # smartctl -a /dev/ada0 # smartctl -HA /dev/ada0 # smartctl -d auto -a /dev/ada0 smartctl always tells me: "/dev/ada0: No such file or directory" I tried to...

Yes, I've had chance to discuss briefly with bapt on Matrix and already fixed what he wanted, and it's already landed both main (aka latest) and 2025Q4. Another possible cause he thought of is digged into by himself now.

It's not shipped with bash because it's entirely system dependant. You may or may not have noticed, in general, ports install fairly standard configuration files that came with the original distribution (which is why they often need a bit of...

when you're mounting a ZFS in a rescue environment, you should use mkdir -p /altroot; zpool import -R /altroot pool to avoid having to muck with the mount points of the datasets.

Split the X/Nvidia driver issue off in a separate thread: https://forums.freebsd.org/threads/x-stopped-working-after-upgrading-to-14-3.99714/

never used it, always used dd for a memstick image or some manner of CD burning program for ISOs

Why would you need a customized kernel in the first place? There's rarely a reason for it nowadays. If you need some highly customized install (for an embedded system for example), you can create your own pkgbase packages. But that's an entirely...

This has nothing to do with it being a 'closed system' or not. It's just not economically viable to repair it, the labor cost alone will be several times the costs of a brand new PI.

There are three ways to update your FreeBSD installation, the first, and original way, is to build from source. The second way (added around version 6.2) is freebsd-update. The third, and latest addition, is pkgbase. You use one of the three methods.

Greetings. You don't need to worry about building FreeBSD from source when using PKGBASE. All system components and kernel are maintained by a package management tool (ports-mgmt/pkg), using pre-built packages, fetched from official FreeBSD...