Faulted Drive will not go Offline

[DifferentStrokes]

I have 2 disks in my Z2 pool that are faulted. I'm trying to replace them per the TrueNAS documentation, that says to offline the disk first then replace it. However, when I trying to offline the disk nothing happens. The GUI still shows faulted. Is this normal behavior?

Below is some info that may help.


Here is the output of zpool status...

Code:

BigNASty% zpool status
  pool: WD6REDS
 state: DEGRADED
status: One or more devices are faulted in response to persistent errors.
    Sufficient replicas exist for the pool to continue functioning in a
    degraded state.
action: Replace the faulted device, or use 'zpool clear' to mark the device
    repaired.
  scan: resilvered 2.17T in 10:20:46 with 0 errors on Sat Sep 11 17:16:55 2021
config:

    NAME                                            STATE     READ WRITE CKSUM
    WD6REDS                                         DEGRADED     0     0     0
      raidz2-0                                      DEGRADED     0     0     0
        gptid/f2fc49fb-a1cd-11e4-b711-0cc47a32cf1c  ONLINE       0     0     0
        gptid/f35b1606-a1cd-11e4-b711-0cc47a32cf1c  ONLINE       0     0     0
        gptid/0d3be6b2-10eb-11ec-86f1-0cc47a32cf1c  FAULTED      0    65     5  too many errors
        gptid/f41f4c31-a1cd-11e4-b711-0cc47a32cf1c  ONLINE       0     0     0
        gptid/b89566f9-0f63-11ec-86f1-0cc47a32cf1c  FAULTED      0    81     4  too many errors
        gptid/f4d9d888-a1cd-11e4-b711-0cc47a32cf1c  ONLINE       0     0     0

errors: No known data errors

  pool: freenas-boot
 state: ONLINE
status: The pool is formatted using a legacy on-disk format.  The pool can
    still be used, but some features are unavailable.
action: Upgrade the pool using 'zpool upgrade'.  Once this is done, the
    pool will no longer be accessible on software that does not support
    feature flags.
  scan: scrub repaired 0B in 00:00:26 with 0 errors on Thu Sep  9 03:45:26 2021
config:

    NAME          STATE     READ WRITE CKSUM
    freenas-boot  ONLINE       0     0     0
      mirror-0    ONLINE       0     0     0
        ada1p2    ONLINE       0     0     0
        ada0p2    ONLINE       0     0     0

This is echoed to the console when I tell the disk to go offline...

Code:

Sep 11 17:53:33 BigNASty GEOM_ELI: Device mirror/swap1.eli destroyed.
Sep 11 17:53:33 BigNASty GEOM_MIRROR: Device swap1: provider destroyed.
Sep 11 17:53:33 BigNASty GEOM_MIRROR: Device swap1 destroyed.
Sep 11 17:53:34 BigNASty GEOM_ELI: Device mirror/swap0.eli destroyed.
Sep 11 17:53:34 BigNASty GEOM_MIRROR: Device swap0: provider destroyed.
Sep 11 17:53:34 BigNASty GEOM_MIRROR: Device swap0 destroyed.
Sep 11 17:53:35 BigNASty GEOM_MIRROR: Device mirror/swap0 launched (3/3).
Sep 11 17:53:35 BigNASty GEOM_MIRROR: Device mirror/swap1 launched (3/3).
Sep 11 17:53:35 BigNASty GEOM_ELI: Device mirror/swap0.eli created.
Sep 11 17:53:35 BigNASty GEOM_ELI: Encryption: AES-XTS 128
Sep 11 17:53:35 BigNASty GEOM_ELI:     Crypto: hardware
Sep 11 17:53:35 BigNASty GEOM_ELI: Device mirror/swap1.eli created.
Sep 11 17:53:35 BigNASty GEOM_ELI: Encryption: AES-XTS 128
Sep 11 17:53:35 BigNASty GEOM_ELI:     Crypto: hardware

Here is the system hardware...

Code:

Software: TrueNAS-12.0-U5.1 (On 2 - Mirrored SSDs)
Case: Fractal Designs Node 804 Case
Power Supply: Seasonic SSR-550RM
Motherboard: Supermicro X10SL7-F (LSI 2308 Flashed to 20.00.07.00-IT)
Processor: Intel Xeon E3-1231 v3
Memory: 32GB Crucial ECC RAM CT102472BD160B
Storage: 6 - 4TB Western Digital Red WD40EFRX (RAIDZ2) 14.5 TB Usable

 

[ChrisRJ]

On my system (FreeNAS 11.3u5) I always do this the following way

• Shut down NAS
• Physically replace drive
• Start up NAS
• Replace missing drive with new one (gives UI error, but otherwise works)
• Wait until resilvering is done

But I have never had the situation of two drives having gone at the same time.

Good luck!

 

[sretalla]

when I trying to offline the disk nothing happens. The GUI still shows faulted. Is this normal behavior?

To be honest, I think this is just a confusion of terminology...

Faulted equates to already offline (because of too many errors), so attempts to offline an already offline disk will, of course, fail.

Just go straight to the replacement steps.

 

[DifferentStrokes]

To be honest, I think this is just a confusion of terminology...

Faulted equates to already offline (because of too many errors), so attempts to offline an already offline disk will, of course, fail.

Just go straight to the replacement steps.

Ok. Thank you. I'll give it a go.