Originally Posted by
JSVM
Have you tried esxcfg-rescan on the iSCSI vmhba from the service console? Does a LUN show up?
Incidentally, there's another issue which you won't encounter until you try to create multiple ISCSI LUNs. ESX, on a given HBA, requires unique LUN numbers, even if they're on different ports/targets. Because Thecus' scripts generate the iscsi conf with all LUNs as LUN 0 (just on different SCSI device numbers), ESX will only see the last one it scans. I had to build a new firmware (after reverse-engineering the firmware including the way it's encrypted) with patched scripts that set a unique LUN # for each LUN.