VMware Cloud Community
zgz87
Contributor
Contributor

Failing registration of device

Hi,

My host was disconnected from vCenter due to connectivity issues with the storage. I am trying to connect it back but it is stuck with the state "In progress". If I go to the esxi CLI and read the output of /var/log/vmkernel.log, I can see the next messages repeating and repeating:

2012-10-22T08:12:58.386Z cpu2:2175)ScsiDevice: 3084: Failing registration of device 'sym.029260367230314444': failed to acquire legacy uid on path vmhba38:C0:T10:L4: Busy

2012-10-22T08:12:58.387Z cpu2:2175)WARNING: NMP: nmp_RegisterDevice:96:Registration of NMP device with primary uid 'sym.029260367230314444' failed. Busy
2012-10-22T08:12:58.387Z cpu2:2175)VMW_SATP_INV: satp_inv_UpdatePath:749: Failed to update path "vmhba38:C0:T0:L4" state. Status Transient storage condition, suggest retry
2012-10-22T08:12:58.387Z cpu2:2175)VMW_SATP_INV: satp_inv_UpdatePath:749: Failed to update path "vmhba38:C0:T3:L4" state. Status Transient storage condition, suggest retry
2012-10-22T08:12:58.387Z cpu2:2175)VMW_SATP_INV: satp_inv_UpdatePath:749: Failed to update path "vmhba38:C0:T2:L4" state. Status Transient storage condition, suggest retry
2012-10-22T08:12:58.387Z cpu2:2175)VMW_SATP_INV: satp_inv_UpdatePath:749: Failed to update path "vmhba38:C0:T1:L4" state. Status Transient storage condition, suggest retry
2012-10-22T08:12:59.634Z cpu10:2175)WARNING: NMP: nmpPathClaimEnd:1195:Device, seen through path vmhba38:C0:T1:L4 is not registered (no active paths)
2012-10-22T08:12:59.635Z cpu10:2175)VMW_SATP_INV: satp_inv_UpdatePath:749: Failed to update path "vmhba38:C0:T0:L3" state. Status Transient storage condition, suggest retry
2012-10-22T08:12:59.635Z cpu10:2175)VMW_SATP_INV: satp_inv_UpdatePath:749: Failed to update path "vmhba38:C0:T3:L3" state. Status Transient storage condition, suggest retry
.
The CLI is responds very slowly, showing that it is doing something that requires a lot of processing... What could I do?
Thanks in advance!
0 Kudos
1 Reply
Sreejesh_D
Virtuoso
Virtuoso

Whats the ESX\ ESXi version?

there is a knows issue with ESXi 4.0 which is fixed in 4.1 Please refer http://kb.vmware.com/kb/1010570.

I would recommend a reboot of the host if there is no running VMs in it. That would be the easier remedy for such storage problems.

0 Kudos