Connectrix Brocade: Firmware commit failed due to inconsistent Primary file system.

Summary: FOS upgrade failed due to 'Failed to download RPM package'.

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Symptoms

The firmware commit failed during the FOS upgrade due to an inconsistent primary file system.

firmwareshow -v:
Appl     Primary/Secondary Versions
------------------------------------------
FOS      v8.2.3
         Unknown
DP       v8.2.3 

firmwaredownloadstatus:
[1]: Fri Feb 18 09:40:45 2023
Firmware is being downloaded to the switch. This step may take up to 30 minutes.

[2]: Fri Feb 18 09:50:02 2023
Firmware download failed - Failed to download RPM package. Please check if the firmware image is accessible. (0x15)

[3]: Fri Feb 18 09:50:02 2023
Firmwarecommit has started on the local CP. Please use firmwaredownloadstatus and firmwareshow to see the firmware status.

[4]: Fri Feb 18 09:50:02 2023
The firmware commit operation has started. This may take up to 10 minutes.

[5]: Fri Feb 18 09:51:14 2023
Firmware commit failed - Primary filesystem is inconsistent. Run firmwarerestore to restore the original firmware, or contact your service provider for recovery. (0x25)

[6]: Fri Feb 18 11:01:10 2023
The firmware commit operation has started. This may take up to 10 minutes.

[7]: Fri Feb 18 11:02:24 2023
Firmware commit failed - Primary filesystem is inconsistent. Run firmwarerestore to restore the original firmware, or contact your service provider for recovery. (0x25)

[8]: Fri Feb 18 12:03:37 2023
The firmware commit operation has started. This may take up to 10 minutes.

[9]: Fri Feb 18 12:04:50 2023
Firmware commit failed - Primary filesystem is inconsistent. Run firmwarerestore to restore the original firmware, or contact your service provider for recovery. (0x25)

The output of errdump indicates that the firmwaredownload command failed as it was unable to download the firmware image followed by firmware commit failure with status code 0X25.

errdump:

2023/02/18-09:40:45, [SULB-1001], 43, CHASSIS, WARNING, DS_6610B, Firmwaredownload command has started. (From v8.2.3 To v9.0.1b).

2023/02/18-09:50:02, [SULB-1011], 44, CHASSIS, INFO, DS_6610B, Firmwaredownload command failed. Failed to download RPM package. Please check if the firmware image is accessible.. 

2023/02/18-09:50:02, [SULB-1003], 45, CHASSIS, INFO, DS_6610B, Firmwarecommit has started.

2023/02/18-09:51:14, [SULB-1010], 46, CHASSIS, INFO, DS_6610B, Firmwarecommit failed (status=0x25).

Cause

Brocade Engineering discussed this with the developer extensively and has confirmed that this issue was an exact match to an internal defect. The trigger was root-caused by a CF issue.

 Another possibility: the CF has been exposed to excessive writes (TSB 2021-281-A).

Resolution

Firmwarecleaninstall (which reformats the CF and isolates bad sectors) could resolve the internal issue.

Affected Products

Connectrix B-Series, Connectrix B-Series Hardware, Connectrix B-Series Software
Article Properties
Article Number: 000220176
Article Type: Solution
Last Modified: 15 Apr 2025
Version:  2
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.