On Sat, Oct 31, 2026 at 09:51:38AM -0700, bob prohaska wrote:

In the meantime, a second Pi, a Pi3 running:
bob@ns2:/usr/local/share/doc/db18 % uname -apKU
FreeBSD ns2.zefox.net 14.4-RELEASE-p6 FreeBSD 14.4-RELEASE-p6 GENERIC arm64 
aarch64 1404000 1404000

just reported:
Checking setuid files and devices:
find: /usr/local/share/doc/db18/api_reference: Input/output error

(snip)

The host is a microSD-based binary-only setup that
hasn't been recently updated, so no recent writes that
might have gone wrong. It hasn't been physically disturbed
in at least a year.

That actually sounds like dirty power. In my office I have
two UPS units, most of the computers run off these.
They clean the power as well as ofc supply power
in an outage. The pi3 running here (also a binary install,
on 14.5-p2 I think) also a dns server (unbound in ports)
is on one of the UPSes and it chugs along just fine
with the three outages we had in the storms last week.
It also has high uptimes, additionally /var/log gets mounted tmpfs to further preserve the microsd.

A rpi4 in another room, not on any UPS, running linux, lost its filesystem to the extent it wouldn't boot. Probably when the power went off on off on off on rapidly before full power loss, and also the surge when it came back.

In the meantime, I let badblocks (the RasPiOS version)
run on the USB hard disk overnight. It generated no
output, which I'm tempted to think means it found no
errors worth reporting. In looking at the FreeBSD man
page for badblocks it appears to be a clone of the
Linux version, intended for use under Linux filechecking.
Is it even meaningful to use badblocks FreeBSD?

for hd health, I find dd works best.
Back up that you need from the disk then something like
' dd if=/dev/your_device_number of=/dev/your_device_number bs=4096 \
conv=sync,noerror status=progress'

run it in a tmux session
--
void<at>f-m.fm | GPG fingerprint: BD97 5B52 1B78 B7A9 AFFE  7DD4 FD32 D1F9 0814 
DECD
Please don't Cc: as I'm already subscribed to the list.

Attachment: signature.asc
Description: PGP signature

Reply via email to