I made a new backplane for my consumer NAS

Original Article ↗ Hacker News Discussion ↗

Overall reaction to the project

  • Many commenters praise the work as elegant, over-engineered “for fun,” and inspiring for hardware hacking.
  • Several admire the reverse-engineering of the original backplane and the professional look of the result.
  • A few note they would have solved the original “dangling OS drive” problem with Velcro or hot glue, contrasting “cheap and easy” with “deep, educational overkill.”

USB 2.0 as OS drive for a NAS

  • Multiple people question why USB 2.0 is “not an option.”
  • Defenders of faster storage argue:
    • USB 2.0’s real-world throughput (~30–40 MB/s, half‑duplex) and low queue depth make OS workloads (logging, updates, paging, package installs) feel sluggish.
    • journalctl/system logging and configuration changes especially suffer.
  • Others report USB 2.0 works “fine” for simple NAS or Raspberry Pi‑style setups, especially if:
    • most of the OS is in RAM (tmpfs, zram, or fully RAM‑loaded images),
    • or only /boot is on USB and the root filesystem lives on disks.
  • Consensus: usable but unpleasant for anything beyond the lightest workloads; the project’s NVMe solution is technically superior but also motivated by tinkering.

Soldering DFN/QFN/BGA and hobbyist techniques

  • Discussion of the “pool of solder paste, float the DFN, then press it down” method:
    • Seen as “insane but fun” yet workable for one‑offs; skepticism about long‑term reliability and heat exposure to nearby sensitive parts.
  • Alternatives and tips:
    • Use stencils or more controlled paste application when possible.
    • Extend pads out from under QFN/DFN to make hand‑soldering easier.
    • Add vias in thermal pads to wick excess solder and allow heating from the back side.
    • Rely on solder surface tension and good solder mask to prevent bridges; tombstoning is a known risk.
  • QFN with “wettable flanks” is highlighted as making visual inspection easier, driven by automotive reliability needs.
  • BGAs are considered possible but difficult for hobbyists: layout is hard, rework requires reballing and often X‑rays, so the advice is to “do it blind” and build multiple boards.

NAS hardware, DIY vs appliance, and standardization

  • Many express desire for consumer‑priced NAS hardware that:
    • allows replacing the vendor OS with a vanilla Linux/BSD,
    • has standardized, swappable backplanes or motherboards to extend chassis life.
  • Examples mentioned: off‑the‑shelf NAS boxes with replaceable internal USB boot media, small x86 mini‑NAS units, ARM boards with SATA, used servers, and full DIY ATX/Mini‑ITX builds with hot‑swap bays.
  • Tradeoffs highlighted:
    • Appliances (e.g., Synology‑like) offer turnkey setup, web UIs, and read‑only OS partitions, at the cost of lock‑in and weaker upgrade paths (e.g., fixed 1 Gbps).
    • DIY builds give flexibility, better performance per dollar, and easier OS replacement, but require more research, assembly, and ongoing maintenance.
  • Some lament the lack of ARM + SSD, ultra‑low‑power consumer NAS boxes, and more modular designs akin to laptop mainboard ecosystems.

Storage, reliability, and backups

  • Comments touch on:
    • ZFS on single disks not being a complete answer to bit rot.
    • RAID (including ZFS RAIDZ/mirrors) as high‑availability, not a substitute for backups.
    • Home strategies combining RAID, nightly on‑box backups, and very infrequent off‑site, air‑gapped HDD syncs.
  • External USB enclosures for multiple disks can work but have pitfalls:
    • Some systems map drives by discovery order rather than stable IDs, which can cause pool confusion when adding/removing USB devices (noted as implementation‑specific).