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

Last Modified: Oct 16, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP All(all modules)

Known Affected Versions:
13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1

Opened: Sep 10, 2019
Severity: 3-Major

Symptoms

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: }

Impact

Clusterd keeps restarting, BIG-IP is unusable.

Conditions

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

Workaround

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

Fix Information

None

Behavior Change