Expert
Expert

Can't See New Datastore

Jump to solution

I have created a New LUN on my NetApp storage system.   In VMware, the iSCSI software initiator in "Static Discovery" shows that the targets have been discovered.  On the NetApp system, an ">iscsi show initiator" shows that the iSCSI HBA has successfully logged in to the storage system.  However, when I rescan for datastores in vSphere client, the new LUN never shows up so I can format it with VMFS.  Anyone know what the issue could be?

Thanks!

0 Kudos
1 Solution

Accepted Solutions
Leadership
Leadership

Did you present the LUN to the host/initiator group?

André

View solution in original post

0 Kudos
7 Replies
Leadership
Leadership

Did you present the LUN to the host/initiator group?

André

View solution in original post

0 Kudos
Expert
Expert

I attempted to - I assumed that the mapping of the LUN to the initiator group/host was successful based on the fact that I saw the target logged in.  Is that not a safe assumption?  How can I doublecheck this and know for sure it is correct?

0 Kudos
Enthusiast
Enthusiast

This is a really big problem with ESXi 5.  Enable SSH and post the output of "cat /var/log/vmkernel.log".  It is likely that there will be a lot of "No FS driver claimed device".

I had to go back to ESXi 4.1 to get past this.  I'll never use the .0 releases ever again.  Test dummies.

Enthusiast
Enthusiast
0 Kudos
Virtuoso
Virtuoso

I'm interested in the output of fdisk -l on an affected server.

0 Kudos
Enthusiast
Enthusiast

http://communities.vmware.com/thread/345165

I solved my issue.  You might want to look at this if your LUN is greater than 2TB.

Expert
Expert

Actually I found the problem.  I had not correctly mapped the iqn of the iSCSI software initiator within Data OnTap.  I reran >lun setup and chose the correct iqn of the initiator and added it to the intiator group.   After that I was able to see the LUN from within vSphere client and then create a datastore on it.

Thanks all for your input.

0 Kudos