The 'Critical' state will look like the one below on the GUI.
The proxy is running as a virtual appliance.
The reason the proxy triggered the alert is that Disk 1 attribute has become "none" instead of "boot". Below is the current drive status.
Storage: 2 drives
Disk in slot 1: 214 GB VMware Virtual disk , rev:2.0 serial: attributes:none status:present
Disk in slot 2: 214 GB VMware Virtual disk , rev:2.0 serial: attributes:data status:present
By right a virtual proxy should have two types of disks - a boot disk and a data disk as mentioned in the document below.
Here is an example where it shows the "boot" attribute for Disk 1 and not "None".
Storage: 2 drives
Disk in slot 1: 8 GB KVM VirtIO Disk, rev:N/A serial:N/A attributes:boot status:present
Disk in slot 2: 214 GB KVM VirtIO Disk, rev:N/A serial:N/A attributes:data status:present
The proxy originally came with the boot and the data drive but then Disk 1 was resized causing it to lose the "boot" attribute. Even though the proxy is still working fine due to the absence of "boot" disk, it triggers the critical alert for Disk 1. Below is a document that mentioned Disk 1 or boot disk should not be resized or removed.
To resolve the issue, the proxy needs to be rebuilt and should take note of which package should be downloaded.