Google Drive

The shift from cloud dependence to local sovereignty Relying on a single gaming PC for both high-end performance and background tasks like Plex streaming is a recipe for compromised frame rates and data vulnerability. For tech enthusiast Plouffe, the frustration with the declining user experience of Google Drive and Microsoft OneDrive reached a breaking point. The solution is not another subscription, but a dedicated Network Attached Storage (NAS) system. This guide details how to build a high-capacity, upgradable server that keeps your data local, accessible, and under your absolute control. Essential hardware for a 40TB storage powerhouse Building a NAS requires a balance between power efficiency and future-proof expansion. While off-the-shelf units exist, a custom build offers superior flexibility for those who want more than six drive bays without the "enterprise" price tag. **Core Components:** * **CPU:** Intel Core i3-12100. This chip is a standout for its integrated QuickSync capabilities, which handle Plex transcoding with remarkable efficiency and native AV1 support. * **Motherboard:** ASUS Prime B760M-A D4. It provides 2.5G LAN and essential PCIe expansion slots. * **Storage:** Six Seagate IronWolf 8TB CMR drives. Conventional Magnetic Recording (CMR) is critical here; unlike cheaper SMR drives, CMR maintains performance during intensive RAID rebuilds. * **HBA Card:** An LSI Host Bus Adapter in "IT Mode" is the secret weapon for connecting more drives than a standard motherboard allows. * **Case:** Jonsbo N5. A massive, aesthetically pleasing chassis supporting up to twelve 3.5-inch drives. Step-by-step assembly and software deployment 1. **Physical Assembly:** Seat the Intel Core i3-12100 and RAM into the ASUS Prime B760M-A D4. Install the LSI HBA card into a PCIe slot. Mount the drives into the Jonsbo N5 using the provided rubber stoppers and handles. 2. **Cable Management:** Connect the HBA card to the backplane using SAS-to-SATA cables. Ensure the power supply—ideally an ATX unit for this specific case—is securely connected to the motherboard and backplane. 3. **OS Installation:** Flash HexOS onto a USB drive. Boot the system from the USB and select your dedicated OS drive (a spare 500GB SSD works well). Follow the prompts to set the admin password. 4. **Network Setup:** Once installed, access the HexOS web interface from another computer on the same network. If the server isn't auto-detected, enter the IP address manually to "claim" the server. 5. **Pool Configuration:** Use the dashboard to format your drives into a storage pool. A RAID Z1 configuration allows for 40TB of usable space with one-drive fault tolerance. Troubleshooting the Windows SMB bottleneck Hardware is rarely the roadblock; software permissions are. Even with a perfect HexOS setup, Windows 11 may refuse to access network folders. If you can see the NAS but cannot open folders, the culprit is often the SMB client configuration. You must open PowerShell as an administrator and check if `RequireSecuritySignature` is set to true. If it is, toggle it to false. This obscure setting can prevent even fresh Windows installs from communicating with local servers. For remote access without the security risks of port forwarding, integrate Tailscale. This creates a secure virtual mesh network, allowing you to access your files from a cafe as if you were sitting at home. The long-term value of data ownership A $2,000 upfront investment sounds steep, but it is a hedge against the rising costs of cloud subscriptions and hardware shortages. By moving files to a local NAS, you eliminate the "middleman" of corporate data centers. The result is a high-speed, private repository that grows with your needs, ensuring that when the next cloud service hikes its prices or changes its terms, your data remains exactly where it belongs: under your roof.