Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP Install/Upgrade
Known Affected Versions:
10.0.0, 10.0.1, 10.1.0, 10.2.0, 10.2.1, 10.2.2, 10.2.3, 10.2.4, 11.0.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.5.1 HF1, 11.6.1 HF1, 11.5.1 HF2, 11.6.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.1 HF10, 11.5.1 HF11, 11.5.2 HF1, 11.6.2 HF1, 11.5.3 HF1, 11.5.3 HF2, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.1.0, 11.2.0, 11.2.1, 11.3.0, 11.4.0
Fixed In:
11.4.1
Opened: Jun 26, 2013 Severity: 2-Critical Related Article:
K14718
When you attempt to upgrade to BIG-IP software version 11.4.0 using any of the supported methods (GUI, tmsh, etc.), the installation might fail, reporting one of the two following error signatures in the /var/log/liveinstall.log file: 1. 'Maintenance OS update failed' error with no Solution reference. info: Updating MOS from 2.7.5 - 47.0 to 2.8.1 - 44.0 info: Growing maintenance volume sda.dat.maint.1 error: status 256 returned by command: /sbin/e2fsck -fp /dev/vg-db-sda/dat.maint.1 info: >++++ result: info: dat.maint.1: Superblock last mount time is in the future. FIXED. info: dat.maint.1: Superblock last write time is in the future. FIXED. info: dat.maint.1: 13/51200 files (0.0% non-contiguous), 143633/204800 blocks info: >---- Terminal error: Maintenance OS update failed. *** Live install end at 2013/06/19 08:58:21: failed (return code 9) *** 2. 'Maintenance OS update failed' error with Solution 10636 reference. info: Updating MOS from 2.7.3 - 19.0 to 2.8.1 - 44.0 debug: tm_install::DosPtable::DosPtable_get_all_devices -- current = 1 debug: tm_install::Volume::Volume_open -- name=sda.dat.share.1, nw=yes, rp=(none) debug: new temp mount dir /mnt/tm_install/5958.WY9qjy created for sda.dat.share.1 info: Unpacking cpio archive for init stage two. info: Moving 'init' from '/' to '/sbin' info: Creating iso file for st.mos info: Creating iso md5sum for st.mos info: Updating boot partitions(s) for st.mos debug: tm_install::DosPtable::DosPtable_get_all_devices -- current = 1 debug: tm_install::Volume::Volume_open -- name=sda.dat.maint.1, nw=yes, rp=(none) debug: new temp mount dir /mnt/tm_install/5958.pEmPFZ created for sda.dat.maint.1 error: copy /var/tmp/941XVBlqcS failed; No space left on device debug: tm_install::Volume::Volume_close -- handle = /dev/vg-db-sda/dat.maint.1 error: Disk full (boot partition). See SOL#10636 debug: tm_install::Volume::Volume_close -- handle = /dev/vg-db-sda/dat.share.1 Terminal error: Maintenance OS update failed. *** Live install complete at 2013/06/17 11:27:38: status=65280 *** Important: The second error message is misleading, as this failure is not related to problems with the boot partition. This failure is actually related to the dat.maint.1 volume, which is the volume used by the Maintenance Operating System (MOS). Therefore, the recommendations in SOL10636 do not resolve the problem.
The user cannot upgrade to BIG-IP software version 11.4.0.
The update failure occurs when the user tries to upgrade an existing system to BIG-IP software version 11.4.0. There are no other known conditions required for the failure to occur. The failure depends on whether the e2fsck utility finds and corrects any benign/trivial errors. Unfortunately, this is likely, and causes the update failure.
The workaround is straightforward and safe to apply. Log on to the BIG-IP system and run the following three commands: # lvresize -L +200M /dev/vg-db-sda/dat.maint.1 # e2fsck -f /dev/vg-db-sda/dat.maint.1 # resize2fs /dev/vg-db-sda/dat.maint.1 Note: On some systems, the volume group name may be something else. For example, it could be vg-db-hda instead of vg-db-sda. To determine the exact commands to run, refer to the error message logged in the /var/log/liveinstall.log file the first time the installation is attempted. The procedure is innocuous and can be executed on a live system processing traffic. There should be no impact. After performing this procedure, you should be able to upgrade to BIG-IP software version 11.4.0.
In versions that contain the fix for this issue, (specifically, BIG-IP software version 11.4.1 or later), the installation occurs without Maintenance OS update errors and completes successfully.