Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP TMOS
Known Affected Versions:
12.1.2, 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, 12.1.5, 12.1.5.1, 12.1.5.2, 12.1.5.3, 12.1.6, 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.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 13.1.3.2, 13.1.3.3, 13.1.3.4, 13.1.3.5, 13.1.3.6, 13.1.4, 13.1.4.1, 13.1.5, 13.1.5.1, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.0.1, 14.0.1.1, 14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 14.1.2.7, 15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.0.1.4
Fixed In:
15.1.0, 14.1.2.8
Opened: Jul 02, 2018 Severity: 3-Major
The blade error 'Physical disk HD1 not found for logical disk create' is observed when bigstart restart happens on primary blade of chassis-based systems using solid state drives (SSD). /var/log/ltm shows messages similar to the following: -- localhost.localdomain debug chmand[25459]: 012a0007:7: mcp_logical_disk mcp_create received -- localhost.localdomain debug chmand[25459]: 012a0007:7: logical_disk create received: name[HD1] media[general_use_ssd] -- localhost.localdomain err chmand[25459]: 012a0003:3: Physical disk HD1 not found for logical disk create -- localhost.localdomain debug chmand[25459]: 012a0007:7: mcp_physical_disk mcp_create received -- localhost.localdomain debug chmand[25459]: 012a0007:7: physical_disk create received: serial number[S3F3NX0K810723] name[HD1] and/or err chmand[4712]: 012a0003:3: Physical disk HD1 not found for logical disk create ltm log implies that logical disk create is requested before physical disk creation.
The system posts the following error under ltm log: err chmand[3370]: 012a0003:3: Physical disk HD1 not found for logical disk create. When system posts the error, it just skips executing couple of lines of code, to be precise two API calls. These API calls are related to updating DiskInfo and disk wearout information. This message is benign and can be safely ignored
This occurs on chassis-based systems (more than one blade) using SSD, when bigstart restart happens on primary blade.
There is no workaround.
The message is not printed anymore