Home Server From Spare Parts: Avoid Ryzen 3400G B550 Mismatches and Check Proxmox Hardware

MakeUseOf writer Dipan Saha describes an AM4 server built around a Ryzen 3400G and a B550M micro-ATX board. He says the small board ran out of expansion slots. That part is plausible. The pairing itself is a problem, though.

The 3400G and B550 problem​

AMD's AM4 compatibility table lists B550 as not compatible with Ryzen 3000 Series Processors with Radeon Graphics, while X570 is marked compatible. The 3400G is a 3000-series APU, so it falls in that category. TechPowerUp's coverage of the B550 launch makes the same point: B550 supported 3rd-gen "Matisse" processors, and Ryzen 3000 "Picasso" APUs were not supported.

Practical takeaway:

• Check the exact motherboard model's CPU-support list and required BIOS version before you buy or reuse a board.
• Don't treat "it's AM4, so it fits" as a guarantee.
• If your spare CPU is an older APU, an X570 board is on AMD's compatible list for that category. B550 is not.

Start with the job, not the parts​

The strongest idea in the original piece is to decide what the server will do first. The author's rough tiers:

• Media or backup server: a modest build. He suggests about 16 GB of RAM and a GPU or integrated graphics that can handle video decoding. He also suggests a small NVMe boot drive, with 128 GB being enough, plus a couple of large hard drives for data.
• Virtual machines (for example, Proxmox): more CPU cores, more RAM, and possibly extra GPUs.
• Containers: a lighter alternative to full virtual machines, as the author notes.

These are one writer's starting points, not minimums. Real needs depend on how many users, which services, how large the media files are, and how much redundancy you want.

What Proxmox actually requires​

Proxmox's documentation gives firmer numbers than the original article does.

• Virtualization support: x86 hosts need an Intel VT or AMD-V capable CPU and motherboard. The source packet's Proxmox excerpt states this requirement for KVM.
• Evaluation minimum: 1 GB of RAM plus whatever the guests need. The documentation says this is for evaluation only, not production.
• Recommended memory: a minimum of 2 GB for the OS and Proxmox services, plus memory for guests. For ZFS and Ceph, plan on roughly 1 GB per TB of used storage.
• Storage: the docs favor fast, redundant storage and say SSDs give the best results. They also say consumer SSDs are discouraged and recommend power-loss-protected drives. A home lab doesn't have to follow that, but you should know the guidance exists.
• PCIe passthrough: the CPU and motherboard must support an IOMMU, meaning Intel VT-d or AMD-Vi. It usually has to be enabled in BIOS/UEFI.

"One or more GPUs" is therefore not a Proxmox requirement. A second GPU only matters if you plan to pass it through to a guest. In that case, check the exact board, CPU, GPU and firmware first.

Expansion slots and bifurcation​

The original piece says to look for boards whose slots support PCIe bifurcation. The idea is sound, but bifurcation depends on the board and its firmware, not just on having an x16 slot. A few things to check in the manual:

1. How many physical slots there are, and how many lanes each is wired for. An x16-length slot can be wired as x4.
2. Whether using an M.2 socket disables or shares lanes with a slot.
3. Which bifurcation modes the BIOS actually offers.
4. Which slots still work with your specific CPU. APUs expose fewer PCIe lanes than standard Ryzen chips. That is general industry knowledge, not something the source states.

On chipsets, AMD's table lists X570 as compatible with a wider range of CPUs than B550. That makes X570 more flexible for a mixed pile of spare parts. It is still no guarantee of a specific slot layout, so read the manual.

Intel graphics and SR-IOV​

The author recommends Intel integrated graphics for better hardware decoding and for SR-IOV. Keep those two ideas apart. Hardware decoding and SR-IOV are separate capabilities. Both depend on the exact processor, drivers and software. Before you pick a chip for media duty, confirm that your media server software supports the acceleration method you plan to use.

What to buy used, and what to skip​

The author's rules:

• Power supplies: avoid used ones, because an aging unit can fail and damage other parts.
• Storage: a grey area. He suggests stress-testing and buying only from a seller with an assurance policy.
• Everything else: fine used, if you inspect it and check seller reviews.

Here is how I would tighten that advice:

• The PSU risk is about unknowns. Age alone doesn't prove a unit is bad. You usually can't verify its history, condition or remaining capacitor life. A cheap used PSU is a bad bet when it powers your only copy of everything.
• Drive tests are screening, not insurance. Manufacturer tools exist for this. Seagate's support material, for example, describes SeaTools for checking compatible drives. A passing test doesn't predict future failure. Keep independent backups, and don't let a used drive hold the only copy of anything.
• "Buy everything else used" is too broad. Condition, compatibility and return rights matter. The cost of replacing a dud should factor into your budget.

The article also says storage is expensive right now. It gives no prices or dates, so treat that as the author's impression, not a measured fact.

A short checklist​

1. Write down the services you want to run.
2. Pick the CPU first, then confirm the motherboard's CPU-support list and BIOS version.
3. Read the board manual for slot wiring, lane sharing and bifurcation.
4. For Proxmox, check virtualization support, and IOMMU support if you want passthrough.
5. Test used drives, buy from sellers who offer protection, and keep backups.
6. Remember that older CPUs draw more power. That raises your electricity bill, as the author points out.

Bottom line​

Reusing spare parts is a sensible way to build a home server, and the "define the workload first" principle holds up. Verify the details before you spend money: chipset and CPU compatibility, slot wiring, passthrough support, and the condition of any used drives or power supplies. The author's own pairing shows how easily that goes wrong. His account has no exact board model, BIOS version, power measurements or drive-health results, so don't read it as a tested parts list.