SOLVED Unable to Replace Faulted Drive

[dakotta]

One of the mirrors in my zpool is degraded because of a faulty drive.

1. According to this section of the manual, I changed the status of the faulted drive to "Offline".
2. I powered down the server and replaced the problem drive with a like-for-like exchange.
3. I booted up the server, selected the OFFLINE drive and selected "Replace".
4. However, the popup window does not allow me to select the "member disk", because the dropdown list is empty. (Even after rebooting.)

Code:

tank

__MIRROR
____da1p2
____/dev/gptid/77e8fb8b-f72b-11eb-a7fa-3417ebecd9d8

__MIRROR
____da2p2
____da3p2

/dev/gptid/77e8fb8b-f72b-11eb-a7fa-3417ebecd9d8 was the id of the faulted drive, not the newly-installed drive. According to smartctl, the device is recognized by the system.

Code:

sudo smartctl /dev/da0
-------------------------------------------------------------------------------
=== START OF INFORMATION SECTION ===
Model Family:     Seagate Barracuda 7200.12
Device Model:     ST3500418AS
Serial Number:    9VM0HNL4
LU WWN Device Id: 5 000c50 014dd723a
Firmware Version: CC44
User Capacity:    500,107,862,016 bytes [500 GB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    7200 rpm
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS T13/1699-D revision 4
SATA Version is:  SATA 2.6, 3.0 Gb/s
Local Time is:    Sat May 28 15:41:44 2022 PDT

How do I get this drive to show up in the GUI so I can continue the disk replacement?

Cheers,

 

[dakotta]

Can I replace the drive using the command line?

I will be visiting the site this week and I'd like to get the drive replaced.

Cheers,

 

[Samuel Tai]

This is in the Release Notes for 13. This is a bug with the 13 GUI, and there's a CLI work-around.

 

[dakotta]

Thanks Samuel!

I'm not 100% sure that system is running ver 13.0. (It could still be using 12.0-U5.)

As I understand the release notes, the method described should only be used for ver 13.0. Correct? So, if I'm still running 12.0-U5, I should upgrade to ver 13.0 then follow the method in the release notes to replace the faulted drive?

Cheers,

 

[dakotta]

I was onsite today and confirmed that the server was running ver 12.0-U5.

Rather than upgrade directly to 13.0, I decided to upgrade to ver 12.0-U8.1 and reboot.

After that, the GUI started working again and I was able to complete steps 1-4 in my original post.

Cheers,