unsupported initiator after migrating a virtual machine to an esx 4.1 server and upgrading the vm-tools the FC lun is still visible in snapdrive, after a reboot snapdrive doesn't see the FC lun anymore, however it is still visible/usable as drive. The eventlog shows the following.
Event Type: Warning
Event Source: SnapDrive
Event Category: Generic event
Event ID: 317
Date: 27-9-2010
Time: 15:52:21
User: N/A
Computer: SNAPDRIVE
Description:
Failed to enumerate LUN.
Device path: '\\?\scsi#disk&ven_netapprev_7340#40&000100#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}'
Storage path: '/vol/testvol/q_test/test.lun'
SCSI address: (2,0,1,0)
Error code: 0xc00402fa
Error description: A LUN with device path \\?\scsi#diskprod_lun&rev_7340#40&000100#{53f56307-b6bf-11d0-94f2-00a0c91efb8b} and SCSI address (2, 0, 1, 0) is exposed through an unsupported initiator.
Event Type: Information
Event Source: SnapDrive
Event Category: Service execution status
Eve
nt ID: 100
Date: 27-9-2010
Time: 15:52:28
User: N/A
Computer: SNAPDRIVE
Description:
SnapDrive service (version 6.3.0.4601 (6.3), ESX Server Version:4.1.0 (1028)) started.
Event Type: Warning
Event Source: SnapDrive
Event Category: Generic event
Event ID: 317
Date: 27-9-2010
Time: 15:52:28
User: N/A
Computer: SNAPDRIVE
Description:
Failed to enumerate LUN.
Device path: '\\?\scsi#disk&ven_netapprev_7340#40&000100#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}'
Storage path: '/vol/testvol/q_test/test.lun'
SCSI address: (2,0,1,0)
Error code: 0xc00402fa
Error description: A LUN with device path \\?\scsi#diskprod_lun&rev_7340#40&000100#{53f56307-b6bf-11d0-94f2-00a0c91efb8b} and SCSI address (2, 0, 1, 0) is exposed through an unsupported initiator.
After de-installing the vmtools, migrate the virtual machine back to an ESX 4.0 host and reinstalling the vmtools, everything works fine and the luns can be managed with snapdrive.
