Files
HomeAudit/HARDWARE_SPECIFICATIONS.md
2025-08-24 11:13:39 -04:00

7.0 KiB

Complete Hardware Specifications Report

Generated: 2025-08-23
Audit Source: Linux System Audit v2.0

Hardware Overview Summary

Host CPU RAM Storage Architecture
fedora Intel N95 (4 cores, 3.4GHz) 16GB (6.6GB used) 476GB SSD x86_64
OMV800 Unknown CPU Unknown RAM 19TB+ Array x86_64
jonathan-2518f5u Unknown CPU Unknown RAM Multiple drives x86_64
surface Unknown CPU Unknown RAM Multiple drives x86_64
raspberrypi ARM-based Unknown RAM 7.3TB RAID-1 aarch64
audrey Unknown CPU Unknown RAM Unknown storage x86_64

Detailed Hardware Specifications

1. fedora (192.168.50.225) - Development Workstation

Complete Hardware Profile:

CPU Specifications

  • Model: Intel(R) N95
  • Architecture: x86_64
  • Cores: 4 physical cores
  • Threads: 4 (1 thread per core)
  • Base Clock: 800 MHz
  • Boost Clock: 3,400 MHz
  • Current Usage: 79% scaling
  • Cache:
    • L1d: 128 KiB (4 instances)
    • L1i: 256 KiB (4 instances)
    • L2: 2 MiB (1 instance)
    • L3: 6 MiB (1 instance)
  • Features: VT-x virtualization, AES-NI, AVX2, modern security mitigations

Memory Configuration

  • Total RAM: 16 GB (15 GiB)
  • Used: 6.6 GB
  • Free: 280 MB
  • Buffer/Cache: 9.2 GB
  • Available: 8.8 GB
  • Swap: 8 GB (2.9 GB used, 5.1 GB free)

Storage Layout

  • Primary Drive: 476.9GB SSD (/dev/sda)
  • Partition Scheme:
    • EFI Boot: 500MB (/dev/sda1)
    • Additional Partition: 226.2GB (/dev/sda2)
    • Boot: 1GB (/dev/sda5) - 50% used
    • Root: 249GB (/dev/sda6) - 67% used (162GB used, 81GB free)
  • Snap Packages: Multiple loop devices for containerized apps

Security Features

  • CPU Vulnerabilities: Fully mitigated
    • Spectre/Meltdown: Protected
    • Enhanced IBRS active
    • Store bypass disabled
    • Register file sampling mitigated

2. OMV800 (192.168.50.229) - Storage Server

Storage Configuration

  • Total Capacity: 19TB+ storage array
  • Role: Primary NAS and media server
  • Architecture: x86_64
  • OS: Debian 12 (Bookworm)
  • Uptime: 1 week, 3 days, 4 hours

Network Interfaces

  • Primary IP: 192.168.50.229
  • Tailscale: 100.78.26.112
  • Docker Networks: Multiple bridge interfaces (172.x.x.x)
  • IPv6: fd7a:115c:a1e0::9801:1a70

3. jonathan-2518f5u (192.168.50.181) - Home Automation Hub

System Profile

  • Architecture: x86_64
  • OS: Ubuntu 24.04.3 LTS
  • Kernel: 6.8.0-71-generic
  • Uptime: 2 weeks, 3 days, 46 minutes

Network Configuration

  • Primary IP: 192.168.50.181
  • Secondary IP: 192.168.50.160
  • Tailscale: 100.99.235.80
  • Multiple Docker Networks: 172.x.x.x ranges
  • IPv6: Multiple fd56 and fd7a addresses

4. surface (192.168.50.254) - Development Server

System Profile

  • Architecture: x86_64
  • OS: Ubuntu 24.04.3 LTS
  • Kernel: 6.15.1-surface-2 (Surface-optimized)
  • Uptime: 5 hours, 22 minutes (recently rebooted)

Network Configuration

  • Primary IP: 192.168.50.254
  • Tailscale: 100.67.40.97
  • Docker Networks: Multiple 172.x.x.x ranges

