Bug ID 715200: VE with only hda drive does not report disk statistics

Last Modified: Jun 10, 2021

Bug Tracker

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

Known Affected Versions:
12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 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, 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, 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

Fixed In:
14.1.0

Opened: Apr 16, 2018
Severity: 3-Major

Symptoms

On a BIG-IP Virtual Edition (VE) setup, there are no disk stats. The system logs error messages similar to the following: err chmand[7946]: 012a0003:3: Disk Latency Monitor: No disks found.

Impact

Disk usage statistics are all zeroes. 'No Data' on Inspector pages charts: 'Disk Operations', 'Disk Throughput', and 'Disk Merges' The system reports that no disks are found.

Conditions

-- VE with only an hda drive. -- Navigate to inspector pages Monitoring :: Dashboards :: Device :: Health to view the statistics.

Workaround

Reconfigure the VE hypervisor so the virtual disk is named sda or vda instead of hda.

Fix Information

The system now uses the hda disk when it is the only available disk, so the statistics are correctly reported.

Behavior Change