Optional Settings

The Optional Settings category provides additional features and optimizations that you can choose to apply to your Proxmox VE installation. These settings are not essential but can enhance your system's capabilities in specific scenarios.

Available Optional Features

1

Add Latest Ceph Support

This option installs the latest Ceph storage system support for Proxmox VE. Ceph is a distributed storage system that provides high performance, reliability, and scalability.

What it does:

• Adds the Ceph repository to your system
• Updates package lists
• Installs Ceph packages using the 'pveceph install' command
• Verifies the installation

How to use: After installation, you can configure and manage Ceph storage using the Proxmox VE web interface or command-line tools.

This adjustment automates the following commands:

# Add Ceph repository
echo "deb https://download.proxmox.com/debian/ceph-squid $(lsb_release -cs) no-subscription" > /etc/apt/sources.list.d/ceph-squid.list

# Update package lists
apt-get update

# Install Ceph
pveceph install

# Verify installation
pveceph status
      

2

Apply AMD CPU Fixes

This option applies specific fixes for AMD EPYC and Ryzen CPUs to improve stability and compatibility.

What it does:

• Detects if an AMD EPYC or Ryzen CPU is present
• Applies kernel parameter 'idle=nomwait' to prevent random crashes
• Configures KVM to ignore certain MSRs (Model Specific Registers) for better Windows guest compatibility
• Installs the latest Proxmox VE kernel

How to use: These fixes are applied automatically and require a system reboot to take effect.

This adjustment automates the following commands:

# Set kernel parameter
sed -i 's/GRUB_CMDLINE_LINUX_DEFAULT="/GRUB_CMDLINE_LINUX_DEFAULT="idle=nomwait /g' /etc/default/grub
update-grub

# Configure KVM
echo "options kvm ignore_msrs=Y" >> /etc/modprobe.d/kvm.conf
echo "options kvm report_ignored_msrs=N" >> /etc/modprobe.d/kvm.conf

# Install latest Proxmox VE kernel
apt-get install pve-kernel-$(uname -r | cut -d'-' -f1-2)
      

3

Enable High Availability Services

This option enables High Availability (HA) services in Proxmox VE, allowing for automatic failover of VMs and containers in case of node failure.

What it does:

• Enables and starts the pve-ha-lrm (Local Resource Manager) service
• Enables and starts the pve-ha-crm (Cluster Resource Manager) service
• Enables and starts the corosync service for cluster communication

How to use: After enabling these services, you can configure HA groups and resources in the Proxmox VE web interface.

This adjustment automates the following commands:

systemctl enable --now pve-ha-lrm pve-ha-crm corosync
      

4

Enable Proxmox Testing Repository

This option enables the Proxmox testing repository, allowing access to the latest, potentially unstable versions of Proxmox VE packages.

What it does:

• Adds the Proxmox testing repository to the system's package sources
• Creates a new file in /etc/apt/sources.list.d/ for the testing repository
• Updates the package lists to include packages from the new repository

How to use: After enabling this repository, you can update and upgrade your system to get the latest testing versions of Proxmox VE packages. Use with caution as these versions may be unstable.

To manually add the Proxmox testing repository, you can use these commands:

    # Add Proxmox testing repository
    echo "deb http://download.proxmox.com/debian/pve $(lsb_release -cs) pvetest" | sudo tee /etc/apt/sources.list.d/pve-testing-repo.list

    # Update package lists
    sudo apt update
      

Note: $(lsb_release -cs) automatically detects your Proxmox VE version codename (e.g., bullseye).

Warning: Enabling the testing repository may lead to system instability. It's recommended for testing environments only.

5

Install and Configure Fastfetch

This option silently installs and configures Fastfetch, a system information tool that displays system specs and a custom logo at login.

What it does:

• Silently downloads and installs the latest version of Fastfetch
• Allows you to choose a custom logo (ProxMenux, Proxmox, Helper-Scripts, Home-Labs-Club, Proxmology, or a custom one)
• Configures Fastfetch to display "System optimised by ProxMenux"
• Sets up Fastfetch to run automatically at console login

Example Logos:

ProxMenux

Proxmox

JC Channel

Helper-Scripts

Home-Labs-Club

Proxmology

This adjustment automates the following commands:

