VMFS not showing up after rescan.

[ryanismean]

I am unable to clone a VMFS volume on my Dell EqualLogic and then add it as a datastore without formatting it. Based on the logs, I suspect this is because ESX thinks it is a snapshot:

Apr 16 05:56:04 rycon vmkernel: 8:17:50:56.961 cpu2:1041)LVM: 5573: Device vml.02000000006090a038b0bfc642749e34090000c0b8313030452d30:1 detected to be a snapshot:

Apr 16 05:56:04 rycon vmkernel: 8:17:50:56.961 cpu2:1041)LVM: 5580: queried disk ID: <type 2, len 22, lun 0, devType 0, scsi 6, h(id) 18395505175267223433>

Apr 16 05:56:04 rycon vmkernel: 8:17:50:56.961 cpu2:1041)LVM: 5587: on-disk disk ID: <type 2, len 22, lun 0, devType 0, scsi 6, h(id) 7093051688803509987>

Apr 16 05:56:04 rycon vmkernel: 8:17:50:56.961 cpu2:1041)LVM: 4581: Clash between snapshot (vml.02000000006090a038b0bfc642749e34090000c0b8313030452d30:1) and non-snapshot (vml.02000000006090a038b0bff6774b9e94070000c030313030452d30:1) device

After searching around, I followed the advice in KB 6482648 and set LVM.DisallowSnapshotLun to 0 on all my ESX hosts and rescanned, but the volume is still not available and the above still appears in the logs every time I refresh the storage list.

Any ideas?

[SuryaVMware · Accepted solution]

Well did you make sure all the ESX servers are seeing this LUN with the same LUN ID ?

First of all what changes caused this issue? Do you know anything that changed in the environment?

If the volume is seen by another host there is a possibility that you might have to re-signature the VMFS volume.

This might help.

http://pubs.vmware.com/vi3i_i35/iscsi_san_config/wwhelp/wwhimpl/common/html/wwhelp.htm?context=iscsi...

[ryanismean]

Sorry, forgot to mention that. Yes, all the hosts see the LUN in

question with LUN ID 0. Didn't realize I'd have to resignature,

though...enabling that fixed it. Thanks!