From nobody Tue Apr 16 01:50:29 2024 X-Original-To: freebsd-stable@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 4VJRnj3Yssz5HWcH for ; Tue, 16 Apr 2024 01:50:33 +0000 (UTC) (envelope-from henrichhartzer@tuta.io) Received: from w1.tutanota.de (w1.tutanota.de [81.3.6.162]) (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-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mail.tutanota.de", Issuer "Sectigo RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4VJRnh3yC9z4CLw for ; Tue, 16 Apr 2024 01:50:32 +0000 (UTC) (envelope-from henrichhartzer@tuta.io) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=tuta.io header.s=s1 header.b=XaIotSOP; dmarc=pass (policy=quarantine) header.from=tuta.io; spf=pass (mx1.freebsd.org: domain of henrichhartzer@tuta.io designates 81.3.6.162 as permitted sender) smtp.mailfrom=henrichhartzer@tuta.io Received: from tutadb.w10.tutanota.de (unknown [192.168.1.10]) by w1.tutanota.de (Postfix) with ESMTP id 10022FBFAA9 for ; Tue, 16 Apr 2024 01:50:30 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1713232229; s=s1; d=tuta.io; h=From:From:To:To:Subject:Subject:Content-Description:Content-ID:Content-Type:Content-Type:Content-Transfer-Encoding:Content-Transfer-Encoding:Cc:Date:Date:In-Reply-To:In-Reply-To:MIME-Version:MIME-Version:Message-ID:Message-ID:Reply-To:References:References:Sender; bh=TyUTW8m7A5ZelbxPLLfsoTCIKPLVzTZdTgLinoaknCA=; b=XaIotSOPWRoJ4WrReZyzPSv3sk/wsieBjALM3WqkpuNKEolyvO0ESCtALQMuRP8m ApTwZkVjmRXRLrhZD7XMJTjOZDJNqmAQsNHAkglwNP7uyc6cLxHmtRNaV08ycSlY46l S/H2QN5k4eBXq+gUF23yLRTjbIgOSvlrHKEKmvniDHg+F0Fqv8rkdKBfq5bD19QzIcO 3XN+P3NdxFELZyuJ7V8Eqj6GYaLadVgHcZmDlOSDf+c2IPPNILf+EjyauuhO71Oj2+c TLuOPtQV4sZBjZyv/CRjPIwNOQjgoimOYrr8ZuQm81pEuNn9mal5ImLU35Ow2BmMzYp mPu6DrXCGA== Date: Tue, 16 Apr 2024 03:50:29 +0200 (CEST) From: henrichhartzer@tuta.io To: Freebsd Stable Message-ID: In-Reply-To: References: Subject: zroot on 14.0-RELEASE quickly becomes unreadable by the boot loader List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.08 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.98)[-0.985]; DMARC_POLICY_ALLOW(-0.50)[tuta.io,quarantine]; R_SPF_ALLOW(-0.20)[+ip4:81.3.6.160/28]; R_DKIM_ALLOW(-0.20)[tuta.io:s=s1]; RWL_MAILSPIKE_VERYGOOD(-0.20)[81.3.6.162:from]; MIME_GOOD(-0.10)[text/plain]; ONCE_RECEIVED(0.10)[]; FROM_NO_DN(0.00)[]; ASN(0.00)[asn:24679, ipnet:81.3.0.0/18, country:DE]; MIME_TRACE(0.00)[0:+]; RCVD_COUNT_ONE(0.00)[1]; MISSING_XM_UA(0.00)[]; ARC_NA(0.00)[]; TO_DN_ALL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MLMMJ_DEST(0.00)[freebsd-stable@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-stable@freebsd.org]; MID_RHS_MATCH_FROM(0.00)[]; DKIM_TRACE(0.00)[tuta.io:+] X-Rspamd-Queue-Id: 4VJRnh3yC9z4CLw Hi everyone, I had previous thread titled: Can't find bootable partition I also have a forum thread for this, but it's slow going as my account is not yet verified and each post requires approval: https://forums.freebsd.org/threads/14-0-stopped-booting-mysteriously-zfs-mirror.93101/ Here's what I had to do to produce a non-booting system: Details: 14.0-RELEASE x86_64 2x 16TB harddrives ZFS mirror installed with GPT UEFI. "Automatic" ZFS install. 8GB RAM Hardware has ECC and passed memtest. Fully updated with freebsd-update. Intel S1260 Atom (non-speculative execution processor) After writing over 1TB of random data to the filesystem and pressing the reset button on the server, (a regular reboot might've been sufficient as well, but not sure) it booted but the boot loader had "zio_read error: 5" errors plastering over top of the menu. It still booted, nonetheless. After that successful boot, I rebooted and the boot loader failed quickly, dumping me into a UEFI shell. I've had at least two similar failures like this already. I don't suspect a full 1TB written is required to cause it. BIOS boot, from a previous install, also did not appear to work. I also don't suspcet that patches, or lack of patches, influences the issue. It's *possible* that somehow hardware is to blame, but while running the server has had no instability or odd behaviors. I've done make kernel and make world without incident. I've rsynced several TB without issue as well. Whenever this happens, I can zpool import zroot from the installer and zpool shows no errors. And smartctl shows no errors (this is the third pair of drives I've had this happen with). I've yet to have a zpool scrub come back with errors. Has anyone else had any issues like this? It's very perplexing and concerning. Thank you! -Henrich