Skip to content

🕵️ Isolinear-Video Investigation Report

Date: 2026-01-21 Subject: Missing Server isolinear-video (192.168.1.12) Status: 🔴 CRITICAL - MISSING

🚨 Executive Summary

The server isolinear-video, expected to be at IP 192.168.1.12, is currently unreachable. Comprehensive searches on the Proxmox host and the Backup Server have failed to locate any configuration, virtual machine, or backup associated with this hostname or IP address.

🔎 Investigation Findings

1. Network Status

  • Target IP: 192.168.1.12
  • Result: Destination Host Unreachable (Ping failed).
  • ARP Table: No entry found on gateway or neighbor nodes.

2. Proxmox Host Analysis (proxmox-host / 192.168.1.5)

  • Active VMs: Scanned qm list. Found VMs 100, 101, 103, 104, 106, 199. None match isolinear.
  • Configuration Search:
    • Executed recursive grep on /etc/pve/ for "isolinear" and "192.168.1.12".
    • Result: 0 matches. No residual configuration files found.
  • Log Analysis:
    • Executed recursive grep on /var/log/ for "isolinear" and "192.168.1.12".
    • Result: 0 matches. No recent activity logs found.

3. Backup Server Analysis (pbs-backups / 192.168.1.4)

  • Repository: ds9-backups
  • Method: Direct file system inspection at /mnt/ds9-infra/backups/ds9-backups/vm/.
  • Found Backups:
    • vm/100 -> ds9-truenas (Verified)
    • vm/101 -> holodeck-audiobookshelf (Verified running, user confirmed strictly Audiobooks)
    • vm/103 -> nexus-win11pro (Windows 11 Desktop, recently restored & deleted)
    • vm/104 -> memory-alpha-ubuntu (Verified)
    • vm/106 -> holodeck-subspace (Verified as deepspace-media / 192.168.1.11)
  • Result: No backup directory exists for a distinct isolinear-video VM.

📉 Conclusion

The server isolinear-video appears to have been: 1. Deleted from the Proxmox host without a trace. 2. Never Backed Up to the primary ds9-backups datastore. 3. Or: It exists on a completely different physical machine or storage medium not currently cataloged.

⏭️ Next Steps

  1. User Query: Confirm if isolinear-video might have been an LXC container (ID 110 is enterprise-dev, are there others?) or a physical machine.
  2. Deep Storage Scan: Check if ds9-truenas has any raw disk images (.qcow2, .img) in its NFS shares that aren't attached to a VM config.
  3. Rebuild: If the VM is truly lost, we must provision a new VM at 192.168.1.12 and redeploy the Video stack.