Hello everyone,
I'm wrestling with this problem:
in our lab we have two ESX 3.0.1 servers running on ProLiant BL465c G1 blades. When trying to add SAN storage, I found out the LUNs are visible but when trying to access them, the VI Client gui just hangs (timeout error). When trying to access those disks through the console: same problem except it worked when using the Linux device files:
fdisk /vmfs/devices/disks/vmhba0:0:1 just hangs but
fdisk /dev/sda works perfectly
esxcfg-vmhbadevs
vmhba0:0:1 /dev/sda
vmhba0:0:2 /dev/sdb
vmhba2:0:0 /dev/cciss/c0d0
While trying to figure out what the problem was I created a vmfs partition + filesystem through the console:
fdisk /dev/sda (manually create vmfs partition)
...
vmkfstools -C vmfs3 -S sanstorage vmhba0:0:1:1
This works fine via the console but doesn't solve the problem at all. A collegue pointed there were quite some problems with QLogic HBAs and downloading ESX 3.0.2 and all latest patches would be a good start. But even after upgrading one of the servers they still refuse. The HBAs are incorrectly recognised as QLA2432 but I read this is just a stupid bug... in reality they're of type QMH2462.
Anyone has an idea / had a similar problem? Wasn't able to find a solution on forums...
Regards, Dirk
ps: if I need to post detailed info, could you point me to the correct file?