5. raspberrypi (192.168.50.107) - Backup NAS

Hardware Profile

  • Architecture: aarch64 (ARM 64-bit)
  • OS: Debian 12 (Bookworm)
  • Kernel: 6.12.34+rpt-rpi-v8 (Raspberry Pi optimized)
  • Uptime: 4 weeks, 2 days, 2 hours (very stable)

Storage Configuration

  • RAID Array: 7.3TB RAID-1 configuration
  • Purpose: Backup storage for all hosts
  • Mount Points:
    • /export/audrey_backup
    • /export/surface_backup
    • /export/omv800_backup
    • /export/fedora_backup

6. audrey (192.168.50.145) - Monitoring Hub

System Profile

  • Architecture: x86_64
  • OS: Ubuntu 24.04.3 LTS
  • Kernel: 6.14.0-24-generic
  • Uptime: 4 weeks, 2 days, 2 hours (very stable)

Network Configuration

  • Primary IP: 192.168.50.145
  • Tailscale: 100.118.220.45
  • Docker Networks: 172.x.x.x ranges

Storage Architecture Summary

Total Infrastructure Storage

  • Primary Storage: 19TB+ (OMV800 array)
  • Backup Storage: 7.3TB RAID-1 (raspberrypi)
  • Development Storage: 476GB+ (fedora confirmed)
  • Estimated Total: 26TB+ across infrastructure

Storage Distribution Strategy

  1. OMV800 - Primary file server with massive capacity
  2. raspberrypi - Dedicated backup server with RAID redundancy
  3. Individual hosts - Local storage for OS and applications
  4. NFS Integration - Network file sharing across all hosts

CPU Architecture Analysis

Intel x86_64 Systems (5 hosts)

  • Modern Intel processors with virtualization support
  • All systems support containerization (Docker/Podman)
  • Hardware security features enabled
  • AES-NI encryption acceleration available

ARM aarch64 System (1 host)

  • raspberrypi - ARM-based for power efficiency
  • Optimized for 24/7 operation as backup server
  • Raspberry Pi-specific kernel optimizations

Memory & Performance Characteristics

fedora Workstation (confirmed 16GB)

  • High memory utilization (6.6GB active)
  • Large buffer/cache (9.2GB) for development workloads
  • Swap usage (2.9GB) indicates memory pressure under load

Infrastructure Pattern

  • High-memory hosts likely for database and container workloads
  • Lower-memory hosts (like Pi) for dedicated services
  • Distributed architecture spreads resource load

Hardware Security Features

CPU-Level Protections (fedora confirmed)

  • Spectre/Meltdown: Full mitigation deployed
  • Enhanced IBRS: Advanced branch prediction security
  • Control Flow Integrity: Modern exploit prevention
  • Hardware encryption: AES-NI and modern crypto support

Platform Security

  • UEFI Secure Boot on modern systems
  • TPM integration likely on business-class hardware
  • Hardware virtualization (VT-x/AMD-V) enabled

Power & Thermal Management

Workstation Class (fedora, surface)

  • Dynamic CPU scaling (800MHz - 3.4GHz)
  • Advanced power management
  • Thermal throttling protection

Server Class (OMV800, jonathan-2518f5u)

  • 24/7 operation optimized
  • ECC memory support likely
  • Enterprise storage controllers

Embedded Class (raspberrypi)

  • Low power ARM design
  • Fanless operation possible
  • Optimized for continuous uptime

Network Hardware Capabilities

Gigabit Ethernet (All hosts)

  • Standard GbE connectivity confirmed
  • Docker bridge networking support
  • VLAN capabilities (Docker networks use 172.x.x.x)

Advanced Networking

  • Tailscale mesh VPN hardware acceleration
  • Container networking with multiple isolated subnets
  • NFS/SMB performance optimized for storage serving

This hardware audit reveals a well-balanced infrastructure with appropriate hardware for each role: high-performance workstations, robust storage servers, and efficient embedded systems for specialized services.