Two Device ID’s on a RDM

I’ve been working on migration our current VMWare hosts to a new install that i’ve designed with optimised storage configuration and memory sharing as so to optimise the customer customer experience. While migrating VM’s from the last five hosts i’ve started running into issues with some VM’s that have RDMs attached. These RDMs won’t migrate to any of the new hosts, but they will migrate to the remaining old ones.

Usually this would mean that either the datastore containing the VMDK or the RDM pointer is not present on the new hosts or the RDM itself is presented to the new hosts. But i verified this and all those are available.

However on further investigation on the RDM i noticed that the RDM had two device ID’s, which is rather unusual.

two device IDs

 

Also when i did a storage refresh i received a lot of unexpected errors

vmkernel: cpu3:106232)ScsiDeviceIO: 2331: Cmd(0x412401b6eb40) 0x1a, CmdSN 0x20568 from world 0 to dev "naa.50002ac000ba0f6e" failed H:0x5 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0.
vmkernel: cpu14:11813)FSS: 4972: No FS driver claimed device 'naa.50002ac0011e0f6e:2': Not supported
vmkernel: cpu23:11813)FSS: 4972: No FS driver claimed device 'naa.50002ac000f50f6e:2': Not supported
vmkernel: cpu23:11813)FSS: 4972: No FS driver claimed device 'naa.50002ac0011d0f6e:2': Not supported
vmkernel: cpu15:11813)FSS: 4972: No FS driver claimed device 'naa.50002ac001060f6e:2': Not supported
vmkernel: cpu18:11813)FSS: 4972: No FS driver claimed device 'naa.50002ac0010a0f6e:2': Not supported
vmkernel: cpu18:11813)FSS: 4972: No FS driver claimed device 'naa.50002ac000e80f6e:2': Not supported
vmkernel: cpu22:11813)FSS: 4972: No FS driver claimed device 'naa.50002ac0010f0f6e:2': Not supported
vmkernel: cpu15:11813)FSS: 4972: No FS driver claimed device 'naa.50002ac001030f6e:2': Not supported
vmkernel: cpu15:11813)FSS: 4972: No FS driver claimed device 'naa.50002ac001090f6e:2': Not supported
vmkernel: cpu4:11813)FSS: 4972: No FS driver claimed device 'naa.50002ac000f70f6e:2': Not supported
vmkernel: cpu4:11813)Vol3: 705: Couldn't read volume header from control: Not supported
vmkernel: cpu4:11813)Vol3: 705: Couldn't read volume header from control: Not supported
vmkernel: cpu4:11813)FSS: 4972: No FS driver claimed device 'control': Not supported
vmkernel: cpu8:11813)FSS: 4972: No FS driver claimed device 'naa.50002ac000aa0f6e:2': Not supported
vmkernel: cpu6:11813)FSS: 4972: No FS driver claimed device 'naa.50002ac0010e0f6e:2': Not supported
vmkernel: cpu1:11813)FSS: 4972: No FS driver claimed device 'naa.50002ac000f20f6e:2': Not supported
vmkernel: cpu2:11813)FSS: 4972: No FS driver claimed device 'naa.50002ac001050f6e:2': Not supported
vmkernel: cpu3:11813)FSS: 4972: No FS driver claimed device 'naa.50002ac0011c0f6e:2': Not supported
cpu7:11813)FSS: 4972: No FS driver claimed device 'naa.50002ac0010b0f6e:2': Not supported
vmkernel: cpu7:11813)FSS: 4972: No FS driver claimed device 'naa.50002ac0010c0f6e:2': Not supported
vmkernel: cpu2:11813)FSS: 4972: No FS driver claimed device 'naa.50002ac001070f6e:2': Not supported
vmkernel: cpu0:11813)FSS: 4972: No FS driver claimed device 'naa.50002ac0010d0f6e:2': Not supported
vmkernel: cpu10:11813)FSS: 4972: No FS driver claimed device 'naa.50002ac000ea0f6e:2': Not supported
vmkernel: cpu8:11813)VC: 1591: Device rescan time 71448 msec (total number of devices 59)
vmkernel: cpu8:11813)VC: 1594: Filesystem probe time 786 msec (devices probed 24 of 59)

First off i found that Device ID 214 was visible on the vSphere host. but Device ID 169 was not.

I’ve had a nice talk with VMWare support about this and their conclusion, somewhere in the storage controller the LUN is published to the vSphere hosts twice, causing the LUN to be found two times. However, it seems that the lower Device ID is somehow hidden when the higher Device ID is found, causing the VM to be locked on hosts that know about both ID’s.

Leave a Reply

Your email address will not be published. Required fields are marked *