From nobody Sat Dec 20 22:31:00 2025 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4dYfJq506sz6L8Z3 for ; Sat, 20 Dec 2025 22:31:39 +0000 (UTC) (envelope-from freebsd@walstatt-de.de) Received: from smtp6.goneo.de (smtp6.goneo.de [85.220.129.31]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4dYfJq2dttz4Q26 for ; Sat, 20 Dec 2025 22:31:39 +0000 (UTC) (envelope-from freebsd@walstatt-de.de) Authentication-Results: mx1.freebsd.org; none Received: from hub2.goneo.de (hub2.goneo.de [IPv6:2001:1640:5::8:53]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by smtp6.goneo.de (Postfix) with ESMTPS id BAD0B24074D; Sat, 20 Dec 2025 23:31:36 +0100 (CET) Received: from hub2.goneo.de (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by hub2.goneo.de (Postfix) with ESMTPS id 2ED072400D4; Sat, 20 Dec 2025 23:31:35 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=walstatt-de.de; s=DKIM001; t=1766269895; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=Df5gX7Sq2qa9JfkvUKzsPHKdCt9RY4iVA5uKROEHZq8=; b=DAZnPi2dSduA3AV43Pinw0UiuoAIHBVdGuP9eEYLJ+LGjwxLz7H8zUllwmP8pboXczGGoC 5ihiIpR+82pias9NdItGjVsb3q3Pzm70EXc9nleqTU+X1d0oQWsIvmVnCtjclDLvLSlBAI kM915yIVjUKredDw+GM/U3neEfrDtPXkzvcvNeFqlNJKrgZhPLUMs6JkG5d7f+btutmOCf SRNWG1QFTGB9lsO14vBmCLJXS4bnNAh5veIuoKuYp3rGLkhWF0sCVsj2k0O0BAJ39HsBGJ XdqsrnI74UIrRiueucsBZU+UYYMcHVo7Oc4pHyj7oUg/p6ENj7x/u31qr+LBdA== Received: from thor.sb211.local (dynamic-2a02-3100-28f8-1c02-021b-21ff-fe4e-8f4d.310.pool.telefonica.de [IPv6:2a02:3100:28f8:1c02:21b:21ff:fe4e:8f4d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (prime256v1) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by hub2.goneo.de (Postfix) with ESMTPSA id E9229240056; Sat, 20 Dec 2025 23:31:34 +0100 (CET) Date: Sat, 20 Dec 2025 23:31:00 +0100 From: A FreeBSD User To: Warner Losh Cc: FreeBSD CURRENT Subject: Re: CURRENT: havock: elf_load_section: truncated ELF file Message-ID: <20251220233127.2ad04793@thor.sb211.local> In-Reply-To: References: <20251220141124.1606aa7c@thor.sb211.local> X-Mailer: Claws Mail 3.21.0 (GTK+ 2.24.33; amd64-portbld-freebsd16.0) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_/8J=C6lbZTsPRN5i0z2n5AIR"; protocol="application/pgp-signature"; micalg=pgp-sha512 X-Rspamd-UID: 5ee145 X-Rspamd-UID: dbbae7 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:25394, ipnet:85.220.128.0/17, country:DE] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Rspamd-Queue-Id: 4dYfJq2dttz4Q26 --Sig_/8J=C6lbZTsPRN5i0z2n5AIR Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Am Tage des Herren Sat, 20 Dec 2025 08:10:59 -0700 Warner Losh schrieb: > On Sat, Dec 20, 2025 at 6:12=E2=80=AFAM A FreeBSD User > wrote: >=20 > > 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 drive= s 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 t= he > > CAM infrastructure > > (I can't find any notes on this in man cam, so I feel lost). > > =20 >=20 > Unlikely, but you can set this in the boot loader: > kern.cam.tur_timeout=3D60 > kern.cam.inquiry_timeout=3D60 > kern.cam.modesense_timeout=3D60 I'll check, thanks. Are these OIDs documented somewhere to be at hand just = in case? I searched the recent cam manpage ... >=20 > and see if that works. You should see new errors on boot if his is the > issue. Can you share a dmesg? >=20 > I kinda doubt they'd cause the issues that you've had. If disks are gone, > then there'd be different errors to what you are seeing, I'd think. >=20 > To recover, your best bet is to use a USB stick from one of the release or > snapshots. In earlier times, when "make installkernel and/or make installworld crashed= midair, some binaries in the installed tree were corrupted and since I run CURRENT which= has a tough pace at the moment, the USB image booting should be close to the CURRENT made vi= a "make world" ... I assume. I did so and had some problems with the new pkg concept ... (work= ing offline, is a problem with the install-blob.txz ...) >=20 > Warner >=20 >=20 > > 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 obvi= ous > > 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 simi= lar > > hardware. > > > > After the second reboot with the old kernel the box in question went in= to > > 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 bro= ken > > - 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 acti= on > > 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 ev= en > > /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 so= me > > note here. > > =20 >=20 > Can you provide error messages at boot for this? You talk about fsck and > about ZFS, so I'm a little confused as to your setup. No need to be confused: the CURRENT crashed/froze after two of five HDD wer= e reported as "removed" from a RAIDZ pool. The box hung forever.=20 The OS resides on a SSD with UFS. After > 30 min I had to switch off/on th= e box physically. So the UFS filesystem had a bump (journalling didn't fix it). ZFS "healed" = after reboot and checking the HDD. UFS SSD didn't ... I spent a while now to bring back everything. Boot device is now ZFS, too. = And, therefore, obvious slower but somehow save.=20 The only issue I have now is a crash after a reboot. While rebooting and ki= lling jails, the box drops into kernel debugger ... Somehow I need to copy the picture I made from the box, since the machine i= sn't connected to the net at the moment ... >=20 > Warner >=20 >=20 > > The other question would be how to fix: one strategy would be to boot f= rom > > 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 ... > > =20 >=20 >=20 >=20 >=20 > > Thanks in advance, > > > > oh > > > > > > -- > > > > A FreeBSD user > > =20 --=20 A FreeBSD user --Sig_/8J=C6lbZTsPRN5i0z2n5AIR Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iHUEARYKAB0WIQRQheDybVktG5eW/1Kxzvs8OqokrwUCaUcjvwAKCRCxzvs8Oqok r2+yAQC3BqDvqRP4NtrqKTrwXOyb2Z2RhwFVyF6lCMVVB/HCVAEAjMNla3Px2A6a 8hTrBPW3Yb2jk4CNKTW4EwgEHO8tSQE= =6xmJ -----END PGP SIGNATURE----- --Sig_/8J=C6lbZTsPRN5i0z2n5AIR--