Compute
Dedicated server hardware provides the foundation for storage, containers, media services, networking tools, and infrastructure experiments.
← Back to Projects
Infrastructure
Infrastructure & Systems Lab
A long-running infrastructure environment for storage, Linux, containers, media services, networking, permissions, troubleshooting, recovery, and hands-on systems administration.
TrueNASZFSLinuxDockerPlexNetworkingStorageRecovery
Project at a Glance
Active Lab- Purpose
- A hands-on environment for storage, networking, Linux, containers, remote access, monitoring, resilience, and troubleshooting infrastructure failures.
- My Role
- Independent lab research, design, and documentation.
- Implementation Status
- The existing case study documents TrueNAS and ZFS storage, Linux and container services, remote access, and troubleshooting. Stronger network segmentation is still evolving.
- Next Milestone
- Publish a sanitized topology, a recovery exercise with observed timings, and a repeatable service-health checklist.
Implementation repository: not yet published.
Evidence & Outcomes
What the Work Demonstrates
Active LabThe existing case study documents TrueNAS and ZFS storage, Linux and container services, remote access, and troubleshooting. Stronger network segmentation is still evolving.
Clients · Remote access
Network connectivity
Linux · Container services
TrueNAS · ZFS storage
Documented Work
- ZFS ARC cache growth was evaluated in context rather than treated as a memory fault.
- Storage paths, permissions, container dependencies, and service recovery are documented as troubleshooting concerns.
Next Evidence to Publish
Publish a sanitized topology, a recovery exercise with observed timings, and a repeatable service-health checklist.
The source link contains this published case study, not a separate implementation repository.
Overview
Infrastructure I Can Operate, Break, and Rebuild
The lab gives me an environment where storage, networking, applications, Linux, containers, and media services all depend on one another.
It has evolved through hardware changes, storage migrations, application failures, permission issues, media-library problems, networking troubleshooting, and experiments with different self-hosted services.
The value of the platform is not any single application. It is the experience of running infrastructure where failures must be diagnosed across layers and where recovery matters as much as deployment.
Architecture
Systems Working Together
Storage
ZFS pools and datasets provide the core storage layer for media, applications, backups, and long-term data management.
Services
Containerized and self-hosted applications run as managed services instead of being tied to a desktop environment.
Network
High-speed networking connects the lab to clients, remote-management tools, media devices, and the rest of the environment.
Hardware
Current Infrastructure Platform
CPU
Intel Xeon E5-2699 v4
Motherboard
ASUS X99-DELUXE II
Memory
128 GB DDR4
GPU
Dual NVIDIA T400 4 GB
Storage
6 × 8 TB Helium HDDs
Solid State
NVMe + SATA SSDs
File System
ZFS
Platform
TrueNAS
Primary Use
Storage · Media · Containers · Lab Services
Hands-On Work
Operating the Lab
Real services create real dependencies. That makes the platform useful for learning because storage, permissions, networking, containers, applications, and recovery all matter.
TrueNAS & ZFS
Manage storage pools, datasets, permissions, snapshots, application storage, and capacity across the environment.
Plex Media Services
Operate self-hosted media services with storage, transcoding, metadata, client access, and library management requirements.
Containers & Applications
Run containerized services that depend on persistent storage, networking, permissions, updates, and service health.
Linux Administration
Use command-line administration, service management, logs, permissions, and troubleshooting to maintain the environment.
Networking
Work with local addressing, high-speed connectivity, remote access, service reachability, and segmentation planning.
Recovery
Treat snapshots, documentation, backups, and rebuild procedures as part of the design rather than something added after failure.
Storage
ZFS as the Foundation
Storage is the foundation of the lab. Media services, containers, application data, configuration, and long-term files all depend on the underlying ZFS environment.
Working with ZFS has required understanding more than disk capacity. Pools, datasets, permissions, caching, snapshots, and workload behavior all affect how the system operates.
One of the useful lessons has been learning that high memory consumption is not automatically a problem. ZFS ARC uses available memory aggressively for caching, so system health has to be evaluated in context rather than by looking at a single utilization number.
Troubleshooting
Failure Is Part of the Lab
Some of the most useful infrastructure lessons have come from the moments when services, storage, permissions, or application integrations did not behave as expected.
Troubleshooting Approach
Separate storage, networking, permissions, containers, applications, and client behavior before changing multiple layers at once.
Application Restarts
Problem
Containerized services and hosted applications can fail, restart unexpectedly, or become unavailable after configuration changes.
Response
Review service state, logs, storage dependencies, permissions, and configuration rather than assuming the application itself is the only failure point.
ZFS Memory Behavior
Problem
ZFS can consume significant system memory for ARC caching, which can look like abnormal RAM usage if the behavior is not understood.
Response
Validated that cache growth is expected behavior and evaluated system memory in the context of ZFS rather than treating all used RAM as a fault.
Plex Library Issues
Problem
Media libraries can develop duplicates, missing items, metadata mismatches, or inconsistent paths.
Response
Worked through library paths, naming, metadata, scans, storage layout, and application behavior to isolate the source of inconsistencies.
Application Integration
Problem
Supporting services such as Tautulli or Bazarr may fail even when the core media server remains operational.
Response
Validated networking, API connectivity, application configuration, storage access, and dependencies independently.
Permissions
Problem
Datasets, containers, users, and applications can require different ownership and access patterns.
Response
Treat file permissions and application access as an infrastructure layer that must be designed and tested rather than guessed at.
Dependency Mapping
Problem
A single visible failure can originate in storage, networking, containers, permissions, or another supporting service.
Response
Use layer-by-layer diagnosis to identify the real dependency causing the failure before making changes.
Security
Infrastructure That Can Be Controlled
Storage and self-hosted services create their own security requirements around permissions, network exposure, administrative access, and recovery.
Access Separation
Administrative access and application access are treated as separate concerns so services do not require unnecessary privileges.
Dataset Permissions
Storage permissions are managed intentionally so applications, users, and services receive only the access they need.
Service Isolation
Containers and separated applications reduce the number of services that must share a single runtime environment.
Network Boundaries
The lab continues to evolve toward stronger segmentation between infrastructure, client devices, management interfaces, and exposed services.
Remote Administration
Remote access is handled through controlled management paths instead of exposing storage administration directly to the public internet.
Recovery Planning
Snapshots, configuration documentation, and rebuild thinking reduce the impact of mistakes, failed updates, or service corruption.
Lessons Learned
Infrastructure Is About Dependencies
01
Storage architecture affects almost every service layered on top of it.
02
A healthy infrastructure platform requires understanding dependencies, not just individual applications.
03
ZFS behavior makes more sense when memory, caching, datasets, and workload patterns are considered together.
04
Media and container services are useful because they create real storage, networking, permissions, and recovery problems to solve.
05
Documentation and repeatable recovery procedures become more valuable as the environment grows.
Next Steps
Where the Lab Goes Next
01
Improve network segmentation
02
Expand infrastructure monitoring
03
Strengthen backup and recovery documentation
04
Standardize container deployment patterns
05
Improve application health visibility
06
Continue storage and performance tuning
More Projects