VM Inaccessible

[Anupreet01]

After RAID was rebuilt (lost 2 disks) we are experiencing issues with seeing some of the VMs in the vCenter console. Two out of 5 show up. Wondering if there is a way to recover the other ones. I can log into the VMs that are missing from vCenter console so I know they are at least alive.

[a_p_]

I can log into the VMs that are missing from vCenter console ...

How can you login into missing VMs? Can you please explain this and/or provide some more details?

What RAID level do you use?

André

[Kahonu84 · Accepted solution]

If you can see them in the Datastore Browser, re-add them to your inventory.

[chungyl]

I got the same situation, VMFS failed to mount due to 8k bad sector.

I using ddrescue to clone the partition to another new disk, now add the datastore back without assign new signature.

Another problem facing is all the VM is locked and no way to add back to inventory list.

/vmfs/volumes/4f48a73b-19854499-46ae-14dae9991e03/FreeNAS # touch *

touch: FreeNAS-066caf3a.vswp: Invalid argument

touch: FreeNAS-flat.vmdk: Invalid argument

touch: FreeNAS.nvram: Invalid argument

touch: FreeNAS.vmx: Invalid argument

touch: FreeNAS_1-flat.vmdk: Invalid argument

touch: FreeNAS_2-flat.vmdk: Invalid argument

touch: vmware-32.log: Invalid argument

touch: vmware-34.log: Invalid argument

touch: vmware.log: Invalid argument

touch: vmx-FreeNAS-107786042-1.vswp: Invalid argument

touch: vmx-FreeNAS-107786042-2.vswp: Invalid argument

Any idea how to unlock it ? Thanks in advance.

[AndreTheGiant]

Which kind of controller do you have? (I suppose is a local storage)

[chungyl]

Local storage also....(SATA Drive)

[AndreTheGiant]

Check controller firmware and don't use a write back cache policy unless you have a controller battery.