Introduction
This document describes the steps to fix the fault: "Partition bootflash on fabric interconnect A|B is clean but with errors".
Prerequisites
Requirements
Cisco recommends that you have knowledge of these topics:
- Cisco Unified Computing System Manager (UCSM)
- Cisco Fabric interconnects
Components Used
The information in this document is based on these software and hardware versions:
- 6400 Fabric interconnects
- 6300 Fabric interconnects
- 6200 Fabric interconnects
- 4.0(4k) or 4.1(2a) and later
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, ensure that you understand the potential impact of any command.
Problem
UCSM displays the error message: "Partition bootflash on fabric interconnect A|B is clean but with errors" - Fault 2016.
The alert is displayed on the system when the Fabric interconnects face file system errors.
Solution
The Fabric Interconnect requires a file system check repair and must undergo a reboot. On reboot with the e2fsck option, the Fabric Interconnects SSD undergoes a thorough file system check and non-interactive repair process which could result in data loss. Before you proceed further, you must ensure the backup of the critical data includes the Cisco UCS Manager database. The fix is suggested to be done on a maintenance window since the Fabric Interconnect(s) require(s) a reboot. If only one Fabric Interconnect displays the fault, than only that Fabric Interconnect needs to be rebooted. If both Fabric Interconnects display the fault and require reboot, ensure that you validate the data path is fully available after the first Fabric Interconnect is rebooted before you proceed with the second to avoid any outage.
Steps need to be performed on the Fabric interconnect that reports the alert.
Go to UCSM CLI to enter the commands:
FI-A# connect local-mgmt
FI-A(local-mgmt)# reboot e2fsck
The alert clears within 72 hours after the fix is performed. If the fault does not clear within this time period a TAC case can be opened for further investigation. If the fault is raised on firmware that is earlier than 4.0(4k) or 4.1(2a) and later, this also requires TAC assistance to resolve as they can perform the file system check manually through the debug shell.
Related Information
Feedback