Sorry if this is in the wrong section.
ESX 3.5 - rescan not only does not see newly assigned lun (others do OK) but the rescan process is still in the VC event list for several hours.
Does this appear to be a VC refresh issue or something more serious ?
Usually I see this behavior when you have many LUNs presented to the ESX that are RDM, and the SO owning this RDM have some kind of lock on it. Do you have such a thing? Win2008/2003/2000 with MSCS? Oracle RAC?
Marcelo Soares
VMWare Certified Professional 310
Technical Support Engineer
Linux Server Senior Administrator
Unsuccessful
One of the hosts involved has no RDMs assignewd at all.
So I only can assume you are having FC problems. Do a "tail -f /var/log/vmkernel > /root/log.txt" and after that do a rescan and paste here the log.txt file generated.
Marcelo Soares
VMWare Certified Professional 310
Technical Support Engineer
Linux Server Senior Administrator
Stopped and started VC - thanks all.