Last Modified: Jul 28, 2026
Affected Product(s):
BIG-IP Install/Upgrade, TMOS
Known Affected Versions:
17.5.1.6, 17.5.1.8
Opened: May 15, 2026 Severity: 1-Blocking Related Article:
K000161170
- When upgrading to BIG-IP v17.5.1.6 and an Engineering Hotfix that includes the fix for ID2291757, systems other than iSeries appliances will fail to boot into the new boot location. This affects F5OS tenants, vCMP guests (including on iSeries appliances), VIPRIONs, and all other hardware platforms. BIG-IP Virtual Editions may also be affected, depending on their disk partition layout (which varies by deployment history and cannot be reliably predicted without inspecting the filesystem) When this occurs, the system hangs during early boot. An error similar to the following may be seen at the console: [ 3.201968] systemd-fsck[1230]: set.2./var: clean, 10131/294912 files, 148631/1179648 blocks [FAILED] Failed to mount Mount TMOS 'share' filesystem See 'systemctl status shared.mount' for details - Upgrading an iSeries appliance to BIG-IP v17.5.1.6 (or an Engineering Hotfix that does not include a fix for ID2291757) results in degraded operation: the system boots, but SSH is unavailable. The system may be partially accessible via GUI or console. These issues stem from insufficient space on the /usr filesystem during the upgrade. For background, see K000161170. The fix for ID2291757 addressed the /usr space issue for iSeries appliances, but introduced a boot failure when applied to other platforms. The fix for ID2296269 resolves this regression.
- Non-iSeries platforms: The system fails to boot and is inaccessible. Recovery requires accessing the console of the system and booting into the previous boot location - Bare-metal iSeries appliances (without FIPS HSM): The system boots but operates in a degraded state. SSH is unavailable, and the configuration may not fully load, but GUI and console access are still available
- Upgrading any platform other than an iSeries appliance to a BIG-IP v17.5.1.6 Engineering Hotfix that includes the fix for ID2291757. This affects vCMP guests on iSeries appliances. - Upgrading an iSeries appliance to the base BIG-IP v17.5.1.6 release, or to an Engineering Hotfix that does not include the fix for ID2291757. Note that this issue only occurs on BIG-IP 17.5.1.6, due to incorrect volume sizing metadata applied when creating the /usr volume during installation of the BIG-IP 17.5.1.6 release image. This condition is specific to the BIG-IP 17.5.1.6 release only. This issue is addressed by BIG-IP 17.5.1.6 Engineering Hotfixes which contain code to expand the size of the /usr volume during Engineering Hotfix installation, prior to installing the Engineering Hotfix. This solution was first implemented under ID2291757, then refined by the fix for ID2296269, then further refined by the fix for ID2298081. This incorrect volume sizing metadata issue is resolved under ID2301585 for BIG-IP 17.5.1.8 and later.
Select the appropriate path based on your platform: - F5OS tenants, vCMP guests, VIPRIONs, Virtual Editions, and other non-iSeries platforms: Obtain a BIG-IP 17.5.1.6 Engineering Hotfix that includes the fix for ID2296269 or ID2298081. - Bare-metal iSeries appliances (without onboard FIPS HSM): Obtain a BIG-IP 17.5.1.6 Engineering Hotfix that includes the fix for ID2291757, ID2296269 or ID2298081. - iSeries appliances with onboard FIPS HSM: Engineering Hotfixes are not applicable. Follow the manual workaround (Option B) in K000161170 For more details, see https://my.f5.com/manage/s/article/K000161170 The generally recommended solution is to upgrade to BIG-IP 17.5.1.8 or later.
None