Bug ID 1049085: Booting into a newly installed hotfix volume may stall on RAID-capable platforms

Last Modified: May 29, 2024

Affected Product(s):
BIG-IP Install/Upgrade(all modules)

Known Affected Versions:, 15.1.4,, 15.1.5,, 15.1.6,, 15.1.7, 15.1.8,,, 15.1.9,, 15.1.10,,,

Opened: Sep 23, 2021

Severity: 1-Blocking


Upon booting into a RAID volume containing a newly installed instance of BIG-IP system software which is an Engineering Hotfix, the following messages may appear, after which the boot process stalls: [...] [ 11.705219] dracut-initqueue[324]: mdadm: Duplicate MD device names in conf file were found. [ 133.844644] dracut-initqueue[324]: Warning: dracut-initqueue timeout - starting timeout scripts [ 133.932885] dracut-initqueue[324]: mdadm: Devices UUID-012345678:9abcdef0:12345678:9abcdef0 and UUID-abcdef01:23456789:abcdef01:23456789 have the same name: /dev/md4 [...] [ *** ] A start job is running for dev-disk...


Impossible to boot into the volume of the new installation, it is necessary to physically reboot the device and revert to a previously working volume to rectify the problem.


1) a hardware platform is configured to use RAID for redundancy 2) duplicate RAID array declarations are introduced into /etc/mdadm.conf 3) a hotfix installation is performed to one of the RAID volumes


Instead of installing the hotfix directly, first install the plain base version on which the hotfix is based and boot into it - this will resolve the problem with the duplicate entries in /etc/mdadm.conf. Then install the hotfix as normal.

Fix Information


Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips