From nobody Thu Jan 30 12:19:23 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 4YkJ4H2zGKz5mD36 for ; Thu, 30 Jan 2025 12:19:43 +0000 (UTC) (envelope-from pmh@hausen.com) Received: from mail2.pluspunkthosting.de (mail2.pluspunkthosting.de [217.29.33.228]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4YkJ4H0hldz3w7T for ; Thu, 30 Jan 2025 12:19:42 +0000 (UTC) (envelope-from pmh@hausen.com) Authentication-Results: mx1.freebsd.org; none Received: from smtpclient.apple (87.138.185.145) by mail2.pluspunkthosting.de (Axigen) with (ECDHE-RSA-AES256-GCM-SHA384 encrypted) ESMTPSA id 254289; Thu, 30 Jan 2025 13:19:34 +0100 Content-Type: text/plain; charset=us-ascii 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 (Mac OS X Mail 16.0 \(3776.700.51\)) Subject: Re: ZFS: Rescue FAULTED Pool From: "Patrick M. Hausen" In-Reply-To: <20250130123354.2d767c7c@thor.sb211.local> Date: Thu, 30 Jan 2025 13:19:23 +0100 Cc: David Wolfskill , freebsd-current@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <20250129112701.0c4a3236@freyja> <20250130123354.2d767c7c@thor.sb211.local> To: A FreeBSD User X-Mailer: Apple Mail (2.3776.700.51) X-Rspamd-Queue-Id: 4YkJ4H0hldz3w7T X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:16188, ipnet:217.29.32.0/20, country:DE] Hi all, > Am 30.01.2025 um 12:35 schrieb A FreeBSD User = : > Well, in this case I do not use dedicated ZIL drives. I also made = several experiences with > "single" ZIL drive setups, but a dedicated ZIL is mostly useful in = cases were you have > graveyard full of inertia-suffering, mass-spinning HDDs - if I'm right = the concept of SSD > based ZIL would be of no use/effect in that case. So I ommited tose. Dedidated SLOG vdevs only make sense if your workload involves = synchronous writes like when running databases or VM virtual disks over NFS or iSCSI. > Every single SSD originally plugged in is now back in place, even the = faulted one (which > doesn't report any faults at the moment). >=20 > Although the pool isn't "importable", zdb reports its existence, = amongst zroot (which resides > on a dedicated drive). There a various things yet to try, but I have no personal experience = with them: - "force" read-only import - import referencing a past transaction group, i.e. a previous version = of the entire pool How to find these transaction groups - no idea, sorry. >>> The host is running the lates Xigmanas BETA, which is effectively >>> FreeBSD 14.1-p2, just for the record. This topic including sometimes successful recovery frequently pops up on = the TrueNAS forum. Did you ask in the Xigmanas community? Weren't they able to help? I know there are regulars on the TrueNAS forum who know what to do. = Maybe head over there? As I wrote there are threads going like: "please provide the output of `zdb something someting`" *output* "now to `zpool import something something`" ... etc. HTH, Patrick=