From nobody Wed Jan 29 16:11:40 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 4YjnGf3Pwtz5lV07 for ; Wed, 29 Jan 2025 16:11:54 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-ed1-f41.google.com (mail-ed1-f41.google.com [209.85.208.41]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4YjnGf1j3wz3cf9 for ; Wed, 29 Jan 2025 16:11:54 +0000 (UTC) (envelope-from asomers@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ed1-f41.google.com with SMTP id 4fb4d7f45d1cf-5d3e6274015so12997573a12.0 for ; Wed, 29 Jan 2025 08:11:54 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1738167112; x=1738771912; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=FVI1lP2nYFc7GITLlvknp3warcpAnXjg9LXWT984QMk=; b=jXOAXGDYgz9g7/DLJa62uqUe+1Bz3/W2ZCA2mIpX8VpnbJuJPgJUODMyKQ6J0or5xS yxwoXX4MtriZTWAzLASFNHM5BLUHlPp4pqflHF7Kc/tkQwwh3SorpfW/8JYE/gnTGtr1 as+e3OgMur6br9/LWSavRE+LsYSsuGxy6jfyeEgzeXl+kjsWrp4Hadkbb83OQin8idOt RRqS1ZZ9uijGzEs1Y5yQqxPsOusf1rdGui13q7Ik22YYfwhK5AIn2T8f2Xyo26jHeJDz 1XE677wiCykuz9UsoVX7fIbWPB8mGRUIfZY4GGfuiS51B3Um7mMv/Idgn4yeIPGXhTD9 qoqw== X-Gm-Message-State: AOJu0YxFBxoJogKW+vHaGbiEi6xN6Fgp8Mqgjvv5j7a2Sx5+wHYdnsIL FxqKWldHBU/GvO6zw2ti+eD8rIrLgnp020CBERzJ+dBIzFQCpJTxZni8a+umf4HP/7oL7CKD0Ss AP4Uzb3965rXl7++XCetk8q2nq5kENA== X-Gm-Gg: ASbGncsvRtHFA86i8eefiPl5oD565/gbEwiTbys68CItS/ZYPmtmaP/CRZ+VQJbk8/x z5sW72c2y8AasMe2R7cv/F+f3S3WbbTCAGD0dooLy3XZvQV8Yi4j+Yw3XpzsUkLpFHCLBsrETxi QPMICgU0g= X-Google-Smtp-Source: AGHT+IFZUA8SonVHSIgemIfSB7rAc6rIb2ABuG/IDI2KaPq3a+dcqNWDmXs64s55pFlI6oxkZM5kM8HSayfLCIgrLu4= X-Received: by 2002:a05:6402:34c8:b0:5d4:1ac2:271b with SMTP id 4fb4d7f45d1cf-5dc5efc09acmr4166932a12.11.1738167112009; Wed, 29 Jan 2025 08:11:52 -0800 (PST) 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 References: <20250129112701.0c4a3236@freyja> In-Reply-To: <20250129112701.0c4a3236@freyja> From: Alan Somers Date: Wed, 29 Jan 2025 09:11:40 -0700 X-Gm-Features: AWEUYZlQxws04C-T637ftjevpDDwbbdUx0seerw23QFj_MVwdp_JKOEdYiZd8XM Message-ID: Subject: Re: ZFS: Rescue FAULTED Pool To: FreeBSD User Cc: freebsd-current@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4YjnGf1j3wz3cf9 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:15169, ipnet:209.85.128.0/17, country:US] On Wed, Jan 29, 2025 at 3:27=E2=80=AFAM FreeBSD User wrote: > > Hello, > > a ZFS pool (RAINDZ(1)) has been faulted. The pool is not importable > anymore. neither with import -F/-f. > Although this pool is on an experimental system (no backup available) > it contains some data to reconstruct them would take a while, so I'd > like to ask whether there is a way to try to "de-fault" such a pool. > > The pool is comprised from 7 drives as a RAIDZ1, one of the SSDs > faulted but I pulled the wrong one, so the pool ran into suspended > state. > The host is running the lates Xigmanas BETA, which is effectively > FreeBSD 14.1-p2, just for the record. > > I do not want to give up, since I hoped there might be a rude but > effective way to restore the pool even under datalosses ... > > Thanks in advance, > > Oliver Reinserting the wrongly pulled SSD and rebooting should be sufficient. Have you not yet tried that? If you really can't reboot for some reason, you could try "zpool clear". However, the only time I tried that to fix a suspended pool it resulted in some data corruption. So I recommend rebooting instead.