Description | This article describes a boot failure that occurs after upgrading to an affected firmware version without following a recommended upgrade path. |
Scope | Direct upgrade to v7.0.15, v7.2.9, v7.4.4, or v7.6.0 from firmware v7.0.11, v7.2.4, or any earlier version. |
Solution |
The filesystem integrity check is enforced on boot in v7.0.15, v7.2.9, v7.4.4, and v7.6.0.
If an administrator directly upgrades to one of these firmware versions from v6.4.12, v7.0.11, v7.2.4, or any earlier version, the filesystem integrity check will fail and the device will not boot.
The failure to boot after upgrade owing to this check is fixed in v7.0.16, v7.2.10, v7.4.5, or v7.6.1 as Resolved Issue 1069554, see v7.0.16 Release Notes - Resolved Issues.
Upgrading from earlier versions to these versions does not fail the filesystem check, but may fail for other reasons or have other issues. It is strongly recommended to follow a recommended FortiGate/FortiOS Upgrade Path rather than directly upgrade.
Selecting an alternate firmware for the next reboot: Loading Alternate Firmware Upgrade path tool:
Related documents: Technical Tip: Formatting and loading FortiGate firmware image using TFTP v7.0.15 Release Notes: Upgrading from 7.0.11 or earlier versions v7.0.12 New Features: Enhance BIOS-level signature and file integrity checking |