Date: Fri, 6 Sep 2024 11:59:26 -0600 From: Alan Somers <asomers@freebsd.org> To: Chris Ross <cross+freebsd@distal.com> Cc: mike tancsa <mike@sentex.net>, FreeBSD Filesystems <freebsd-fs@freebsd.org> Subject: Re: Unable to replace drive in raidz1 Message-ID: <CAOtMX2jfcd43sBpHraWA=5e_Ka=hMD654m-5=boguPPbYXE4yw@mail.gmail.com> In-Reply-To: <6A20ABDA-9BEA-4526-94C1-5768AA564C13@distal.com> References: <5ED5CB56-2E2A-4D83-8CDA-6D6A0719ED19@distal.com> <AC67D073-D476-41F5-AC53-F671430BB493@distal.com> <CAOtMX2h52d0vtceuwcDk2dzkH-fZW32inhk-dfjLMJxetVXKYg@mail.gmail.com> <CB79EC2B-E793-4561-95E7-D1CEEEFC1D72@distal.com> <CAOtMX2i_zFYuOnEK_aVkpO_M8uJCvGYW%2BSzLn3OED4n5fKFoEA@mail.gmail.com> <6A20ABDA-9BEA-4526-94C1-5768AA564C13@distal.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Sep 6, 2024 at 11:50=E2=80=AFAM Chris Ross <cross+freebsd@distal.co= m> wrote: > > > > > On Sep 6, 2024, at 13:02, Alan Somers <asomers@freebsd.org> wrote: > > > > This looks like you got into a split-brain situation where the disks > > have inconsistent labels. Most disks think that da10 is not a member > > of the pool, but da10 thinks that it is. Perhaps you added it as a > > spare, then physically removed it, and then did a "zpool remove" to > > remove the spare from the configuration? > > I did configure it as a spare, and remove it as a spare, but I > haven=E2=80=99t moved any disks physically since the once when I > switched it in. And this problem started before I ever tried > adding da10 into the pool as a spare. > > > If you're very very very > > sure that there is no data on da10 that you care about, you can do > > "zpool labelclear -f /dev/da10=E2=80=9D > > > I am sure, and I didn=E2=80=99t even need the -f. But, no change. > > % sudo zpool labelclear /dev/da10 > Password: > > % sudo zdb -l /dev/da10 > failed to unpack label 0 > failed to unpack label 1 > failed to unpack label 2 > failed to unpack label 3 > > % sudo zpool replace tank da3 da10 > cannot replace da3 with da10: already in replacing/spare config; wait for= completion or use 'zpool detach' > > > :-( > > - Chris If there is no label on da10, and "zpool status" doesn't show any spares, then I don't know what the problem is. It's possible that /sbin/zpool is printing an incorrect error message; it's fairly notorious for that. You could try to debug it. Other wild guesses include: * maybe da3 is the disk with the out-of-date label. You could try physically removing it before doing "zpool replace" * Since exported pools can't have active spares, you could try exporting the pool and then reimporting it. -Alan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOtMX2jfcd43sBpHraWA=5e_Ka=hMD654m-5=boguPPbYXE4yw>