Should this work?

[John Corbin]

I have a 3 node physical cluster I am trying to use as a home lab. I have used to study for VCP twice. I have not run across any features that do not work until now, vSAN

each has:

ASUS M5A78L-M LX PLUS mobo has a AMD SB710 SATA Controller

AMD FX8320e CPU      

Ballistix DDR3 32GB RAM

SanDisk Cruzer 8gb  ESXi installed on

AData SU650 120gb SSD (cache)

AData SU650 480gb SSD (Capacity)

I can create VMFS data stores on all disks

I have used these same disks in FreeNAS to create 2 NFS shares and run VM's from that share

I have used gparted to wipe any partition off the disks

I installed ESXi 6.7 on each host

I then tried to deploy vCenter and create a vSAN as part of that.  I iterated to each host and can see both disks on every host, but none of the hosts will create the vSAN, I get the LSOM error when creating the data store. I end up with a vsanDatastore that has 0 bytes Capacity

I repeated install,  enabled NTP,  set to start with host and restarted host then tried vcenter install again same result

I changed the BIOS settings to controller type of IDE, RAID and AHCI and same results

I turned on the RAID controller and set to JBOD and same result

I have built vSAN on nested (on my laptop) and in my job (test lab)

Am I having a HCL issue? The mobo I admit is not on the HCL, so I understand it MAY not work but not sure how to 100% determine

IF that is the case what PCI controller could I put in that would likely work??

thanks in advance

john

[IT_pilot]

I did not find the AMD SB710 SATA Controller in the vSAN compatibility list. And in the compatibility list ESXi only version 5.1. https://www.vmware.com/resources/compatibility/pdf/vi_vsan_guide.pdf

  You have correctly indicated the name. Most likely this is the case.

Did you make the installation according to the instructions? The vSAN traffic in the interface properties included?

[TheBobkin]

Hello John,

Welcome to Communities.

"I iterated to each host and can see both disks on every host, but none of the hosts will create the vSAN, I get the LSOM error when creating the data store. I end up with a vsanDatastore that has 0 bytes Capacity"

What error? Please attach copy/screenshot of Web Client error and clomd.log + vmkernel.log from a host.

The 1st thing to check is whether the 2 vsan partitions are being created on each disk (Host > Configure > Storage Devices > Select Device > scroll down).

If they are then verify that the Disk-Groups are being created via CLi  #vdq -Hi and #esxcli vsan storage list (all should be 'In CMMDS: true'). If this is all bueno then check the cluster is formed of all three members #esxcli vsan cluster get

"I changed the BIOS settings to controller type of IDE, RAID and AHCI and same results

I turned on the RAID controller and set to JBOD and same result"

RAIDed how? Exposing as Passthrough or every device as an individual RAID0 Virtual Disk are the two modes supported for vSAN (and which one(s) depends on the controller/driver/firmware).

"IF that is the case what PCI controller could I put in that would likely work??"

There were lower-end HCL-Compliant controllers to be found for ~€150 (new, less pre-loved) last I priced, not sure what is cheapest for 6.7 though - controller is potentially not your issue here but probably any real controller will function better than onboard.

Bob

[John Corbin]

Yes 2 partitions were being created on each disk - I checked all 6 and they were all there.

RAID - I set them as individual RAID0 disks using the onboard controller.

Each host would end up with a vSan datastore but I do not know about the forming of the cluster.

I will have to reset all and recreate in order to do the CLI commands, I'm learning as we go here so thank you for those.

Error:

2018-07-18T16:33:56.192Z - error: No VM found with hostname 192.168.0.200

2018-07-18T16:33:56.192Z - debug: Error in getVmWithIPFQDN: No VM found with hostname 192.168.0.200

2018-07-18T16:33:56.192Z - info: Network Prechecks Succeededundefined

2018-07-18T16:33:56.211Z - debug: scope.networkPrefixLabel: Subnet mask or prefix length

2018-07-18T16:33:56.212Z - debug: Summary page: summaryTargetLabel: Target ESXi host

2018-07-18T16:33:58.512Z - debug: sucMsg: You have successfully deployed the vCenter Server with an Embedded Platform Services Controller.

2018-07-18T16:34:01.657Z - debug: Tracking task:

2018-07-18T16:34:01.657Z - debug: [object Object]

2018-07-18T16:34:04.654Z - debug: Tracking task:

2018-07-18T16:34:04.654Z - debug: [object Object]

2018-07-18T16:34:07.646Z - debug: Tracking task:

2018-07-18T16:34:07.646Z - debug: [object Object]

2018-07-18T16:34:10.659Z - debug: Tracking task:

2018-07-18T16:34:10.659Z - debug: [object Object]

2018-07-18T16:34:13.653Z - debug: Tracking task:

2018-07-18T16:34:13.653Z - debug: [object Object]

2018-07-18T16:34:18.663Z - debug: VSAN is enabled.

2018-07-18T16:34:19.693Z - debug: vsphere returned vsanService

2018-07-18T16:36:25.802Z - error: Error occurred in bootstraping VSAN: A general system error occurred: Unable to create LSOM file system for vSAN disk t10.ATA_____ADATA_SU650_____________________________2I1620030028________ please see VMkernel log for more details

2018-07-18T16:36:25.802Z - debug: A general system error occurred: Unable to create LSOM file system for vSAN disk t10.ATA_____ADATA_SU650_____________________________2I1620030028________ please see VMkernel log for more details

2018-07-18T16:36:25.810Z - info: Cancelling the ping timer for session mgmt

2018-07-18T16:43:05.717Z - info: Log file was saved at: C:\Users\johnj\Desktop\installer-20180718-113202966.log