# Download and install the latest version of Fastfetch
FASTFETCH_URL=$(curl -s https://api.github.com/repos/fastfetch-cli/fastfetch/releases/latest | grep "browser_download_url.*fastfetch-linux-amd64.deb" | cut -d '"' -f 4)
wget -q -O /tmp/fastfetch.deb "$FASTFETCH_URL"
dpkg -i /tmp/fastfetch.deb
apt-get install -f -y

# Configure Fastfetch (logo selection remains interactive)
# The configuration is done through a series of jq commands

# Set Fastfetch to run at login
echo "clear && fastfetch" >> ~/.bashrc
      

6

Install and Configure Figurine

This option installs and configures Figurine, a tool that creates stylish ASCII text banners for your terminal, displaying your hostname in a visually appealing 3D format.

What it does:

• Downloads and installs Figurine v2.0.0 from GitHub
• Creates a welcome message that displays your hostname in 3D ASCII art when you log in
• Automatically removes any previous Figurine installation if present
• Sets up the welcome message to run automatically at login

Example Output:

This adjustment automates the following process:

# Check for previous installation and remove if found
if command -v figurine &> /dev/null; then
  rm -f "/usr/local/bin/figurine"
fi

# Download and install Figurine
version="2.0.0"
file="figurine_linux_amd64_v${version}.tar.gz"
url="https://github.com/arsham/figurine/releases/download/v${version}/${file}"
wget -qO "/tmp/${file}" "${url}"
tar -xf "/tmp/${file}" -C "/tmp"
mv "/tmp/deploy/figurine" "/usr/local/bin/figurine"
chmod +x "/usr/local/bin/figurine"

# Create welcome message script
cat << 'EOF' > "/etc/profile.d/figurine.sh"
/usr/local/bin/figurine -f "3d.flf" $(hostname)
EOF
chmod +x "/etc/profile.d/figurine.sh"
  

After installation, you'll see your hostname displayed in 3D ASCII art each time you log in, making it immediately clear which Proxmox node you're working on.

7

Install Log2RAM (SSD/NVMe wear reduction)

Log2RAM mounts /var/log on a tmpfs ramdisk and periodically syncs the contents back to the underlying disk. On a hypervisor journald churn hits the root SSD every few seconds; moving the writes to RAM reduces wear and disk I/O without losing logs — the periodic sync flushes them to disk and a clean shutdown flushes them too.

Upstream project:azlux/log2ram on GitHub

What ProxMenux does:

• Detects whether the root disk is SSD/NVMe by reading /sys/block/<dev>/queue/rotational. On a rotational disk the Automated flow asks first before installing.
• Clones the upstream repository (azlux/log2ram) into /tmp/log2ram and runs its install.sh, then enables the log2ram systemd unit.
• Sizes the ramdisk based on host RAM: ≤ 8 GB → 128M, ≤ 16 GB → 256M, > 16 GB → 512M. Writes the value to SIZE= in /etc/log2ram.conf.
• Schedules a periodic disk sync via /etc/cron.d/log2ram: every 1h / 3h / 6h according to the same RAM tier.
• Installs an auto-sync guard at /usr/local/bin/log2ram-check.sh, wired to /etc/cron.d/log2ram-auto-sync to run every 10 minutes. When /var/log reaches 80% of the ramdisk size the guard vacuums journald; at 92% it also truncates pveproxy access/error and pveam.log before syncing — the plain log2ram write command copies tmpfs to disk but does NOT shrink the tmpfs, so this guard prevents PVE from crashing with No space left on device when logs grow uncontrolled.
• Adjusts systemd-journald limits (SystemMaxUse, RuntimeMaxUse) to fit within the ramdisk so a single burst cannot fill it.
• Registers itself in installed_tools.json so it can be reverted from Uninstall Optimizations.

How to use: On the Automated flow Log2RAM applies unattended when an SSD/NVMe root is detected. On the Customizable flow the script prompts for size, sync interval and whether to enable the 90% auto-sync guard.

Verify and manage from the shell:

# Service state and configured timers
systemctl status log2ram
systemctl list-timers log2ram*

# Current ramdisk usage — /var/log IS the tmpfs itself
df -h /var/log

# Force a sync now (tmpfs → disk); does NOT shrink the tmpfs
log2ram write

# Trigger the auto-sync guard on demand (vacuum + sync when usage is high)
/usr/local/bin/log2ram-check.sh

# Current config: SIZE, mail settings, path
cat /etc/log2ram.conf

# ProxMenux-specific cron jobs
cat /etc/cron.d/log2ram /etc/cron.d/log2ram-auto-sync

# Recent Log2RAM activity
journalctl -u log2ram -n 50 --no-pager