topic SnapDrive fails to remap LUN after VM reboot in VMware Solutions Discussions https://community.netapp.com/t5/VMware-Solutions-Discussions/SnapDrive-fails-to-remap-LUN-after-VM-reboot/m-p/64324#M6011 <HTML><HEAD></HEAD><BODY><P>I am running SnapDrive 6.3.0.4601 in a few Windows 2008 R2 VMware VM's that map to a few different LUN's (iSCSI) via the Windows iSCSI initiator. Sometimes after a graceful Windows restart the LUN's fail to map. When I open up SnapDrive and try to manually map/connect them I am given the error that they are already mapped to the initiator name corresponding that same VM and it gives me a few options, one of which is to unmap the LUN and remap, which is what I end up doing to fix the problem.</P><P></P><P>What could be causing this issue? Are the LUNs supposed to unmap when the VM's reboot and remap upon restart? Any help is greatly appreciated!!</P><P></P><P>Our NetApp is a FAS2040 rev A4 running ontap&nbsp; 8.0.1 7-Mode. The LUNs are being mapped for SQL or Exchange databases.</P></BODY></HTML> Thu, 05 Jun 2025 06:52:56 GMT cserpadss 2025-06-05T06:52:56Z SnapDrive fails to remap LUN after VM reboot https://community.netapp.com/t5/VMware-Solutions-Discussions/SnapDrive-fails-to-remap-LUN-after-VM-reboot/m-p/64324#M6011 <HTML><HEAD></HEAD><BODY><P>I am running SnapDrive 6.3.0.4601 in a few Windows 2008 R2 VMware VM's that map to a few different LUN's (iSCSI) via the Windows iSCSI initiator. Sometimes after a graceful Windows restart the LUN's fail to map. When I open up SnapDrive and try to manually map/connect them I am given the error that they are already mapped to the initiator name corresponding that same VM and it gives me a few options, one of which is to unmap the LUN and remap, which is what I end up doing to fix the problem.</P><P></P><P>What could be causing this issue? Are the LUNs supposed to unmap when the VM's reboot and remap upon restart? Any help is greatly appreciated!!</P><P></P><P>Our NetApp is a FAS2040 rev A4 running ontap&nbsp; 8.0.1 7-Mode. The LUNs are being mapped for SQL or Exchange databases.</P></BODY></HTML> Thu, 05 Jun 2025 06:52:56 GMT https://community.netapp.com/t5/VMware-Solutions-Discussions/SnapDrive-fails-to-remap-LUN-after-VM-reboot/m-p/64324#M6011 cserpadss 2025-06-05T06:52:56Z SnapDrive fails to remap LUN after VM reboot https://community.netapp.com/t5/VMware-Solutions-Discussions/SnapDrive-fails-to-remap-LUN-after-VM-reboot/m-p/64329#M6012 <HTML><HEAD></HEAD><BODY><P>While reviewing the logs I restarted the VM and noticed that when the VM would boot up I would get a LUN mapping authentication failure message. So I unmapped the LUNs "lun unmap &lt;lun&gt; &lt;igroup&gt;" and removed the Microsoft iSCSI initiator information from the VM, then remapped/reconnected the LUNs via SnapDrive which prompted me to recreate the igroup information....I then rebooted the VM a few times to make sure everything was working fine.</P></BODY></HTML> Tue, 21 Jun 2011 02:02:24 GMT https://community.netapp.com/t5/VMware-Solutions-Discussions/SnapDrive-fails-to-remap-LUN-after-VM-reboot/m-p/64329#M6012 cserpadss 2011-06-21T02:02:24Z