Hello everyone,
I have a cluster with 4 hosts with ESXI 5.0. They are connected with one storage using fiber channel and the VMs are now in a Unknown state.
Before this problem, everything was working just fine. Reading a lot in the forum and in the internet I found something about removing the VMs from the inventory and adding it again. But the problem is that now the hosts can't access the storages anymore and I couldn't find the VM files. Very strange since everything was ok. Following this article http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&externalId=1003659 and trying to found out what is wrong I tried to rescan without success.
Here is the log of /var/log/vmkernel.log
2013-02-19T14:47:32.456Z cpu15:4111)ScsiDeviceIO: 2322: Cmd(0x412440bb1200) 0x12, CmdSN 0x2aa8 from world 0 to dev "naa.600508e0000000007ab1c149b4a15a02" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.
2013-02-19T14:52:32.456Z cpu15:4111)ScsiDeviceIO: 2322: Cmd(0x412440c5ebc0) 0x12, CmdSN 0x2aaa from world 0 to dev "naa.600508e0000000007ab1c149b4a15a02" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.
2013-02-19T14:57:32.455Z cpu14:4110)ScsiDeviceIO: 2322: Cmd(0x412440c5ebc0) 0x12, CmdSN 0x2aac from world 0 to dev "naa.600508e0000000007ab1c149b4a15a02" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.
2013-02-19T15:02:32.454Z cpu2:4098)ScsiDeviceIO: 2322: Cmd(0x412400ef91c0) 0x12, CmdSN 0x2ab8 from world 0 to dev "naa.600508e0000000007ab1c149b4a15a02" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.
2013-02-19T15:07:32.454Z cpu4:4100)ScsiDeviceIO: 2322: Cmd(0x412400ef91c0) 0x12, CmdSN 0x2aba from world 0 to dev "naa.600508e0000000007ab1c149b4a15a02" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.
2013-02-19T15:12:32.453Z cpu20:4780)ScsiDeviceIO: 2322: Cmd(0x412440d61480) 0x12, CmdSN 0x2abc from world 0 to dev "naa.600508e0000000007ab1c149b4a15a02" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.
2013-02-19T15:17:32.452Z cpu8:4104)ScsiDeviceIO: 2322: Cmd(0x412400381800) 0x12, CmdSN 0x2abe from world 0 to dev "naa.600508e0000000007ab1c149b4a15a02" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.
2013-02-19T15:22:32.452Z cpu6:4102)ScsiDeviceIO: 2322: Cmd(0x4124003e9c00) 0x12, CmdSN 0x2acf from world 0 to dev "naa.600508e0000000007ab1c149b4a15a02" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.
2013-02-19T15:27:32.451Z cpu2:4098)ScsiDeviceIO: 2322: Cmd(0x412400384500) 0x12, CmdSN 0x2ad1 from world 0 to dev "naa.600508e0000000007ab1c149b4a15a02" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.
2013-02-19T15:32:32.451Z cpu2:4098)ScsiDeviceIO: 2322: Cmd(0x412401043040) 0x12, CmdSN 0x2ad3 from world 0 to dev "naa.600508e0000000007ab1c149b4a15a02" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.
2013-02-19T15:37:32.450Z cpu2:4098)ScsiDeviceIO: 2322: Cmd(0x412401043040) 0x12, CmdSN 0x2ad5 from world 0 to dev "naa.600508e0000000007ab1c149b4a15a02" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.
2013-02-19T15:42:32.450Z cpu22:4118)ScsiDeviceIO: 2322: Cmd(0x4124403d44c0) 0x12, CmdSN 0x2ad7 from world 0 to dev "naa.600508e0000000007ab1c149b4a15a02" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.
2013-02-19T15:47:32.449Z cpu12:4108)ScsiDeviceIO: 2322: Cmd(0x412440d64a80) 0x12, CmdSN 0x2ad9 from world 0 to dev "naa.600508e0000000007ab1c149b4a15a02" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.
2013-02-19T15:52:32.448Z cpu18:4268)ScsiDeviceIO: 2322: Cmd(0x4124403dc1c0) 0x12, CmdSN 0x2adb from world 0 to dev "naa.600508e0000000007ab1c149b4a15a02" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.
2013-02-19T15:57:32.447Z cpu20:4116)ScsiDeviceIO: 2322: Cmd(0x4124403d29c0) 0x12, CmdSN 0x2add from world 0 to dev "naa.600508e0000000007ab1c149b4a15a02" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.
2013-02-19T16:02:32.447Z cpu22:4118)ScsiDeviceIO: 2322: Cmd(0x4124403dacc0) 0x12, CmdSN 0x2af8 from world 0 to dev "naa.600508e0000000007ab1c149b4a15a02" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.
2013-02-19T16:06:18.693Z cpu14:5817)Vol3: 647: Couldn't read volume header from control: Invalid handle
2013-02-19T16:06:18.693Z cpu14:5817)FSS: 4333: No FS driver claimed device 'control': Not supported
2013-02-19T16:06:18.725Z cpu14:5817)VC: 1449: Device rescan time 14 msec (total number of devices 6)
2013-02-19T16:06:18.725Z cpu14:5817)VC: 1452: Filesystem probe time 42 msec (devices probed 5 of 6)
2013-02-19T16:06:18.759Z cpu14:5817)Vol3: 647: Couldn't read volume header from control: Invalid handle
2013-02-19T16:06:18.759Z cpu14:5817)FSS: 4333: No FS driver claimed device 'control': Not supported
2013-02-19T16:06:18.773Z cpu14:5817)VC: 1449: Device rescan time 3 msec (total number of devices 6)
2013-02-19T16:06:18.773Z cpu14:5817)VC: 1452: Filesystem probe time 18 msec (devices probed 5 of 6)
2013-02-19T16:06:18.797Z cpu14:5817)Vol3: 647: Couldn't read volume header from control: Invalid handle
2013-02-19T16:06:18.797Z cpu14:5817)FSS: 4333: No FS driver claimed device 'control': Not supported
2013-02-19T16:06:18.806Z cpu14:5817)VC: 1449: Device rescan time 3 msec (total number of devices 6)
2013-02-19T16:06:18.806Z cpu14:5817)VC: 1452: Filesystem probe time 13 msec (devices probed 5 of 6)
2013-02-19T16:06:18.866Z cpu14:5817)Vol3: 647: Couldn't read volume header from control: Invalid handle
2013-02-19T16:06:18.866Z cpu14:5817)FSS: 4333: No FS driver claimed device 'control': Not supported
2013-02-19T16:06:18.881Z cpu14:5817)VC: 1449: Device rescan time 3 msec (total number of devices 6)
2013-02-19T16:06:18.881Z cpu14:5817)VC: 1452: Filesystem probe time 14 msec (devices probed 5 of 6)
2013-02-19T16:06:18.944Z cpu14:5817)Vol3: 647: Couldn't read volume header from control: Invalid handle
2013-02-19T16:06:18.944Z cpu14:5817)FSS: 4333: No FS driver claimed device 'control': Not supported
2013-02-19T16:06:18.956Z cpu14:5817)VC: 1449: Device rescan time 3 msec (total number of devices 6)
2013-02-19T16:06:18.956Z cpu14:5817)VC: 1452: Filesystem probe time 14 msec (devices probed 5 of 6)
2013-02-19T16:06:19.024Z cpu14:5817)Vol3: 647: Couldn't read volume header from control: Invalid handle
2013-02-19T16:06:19.024Z cpu14:5817)FSS: 4333: No FS driver claimed device 'control': Not supported
2013-02-19T16:06:19.030Z cpu14:5817)VC: 1449: Device rescan time 3 msec (total number of devices 6)
2013-02-19T16:06:19.030Z cpu14:5817)VC: 1452: Filesystem probe time 13 msec (devices probed 5 of 6)
2013-02-19T16:06:19.095Z cpu14:5817)Vol3: 647: Couldn't read volume header from control: Invalid handle
2013-02-19T16:06:19.095Z cpu14:5817)FSS: 4333: No FS driver claimed device 'control': Not supported
2013-02-19T16:06:19.105Z cpu14:5817)VC: 1449: Device rescan time 3 msec (total number of devices 6)
2013-02-19T16:06:19.105Z cpu14:5817)VC: 1452: Filesystem probe time 13 msec (devices probed 5 of 6)
2013-02-19T16:06:19.228Z cpu2:5819)Vol3: 647: Couldn't read volume header from control: Invalid handle
2013-02-19T16:06:19.228Z cpu2:5819)FSS: 4333: No FS driver claimed device 'control': Not supported
2013-02-19T16:06:19.253Z cpu2:5819)VC: 1449: Device rescan time 6 msec (total number of devices 6)
2013-02-19T16:06:19.253Z cpu2:5819)VC: 1452: Filesystem probe time 30 msec (devices probed 5 of 6)
This LUN naa.600508e0000000007ab1c149b4a15a02 is the local disk of the host. In the third step of the article it says to call the vendor of storage. Should I do this or it is somenthing simple, something that I am missing?
Thank you in advance,
Davi