The long red hex might represent your volume name or something i'm not sure but looking at the log, seems like it having problems with your SAN being able to failovered and it uses manual method to switched over. I would look at esxtop to check out any performance problems with disk I/O otherwise check with your SAN guy to specific LUN/hosts. You can use disk I/O monitoring tool such as IOMeter to check things out.
If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!!!
VMware vExpert 2009
iGeek Systems Inc.
VMware, Citrix, Microsoft Consultant
The vml.xxxxxxxxxxxxxxxxxxxxxxx is your LUN path. There is a powershell script (http://www.peetersonline.nl/index.php/vmware/translate-vml-to-lun-path-with-powershell/) which does the translation for you, however you already have the effected LUN Path (and therefore the datastore) in the vmkernel logs, i.e. vmhba2:3:74 in your case.
As the other poster mentioned it looks like you are having trouble failing over to this path for some reason.