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