jgreco
Resident Grinch
- Joined
- May 29, 2011
- Messages
- 18,680
That’s right. I only had six SATA ports, no hba, so the entire SATA controller was passed into FreeNAS leaving NO Sata ports for ESXi! and I needed a place for the FreeNAS vm boot image. M.2 is overkill, but was the best solution to my problem. Evo drives were cheap/reliable.
In a full size build I’d probably be using an HBA for FreeNAS, and that’d leave a lot of motherboard SATA for ESXi. Then I would use a 2.5” ESXi datastore SSD. Best practice for ESXi is to boot off a USB. In an enterprise scenario ESXi boot usbs are disposable/replaceable and a created with scripts. In a once off install, it probably makes sense to just boot off the primary datastore.
M.2 would probably get used for an optane slog. 900p?
I was kinda curious here why you wouldn't pass the SATA ports through to FreeNAS and use a RAID controller for ESXi datastores. Then I realized that a lot of people here probably have nonredundant datastores for their ESXi.
If your mainboard has sufficient SATA/SAS for your NAS deployment, a better ESXi strategy is to pass those to FreeNAS, and then use something like an LSI 9270CV-8i for your ESXi datastores. These are available dirt cheap on eBay from time to time and will give you much better I/O performance in ESXi. The mainboard SATA are also more competent at things like SSD, so if you're doing SSD with FreeNAS, that's the way to go.
I'm not sure who said it was best practice for ESXi to boot off USB. It's supported but it sucks for a lot of the same reasons FreeNAS 8 and 9 sucked booting that way. If you want nonredundant ESXi boot, use SLC SATADOM. If you want redundant ESXi boot, do it via DAS RAID1. It probably doesn't matter if you have a rack full of hypervisors running VM's off a SAN array, where the loss of a hypervisor is a *shrug* and vSphere just spins them up on a different hv, but where reliable booting of ESXi is required, USB is definitely *not* recommended.