ESX 3.02 strangeness with iSCSI-R3 2.30

[roxer]

I fixed this by naming the LUNs the same as the vg/lv numbers:

VG01 = LV0001 LUN 10
LV0002 LUN 20
LV0003 LUN 30 - etc.

Targets have the same id as the LUN series.

[mhilbrand@vrz.net]

Hello Craig

I had the same problem and tried the work-around with the LUN ID, but with no success. Then I mapped the target with the newly created columes to a windows machine (instead of ESX) and opened the disk management for writing a disk signature.

After the disk signature was written, ESX was able to map the drives. Don't ask my why ESX cannot read new volumes, but it works...

best regards

Maxx