Re: Unable to replace drive in raidz1
- Reply: Chris Ross : "Re: Unable to replace drive in raidz1"
- Reply: Wes Morgan : "Re: Unable to replace drive in raidz1"
- In reply to: Alan Somers : "Re: Unable to replace drive in raidz1"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Fri, 06 Sep 2024 18:21:06 UTC
> On Sep 6, 2024, at 14:08, mike tancsa <mike@sentex.net> wrote:
>
> On 9/6/2024 2:06 PM, Chris Ross wrote:
>> How can I map the diskid’s listed to the underlying device?either by serial number or da#…
>>
> What does
> glabel status
That shows labels for many drives, though not da1 and da2, the
remaining members of zraid1-0. Intersting. But, I hope the below
Is the fix...
> On Sep 6, 2024, at 14:10, Alan Somers <asomers@freebsd.org> wrote:
>
> Ahh, this means that there are two different vdevs that can be
> described by "da3". You can still refer to them unambiguously by guid
> though. Do "zpool status -g" to find the guid of the disk that you
> want to replace, and then do "zpool replace <GUID> /dev/da10”
Ahh, okay. That makes sense. I have ever only known how to replace things
using the key that "zpool status” shows. Thanks for that!
Oh. Trying, that doesn’t work either. :-/
NAME STATE READ WRITE CKSUM
tank DEGRADED 0 0 0
16506780107187041124 DEGRADED 0 0 0
9127016430593660128 FAULTED 0 0 0 external device fault
4094297345166589692 ONLINE 0 0 0
17850258180603290288 ONLINE 0 0 0
[…]
% sudo zpool replace tank 9127016430593660128 /dev/da10
cannot replace 9127016430593660128 with /dev/da10: already in replacing/spare config; wait for completion or use 'zpool detach’
% 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.
- Chris