rrsync is no longer part of the rsync backage all my daily backups are broke reeEEEEeeee

ok i installed rsync-python but it conflicted with and deleted mariadb lol

this is lulzy bugs.freebsd.org/bugzilla/show_bug.cgi?id=286073

I thought I could limit the # of cpu cores by setting `hw.ncpu="2"` in loader.conf

or do I recall wrongly and that only works for memory?

that's a read only var

perhaps this can reach you to your goal, man.freebsd.org/cgi/man.cgi?cpuset

dch: yes, that should work

dch: although maybe this is only on ARM

i don't see anything in sys/amd64 that fetches the tunable

iRobbery: not in loader.conf its not

ivy: do you look for something like egrep GETSYSCTL.+hw.ncpu ?

dch: TUNABLE.*ncpu

ivy: thanks, that a neat trick

I worked backwards from that to find the smp(4) manpage

use git grep btw, it's often a lot faster than grep(1) :-)

I use ripgrep, its 2x faster than git grep

what's the difference between cpuset and maxcpus ? I understand the first is non-permanent?

so yes hw.ncpus appears to be an ARM only thing, and kern.smp.maxcpus isn't writable as far as I can tell

would be nice to have this, so I logged a PR

dch: ah good catch, ill remember that from now

ek: hi!

just read ur mail, gonna ask the postmaster

very funny that my "test" email got delivered (altough after a few hours)

and i tried sending a mail to pi@ directly, but this one got delayed again for same reason -_-

riad, maybe test your E-mail config at learndmarc.com

CrtxReavr: thanks, will try

really cool site

Indeed.

My SPF & DKIM passed (Google Apps domain), but DMARC failed. . .

But I had to regenerate a different DKIM key, amongst other work, to get my DMARC working correctly.

It was actually a longer story than that.

Needed some help from #email.

Vaultwarden is now broken on 13.x and one of its deps is broken on 15.x and 16.x. I hope capnproto will work again soon.

eek. hopefully I don't need to update during this period where it must be fixed

CrtxReavr: that sounds like a bit of a pain in the ass...

dmarc is passing for me though

Is SPF & DKIM passing?

CrtxReavr:

yes

ek thinks ipv6 routing is failing somethere along the line

might be possible

riad: Do you not have access to the mail server?

ek: i do not

but email to admin is sent

I just find it strange that it doesn't also attempt via v4 if v6 fails. Might be a shoddy SMTP setup or something.

vkarlsen Oh wow. Thanks for letting me know.

hey

i have FreeBSD 15.0 with ZFS pool disk. One of my disk failed so i'm trying to replace it. I did that many times in the past without any problem but when I stop the computer, change the failed disk and boot it again I got "zio_read error: 5" and "ZFS: i/o error - all block copies unavailable", "ZFS: failed to read pool disk directory object" and it can't boot

when I remove the new disk and put the old one in place, the computer accepts to boot...

zpool status only complains about the faulty disk and not the others

My first thought is that the good disk was replaced instead of the faulty disk.

it's a RAID 5 with 5 disks

4 disks*

I also checked that the serial number of the faulty disk is the same as the one returned by smartctl

And unfortunately the hardware does not have hot swap bays requiring you to power down? :-(

Reading your report carefully the main problem is that it can't boot. Makes me think maybe the boot loader code is on the disk being removed maybe? I might boot the installer iso and then use it to examine things in the new configuration using the "zpool import" command.

titou: yeah, that'd be my guess, the failed drive is the first one, and it's the one with the loader

swap drive 0 and 1 and i would expect it to boot

I was thinking that too.

Booting the install ISO allows getting a live boot shell. And in the live boot shell one can examine the array with "zpool import" to see what arrays are available and what devices are in them and the state of the collection.

Also another possibility is that the currently failed drive is not fully failed but is providing just enough data blocks to make things work because the remaining drive is also faulting. I had that situation. I could not /remove/ the failing drive because that put the remaining disks below the redundancy limit and the array was FAULTED.

You might need to add in the new replacement drive along with the existing drives and then use the zpool replace to silver it while the quorum of drives is still in place.

Please post the output of zpool status?

hum

I installed the bootloader on the four disks

by using: gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 2 adaX with X from 0 to 3

I also put the EFI file system on the four disks

since I restarted zpool status returns nothing.. i had checksum errors on the faulty disks. Smartctl returns no error.. and no error into dmesg too

I bought my four disks on the same time and they are dying one after the other.. silly barracuda :(

got a faulty zpool satus from daily mails: pastebin.com/HPxxjstU

I assume the faulty disk is ada3 with the cksum error count? The problem with the adaX device names is that they might change between reboots. So be sure to triple check the serial number of the drive. I use "smartctl -i /dev/ada3" for it and "smartctl -a /dev/ada3" to look at all of the data from it.

indeed I will double check

i restarted a zpool scrub and check again

thank you for your help

Is there a web based provides like the pkg plugin?

ex: What remote package provide a given file/glob

there is freshports.org, unless you were thinking of something else

ah that's right. Thanks.

titou, I know you are already scrubbing now but since it was only showing a smallish number of cksum errors the disk might not be actually fully bad yet. And sometimes errors can be caused by cable problems and power connector problems. By doing what you have already done of removing and replacing the drive that might rub the connectors and things might work better now.

I know you are already scrubbing but running a "zpool clear" to reset the counts and clear errors followed by a "zpool scrub" so that you know any new error counts are new since then would be appropriate.

Also I would run smart selftests and see the result. "smartctl -l error /dev/ada3" and "smartctl -l selftest /dev/ada3". At least a "short" test but depending upon the drive a long test may be useful. My latest drives I can't run the long test because it takes longer than a day to complete and the drive is consumed during that time. So I don't. But the short test is good.

SMART has never predicted a drive failure for me but if a drive is actually failing then it has always been accompanied by smart failures logged. But if an error has been a power connector and sometimes SATA cabling then sometimes the drive will log DMA failures that are really data transfer errors and I can ignore them when used with ZFS with redundancy.

rwp++

rwp: thank you for these information

I'm agree with you that previous failed disks had smart errors.. and that's strange that i don't have smart errors in this case

i did zpool clear two or three times and errors were corrected during each scrub

but maybe the SATA connector is failing.. i'll check with another one

Also double check the power connector. I had a bad 4-pin MOLEX power connector previously that caused me trouble. If the drive's own smart data is error free then I suspect cables.

Additionally if the drive is actually producing errors then the kernel should be logging something in /var/log/messages system log file.

rwp: nothing into the logs..

i will double check. Thanks a lot