Bug ID 824681: Invalid volume name, clusterd error at boot time

Last Modified: Sep 14, 2023

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

Known Affected Versions:
13.1.0,,,,,,,,, 13.1.1,,,,, 13.1.3,,,,,,, 13.1.4,, 13.1.5,, 14.0.0,,,,,, 14.0.1,, 14.1.0,,,,,, 14.1.2,,,,,,,,, 14.1.3,, 14.1.4,,,,,,, 14.1.5,,,,,

Opened: Sep 10, 2019

Severity: 3-Major


In certain cases, booting a new blade or upgrading can result in HD1.0 being created and the following error on startup in /var/log/ltm: err mcpd[6426]: 01070945:3: Invalid volume name (HD1.0) err clusterd[8217]: 013a0004:3: result { err clusterd[8217]: 013a0004:3: result.code 17238341 err clusterd[8217]: 013a0004:3: result.message 01070945:3: Invalid volume name (HD1.0) err clusterd[8217]: 013a0004:3: result.attribute volume err clusterd[8217]: 013a0004:3: }


Clusterd keeps restarting, BIG-IP system is unusable.


Conditions are not yet fully understood, but it has been documented only to occur on VIPRION systems, and specifically when booting to a newly upgraded volume or installing a new blade.


Workarounds include: -- Deleting volume HD1.0. -- Replacing volume HD1.0 with the name of the desired boot volume in /shared/db/cluster.conf.

Fix Information


Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips