Bug ID 726416: Physical disk HD1 not found for logical disk create

Last Modified: May 23, 2019

Bug Tracker

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

Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 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, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.4, 14.1.0.5, 15.0.0

Opened: Jul 02, 2018
Severity: 3-Major

Symptoms

The blade error 'Physical disk HD1 not found for logical disk create' occurred preceding a CPU reboot on a VIPRION 2250 blade. /var/log/ltm shows messages similar to the following: -- debug chmand[3370]: 012a0007:7: mcp_logical_disk mcp_create received -- debug chmand[3370]: 012a0007:7: logical_disk create received: name[HD1] media[general_use_ssd] -- err chmand[3370]: 012a0003:3: Physical disk HD1 not found for logical disk create -- debug chmand[3370]: 012a0007:7: other mcp_create (tag=8124) messages -- debug chmand[3370]: 012a0007:7: mcp_physical_disk mcp_create received -- debug chmand[3370]: 012a0007:7: physical_disk create received: serial number[BTDV466121NK840JVN] name[HD1] Notice that physical_disk HD1 was created right after logical_disk HD1 was created. BIG-IP system operations expect the reverse, i.e., physical_disk HD1 should be created first. Note: These messages are visible only when you have the sys db log.libhal.level set to DEBUG and run the following command: tmsh modify sys db log.libhal.level value "Debug"

Impact

This occurs because the Logical disk was created before the physical one. The system posts the following error: err chmand[3370]: 012a0003:3: Physical disk HD1 not found for logical disk create. The system is forced to reboot. Traffic disrupted while the system restarts.

Conditions

The exact conditions that result in this issue are still being investigated.

Workaround

There is no workaround.

Fix Information

None

Behavior Change