Print View

"One LUN could not be opened" or "No path to device" mounting a Virtual Machine in VCB

Issue

When mounting a virtual machine on the VCB Proxy using either pre-command.wsf or vcbMounter the mount fails with "One LUN could not be opened" or "No path to device" depending on the version.

vcbMounter (VCB 1.0.1 Build 32040)
[2007-04-16 17:11:58.981 'vcbMounter' 2200 error] Error: Failed to open the disk: One LUN could not be opened
[2007-04-16 17:11:58.981 'vcbMounter' 2200 error] An error occured, cleaning up...

vcbMounter (VCB 1.0.2 Build 42090)
[2007-05-09 15:49:21.737 'App' 6728 trivia] Attempting to open SERIAL_NUM:44363030323131303030314520202020444636303046/7.
[2007-05-09 15:49:21.737 'App' 6728 error] No path to device SERIAL_NUM:44363030323131303030314520202020444636303046/7 found.

The VMFS LUNS are presented at the same LUN Host ID as required by VMware Consolidated Backup.

Resolution

This is caused by a mismatch in the disk signatures:

# grep Id /proc/vmware/scsi/vmhba0/* 
/proc/vmware/scsi/vmhba0/0:7:Id: 44 36 30 30 32 31 31 30 30 30 31 45 20 20 20 20 44 46 36 30 30 46 


vcbSanDbg
[2007-05-09 13:46:55.979 'App' 6832 info] **** Begin SCSI Device LIst ****
[2007-05-09 13:46:55.979 'App' 6832 info] Found SCSI Device SERIAL_NUM:44463630302d30304220202020202020444636303046/00007
[2007-05-09 13:46:55.979 'App' 6832 info] Visible on 1 paths:
[2007-05-09 13:46:55.979 'App' 6832 info] Device Name: \\?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#6&d76ffdd&0&117#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}, Bus: 1 Target: 1 Lun: 7
[2007-05-09 13:46:55.979 'App' 6832 info] Lun contains VMFS/LVM signatures:
[2007-05-09 13:46:55.979 'App' 6832 info] VMFS LVM signature.
[2007-05-09 13:46:55.979 'App' 6832 info] LV ID: 4609e62d-86f9e334-1b67-0019bbceed38 - 1 First PE: 0 Name: 4609e62d-86f9e334-1b67-0019bbce
[2007-05-09 13:46:55.979 'App' 6832 info] **** End SCSI Device LIst ****

To resolve the issue enable the SUN Cluster Connection Mode on the VCB Proxy Host Group in the HDS Disk Array Program Manager:

- Enter Management Mode
- Open the required array
- Select the Logical Status tab
- Expand Host Groups | Controller | Port | required Host Group
- Right click on Option and select Modify Host Group Option | Detail
- Check Sun Cluster Connection Manager and click OK

The correct ID is now seen:

# grep Id /proc/vmware/scsi/vmhba0/* 
/proc/vmware/scsi/vmhba0/0:7:Id: 44 36 30 30 32 31 31 30 30 30 31 45 20 20 20 20 44 46 36 30 30 46 


vcbMounter (VCB 1.0.2)
[2007-05-09 15:53:45.827 'App' 5816 trivia] Attempting to open SERIAL_NUM:44363030323131303030314520202020444636303046/7.
[2007-05-09 15:53:45.827 'App' 5816 trivia] Evaluating 1 paths.

vcbSanDbg
[2007-05-09 16:06:29.133 'App' 6360 info] **** Begin SCSI Device LIst ****
[2007-05-09 16:06:29.133 'App' 6360 info] Found SCSI Device SERIAL_NUM:44363030323131303030314520202020444636303046/00007
[2007-05-09 16:06:29.133 'App' 6360 info] Visible on 1 paths:
[2007-05-09 16:06:29.133 'App' 6360 info] Device Name: \\?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#6&d76ffdd&0&117#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}, Bus: 1 Target: 1 Lun: 7
[2007-05-09 16:06:29.133 'App' 6360 info] Lun contains VMFS/LVM signatures:
[2007-05-09 16:06:29.133 'App' 6360 info] VMFS LVM signature.
[2007-05-09 16:06:29.133 'App' 6360 info] LV ID: 4609e62d-86f9e334-1b67-0019bbceed38 - 1 First PE: 0 Name: 4609e62d-86f9e334-1b67-0019bbce
[2007-05-09 16:06:29.149 'App' 6360 info] **** End SCSI Device LIst ****

Adding this setting on a VCB Proxy that also has NTFS LUNs will cause the volumes to disappear and reappear when the LUNs are rescanned from Computer Management | Disk Management | Rescan Disks. The NTFS disk signatures will ensure the disks appear with the same drive letter, but services or applications using these volumes should be stopped while the rescan is done.

References

Configuring Identical SAN LUN IDs
"When configuring SAN for Consolidated Backup, make sure that for every LUN containing VMFS or RDM data, the LUN ID on the VCB proxy matches the LUN ID seen by the ESX Server system."
http://theether.net/download/VMware/vi3_301_201_vm_backup.pdf

The disk signature, a unique number at offset 0x01B8, identifies the disk to the operating system. Windows uses the disk signature as an index to store and retrieve information about the disk in the registry subkey HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices.

Products

VMware Consolidated Backup 1.0.X
HDS Thunder 9500V DF600

Created: 10th May 2007
Updated: 10th May 2007

Print View

© 2005-2024 Jamie Morrison