AORXI Homelab
Hardware

RAM & Storage Allocation

RAM pool distribution across Supermicro hosts and storage plans for Site A ZFS and Site B Ceph.

RAM and storage are split by role: 17 × 32 GB DDR4 ECC RDIMMs are distributed across Supermicro hosts; ThinkPads use their own SO-DIMM inventory. Storage divides between sa-stor-01 running ZFS at Site A and a five-node Ceph cluster at Site B.

RAM

32 GB RDIMM Pool

Seventeen 32 GB DDR4 ECC RDIMM sticks cover all Supermicro hosts except sa-stor-01, which carries its own installed memory. ThinkPads (sa-cmp-01, sa-cmp-02) cannot accept RDIMM server RAM and are excluded from this pool.

HostSticksTotalSite
sa-edge-012 × 32 GB64 GBSite A
sb-edge-012 × 32 GB64 GBSite B
sb-cmp-01 (FN8TP #1)3 × 32 GB96 GBSite B
sb-cmp-02 (FN8TP #2)3 × 32 GB96 GBSite B
sb-cmp-03 (FN4T #1)3 × 32 GB96 GBSite B
sb-cmp-04 (FN4T #2)2 × 32 GB64 GBSite B
sb-cmp-05 (FN4T #3)2 × 32 GB64 GBSite B
Total17 × 32 GB544 GB

To bring every non-5049A-T Supermicro host to 128 GB, 28 × 32 GB sticks are needed — 11 more than the current 17.

sa-stor-01 Memory

sa-stor-01 (Supermicro 5049A-T, X11SPA-T board) has 96 GB installed: 6 × 16 GB DDR4-2933 ECC RDIMM (PC4-23400).

Tentative — upgrade path not yet confirmed

Three upgrade options are under consideration. None has been ordered or finalized.

OptionChangeResulting total
AAdd 6 × 16 GB DDR4-2933 ECC RDIMM (matching sticks)192 GB
BAdd 6 × 32 GB DDR4-2933 ECC RDIMM288 GB
CReplace all with 12 × 32 GB DDR4-2933 ECC RDIMM384 GB

Do not mix RDIMM and LRDIMM in the same system. Avoid asymmetric single-stick upgrades.

Storage

Drive Inventory

ModelCapacityCountForm factor
Samsung SM8631.92 TB20SATA SSD
Micron 5200 MAX1.92 TB10SATA SSD
Micron 5300 Pro1.92 TB8SATA SSD
Samsung 512 GB NVMe M.2512 GB5NVMe M.2
Samsung SM9A1512 GB1NVMe M.2
Micron 1300512 GB1SATA M.2

Boot Drives

All Proxmox hosts use 512 GB M.2 drives as boot volumes. sa-stor-01 already has a boot drive installed.

Never use enterprise SSDs for boot

1.92 TB drives — Samsung SM863, Micron 5200 MAX, Micron 5300 Pro — are entirely allocated to ZFS vdevs and Ceph OSDs. None should be used as a boot drive.

HostBoot drive
sa-stor-01Existing boot drive (installed)
sa-edge-01512 GB NVMe M.2
sb-edge-01512 GB NVMe M.2
sb-cmp-01512 GB NVMe M.2
sb-cmp-02512 GB NVMe M.2
sb-cmp-03512 GB NVMe M.2
sb-cmp-04512 GB M.2 (NVMe or SATA)
sb-cmp-05Micron 1300 512 GB SATA M.2

Site A — ZFS on sa-stor-01

sa-stor-01 runs ZFS mirror vdevs using Samsung SM863 1.92 TB drives. This pool backs Proxmox Backup Server (PBS-A), DNS VMs, monitoring, databases, and core infrastructure VMs.

Drive countZFS layoutMirror vdevs
84 × mirror-24
126 × mirror-26

See Site A ZFS for pool creation and dataset layout.

Site B — Ceph

Ceph runs across five Site B nodes with 20–30 OSDs total and replication size 3. Each node contributes 4–6 × 1.92 TB enterprise SSDs.

HostPlatformSSDs per node
sb-cmp-01SYS-5019D-4C-FN8TP4–6
sb-cmp-02SYS-5019D-4C-FN8TP4–6
sb-cmp-03SYS-5018D-FN4T4–6
sb-cmp-04SYS-5018D-FN4T4–6
sb-cmp-05SYS-5018D-FN4T4–6

Drive model selection follows workload type:

ModelRecommended use
Micron 5200 MAX 1.92 TBWrite-heavy OSDs and workloads
Micron 5300 Pro 1.92 TBVM storage and Kubernetes persistent volumes
Samsung SM863 1.92 TBFlexible — remaining OSDs or cold spares (reserve 2–4 drives)

See Site B Ceph for OSD layout and pool configuration.

On this page