Member volume of the FlexGroup volume went offline due to file system inconsistencies

After a reboot, some member volumes of the FlexGroup volume went offline due to file system inconsistencies, making the FlexGroup inaccessible.

• The following is recorded in the EMS log:

[?]  Sun Feb 18 11:34:39 +0000 [XXX: mgwd: mgmtgwd.fg.modify.constituent.fail:error]: Failed to modify the state of FlexGroup constituent XXX in Vserver XXX. Reason: Unable to set volume attribute "state" for volume "XXX" on Vserver "XXX". Reason: Volume is inconsistent.
[?]  Sun Feb 18 11:35:04 +0000 [XXX: mgwd: mgmtgwd.jobmgr.jobcomplete.failure:info]: Job "Vol Modify" [id 8986] (Modify XXX) completed unsuccessfully: Failed to change the state of FlexGroup volume "XXX". Constituent "XXX" failed to be modified to the desired state. Reason: "Unable to set volume attribute "state" for volume "XXX" on Vserver "XXX". Reason: Volume is inconsistent." (13107347).

• The `VOL-STATUS-V` also shows wafl inconsistent.

Volume name: XXX
  State: offline
  Status: raid_tec, flex, cluster, wafl inconsistent, fast zeroed, 64-bit
 Options: schedsnapname=ordinal, nbu_archival_snap=off,
  batched_free_log_cap=, space_slo=none(disabled),
  zombie_reclamation_priority=urgent
 Volume UUID: XXX
 Containing aggregate: 'XXX'
 Volume Buftree UUID: XXX
 Volinfo mode: cluster-mode
 Volume Instance UUID: XXX
 Hybrid Cache: Eligibility=read-write