From nobody Mon Jan 02 05:35:33 2023 X-Original-To: questions@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 4Nll2N00Tkz2p0BP for ; Mon, 2 Jan 2023 05:35:40 +0000 (UTC) (envelope-from sysadmin.lists@mailfence.com) Received: from wilbur.contactoffice.com (wilbur.contactoffice.com [212.3.242.68]) (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 4Nll2L2118z3J5k for ; Mon, 2 Jan 2023 05:35:37 +0000 (UTC) (envelope-from sysadmin.lists@mailfence.com) Authentication-Results: mx1.freebsd.org; dkim=fail ("body hash did not verify") header.d=mailfence.com header.s=20210208-e7xh header.b=TeavoOLD; spf=pass (mx1.freebsd.org: domain of sysadmin.lists@mailfence.com designates 212.3.242.68 as permitted sender) smtp.mailfrom=sysadmin.lists@mailfence.com; dmarc=pass (policy=quarantine) header.from=mailfence.com Received: from fidget.co-bxl (fidget.co-bxl [10.2.0.33]) by wilbur.contactoffice.com (Postfix) with ESMTP id 705241498; Mon, 2 Jan 2023 06:35:35 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1672637735; s=20210208-e7xh; d=mailfence.com; i=sysadmin.lists@mailfence.com; h=Date:From:To:Message-ID:In-Reply-To:References:Subject:MIME-Version:Content-Type:Content-Transfer-Encoding:Cc; l=1416; bh=Cezlw3pPOWhpuL5CDtwS3QA7o1S1zYXvIiXZQ3IWNr0=; b=TeavoOLDwLmBHb+aWbdt/pTcs+4zDaT7AptyBK2skT2ADZrZMTQ8gLPIZnTCysWz P7nCYgN1EMquQSoB1vlJ7byC+60qtNXckX/c6AZTJ7H4OFKxFFwoEBvWm21zK7KK4Xg 8sB2O69nA8H7eUe8naSlmYHoZ8Dff+FG8PtguSKNNHrcIbOGscx33dbtttlWEh+k3nd RszoATrQyDk5/YXTOA6dWqbZxzRoQb6p+dtl2tO95zo2oSNmQB+0EHJsz9Xc6kFysFp bS3VU6tx5iAxJatcztks+QjwtVlN9WMdh/SgZ13HMKf0a7qUxgSX6+ojpn8H+x6kFw5 pWWkRiK//w== Date: Mon, 2 Jan 2023 06:35:33 +0100 (CET) From: Sysadmin Lists To: questions@freebsd.org Message-ID: <1473452120.791291.1672637733468@fidget.co-bxl> In-Reply-To: References: <0ddaa537-ffa9-af0d-1a5a-1874a67ed2b5@netfence.it> <5def1695-82b3-3441-c11a-d64ca0c7c30a@netfence.it> <255658040.26515.1669699637761@orville.co-bxl> <47265e09-3aa0-24fa-22cb-56e09bb524f0@netfence.it> <597333482.1125294.1669791240602@ichabod.co-bxl> <2d897f57-5bdc-7497-d374-e7a536d9a440@netfence.it> <905137278.91788.1669965304646@fidget.co-bxl> Subject: Re: ZFS Permanent error <0xffffffffffffffff>:<0x0> List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Andrea Venturoli X-Mailer: ContactOffice Mail X-ContactOffice-Account: com:312482426 X-Spamd-Result: default: False [-3.89 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; DMARC_POLICY_ALLOW_WITH_FAILURES(-0.50)[]; R_SPF_ALLOW(-0.20)[+ip4:212.3.242.64/26]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[212.3.242.68:from]; XM_UA_NO_VERSION(0.01)[]; ASN(0.00)[asn:10753, ipnet:212.3.242.64/26, country:US]; MLMMJ_DEST(0.00)[questions@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+]; DKIM_TRACE(0.00)[mailfence.com:-]; RCPT_COUNT_TWO(0.00)[2]; TO_DN_SOME(0.00)[]; FROM_HAS_DN(0.00)[]; DMARC_POLICY_ALLOW(0.00)[mailfence.com,quarantine]; R_DKIM_REJECT(0.00)[mailfence.com:s=20210208-e7xh]; RCVD_COUNT_TWO(0.00)[2]; TO_MATCH_ENVRCPT_SOME(0.00)[]; ARC_NA(0.00)[] X-Rspamd-Queue-Id: 4Nll2L2118z3J5k X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N > ---------------------------------------- > From: Andrea Venturoli > Sent: Sat Dec 31 11:41:39 CET 2022 > To: > Subject: Re: ZFS Permanent error <0xffffffffffffffff>:<0x0> > > The RAM alas... just removed a faulty module. > So I hope I don't get any more troubles, even if I don't know how to > clear/fix the old one. > Recreating the pool is what ultimately cleared it for me: Attached a backup disk, booted into a livecd, took a recursive snapshot of zroot, sent it to the backup disk, destroyed the old pool, recreated it, sent the backed-up datasets to the old disk. I initially did the waiting game like you, but then started getting CAM errors that made the system unusable. I tried refreshing the disk, but that didn't help: dd if=/dev/ada0p3 of=/dev/ada0p3 bs=1m The ZFS metadata errors vanished after recreating the pool. It's about an hour-long project. A recursive snapshot of zroot sends everything over with a single command: livecd# zfs send -vR zroot@migration | zfs recv -vFud new_zroot And then back again after recreating the pool: livecd# zfs send -vR new_zroot@migration | zfs recv -vFud zroot Just have to make sure you're using a livecd with a ZFS version that's equal or newer. After all the hassle, I did contemplate setting up a mirror raid. -- Sent with https://mailfence.com Secure and private email