nixos-config/machines/koyomi
2024-08-27 01:38:48 +02:00
..
services koyomi: Reinstall on AX41-NVMe 2024-08-27 01:38:44 +02:00
configuration.nix restic: Prepare for additional backups 2024-08-27 01:38:48 +02:00
hardware-configuration.nix koyomi: Reinstall on AX41-NVMe 2024-08-27 01:38:44 +02:00
README.md koyomi: Reinstall on AX41-NVMe 2024-08-27 01:38:44 +02:00
secrets.yaml koyomi: Reinstall on AX41-NVMe 2024-08-27 01:38:44 +02:00

koyomi

Hardware

Hetzner Online AX41-NVMe

  • Motherboard: ASRockRack B565D4-V1L
  • CPU: AMD Ryzen 5 3600
  • RAM: 2×32GB Samsung M378A4G43AB2-CWE (DDR4 3200MHz)
  • SSD: 2×512GB M.2 NVMe SAMSUNG MZVL2512HCJQ-00B00

Setup

As it is a physical server (not a VM) in a remote location, extra care must be taken when installing. Fortunately, Hetzner provides an automated way to reset the server (by sending Ctrl+Alt+Del or force resetting) and a rescue system that can be activated before a reboot. Additionally, there is also a vKVM rescue system, that boots a hypervisor from the network and runs a VM which boots from the physical disks.

The rescue system can be used to start a kexec installer provided by this flake (nix build .#kexec-bundle). Ideally, everything goes well and the next reboot works, but in the case it does not, the vKVM rescue system can be used for debugging.

Even though the Hetzner documentation states that all current systems have UEFI enabled by default, my server did not boot when configured for UEFI, so I used MBR boot instead.

Purpose

Hypervisor. Exact scope is to be determined.

Name

Araragi Koyomi is a student from the Monogatari Series.