From nobody Fri Sep 06 18:39:24 2024 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 4X0lQ25XG4z5VSvb for ; Fri, 06 Sep 2024 18:39:38 +0000 (UTC) (envelope-from morganw@gmail.com) Received: from mail-yw1-x112a.google.com (mail-yw1-x112a.google.com [IPv6:2607:f8b0:4864:20::112a]) (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 4X0lQ13TTtz4gWL for ; Fri, 6 Sep 2024 18:39:37 +0000 (UTC) (envelope-from morganw@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20230601 header.b=AY0FLU3R; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of morganw@gmail.com designates 2607:f8b0:4864:20::112a as permitted sender) smtp.mailfrom=morganw@gmail.com Received: by mail-yw1-x112a.google.com with SMTP id 00721157ae682-699ac6dbf24so21156597b3.3 for ; Fri, 06 Sep 2024 11:39:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1725647976; x=1726252776; darn=freebsd.org; h=content-transfer-encoding:mime-version:message-id:references :in-reply-to:user-agent:subject:to:from:date:from:to:cc:subject:date :message-id:reply-to; bh=aBzhViiCZwByufrm2wgneGHNauaAwpmiF9/bep+2qfw=; b=AY0FLU3RktYrcO9uNqgxEuwozSuvkGdm8VeIcVXzVnyxfykmyhX033AfcXxLyrqOaW QD5HVgYE5FylmoAVMmsg90TDcdYZhEBSeQ/eK+FRBHdWDk6TTTY4x9u3pwYO818ogPFP tbydwttPH0+7QAMsEzCPjSEYHIpa/Vq5T9Fy0Q1J8/D+YBnE5x7vcUCceKjWI2mCCXsK NlEgMG1YmD+ebAXWLtZOMD6xZCdcJkFO8kVXO/fBgTHeiCyofPfq6rBQsLn7LBt+/V0N BI7/9acmMg8kj3UzRQ0D3ScVVOTymwP6lRH3PnggnA2xcGk8VmX3uvBuX0NdsTrjGw/6 kzrA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1725647976; x=1726252776; h=content-transfer-encoding:mime-version:message-id:references :in-reply-to:user-agent:subject:to:from:date:x-gm-message-state:from :to:cc:subject:date:message-id:reply-to; bh=aBzhViiCZwByufrm2wgneGHNauaAwpmiF9/bep+2qfw=; b=E/4VWApcmc3+3qfITrkOlkZUBcmUZy4bDVcXHk4grNY9P0SgHroW8hGIFy92UwT9mn +wrkzwW6bA7mylRsOcXbM8wE/U4x788l2ubVUtBZ4sOgKyRtv7UGF9i3/RZz/j6F2IxB 4ENHrl3ADe58XNwsviwo67PsyJpi5ew6wxDrv3b13E5FX9O7dJPrHp0m2IFuAbTBOMPT nZom7AAvWXvmSvRgzQ3joAUAGr2WqcR0xClRhifMnfjI9IZBO4OChnTy1aL5Ij0fxEaE OBZcUyvj2aRsxb0PZmzV+Qa2lMYBa2o8w/3gIK/4CPsGSlhvZBzXQFZieQbEcU18TUdx l2/g== X-Gm-Message-State: AOJu0YwXT+ZRMsP6xkyIivQoJhycAXU33E0hXxnBuo/NTKfHaq/2x+4l 89a1D/hMjn8J/bxM9jux2h2mh42ZV5JQqtBvRB0JR4l9bAo8Zs90XFBfgsPk X-Google-Smtp-Source: AGHT+IGWhbLUKN3IWoT7P9YXNe5XrqT4+7F9V/sOlEwZidiJ6L+EhXH7Wv5n/HK2L6vbHJOk4QqHlg== X-Received: by 2002:a05:690c:438e:b0:672:e49d:430e with SMTP id 00721157ae682-6db44dc5400mr29536337b3.15.1725647975991; Fri, 06 Sep 2024 11:39:35 -0700 (PDT) Received: from ?IPv6:::1? ([2600:381:642f:e2a:d8f2:e3e8:b579:a70b]) by smtp.gmail.com with ESMTPSA id 00721157ae682-6db56337c15sm934087b3.43.2024.09.06.11.39.34 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 06 Sep 2024 11:39:35 -0700 (PDT) Date: Fri, 06 Sep 2024 13:39:24 -0500 From: Wes Morgan To: freebsd-fs@freebsd.org Subject: Re: Unable to replace drive in raidz1 User-Agent: K-9 Mail for Android In-Reply-To: <29003A7C-745D-4A06-8558-AE64310813EA@distal.com> References: <5ED5CB56-2E2A-4D83-8CDA-6D6A0719ED19@distal.com> <6A20ABDA-9BEA-4526-94C1-5768AA564C13@distal.com> <0CF1E2D7-6C82-4A8B-82C3-A5BF1ED939CF@distal.com> <29003A7C-745D-4A06-8558-AE64310813EA@distal.com> Message-ID: <42346193-AD06-4D26-B0C6-4392953D21A3@gmail.com> 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 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.92 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.92)[-0.921]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20230601]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; RCPT_COUNT_ONE(0.00)[1]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; FREEMAIL_FROM(0.00)[gmail.com]; FROM_HAS_DN(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FREEMAIL_ENVFROM(0.00)[gmail.com]; TO_DN_NONE(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; PREVIOUSLY_DELIVERED(0.00)[freebsd-fs@freebsd.org]; MID_RHS_MATCH_FROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-fs@freebsd.org]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::112a:from] X-Rspamd-Queue-Id: 4X0lQ13TTtz4gWL On September 6, 2024 1:21:06 PM CDT, Chris Ross wrote: > >> On Sep 6, 2024, at 14:08, mike tancsa wrote: >>=20 >> On 9/6/2024 2:06 PM, Chris Ross wrote: >>> How can I map the diskid=E2=80=99s listed to the underlying device?eit= her by serial number or da#=E2=80=A6 >>>=20 >> What does=20 >> glabel status > >That shows labels for many drives, though not da1 and da2, the >remaining members of zraid1-0=2E Intersting=2E But, I hope the below >Is the fix=2E=2E=2E > >> On Sep 6, 2024, at 14:10, Alan Somers wrote: >>=20 >> Ahh, this means that there are two different vdevs that can be >> described by "da3"=2E You can still refer to them unambiguously by gui= d >> though=2E Do "zpool status -g" to find the guid of the disk that you >> want to replace, and then do "zpool replace /dev/da10=E2=80=9D > > >Ahh, okay=2E That makes sense=2E I have ever only known how to replace = things >using the key that "zpool status=E2=80=9D shows=2E Thanks for that! > >Oh=2E Trying, that doesn=E2=80=99t work either=2E :-/ > >NAME STATE READ WRITE CKSUM >tank DEGRADED 0 0 0 > 16506780107187041124 DEGRADED 0 0 0 > 9127016430593660128 FAULTED 0 0 0 external device faul= t > 4094297345166589692 ONLINE 0 0 0 > 17850258180603290288 ONLINE 0 0 0 >[=E2=80=A6] >% sudo zpool replace tank 9127016430593660128 /dev/da10 >cannot replace 9127016430593660128 with /dev/da10: already in replacing/s= pare config; wait for completion or use 'zpool detach=E2=80=99 >% sudo zpool replace tank 9127016430593660128 diskid/DISK-ZGG0A2PA >cannot replace 9127016430593660128 with diskid/DISK-ZGG0A2PA: already in = replacing/spare config; wait for completion or use 'zpool detach' > >Tried with /dev/da10, and the diskid for da10 reported by glabel status= =2E > > - Chris > You should make the changes to your /boot/loader=2Econf as suggested earli= er by Freddie Cash and reboot=2E This will eliminate all the confusion with= diskid=2E Then run "zpool clear", which, if da3 is still online and not co= mpletely dead, the pool should come out of the faulted state=2E Check zpool= status to look for this alleged replacement in progress=2E If it is truly = trying to replace a device, it should show up in zpool status with the actu= al device, or the guid if it can't find the device=2E If you have initiated a replace, and the replacing disk has now been "lost= " or unlabeled, you are in a bind=2E I ran into this problem many years ago= , and I thought it was fixed, but the bug was called something like "can't = replace a replacing vdev"=2E I ultimately solved my problem by manually edi= ting a fake vdev to have the same guid as the missing device, restarting th= e replace and then canceling it before zfs realized it was fake=2E But, I a= m almost certain that zpool cancel can do this now, with the guid=2E If da10 has a label that says it is in the pool, it is probably the "repla= cing" vdev and should be picked up=2E=2E=2E