https://wiki.vi-toolkit.com/index.php?title=ESXi_vSphere_mount_LUN_problems&feed=atom&action=historyESXi vSphere mount LUN problems - Revision history2024-03-28T17:59:48ZRevision history for this page on the wikiMediaWiki 1.41.0https://wiki.vi-toolkit.com/index.php?title=ESXi_vSphere_mount_LUN_problems&diff=1443&oldid=prevWila: forgot to categorize2018-02-12T15:32:06Z<p>forgot to categorize</p>
<table style="background-color: #fff; color: #202122;" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 16:32, 12 February 2018</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l89">Line 89:</td>
<td colspan="2" class="diff-lineno">Line 89:</td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>In vSphere 6.5 this happens when you have only 1 uplink.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>In vSphere 6.5 this happens when you have only 1 uplink.</div></td></tr>
<tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;"></ins></div></td></tr>
<tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">[[Category: ESXi]]</ins></div></td></tr>
</table>Wilahttps://wiki.vi-toolkit.com/index.php?title=ESXi_vSphere_mount_LUN_problems&diff=1442&oldid=prevWila: Created page with "=== cannot connect to LUN === Sometimes the correct LUN does not show up and trying to mount it only gives an option to format the LUN. * 1. Log in as root to the ESX host wh..."2018-02-12T15:27:31Z<p>Created page with "=== cannot connect to LUN === Sometimes the correct LUN does not show up and trying to mount it only gives an option to format the LUN. * 1. Log in as root to the ESX host wh..."</p>
<p><b>New page</b></p><div>=== cannot connect to LUN ===<br />
Sometimes the correct LUN does not show up and trying to mount it only gives an option to format the LUN.<br />
<br />
* 1. Log in as root to the ESX host which cannot mount the datastore using an SSH client.<br />
* 2. Run the command:<br />
esxcfg-volume -l<br />
<br />
The results appear similar to:<br />
<br />
VMFS3 UUID/label: 4b057ec3-6bd10428-b37c-005056ab552a/ TestDS<br />
Can mount: Yes<br />
Can resignature: No (the volume is being actively used)<br />
Extent name: naa.6000eb391530aa26000000000000130c:1 range: 0 – 1791 (MB)<br />
<br />
Record the UUID portion of the output. In the above example the UUID is 4b057ec3-6bd10428-b37c-005056ab552a.<br />
<br />
Note: The Can mount value must be Yes to proceed with this workaround.<br />
<br />
* 3. Run the command:<br />
esxcfg-volume -M <UUID><br />
<br />
Where the <UUID> is the value recorded in step 2.<br />
<br />
or you can just use the label:<br />
esxcfg-volume -M TestDS<br />
<br />
<br />
=== adding a new NFS LUN from the CLI ===<br />
<br />
First list what is there:<br />
esxcli storage nfs list<br />
<br />
Then add:<br />
esxcli storage nfs add -v NEWLUN -H 1.2.3.4 -s /mnt/newstorage<br />
where NEWLUN is the label, -H is the host<br />
<br />
=== adding iSCSI LUN back ===<br />
<br />
disable snapshot LUN<br />
<br />
# esxcfg-advcfg -s 0 /LVM/DisallowSnapshotLun<br />
Value of DisallowSnapshotLun is 0<br />
Then rescan the lot<br />
# esxcli storage core adapter rescan --all<br />
# vmkfstools -V<br />
# esxcli storage vmfs snapshot list<br />
restore the default for your snapshot<br />
# esxcfg-advcfg -s 1 /LVM/DisallowSnapshotLun<br />
Value of DisallowSnapshotLun is 1<br />
# esxcfg-volume -l<br />
# df -h<br />
<br />
The snapshot list and volumes show no results for me, but on df -h after the above commands, the ISCSI mount now shows up at the host.<br />
<br />
[https://kb.vmware.com/kb/2129058 vSAN handling of devices detected as snapshots (2129058)]<br />
<br />
=== Adding a host to an NFS datastore in the VCSA errors out ===<br />
<br />
Trying to add another host to a NFS datastore errors out and generates the error "Failed: An error occurred during host configuration".<br />
The host should be able to connect to the NFS storage as it is allowed from the NFS server.<br />
<br />
Digging deeper on this error gives "Operation failed, diagnostics report: Unable to get console path for volume"<br />
<br />
In my case the host had mounted this NFS LUN before under a slightly different name and as such a now obsolete pointer somewhere was preventing the host from connecting to the LUN.<br />
<br />
You can fix it from the CLI as follows:<br />
<br />
First make sure the LUN isn't in the output of the following command:<br />
# esxcfg-nas -l<br />
<br />
If that's not the case then proceed and try to add the LUN from the CLI.<br />
If your host is 10.0.0.5 and the NFS share on it is /mnt/vol/share which you want to mount as MYLUN then add like<br />
# esxcfg-nas -a -o 10.0.0.5 -s /mnt/vol/share MYLUN<br />
Error performing operation: Unable to add new NAS, volume with the label MYLUN already exists<br />
Here the vSphere server is indeed complaining that MYLUN exists.<br />
Run:<br />
# df -h<br />
and verify that it is NOT in the list.<br />
After that test you can remove the LUN<br />
# esxcfg-nas -d MYLUN<br />
IORM: failed to disable IORM: Unable to get console path for volume, MYLUN<br />
NAS volume MYLUN deleted.<br />
Now you can rerun the above command:<br />
# esxcfg-nas -a -o 10.0.0.5 -s /mnt/vol/share MYLUN<br />
Connecting to NAS volume: MYLUN<br />
MYLUN created and connected.<br />
<br />
=== iSCSI shows as normal, degraded ===<br />
<br />
In vSphere 6.5 this happens when you have only 1 uplink.</div>Wila