Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 20 Dec 2025 14:10:57 +0100
From:      A FreeBSD User <freebsd@walstatt-de.de>
To:        FreeBSD CURRENT <freebsd-current@freebsd.org>
Subject:   CURRENT: havock: elf_load_section: truncated ELF file
Message-ID:  <20251220141124.1606aa7c@thor.sb211.local>

index | next in thread | raw e-mail

[-- Attachment #1 --]
Hello,

recently a small server running recent CURRENT with a UFS basesd system SSD (NVMe) and a data
graveyard based on RAID level 5 with ZFS (attached to a Fujitsu HBA controler) gets corrupted
because of "loosing" a driver - this time the system reported TWO drives a removed froma RAID
level 5 - which is like a death sentence.

I guess this is a fallout of the recently changed timie parameters to the CAM infrastructure
(I can't find any notes on this in man cam, so I feel lost).

A very desastrous side effect of this crash was the inability to reboot the box (CURRENT pre-
16.0-CURRENT #11 master-n282659-7f39d05b67ae: Sat Dec 20 09:35:32 CET 2025amd64, the runtime
system was from 16th or 17th of December). 
After several tenth of minutes I had to hadr reboot the box - with obvious data loss on the
system SSD. And here my problems start to turn into a mess.

After the first initial reboot I performed a fsck -fy, rebootet and whitnessed that
jails didn't come up anymore and SSHD didn't work. So I installed prior to the crash already
compiled CURRENT from /usr/src which is "master-n282659-7f39d05b67ae" (as the sibling box which
is runnig great by the way, but different CPU and smaller RAID, but also system SSD based on
UFS filesystem, same HBA. So CURRENT seem to operate in general on similar hardware.

After the second reboot with the old kernel the box in question went into debugger, rebooting
in single user mode and performing fsck -fy revealed a lot of repairs on the first partitions,
/, /var, /usr. After a reboot I realized that most services now are broken - jails do not
start, sshd doesn't start and the whole system is going into multiuser, but seems to have
serious problems.

uname -a remains empty
cd /usr/src; make buildworld returns immediately empty, no further action 
service ldconfig start also returns complete empty on console

Several onboard/base tools simply return nothing.

trying "/resucue/sh" (install date indicates 20th of December, so it is the latest ) seems to
give me the first indication of something has terribly gone wrong or even /rescue/vi (to edit
loader to change to boot.old):

elf_load_section: truncated ELF file
Abort trap

Checking /boot/kernel, /lib, /usr/lib, /bin or /sbin seems to be intakt (as far as I can
check, all timestamps are 20th Dec 2025, 9:48 UTC).

Well, since this is not the first time I ran into some problems using CURRENT, the outage due
to two lost ZFS drives after the recent chenges seems worthy to make some note here.

The other question would be how to fix: one strategy would be to boot from an official image
from flash drive and try to perform a "make installkernel installworld". Maybe there is
another way idicativ to that what I described above ...

Thanks in advance,

oh


-- 

A FreeBSD user

[-- Attachment #2 --]
-----BEGIN PGP SIGNATURE-----

iHUEARYKAB0WIQRQheDybVktG5eW/1Kxzvs8OqokrwUCaUagfAAKCRCxzvs8Oqok
r/46AP9kSnXi6ECG3rJmy5m3HKu1S+oTGYnRPG4SVulW0eMf6gEAyq01BXtGL+KA
DuFkudIkuFdd35fsMED/fzxszABbGAQ=
=3BUi
-----END PGP SIGNATURE-----
help

Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20251220141124.1606aa7c>