Handling VSAN Ineligible Disks16 Jul 2015
If you are reusing a server and \ or disks which will become a VSAN cluster you may find some of your disks show as ineligible. In the Cluster, Manage tab, Virtual SAN, Disk Management section.
Disks in this state cannot be used for adding to VSAN cluster, the most common reason is pre-existing partition data on the disks. If you not down all of the device ids listed as ineligible with issue ‘Existing partition found on disk…’, then open a SSH connectoin to ESXi.
First you will need to identify which of these devices is in use as the ESXi boot partition, to do this we issue a command to give information about the root volume
This should return assorted information but the important part for us is the path starting /vmfs/volumes/
Once we know the volume UID we can then check which device it is located on by issuing this command
This returns the device ID and partition this volume is housed.
We want to ensure that we don’t remove the partitions from this ESXi boot disk, but for all of the other devices we can go ahead and check the partition table.
On attempting to get the partition you may get an error “Error: Can’t have a partition outside the disk!” if this occurs create a simple gpt partition.
If this still errors with “Error: Can’t have a partition outside the disk!” then you can look to fix the gpt table
This should fix the partition which you then get and remove.
This should return a list of the partitions on the disk for us to remove.
You can then use the following command to remove the partitions, you run this once for every partition
These changes are not quick to populate into VSAN, to encourage this to be picked up quicker refreshing the storage adapter
Repeat this until the only ineligible Disk is the one you use for ESXi boot device, obviously if you boot from SD Card then you should show with zero ineligible Disk.