Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Thanks for using the TrueNAS Community Edition issue tracker! TrueNAS Enterprise users receive direct support for their reports from our support portal.

Pool status will not update unless system is restarted/system panics

Description

TrueNAS-SCALE-20.12-MASTER-20201207-015004
10.20.21.172 (FN05)
10.20.20.139 (FN02)

Pulled a drive in a mirrored pool for testing in 2 different systems. In both instances pool degraded (no alerts received - different ticket). Reinserted drive, pool never updates to a healthy status. Restarting the system from the UI results in the pool status changing to "unhealthy". The only way to clear this, is to hard reboot system. Once back online, pool shows healthy.

Debugs for both systems attached.

Problem/Justification

None

Impact

None

SmartDraw Connector

Katalon Manual Tests (BETA)

Activity

Show:

Ryan MoellerJuly 27, 2021 at 7:29 PM

I'm going to create a new ticket for the hotplug IO errors.

Joe MaloneyJune 16, 2021 at 7:41 PM
Edited

 As discussed in slack:

in general this has improved and shows when disks are reinstalled now and no longer shows missing now requiring a reboot to update that part of pool status.  It's the zpool status reporting (CLI,UI) that is not cleared, or resolved automatically yet like it should be in core/enterprise so pool status itself reports unhealthy as shown above.  Our expectation is that pool status should be 100% healthy from CLI, and UI without a reboot when the issue is resolved.  Let us know if we need to open a new ticket for this specifically.

Jeff ErvinJune 15, 2021 at 6:39 PM

  Staying away from FN02 (Multipath), tried this on FN05.  Pulled a drive from a pool that contained a spare.  Spare kicked in and all applicable alerts received etc.  Reinserting the drive brings the pool back online but "unhealthy".  Following alert received:

CRITICAL

Pool tank state is ONLINE: One or more devices has experienced an unrecoverable error. An attempt was made to correct the error. Applications are unaffected.

2021-06-15 11:17:01 (America/Los_Angeles)

I have attached some screenshots (before/after reinsertion) of zpool status.  Also, rebooting the system cleared this.  After restart, pool shows online/healthy.

 

Joe MaloneyJune 14, 2021 at 12:52 PM

 FWIW fn02 is a freenas certified physically wired for multipath.  The other system fn05 is a FreeNAS mini without multipath.  Just wanted to add this context in case it helps.

Ryan MoellerJune 8, 2021 at 2:42 PM

Complete

Details

Assignee

Reporter

Time remaining

0m

Components

Fix versions

Affects versions

Priority

Katalon Platform

Created December 8, 2020 at 2:09 PM
Updated July 1, 2022 at 4:59 PM
Resolved July 27, 2021 at 7:29 PM

Flag notifications