From nobody Mon Jul 17 12:31:35 2023 X-Original-To: freebsd-fs@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 4R4M016N13z4n08F for ; Mon, 17 Jul 2023 12:31:45 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from smtp.digiware.nl (smtp.digiware.nl [176.74.240.9]) (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 4R4M015XqFz3vw9 for ; Mon, 17 Jul 2023 12:31:45 +0000 (UTC) (envelope-from wjw@digiware.nl) Authentication-Results: mx1.freebsd.org; none Received: from router10g.digiware.nl (localhost.digiware.nl [127.0.0.1]) by smtp.digiware.nl (Postfix) with ESMTP id 260C08B796; Mon, 17 Jul 2023 14:31:44 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=digiware.nl; s=medusa-2017; t=1689597104; bh=y1xyGma6rNQ/E7qm5F0KSHQRcnQBT725Qme5fFz2d60=; h=Date:Subject:To:Cc:References:From:In-Reply-To; b=sWW5jy5i/wtE5qhbmNuBTzGfiBTcsYeiEaOAF60QE1sm033f/B1j6ziuTKJcAGMiC sWKK/uEVtNAom1258engrcyjIhXKxykot1nXIgNGCui7bSF1fpjapuiGGFZw/rAb8K XC7wxeJrCbeXyCOgatG9SGeQV1Aaoje+EWfLYXOTd/5GQ3O+RE15xdFlo0uYfSPGPI 0/zzYGrWZpsyZboDGqQrL04bEe7P6TvUIFmcTGX6qPJ3MaTgGTzxa/LRG2uk9PTQhs e/CxV6XVE+qOXWzElJXtg9WoDStw09dkVeQvG86V9uB7EngZ/VvJRhvRsURd6TrrWh AqmxO8rNKCY5A== X-Virus-Scanned: amavisd-new at digiware.nl Received: from smtp.digiware.nl ([127.0.0.1]) by router10g.digiware.nl (router10g.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sd7V_z1jbd3m; Mon, 17 Jul 2023 14:31:42 +0200 (CEST) Received: from [192.168.10.76] (winrack [192.168.10.76]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by smtp.digiware.nl (Postfix) with ESMTPSA id 7E9768B90D; Mon, 17 Jul 2023 14:31:42 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=digiware.nl; s=medusa-2017; t=1689597102; bh=y1xyGma6rNQ/E7qm5F0KSHQRcnQBT725Qme5fFz2d60=; h=Date:Subject:To:Cc:References:From:In-Reply-To; b=NjP49DE+t58o63SSsnPD07ViAM/LESCBxHkdb6Z5dZW/tpmcXgP7qxnc9QU9eH+vn DJoYktNG2bJ1gtd92KBsJGEmwCSF5etAGtOE6i7fCVzD1pmf7FG6vxIBHQ62e/4RC3 UyJbb+wH1pKhhzqE/8Q89rcyX99HG//5aRlnsjxyDuTmZyhXQiYel4Ve5SoDC+96ZI +kKnkvKvn+itnfvpdqwSoBWQv7ZFyLIG+vbi2LV+27GbRYqqUmoSciIi9xbwGXxrlR nDq3ted8m+AVwA0nayFQW7WL7VniUj+IAPb8no8c9ESTbeZy8I9EsOmSm/lT/2fYda p0LLxh4wFkGpg== Message-ID: <15b852ec-cf95-9203-4a5f-763d1c2b9ba1@digiware.nl> Date: Mon, 17 Jul 2023 14:31:35 +0200 List-Id: Filesystems List-Archive: https://lists.freebsd.org/archives/freebsd-fs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-fs@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Firefox/102.0 Thunderbird/102.13.0 Subject: Re: Having a disk double listes in a zraid3 pool Content-Language: nl To: Julien Cigar Cc: FreeBSD Filesystems References: <82861471-8c7d-a1e0-14aa-9a4e57901af0@digiware.nl> From: Willem Jan Withagen In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4R4M015XqFz3vw9 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:28878, ipnet:176.74.224.0/19, country:NL] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On 17-7-2023 14:10, Julien Cigar wrote: > On Mon, Jul 17, 2023 at 01:59:32PM +0200, Willem Jan Withagen wrote: >> Hi, >> >> I admit it is on Linux, but still hope to find the answer here... >> >> When Replacing a broken disk I ended up with 2 times the same disk > How did you replace the broken disk? > > The correct way is to issue 1) zpool offline, 2) replace physical disk and > 3) gpart backup good_disk|gpart restore -F new_disk 4) zpool replace > > Also, don't forget to boot code on the EFI partition It was a bit more convoluted since it is a disk on an LSI 3108 in jbod mode. So I needed to set JBOD on the disk and reboot. But yes, I first offlined the disk. And after reboot replaced the disk. --WjW > >> and thus the zraid is in DEGRADED state: >> pool: zfs-data >> state: DEGRADED >> status: One or more devices has experienced an unrecoverable error. An >> attempt was made to correct the error. Applications are unaffected. >> action: Determine if the device needs to be replaced, and clear the errors >> using 'zpool clear' or replace the device with 'zpool replace'. >> see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-9P >> scan: resilvered 1.09G in 00:01:10 with 0 errors on Mon Jul 17 13:36:10 >> 2023 >> config: >> >> NAME STATE READ WRITE CKSUM >> zfs-data DEGRADED 0 0 0 >> raidz3-0 DEGRADED 0 0 0 >> sdb ONLINE 0 0 0 >> sdd ONLINE 0 0 0 >> sde ONLINE 0 0 0 >> sdf ONLINE 0 0 0 >> sdg ONLINE 0 0 0 >> sdh ONLINE 0 0 0 >> sdi ONLINE 0 0 0 >> sdj ONLINE 0 0 0 >> sdk ONLINE 0 0 0 >> sdl OFFLINE 0 0 0 >> sdl ONLINE 0 0 0 >> raidz3-1 ONLINE 0 0 0 >> sdm ONLINE 0 0 0 >> sdn ONLINE 0 0 0 >> sdo ONLINE 0 0 0 >> sdq ONLINE 0 0 5 >> sdp ONLINE 0 0 5 >> sdr ONLINE 0 0 0 >> sds ONLINE 0 0 0 >> sdt ONLINE 0 0 0 >> sdu ONLINE 0 0 0 >> sdv ONLINE 0 0 0 >> sdw ONLINE 0 0 0 >> sdx ONLINE 0 0 0 >> >> errors: No known data errors >> >> Any idea how to fix this? >> >> Regards, >> --WjW >>