vSAN 2-node Cluster Claim disks

[yma04]

Good afternoon.
We are considering the possibility of launching vSAN 2-node Cluster in vSphere 6.7.
Each node has 2 disk groups.
Difficulty arises at step 2 Claim disks
There is no option for Local NVMe Disk drives (t10.NVMe____SAMSUNG_MZQL27T6HBLA_00A07______________S6CKNT0W700878______00000001) to select tia Flush only Marked ac HDD.
There is also the error The vSAN service is not responding. Check vSphere Client logs for details.

[TheBobkin]

@yma04 Devices can be marked as SSDs (if they are detected as HDDs) using -M flag (--mark-device-ssd=<bool) via:

# esxcli storage hpp device set -d naa.xxxxxxxxxxxxxxxx -M true

Question though: why are you considering using ESXi/vSAN 6.7? I would advise using minimum of ESXi/vSAN 7.0 U3

[yma04]

@TheBobkin  On the hypervisor, the disk is identified as Flash. (screenshot 2)
When setting up vSAN, 6.99 TB disks cannot be marked as 'Capacity tier' until the 'Drive Type' is changed to 'Marked ac HDD'. (screenshot1)
At the same time, disks for cache - Samsung_SSD _980_500 GB are available for selecting the Flash option. (screenshot 1)

There is only 6.7. No longer purchased. Is it better to use version 7? There is no stability on version 6.7 or what is the reason?

[TheBobkin]

@yma04 , Please learn how to use Snipping Tool - you have shared far too much private information in your first screenshot and should promptly delete it.

Is this a production cluster or a home-lab?
If the former then you shouldn't be using consumer-grade Samsung 980 devices here (NOT on the vSAN HCL), while this might allow configuration and use of these, you will regret this in the long-term when/if resulting in data-loss.

In your screenshot you have mix of devices marked as HDD and SSD, this won't allow this, need to be all of the same type.

[yma04]

@TheBobkin  Thank you, screenshots were deleted, uncropped was added by mistake.
At the moment, we used Samsung 980 drives for testing. For production, another model will be purchased.

We just have a problem that the NVMe 6.99 TB disk cannot be marked as flush when configuring vSAN. The only option available is to mark it as HDD (for Local NVMe Disk (t10.NVMe____SAMSUNG_MZQL27T6HBLA_00A07______________S6CKNT0W702682______00000001)), and Samsung 980 devices (test) drives are available - mark as Flash.

[yma04]

@TheBobkin on ESXI disks are defined as flash. (screenshot3)
But when trying to create vSAN, there is no way to mark it as Flash. Only as HDD.

[yma04]

@TheBobkin 

That was done:

# esxcli storage hpp device set -d naa.xxxxxxxxxxxxxxxx -M true      

esxcli storage hpp device set -d t10.NVMe____SAMSUNG_MZQL27T6HBLA_00A07______________S6CKNT0W702682______00000001 -M true
Error setting SSD mark: Unable to complete Sysinfo operation. Please see the VMkernel log file for more details.: Sysinfo error: FailureSee VMkernel log for details.

VMkernel log:

24-04-06T16:17:53.825Z cpu49:2100405 opID=e8922b05)ScsiDevice: 11938: Device t10.NVMe____SAMSUNG_MZQL27T6HBLA_00A07______________S6CKNT0W702682______00000001 is by default SSD

[depping]

Do you already have existing "hybrid" disk groups?

[yma04]

No. I can’t proceed to setting up disk groups, because the NVMe____SAMSUNG_MZQL27T6HBLA_00A07 disks cannot be marked with the Capacity tier when assembling the VSAN 6.7.

I want to build an all-flush using Nvme disks

https://europe.kioxia.com/ru-ru/business/ssd/enterprise-ssd.html#pm-series   --  Cache tier

NVMe____SAMSUNG_MZQL27T6HBLA_00A07   -- Capacity tier

[depping]

Contact support and let them have a look, assuming it is a production environment and all components are supported.