cannot see lun under add remove datastore but can see under devices

[tdubb123]

I got a FC lun that is a bootlun from another host. I see it under devices under the hba, but when I go to add datastore, I do not see it.

any idea? The lun number is 0. should it matter?

[dhanarajramesh]

try to re-signature it and use it.

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=101138...

[tdubb123]

i cant even see the lun, how do I resignature it? the lun is not visible.

[dhanarajramesh]

use the esxli command to list out and re-signature it.

Command line

The esxcli command is used on the command line.

• To list the volumes detected as snapshots, run this command:
  
  # esxcli storage vmfs snapshot list
  
  The output appears similar to:
  
  49d22e2e-996a0dea-b555-001f2960aed8
   Volume Name: VMFS_1
   VMFS UUID: 49d22e2e-996a0dea-b555-001f2960aed8
   Can mount: true
   Reason for un-mountability:
   Can resignature: true
   Reason for non-resignaturability:
   Unresolved Extent Count: 1
  
  
• To mount a snapshot/replica LUN that is persistent across reboots, run this command:
  
  # esxcli storage vmfs snapshot mount -l label|-u uuid
  
  For example:
  
  # esxcli storage vmfs snapshot mount -l "VMFS_1"
# esxcli storage vmfs snapshot mount -u "49d22e2e-996a0dea-b555-001f2960aed8"
  
  
• To mount a snapshot/replica LUN that is not persistent across reboots, run this command:
  
  # esxcli storage vmfs snapshot mount -n -l label|-u uuid
  
  For example:
  
  # esxcli storage vmfs snapshot mount -n -l "VMFS_1"
# esxcli storage vmfs snapshot mount -n -u "49d22e2e-996a0dea-b555-001f2960aed8"
  
  
• To resignature a snapshot/replica LUN (the volume is mounted immediately after the resignature), run this command:
  
  # esxcli storage vmfs snapshot resignature -l label|-u uuid
  
  For example:
  
  # esxcli storage vmfs snapshot resignature -l "VMFS_1"
# esxcli storage vmfs snapshot resignature -u "49d22e2e-996a0dea-b555-001f2960aed8"

[DavidPasek]

There is possibility your LUN is not empty and there already exist some other partition.

If this is the root case of your issue than there are several possibilities how to solve this issue.

Solution 1: You can delete/destroy your LUN and create new one.

Solution 2: use dd to zero the head of your LUN. The command can looks like

dd if=/dev/zero of=<DEVICE> bs=512 count=100

Please note that I don;t test this command and I have just write it from memory ... use it in on your own risk 😉

[admin]

Are you trying to add the datastore from the vCenter server or from a client directly from host.? if from vCenter server try and check if your able to add the datastore from the host directly.

--Avinash