Welcome to vSAN Communities, I hope you find some good info on this forum.
Are you by any chance using 6.0/6.2 vSAN Standard or ROBO licensed hosts?
All-Flash was/is not a licensed-feature of these (in vSAN 6.5 Standard edition it is).
Do they show as marked after marking them when you run vdq -q?
Are you able to use them as capacity before you reboot (and this is removed)?
Where are you marking them as Capacity from?
Try from CLI:
all Hosts are on Version 6.5 with Standard License.
They do show marked in vdq -q, as I show you here:
"Name" : "naa.5002538d40d3f9a5",
"VSANUUID" : "",
"State" : "Eligible for use by VSAN",
"Reason" : "None",
"IsSSD" : "1",
"IsPDL" : "0",
I marked them with the CLI, now I tried it with RVC too but it doesn't work, there is no selection for the Disks as Capacity.
Is the vCenter/vCSA managing this cluster also on version 6.5?
Is Auto-claim of disks disabled? (Yes I know you likely wouldn't see cache nor anything nor be able to open 'create disk' if this is enabled but still)
After marking them as Capacity-Flash are you able to create a disk-group from the CLI using:
# esxcli vsan storage diskgroup mount -s <naa of cache-tier SSD> -d <naa of 1st capacity-tier SSD> -d <naa of 2nd capacity-tier SSD>
If this fails, does it give an error message and if not (specific) then please post the vmkernel.log and clomd.log from when this occurred (both located in /var/log/ ).
What model of controller and SSDs are you using here and what is the mode on the controller? (e.g. pass-through or RAID0)
auto claim is disabled, yes. The command that you said doesn't worked for me, but it is not that far away from the right answer.
I found the solution for this because of this command!
I managed to create a SSD Cache and SSD Capacity with following command:
esxcli vsan storage add -s naa.xxx-d naa.xxx
While this appears to have been solved by the original poster via the CLI, I am seeing this same thing on a 6.7U1 environment. I can use the exact same hardware on 6.5 and when going through to setup VSAN you can select both capacity and cache disks just fine. If I install 6.7 on the same hardware, the ability to select capacity is absent and also missing is the ability to select Dedupe and Compression at the beginning of the wizard. This looks like it might be a bug?
Welcome to Communities.
Are you perchance using a 6.7 pre-U1 vCenter and 6.7 U1 hosts?
I saw this recently with a customer that various things didn't function when configuring the cluster due to this unsupported setup (and it worked fine after updating the vCenter to 6.7 U1).