---
description: >-
  Comprehensive health report for the mw-pfeddersheim-workstation, including
  system specifications, current status, and runtime environment details.
tags:
  - infrastructure
  - health-check
  - workstation
  - monitoring
last_updated: '2026-06-17'
---
# Workstation Health Report: mw-manjaro-pf

## System Specifications

- **CPU**: AMD Ryzen 7 2700X (16 threads) @ 3.9GHz max
- **Memory**: 64 GiB DDR4-2666 MT/s (4x 16 GiB, 2x Kingston + 2x Samsung)
- **Primary Disk**: 512 GB NVMe SSD (Samsung MZvl2512HCJQ)
- **Secondary Disk**: 500 GB SATA SSD (Samsung 840 EVO) -> `/home/mw/models`
- **OS**: Manjaro Linux (Kernel 6.12)

## Current Health Status (2026-03-17 23:21 CET)

- **Uptime**: ~1 hour, 7 minutes (post-reboot due to OOM crash at 18:33)
- **Load Average**: 0.40, 0.50, 1.45 (very low)
- **Memory**: 7.9 GiB used / 62 GiB total (12%)
- **Swap**: 0 B used / 16 GiB (0%)
- **zswap**: Active (zstd/zsmalloc, 30% pool)
- **Disk Usage (/)**: 84% (371G used, 74G free)
- **OOM Protection**: `systemd-oomd` active, monitoring `/user.slice`
- **Kernel Optimizations**:
  - mglru: Active
  - Transparent hugepages: `madvise`
  - Proactive reclaim: `watermark_scale_factor 100`
  - Dirty bytes: `dirty_ratio=10`, `dirty_background_ratio=5`
- **Maintenance**:
  - Crash analysis performed for 2026-03-17 incident
  - S.M.A.R.T. hardware check passed for NVMe

## Crashlog Analysis (2026-03-17)

### Recent Errors (from journalctl)

No errors in the last hour from `journalctl -p err`

### OOM Events

- **15:06:06 CET**: Node.js process (PID 122570, 122573, 122574, 122575, 122625) dumped core due to OOM
  - These appear to be Cline/agent-related processes that exhausted memory
  - Systemd-oomd correctly intervened and terminated the processes

### Kernel Warnings (Boot)

- **VMSCAPE**: SMT advisory - mitigation available (enable STIBP for full protection)
- **ATA link failures**: ata3/4/7/8 failed to resume (idle SATA ports)
- **Samsung 840 EVO quirks**: noncqtrim, zeroaftertrim, nodmalog (normal for older SSD)
- **NVIDIA taint**: Proprietary driver (expected)
- **UVC webcam warnings**: Non-critical (device firmware)
- **Pipewire Broken Pipe**: Video device initialization issues (non-critical)

### Failed Services

- `archlinux-keyring-wkd-sync.service`: Failed (non-critical, keyring sync)

### Docker

- **Status**: 6 containers running
- **No zombie containers detected**

### Health Check Script Results

```text
Root partition: 78% used
Git status: Dirty (34 changes) - workstation-health.md modified
Docker: 6 containers running
Uptime: ~1 hour, 7 minutes
```

## Recommendations

1. **Monitor Node.js memory**: Today's OOM crash involved multiple Cline-related node processes.
   Consider investigating if agent sessions are consuming excessive memory.
2. **Replace Samsung 840 EVO**: Currently applies SATA quirks (noncqtrim, zeroaftertrim, nodmalog).
   Action: No action needed (non-critical, working as expected)
3. **Monitor memory**: 12% usage is very healthy. Current state is stable.

## Next Steps

1. Consider setting up automated crash monitoring for high-memory applications
2. Run health check script manually as needed: `/home/mw/internal/mw-pfeddersheim-workstation/scripts/morning-health-check.sh` (automated systemd timer removed 2026-05-26)

## Recent Cleanup (2026-06-17)

- **Externally-created bridge `br_vm_internal` (10.10.2.0/24)** discovered and removed. No NM config file, no libvirt network, no attached VMs. Origin traced to Jun 10 2026 (first activation) — likely ad-hoc CLI creation. Bridge had `htb` qdisc suggesting prior VM network isolation attempt. Both the NM connection and kernel interface fully deleted.