pve2

Overview

pve2 is a Proxmox host in Hetzner.

It hosts the Subscriptions Remote PC.

Access

• Proxmox UI and SSH access details are not documented here yet. Follow up and add the canonical host URL, auth path, and credential location.
• Confirm the node name before taking action. During the April 2026 kernel incident, the shell prompt and Proxmox UI both showed pve2, not pve1.

Common Tasks

Check the hosted workload

1. Confirm the status of the Subscriptions Remote PC guest on this node.
2. If user impact is reported, also check the guest note: Subscriptions Remote PC.

Check kernel and /boot capacity

1. Review /boot usage before and after any kernel upgrade.
2. If /boot is close to full, review installed kernels and remove obsolete ones before retrying package operations.
3. After apt upgrade, run apt autoremove.

Troubleshooting

April 2026: /boot full blocked Proxmox kernel install

Problem: /boot reached 100% usage, 982M/989M. During a proxmox-kernel-6.17.13-2-pve update, update-initramfs could not write the new initrd, which left dpkg in a broken state and blocked further apt operations.

Observed broken packages:

• proxmox-kernel-6.17.13-2-pve-signed
• proxmox-kernel-6.17
• initramfs-tools

Root cause: 12 kernel generations had accumulated in /boot, including five Debian kernels of the form linux-image-6.12.x+deb13-amd64 that were not needed on a Proxmox host.

Resolution used:

apt remove \
  linux-image-6.12.57+deb13-amd64 \
  linux-image-6.12.63+deb13-amd64 \
  linux-image-6.12.69+deb13-amd64 \
  linux-image-6.12.73+deb13-amd64
apt autoremove

Result:

• /boot dropped from 100% used to 51% used.
• About 465MB free space remained.
• dpkg completed the previously broken package configuration without extra manual repair steps.

Follow-up:

• Remove linux-image-amd64 and linux-image-6.12.74+deb13+1-amd64, which were noted as the remaining Debian kernels after the incident.
• Keep a “current + one back” kernel retention policy.
• Always run apt autoremove after apt upgrade.