VSAN Weird Issue

[Ahmad313]

Hello Everyone,

i'm facing quiet a weird issue with VSAN, and hoping someone could clarify.

I was recently trying VSAN, installed ESX 6 on 3 hosts, enable VSAN traffic and created Storage Policy

Everything seems well, vsan claims 2 disks from every host

i created a disk group on the first and it automatically got created on the remaining 2 hosts

All disks show as in use

But when i create a VM on vsanDatastore or move a vm there, i get this error:

"Cannot complete file creation operation. The policy requires 3 hosts contributing storage, only found 2 in the cluster. failed to create object"

As far as i know, all 3 hosts are contributing storage.

See below for screenshots:

Could it be related to disk size ?

Many thanks !!

Best Regards

Ahmad

[Ramakrishna Kempaiah]

this seems like only two hosts are part of the vsan cluster.

can you confirm this by looking at

vsan cluster -> Mange -> Disk Management -> { look at the column for Network partition}

All 3 hosts should be in the same group

you can also check by running esxcli vsan cluster info on the host

Thanks,

[Ramakrishna Kempaiah]

you can also check by login to VC run the following rvc cmd

> vsan.disks_stats 1/<datacenter>/computers/<vsancluster>

this will give you details on all the disks used and health status of the vsan cluster

Thanks,

[Ramakrishna Kempaiah]

did your issue get resolved ?

either the former comment on the network partitions or the disks from the CMMDs entry is false might be causing this.

you can check this by this following command on each esxi host and see all the disks shows in CMMDS: true.

# esxcli vsan storage list

Used by this host: true

   In CMMDS: false  <===== issue where the disks is not participating in vSAN storage.

also check Re: vSAN weirdness.....Policy ?

Thanks

[Ahmad313]

Hello ramakrishnakramakrishnak,

Sorry for the late reply

i did get this issue resolved ,

i sshed to the vcenter appliance and noticed that the vsan is only seeing 2 hosts

i digged more and found out that one of the disks in the disk group of one of the hosts isn't healthy

it turned out to be a raid problem, once i corrected it and rebooted the server everything was fine !

Thanks a lot for your help

Ahmad

[Ramakrishna Kempaiah]

Thanks Ahmad.

good to know you were able to resolve the issue :smileyhappy: