Best SATA SSD for a homelab boot mirror and app pool

A boot mirror keeps a dead SSD from turning into a reinstall evening. An app pool has a harder job: databases, containers and VMs can keep writing long after the machine has finished booting. Buy for the job the drives will actually do.

Choose the Micron 5400 PRO 960GB for a write-sensitive app or VM pool with documented power-loss protection. Choose WD Red SA500 1TB for NAS-focused SATA storage. Keep Samsung 870 EVO 1TB on the list for a light-duty boot role or a healthy-drive reuse project. Kingston DC600M is another enterprise option with documented hardware PLP and published per-capacity endurance.

Specifications from Samsung, WD, Micron and Kingston; mirror setup from Proxmox and TrueNAS documentation, checked October 25, 2026.

Compare the exact SATA SSDs

These are 2.5-inch SATA drives. The capacity and part number matter: a larger member of the same family can have a different endurance rating.

Drive and fit	Capacity, endurance, DRAM, PLP and warranty
Micron 5400 PRO: choose it for an app or VM pool where protecting writes through a power interruption is a priority.	960GB, model MTFDDAK960TGA-1BC16ABYYR, TCG Enterprise variant. 2,628TBW for the PRO capacity; enhanced power-loss data protection with capacitor monitoring. DRAM details aren’t specified in the cited technical sheet. Standard five-year data-center warranty, with shipment-date and wear terms.
WD Red SA500: choose the NAS-focused SATA family when you want a mirrored SSD pool for suitable NAS workloads.	1TB, WDS100T1R0A, 600TBW. The maker brief doesn’t specify DRAM or hardware PLP. Five-year limited warranty. This is the cased SATA model, not the M.2 version.
Samsung 870 EVO: choose a consumer SATA drive for a light-duty boot role, with a clearly documented DRAM cache.	1TB, MZ-77E1T0B/AM, 600TBW, 1GB LPDDR4 DRAM. Hardware PLP isn’t specified in the datasheet. Five years or 600TBW, whichever comes first. Samsung lists client PCs as the intended application.
Kingston DC600M: an enterprise alternative when you want hardware PLP and an explicit server-workload endurance rating.	960GB, SEDC600M/960G, 1,752TBW, 1 DWPD over five years. DRAM: yes; hardware PLP: yes. Limited five-year warranty, ending earlier at the specified SSD wear-indicator limit.

The capacity-specific figures come from the Samsung datasheet, WD product brief, Micron technical datasheet hosted by Mouser and Kingston datasheet. An unspecified DRAM field doesn’t mean the drive is DRAM-less; it means that detail isn’t part of these published specifications.

Consumer, NAS or enterprise: where the difference matters

For a busy Proxmox VM/app pool, start with the enterprise choice. Proxmox’s recommended system requirements recommend SSDs with power-loss protection and discourage consumer SSDs. Micron’s documented PLP is the decision-changing feature here, alongside its write budget.

A NAS label answers a different question. WD positions the SA500 for NAS use, including cache and other demanding NAS workloads. That makes it a NAS-focused SATA option; use the platform’s compatibility list and storage role to decide where it belongs. For a pool running write-sensitive databases, the explicitly documented PLP on the enterprise drives is the stronger fit.

The 870 EVO is the consumer option. Its 1TB specification includes 1GB of DRAM and 600TBW, making the hardware details easy to understand. A light-duty boot drive and a VM datastore are different assignments, so don’t turn a boot recommendation into a claim that every consumer SSD suits sustained server writes.

DRAM and power-loss protection are separate features. A DRAM cache entry alone doesn’t tell you how the drive protects pending writes when power disappears. Micron documents enhanced power-loss protection with capacitor monitoring; Kingston explicitly lists hardware PLP. Keep the host on a UPS too—the SSD feature and a clean system shutdown do different jobs.

Do you actually need a boot mirror?

A mirror makes sense when you want to keep operating after one member fails and avoid rebuilding the host just to replace its boot drive. It also needs a recovery plan: firmware must be able to boot from the surviving drive, and you still need saved configuration and backups.

With two identical 1TB drives, a mirror has 1TB nominal usable capacity before filesystem overhead, not 2TB. Proxmox’s ZFS documentation describes RAID1 as identical writes to all members, with the capacity of a single disk. Both SSDs receive the writes; buying a pair doesn’t double the per-drive endurance budget.

For TrueNAS boot only, don’t buy capacity you won’t use. The hardware guide recommends a 20GB minimum boot volume and describes mirrored 2.5-inch boot drives. A 1TB SSD is far beyond that capacity requirement. Healthy drives you already own may be a sensible boot project; reserve the larger SSD pool for the apps and data that need it.

Keep the TrueNAS boot pool and the app/data pool as separate purchases and setup decisions. Proxmox has a different documented installer layout: its ZFS root installation creates an rpool/data subvolume for VM images as well as the root filesystem. Follow the layout for your platform rather than copying partitions from another guide.

Our ZFS vs mdadm vs hardware RAID guide covers the wider storage-stack decision. A mirror helps with drive failure; keep an independent backup for deletion, corruption and recovery mistakes.

Endurance math: how fast will you spend the write budget?

TBW is the published total-bytes-written rating. DWPD expresses daily writes relative to drive capacity over the specified period. Kingston publishes one drive write per day over five years for the 960GB DC600M.

For a worked estimate, assume 500GB written to each SSD every day, use decimal GB/TB and a 365-day year:

Years to consume TBW = TBW × 1,000 ÷ (GB written per drive per day × 365)

Selected capacity	Published TBW	Years to consume TBW at assumed 500GB/day
870 EVO 1TB	600TB	3.29
SA500 1TB	600TB	3.29
5400 PRO 960GB	2,628TB	14.40
DC600M 960GB	1,752TB	9.60

At an assumed 100GB/day, five years adds up to 182.5TB per drive. At 500GB/day, it is 912.5TB. Measure writes reaching the SSDs, including filesystem and VM overhead, when choosing which assumption resembles your workload.

This is write-budget arithmetic, not a service-life forecast; maker test workloads differ, and the calendar/wear warranty limits still apply. Micron’s standard warranty runs from shipment by Micron and can end at its wear limit, so the 14.40-year calculation doesn’t extend the warranty. Its product page describes the standard five-year data-center warranty.

The useful takeaway: light writes can leave plenty of endurance headroom. For a busy pool, buy the endurance and power-loss features your workload calls for instead of judging the drive by capacity alone.

SATA still earns its drive bay

Choose SATA when you have suitable bays, power connectors and SATA ports available, especially when the M.2 sockets already have jobs. The drives here use the SATA interface; they don’t need a PCIe bifurcation setting or an NVMe adapter.

Use the NVMe boot-drive guide if you’re still choosing the interface. For an app pool or a dedicated cache device, our NVMe cache and app-pool guide explains those roles without treating every spare SSD as cache.

Count the SATA ports and power plugs before buying a mirrored pair. Our SATA/HBA expansion guide covers adding connections, while the DIY NAS case guide helps with bays, cooling and cable space. Use the NAS hard-drive guide for the bulk-storage side of the build.

Mirror setup: a short checklist

1. Choose the role and matching pair. Decide whether these are boot devices or app/data storage. Save the host configuration, encryption/recovery material and an independent backup before changing disks.
2. Record the hardware. Note exact models, capacities and serial numbers; check firmware using the maker’s supported tools. Label the bays so a later replacement targets the right SSD.
3. Give ZFS direct disk access. Proxmox says to avoid layering ZFS over a hardware RAID controller with its own cache management. Use a suitable direct SATA or HBA path.
4. Follow the installer for your platform. In Proxmox, use the installer options to choose ZFS RAID1 and the intended pair. In the TrueNAS installer, use Spacebar to select more than one boot drive for a mirror. Installation erases the selected disks, so match their identities before accepting.
5. Use the supported attach route for an existing TrueNAS boot pool. The boot-pool management guide shows the device actions menu, Attach, Member Disk and Save. Monitor the pool until it is healthy before another disk change.
6. Test recovery while you have time. During planned maintenance, verify the firmware’s surviving-drive boot path, pool health and configuration restore. Check again after relevant firmware or bootloader changes; a healthy mirror and a usable boot path both belong on the acceptance list.

For a write-sensitive app pool, Micron 5400 PRO is the enterprise pick here. WD Red SA500 gives you a NAS-focused SATA option; Samsung 870 EVO fits the light-duty boot/reuse end. Choose the role first, then buy the pair that fits it.