soban - IT, Linux, Servers, Security

Proxmox VM Auto-Upgrade Script (qm + vzdump) with Network Tests and Auto-Restore

Posted on January 23, 2026January 23, 2026 by soban

Proxmox VM Auto-Upgrade Script (qm + vzdump) with Network Tests and Auto-Restore

This article describes a simple (but effective) automation script for Proxmox VE that:

creates a backup of a VM (optional),
starts the VM if it was originally stopped,
runs apt upgrade + reboot inside the VM,
performs network tests before and after the update,
restores from backup automatically if tests fail (optional),
shuts down the VM again if it was originally stopped.

Where to download the script

You can download the script directly from my website:

soban.pl/bash/upgrade_proxmox_qm.sh

Required folders

Before you run anything, create two folders for scripts and logs:

mkdir -p /root/automate_scripts /root/logs

1	mkdir -p /root/automate_scripts /root/logs

Install the script

Download the file into /root/automate_scripts/ and make it executable:

cd /root/automate_scripts
curl -fsSL -o upgrade_proxmox_qm.sh "https://soban.pl/bash/upgrade_proxmox_qm.sh"
chmod +x /root/automate_scripts/upgrade_proxmox_qm.sh

cd /root/automate_scripts

curl -fsSL -o upgrade_proxmox_qm.sh "https://soban.pl/bash/upgrade_proxmox_qm.sh"

chmod +x /root/automate_scripts/upgrade_proxmox_qm.sh

How it works (high level)

Backup (vzdump snapshot + zstd) is executed first (if enabled).
If the VM was stopped, the script starts it and waits WAIT_TIME seconds.
Runs network tests BEFORE update:
Executes apt update/upgrade/dist-upgrade/autoremove/clean and finally reboots the VM.
Waits again (WAIT_TIME) and runs the same tests AFTER update.
If tests fail and a backup exists, it performs qmrestore automatically.
If the VM was originally stopped, it shuts down the VM at the end.

Usage

The script expects exactly two arguments:

VMID – the Proxmox VM ID
TIME_SEC – how long to wait after start/reboot (in seconds)

/root/automate_scripts/upgrade_proxmox_qm.sh 901 500

1	/root/automate_scripts/upgrade_proxmox_qm.sh 901 500

Tip: choose a WAIT_TIME that matches your VM boot time and apt upgrade duration. Typical values are 300 to 1000 seconds depending on the VM.

Full script (for reference)

If you prefer to keep everything in one place, below is the full script exactly as used in this setup:

#!/bin/bash
WAIT_TIME=$2  # wait time for VM start/restart (in seconds)
DO_BACKUP="y" # 'y' - create backup, 'n' - skip backup
DO_UPDATE="y" # 'y' - run system update, 'n' - skip update
echo "---------------START---------------"
date
echo "-----------------------------------"
# Argument check
if [ "$#" -ne 2 ]; then
echo "Usage: $0 <VMID> <TIME_SEC>"
exit 1
fi
VMID="$1"
TARGET_HOSTNAME=$(/usr/sbin/qm list | grep -w "$VMID" | awk '{print $2}')
VM_STATUS=$(/usr/sbin/qm status "$VMID" | awk '{print $2}')
HOST_MACHINE=$(hostname)
WAS_STOPPED=0
if [ "$VM_STATUS" = "stopped" ]; then
WAS_STOPPED=1
else
WAS_STOPPED=0
fi
# Create backup if DO_BACKUP is set to 'y'
backup_result="Backup not attempted"
if [ "$DO_BACKUP" = "y" ]; then
echo "Creating backup for VM $VMID..."
BACKUP_OUTPUT=$(/usr/bin/vzdump "$VMID" --storage local --mode snapshot --compress zstd)
BACKUP_FILE=$(echo "$BACKUP_OUTPUT" | grep -oP 'vzdump-qemu-[^\s]+' | tr -d "'")
if [ -z "$BACKUP_FILE" ]; then
echo "Backup failed: No backup file created."
backup_result="Backup created: NOK"
exit 1
else
echo "Backup created successfully: $BACKUP_FILE"
backup_result="Backup created: OK"
fi
else
echo "Backup not attempted (backup is disabled)."
fi
# Start VM if it was originally stopped
if [ "$WAS_STOPPED" -eq 1 ]; then
echo "Starting VM $VMID for update..."
/usr/sbin/qm start "$VMID"
echo "Waiting $WAIT_TIME seconds for VM to start..."
sleep "$WAIT_TIME"
fi
# Test functions
perform_ping_test() {
source="$1"
target="$2"
if ssh root@"$source" "ping -c 3 -W 2 $target" >/dev/null 2>&1; then
echo "Ping from $source to $target: OK"
return 0
else
echo "Ping from $source to $target: NOK"
return 1
fi
}
test_curl() {
source="$1"
target="$2"
if ssh root@"$source" "curl -s --head --connect-timeout 5 $target" >/dev/null 2>&1; then
echo "Curl from $source to $target: OK"
return 0
else
echo "Curl from $source to $target: NOK"
return 1
fi
}
perform_local_ping_test() {
source="$1"
target="$2"
if ping -c 3 -W 2 "$target" >/dev/null 2>&1; then
echo "Ping from $source to $target: OK"
return 0
else
echo "Ping from $source to $target: NOK"
return 1
fi
}
DEFAULT_GW=$(/sbin/ip route | grep default | awk '{print $3}')
perform_tests() {
status=0
perform_local_ping_test "$HOST_MACHINE" "$TARGET_HOSTNAME" || status=1
perform_ping_test "$TARGET_HOSTNAME" "8.8.8.8" || status=1
perform_ping_test "$TARGET_HOSTNAME" "$DEFAULT_GW" || status=1
test_curl "$TARGET_HOSTNAME" "http://google.com" || status=1
return ${status:-0}
}
# General tests before update
echo "--- General tests BEFORE update ---"
if perform_tests; then
echo "All network tests before update: OK"
echo "$backup_result"
if [ "$backup_result" == "Backup created: OK" ] || [ "$backup_result" == "Backup not attempted" ]; then
echo "BEFORE status: OK"
else
echo "BEFORE status: NOK"
fi
else
echo "Some network tests before update: NOK"
echo "$backup_result"
echo "BEFORE status: NOK"
[ "$WAS_STOPPED" -eq 1 ] && /usr/sbin/qm shutdown "$VMID"
exit 1
fi
echo "-----------------------------------"
# System update and reboot
update_result="Upgrade system: NOK"
if [ "$DO_UPDATE" = "y" ]; then
echo "--- Updating VM $VMID ---"
if ssh root@"$TARGET_HOSTNAME" "/usr/bin/apt update && \
/usr/bin/apt upgrade -y && \
/usr/bin/apt dist-upgrade -y && \
/usr/bin/apt autoremove -y && \
/usr/bin/apt autoclean && \
/usr/bin/apt clean && \
/usr/bin/apt --purge autoremove && \
/sbin/reboot"; then
echo "---END Updating VM $VMID ---"
echo "Upgrade system: OK"
update_result="Upgrade system: OK"
else
echo "Upgrade system: NOK"
update_result="Upgrade system: NOK"
[ "$WAS_STOPPED" -eq 1 ] && /usr/sbin/qm shutdown "$VMID"
echo "Update failed. Exiting."
exit 1
fi
fi
# Wait for VM reboot if update was performed
if [ "$DO_UPDATE" = "y" ]; then
echo "Waiting $WAIT_TIME seconds for VM to reboot..."
sleep "$WAIT_TIME"
fi
# Tests after reboot if update was performed
if [ "$DO_UPDATE" = "y" ]; then
echo "--- Network tests AFTER update ---"
if perform_tests; then
echo "All network tests after update: OK"
echo "$update_result"
echo "AFTER status: OK"
else
echo "Some network tests after update: NOK"
echo "$update_result"
echo "Attempting to restore from backup..."
if [ "$DO_BACKUP" = "y" ]; then
/usr/sbin/qm stop "$VMID"
/usr/sbin/qmrestore "/var/lib/vz/dump/$BACKUP_FILE" "$VMID" --force
if [ "$WAS_STOPPED" -eq 1 ]; then
/usr/sbin/qm shutdown "$VMID"
fi
echo "Restore attempt finished. Please check VM status."
echo "AFTER status: NOK"
else
echo "No backup available for restoration. The VM might not function properly after failed update."
echo "AFTER status: NOK"
fi
fi
echo "-----------------------------------"
fi
# Shut down VM if it was originally stopped
if [ "$WAS_STOPPED" -eq 1 ]; then
echo "Shutting down VM $VMID (originally stopped)."
/usr/sbin/qm shutdown "$VMID"
fi
echo "---------------END---------------"
date
echo "-----------------------------------"

100

101

102

103

104

105

106

107

108

109

110

111

112

113

114

115

116

117

118

119

120

121

122

123

124

125

126

127

128

129

130

131

132

133

134

135

136

137

138

139

140

141

142

143

144

145

146

147

148

149

150

151

152

153

154

155

156

157

158

159

160

161

162

163

164

165

166

167

168

169

170

171

172

173

174

175

176

177

178

179

180

181

182

183

184

185

186

187

188

189

190

191

192

#!/bin/bash

WAIT_TIME=$2 # wait time for VM start/restart (in seconds)

DO_BACKUP="y" # 'y' - create backup, 'n' - skip backup

DO_UPDATE="y" # 'y' - run system update, 'n' - skip update

echo "---------------START---------------"

date

echo "-----------------------------------"

# Argument check

if [ "$#" -ne 2 ]; then

echo "Usage: $0 <VMID> <TIME_SEC>"

exit 1

VMID="$1"

TARGET_HOSTNAME=$(/usr/sbin/qm list | grep -w "$VMID" | awk '{print $2}')

VM_STATUS=$(/usr/sbin/qm status "$VMID" | awk '{print $2}')

HOST_MACHINE=$(hostname)

WAS_STOPPED=0

if [ "$VM_STATUS" = "stopped" ]; then

WAS_STOPPED=1

else

WAS_STOPPED=0

# Create backup if DO_BACKUP is set to 'y'

backup_result="Backup not attempted"

if [ "$DO_BACKUP" = "y" ]; then

echo "Creating backup for VM $VMID..."

BACKUP_OUTPUT=$(/usr/bin/vzdump "$VMID" --storage local --mode snapshot --compress zstd)

BACKUP_FILE=$(echo "$BACKUP_OUTPUT" | grep -oP 'vzdump-qemu-[^\s]+' | tr -d "'")

if [ -z "$BACKUP_FILE" ]; then

echo "Backup failed: No backup file created."

backup_result="Backup created: NOK"

exit 1

else

echo "Backup created successfully: $BACKUP_FILE"

backup_result="Backup created: OK"

else

echo "Backup not attempted (backup is disabled)."

# Start VM if it was originally stopped

if [ "$WAS_STOPPED" -eq 1 ]; then

echo "Starting VM $VMID for update..."

/usr/sbin/qm start "$VMID"

echo "Waiting $WAIT_TIME seconds for VM to start..."

sleep "$WAIT_TIME"

# Test functions

perform_ping_test() {

source="$1"

target="$2"

if ssh root@"$source" "ping -c 3 -W 2 $target" >/dev/null 2>&1; then

echo "Ping from $source to $target: OK"

return 0

else

echo "Ping from $source to $target: NOK"

return 1

}

test_curl() {

source="$1"

target="$2"

if ssh root@"$source" "curl -s --head --connect-timeout 5 $target" >/dev/null 2>&1; then

echo "Curl from $source to $target: OK"

return 0

else

echo "Curl from $source to $target: NOK"

return 1

}

perform_local_ping_test() {

source="$1"

target="$2"

if ping -c 3 -W 2 "$target" >/dev/null 2>&1; then

echo "Ping from $source to $target: OK"

return 0

else

echo "Ping from $source to $target: NOK"

return 1

}

DEFAULT_GW=$(/sbin/ip route | grep default | awk '{print $3}')

perform_tests() {

status=0

perform_local_ping_test "$HOST_MACHINE" "$TARGET_HOSTNAME" || status=1

perform_ping_test "$TARGET_HOSTNAME" "8.8.8.8" || status=1

perform_ping_test "$TARGET_HOSTNAME" "$DEFAULT_GW" || status=1

test_curl "$TARGET_HOSTNAME" "http://google.com" || status=1

return ${status:-0}

}

# General tests before update

echo "--- General tests BEFORE update ---"

if perform_tests; then

echo "All network tests before update: OK"

echo "$backup_result"

if [ "$backup_result" == "Backup created: OK" ] || [ "$backup_result" == "Backup not attempted" ]; then

echo "BEFORE status: OK"

else

echo "BEFORE status: NOK"

else

echo "Some network tests before update: NOK"

echo "$backup_result"

echo "BEFORE status: NOK"

[ "$WAS_STOPPED" -eq 1 ] && /usr/sbin/qm shutdown "$VMID"

exit 1

echo "-----------------------------------"

# System update and reboot

update_result="Upgrade system: NOK"

if [ "$DO_UPDATE" = "y" ]; then

echo "--- Updating VM $VMID ---"

if ssh root@"$TARGET_HOSTNAME" "/usr/bin/apt update && \

/usr/bin/apt upgrade -y && \

/usr/bin/apt dist-upgrade -y && \

/usr/bin/apt autoremove -y && \

/usr/bin/apt autoclean && \

/usr/bin/apt clean && \

/usr/bin/apt --purge autoremove && \

/sbin/reboot"; then

echo "---END Updating VM $VMID ---"

echo "Upgrade system: OK"

update_result="Upgrade system: OK"

else

echo "Upgrade system: NOK"

update_result="Upgrade system: NOK"

[ "$WAS_STOPPED" -eq 1 ] && /usr/sbin/qm shutdown "$VMID"

echo "Update failed. Exiting."

exit 1

# Wait for VM reboot if update was performed

if [ "$DO_UPDATE" = "y" ]; then

echo "Waiting $WAIT_TIME seconds for VM to reboot..."

sleep "$WAIT_TIME"

# Tests after reboot if update was performed

if [ "$DO_UPDATE" = "y" ]; then

echo "--- Network tests AFTER update ---"

if perform_tests; then

echo "All network tests after update: OK"

echo "$update_result"

echo "AFTER status: OK"

else

echo "Some network tests after update: NOK"

echo "$update_result"

echo "Attempting to restore from backup..."

if [ "$DO_BACKUP" = "y" ]; then

/usr/sbin/qm stop "$VMID"

/usr/sbin/qmrestore "/var/lib/vz/dump/$BACKUP_FILE" "$VMID" --force

if [ "$WAS_STOPPED" -eq 1 ]; then

/usr/sbin/qm shutdown "$VMID"

echo "Restore attempt finished. Please check VM status."

echo "AFTER status: NOK"

else

echo "No backup available for restoration. The VM might not function properly after failed update."

echo "AFTER status: NOK"

echo "-----------------------------------"

# Shut down VM if it was originally stopped

if [ "$WAS_STOPPED" -eq 1 ]; then

echo "Shutting down VM $VMID (originally stopped)."

/usr/sbin/qm shutdown "$VMID"

echo "---------------END---------------"

date

echo "-----------------------------------"

Cron jobs (weekly schedule + per-VM logs)

Below is an example crontab that runs upgrades once a week (different VM each weekday) and writes separate logs to /root/logs/.

Edit root crontab:

crontab -e

1	crontab -e

Paste rules like these (comments in English):

15 0 * * 1 /root/automate_scripts/upgrade_proxmox_qm.sh 901 500 > /root/logs/kali.log 2>&1                 # Monday: upgrade Kali Linux (VMID 901)
15 0 * * 2 /root/automate_scripts/upgrade_proxmox_qm.sh 903 500 > /root/logs/proxmox-test-01.log 2>&1      # Tuesday: upgrade proxmox-test-01 (VMID 903)
15 0 * * 3 /root/automate_scripts/upgrade_proxmox_qm.sh 904 500 > /root/logs/ubuntu-lte.log 2>&1           # Wednesday: upgrade ubuntu-lte (VMID 904)
15 0 * * 4 /root/automate_scripts/upgrade_proxmox_qm.sh 905 1000 > /root/logs/backup-machine.log 2>&1      # Thursday: upgrade backup-machine (VMID 905)

15 0 * * 1 /root/automate_scripts/upgrade_proxmox_qm.sh 901 500 > /root/logs/kali.log 2>&1 # Monday: upgrade Kali Linux (VMID 901)

15 0 * * 2 /root/automate_scripts/upgrade_proxmox_qm.sh 903 500 > /root/logs/proxmox-test-01.log 2>&1 # Tuesday: upgrade proxmox-test-01 (VMID 903)

15 0 * * 3 /root/automate_scripts/upgrade_proxmox_qm.sh 904 500 > /root/logs/ubuntu-lte.log 2>&1 # Wednesday: upgrade ubuntu-lte (VMID 904)

15 0 * * 4 /root/automate_scripts/upgrade_proxmox_qm.sh 905 1000 > /root/logs/backup-machine.log 2>&1 # Thursday: upgrade backup-machine (VMID 905)

Quick checks / troubleshooting

Make sure root can SSH into the VM by hostname (the script uses ssh root@<vm-hostname>).
Make sure DNS (or /etc/hosts) resolves the VM hostname correctly from the Proxmox host.
If apt needs user interaction, ensure your VMs are set up for non-interactive upgrades (or pin/hold packages that prompt).

That’s it. Drop the script into /root/automate_scripts/, send logs into /root/logs/, and your weekly VM maintenance becomes mostly fire-and-forget.

Dell WD19/WD19S: firmware update on Proxmox/Debian without USB timeouts (fwupd + autosuspend fix)

Posted on January 18, 2026January 18, 2026 by soban

If you’re trying to update the firmware of a Dell WD19/WD19S docking station on Proxmox (or Debian) using fwupdmgr, you may hit the classic Operation timed out error during the Erasing… stage. In practice, the update fails due to USB power management (autosuspend). Below you’ll find a simple, effective fix and a ready-to-run script you can use on a server or laptop.

Symptoms

Most commonly, during a dock firmware update (WD19/WD19S), you’ll see an error similar to:

failed to write-firmware: failed to erase bank: failed after 5 retries: failed to SetReport: USB error: Operation timed out [-7]

1	failed to write-firmware: failed to erase bank: failed after 5 retries: failed to SetReport: USB error: Operation timed out [-7]

At this point, fwupdmgr may show the WD19S device as Update State: Failed or keep reporting pending activation, but the flash process never completes.

Why does this happen?

During flashing, the dock performs long-running operations. If the system tries to save power on USB (autosuspend), control transfers can fail. The result is a timeout exactly during the flash bank erase stage (erase bank).

Quick fix: disable USB autosuspend during the update

The simplest solution is to temporarily set autosuspend to -1 (disabled). This setting lasts until reboot (unless you make it permanent in the kernel cmdline), but it’s more than enough for the update process.

echo -1 > /sys/module/usbcore/parameters/autosuspend

1	echo -1 > /sys/module/usbcore/parameters/autosuspend

Then run the firmware update:

fwupdmgr refresh --force
fwupdmgr update

1 2	fwupdmgr refresh --force fwupdmgr update

After the update: “pending activation” and unplug requirement

After a successful firmware installation for WD19/WD19S, fwupdmgr often prints the following message:

The update will continue when the device USB cable has been unplugged.
WD19S is pending activation; use fwupdmgr activate to complete the update.

1 2	The update will continue when the device USB cable has been unplugged. WD19S is pending activation; use fwupdmgr activate to complete the update.

Do the following in this exact order:

Unplug the USB-C cable from the dock (from the laptop).
(Optional) Unplug the dock power for 10–15 seconds and plug it back in.
Plug the USB-C cable back in.
Run the activation step:

fwupdmgr activate

1	fwupdmgr activate

Finally, verify the status:

fwupdmgr get-updates
fwupdmgr get-devices | less

1 2	fwupdmgr get-updates fwupdmgr get-devices \| less

Ready-to-use script: install + update + autosuspend disable (with restore)

Below is a ready-to-run script that:

installs fwupd
refreshes LVFS metadata
temporarily disables USB autosuspend (so WD19S won’t fail with timeouts)
runs firmware updates
restores the previous autosuspend value afterwards (even if the update fails)

You can copy the script directly from this article, but if you prefer a faster way, you can download it from:

https://soban.pl/bash/dell_updage.sh

Example download and run:

cd /root/scripts
curl -fsSL https://soban.pl/bash/dell_updage.sh -o dell_updage.sh
chmod +x dell_updage.sh
./dell_updage.sh

cd /root/scripts

curl -fsSL https://soban.pl/bash/dell_updage.sh -o dell_updage.sh

chmod +x dell_updage.sh

./dell_updage.sh

If you want to preview the script before running it:

curl -fsSL https://soban.pl/bash/dell_updage.sh | less

1	curl -fsSL https://soban.pl/bash/dell_updage.sh \| less

If you don’t have less installed:

apt update
apt install -y less

1 2	apt update apt install -y less

Script (full content)

#!/bin/bash
set -euo pipefail
# dell upgrade:
# - installs fwupd
# - refreshes metadata
# - runs fwupdmgr update
# - TEMPORARILY disables USB autosuspend to avoid WD19/WD19S timeouts
# - restores autosuspend setting after update
echo "[INFO] Installing fwupd..."
apt update
apt install -y fwupd
echo "[INFO] Refreshing firmware metadata..."
fwupdmgr refresh --force
fwupdmgr get-updates || true
# Save current autosuspend value (if exists)
AUTOSUSPEND_PATH="/sys/module/usbcore/parameters/autosuspend"
OLD_AUTOSUSPEND=""
if [[ -f "$AUTOSUSPEND_PATH" ]]; then
OLD_AUTOSUSPEND="$(cat "$AUTOSUSPEND_PATH" || true)"
echo "[INFO] Current usbcore autosuspend: ${OLD_AUTOSUSPEND}"
else
echo "[WARN] autosuspend sysfs file not found: $AUTOSUSPEND_PATH"
fi
restore_autosuspend() {
if [[ -f "$AUTOSUSPEND_PATH" && -n "${OLD_AUTOSUSPEND}" ]]; then
echo "[INFO] Restoring usbcore autosuspend back to: ${OLD_AUTOSUSPEND}"
echo "${OLD_AUTOSUSPEND}" > "$AUTOSUSPEND_PATH" || true
fi
}
trap restore_autosuspend EXIT
# Disable autosuspend to prevent USB timeout during dock firmware erase/write
if [[ -f "$AUTOSUSPEND_PATH" ]]; then
echo "[INFO] Disabling USB autosuspend (set to -1) to avoid dock update timeouts..."
echo -1 > "$AUTOSUSPEND_PATH"
fi
read -p "Do you want to update the entire device? (y/n): " answer
if [[ "$answer" == "y" || "$answer" == "Y" ]]; then
echo "[INFO] Running fwupdmgr update..."
fwupdmgr update || {
echo "[ERROR] fwupdmgr update failed."
echo "[HINT] If this is Dell dock (WD19/WD19S), try: unplug USB-C, replug, then run: fwupdmgr activate"
exit 1
}
echo "[INFO] Update finished."
echo "[INFO] If you updated a Dell dock and it says 'pending activation':"
echo "       1) Unplug USB-C cable from the dock"
echo "       2) (Optional) Unplug dock power for 10 seconds, plug back"
echo "       3) Run: fwupdmgr activate"
else
echo "[INFO] Skipping firmware update."
fi
echo "[INFO] Done."

#!/bin/bash

set -euo pipefail

# dell upgrade:

# - installs fwupd

# - refreshes metadata

# - runs fwupdmgr update

# - TEMPORARILY disables USB autosuspend to avoid WD19/WD19S timeouts

# - restores autosuspend setting after update

echo "[INFO] Installing fwupd..."

apt update

apt install -y fwupd

echo "[INFO] Refreshing firmware metadata..."

fwupdmgr refresh --force

fwupdmgr get-updates || true

# Save current autosuspend value (if exists)

AUTOSUSPEND_PATH="/sys/module/usbcore/parameters/autosuspend"

OLD_AUTOSUSPEND=""

if [[ -f "$AUTOSUSPEND_PATH" ]]; then

OLD_AUTOSUSPEND="$(cat "$AUTOSUSPEND_PATH" || true)"

echo "[INFO] Current usbcore autosuspend: ${OLD_AUTOSUSPEND}"

else

echo "[WARN] autosuspend sysfs file not found: $AUTOSUSPEND_PATH"

restore_autosuspend() {

if [[ -f "$AUTOSUSPEND_PATH" && -n "${OLD_AUTOSUSPEND}" ]]; then

echo "[INFO] Restoring usbcore autosuspend back to: ${OLD_AUTOSUSPEND}"

echo "${OLD_AUTOSUSPEND}" > "$AUTOSUSPEND_PATH" || true

}

trap restore_autosuspend EXIT

# Disable autosuspend to prevent USB timeout during dock firmware erase/write

if [[ -f "$AUTOSUSPEND_PATH" ]]; then

echo "[INFO] Disabling USB autosuspend (set to -1) to avoid dock update timeouts..."

echo -1 > "$AUTOSUSPEND_PATH"

read -p "Do you want to update the entire device? (y/n): " answer

if [[ "$answer" == "y" || "$answer" == "Y" ]]; then

echo "[INFO] Running fwupdmgr update..."

fwupdmgr update || {

echo "[ERROR] fwupdmgr update failed."

echo "[HINT] If this is Dell dock (WD19/WD19S), try: unplug USB-C, replug, then run: fwupdmgr activate"

exit 1

}

echo "[INFO] Update finished."

echo "[INFO] If you updated a Dell dock and it says 'pending activation':"

echo " 1) Unplug USB-C cable from the dock"

echo " 2) (Optional) Unplug dock power for 10 seconds, plug back"

echo " 3) Run: fwupdmgr activate"

else

echo "[INFO] Skipping firmware update."

echo "[INFO] Done."

Running the script

The simplest way:

chmod +x dell_updage.sh
./dell_updage.sh

1 2	chmod +x dell_updage.sh ./dell_updage.sh

FAQ & tips

The update still fails? Disconnect all peripherals from the dock (monitors/LAN/USB), leave only power and USB-C, do a hard reset of the dock (unplug power for 30s), and try again.
“pending activation” after update – this is normal for WD19/WD19S. You must unplug USB-C, plug it back in, then run fwupdmgr activate.
Does this update the laptop BIOS? Not always. fwupdmgr shows “System Firmware” (BIOS/UEFI) separately from the dock. This article focuses on the dock and the USB timeout issue.

Summary

If Dell WD19/WD19S firmware updates fail on Proxmox/Debian during the Erasing… stage, in most cases it’s enough to disable USB autosuspend temporarily. The script above does that automatically and restores the previous setting afterwards, so your system keeps working normally.

How to Upgrade Proxmox VE 8.x to 9.0 (Debian 12 to Debian 13) – Step-by-Step with Script

Posted on August 11, 2025August 11, 2025 by soban

Introduction

Proxmox VE 9.0 (based on Debian 13 “Trixie”) has been released, and it brings updated packages, a new kernel, and improved stability. This guide will walk you through the in-place upgrade from Proxmox VE 8.4.x (Debian 12 “Bookworm”) to Proxmox VE 9.0.

The process will be automated using a ready-made upgrade script that:

Checks your current version
Runs the pve8to9 pre-upgrade check
Backs up your current APT sources
Updates repositories from Bookworm to Trixie
Performs a full dist-upgrade
Logs all changes before and after the upgrade

Download and run the upgrade script

You can download the ready upgrade script directly from our server, make it executable, and run it:

wget https://soban.pl/bash/upgrade-pve8-to-9.sh -O /root/upgrade-pve8-to-9.sh
chmod +x /root/upgrade-pve8-to-9.sh
LOGF="/root/pve8to9.$(date +%F-%H%M%S).nohup.log"; nohup env NO_REBOOT=0 SKIP_PRECHECK=0 /root/upgrade-pve8-to-9.sh > "$LOGF" 2>&1 & echo $! >/run/pve8to9.pid
tail -f "$LOGF"

wget https://soban.pl/bash/upgrade-pve8-to-9.sh -O /root/upgrade-pve8-to-9.sh

chmod +x /root/upgrade-pve8-to-9.sh

LOGF="/root/pve8to9.$(date +%F-%H%M%S).nohup.log"; nohup env NO_REBOOT=0 SKIP_PRECHECK=0 /root/upgrade-pve8-to-9.sh > "$LOGF" 2>&1 & echo $! >/run/pve8to9.pid

tail -f "$LOGF"

If you lose connection (which can happen during a Proxmox upgrade), you can follow the logs with:

tail -f /root/pve-upgrade-latest.log

1	tail -f /root/pve-upgrade-latest.log

Be patient and wait for the script to finish — it may take some time.

Full script source

#!/bin/bash
# Proxmox VE 8 -> 9 in-place upgrade (Debian 12 "bookworm" -> Debian 13 "trixie")
# Hardened: nuke/lock Enterprise repo, move backups OUT of APT dir, ensure single no-sub,
# robust pve8to9 detection/installation, switch to trixie, non-interactive upgrade, post-boot check.
set -euo pipefail
LOG="/root/pve-upgrade-$(date +%Y%m%d-%H%M%S).log"
SINK="/etc/apt/disabled-sources"        # OUTSIDE of APT scan path
APT_BACKUP_DIR="/root/apt-sources-backup-$(date +%Y%m%d-%H%M%S)"
NO_REBOOT="${NO_REBOOT:-0}"
FORCE_UPGRADE="${FORCE_UPGRADE:-0}"
SKIP_PRECHECK="${SKIP_PRECHECK:-0}"
# Ensure sane PATH for non-interactive shells
export PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:${PATH:-}"
export DEBIAN_FRONTEND=noninteractive
export APT_LISTCHANGES_FRONTEND=none
export UCF_FORCE_CONFFOLD=1
shopt -s nullglob
msg() { echo "$*" | tee -a "$LOG"; }
die() { echo "ERROR: $*" | tee -a "$LOG"; exit 1; }
ts()  { date +%F-%H%M%S; }
sink() { # move file out of sources.list.d safely
local f="$1" base
[[ -e "$f" ]] || return 0
base="$(basename "$f")"
mkdir -p "$SINK"
mv -f "$f" "$SINK/$base.bak.$(ts)"
}
divert_add() {
local p="$1"
if ! dpkg-divert --list | grep -Fq "diversion of $p"; then
dpkg-divert --quiet --local --rename --add "$p" || true
fi
rm -f "$p" || true
}
cleanup_nonlist_sources() {
mkdir -p "$SINK"
find /etc/apt/sources.list.d -maxdepth 1 -type f \
! -name '*.list' ! -name '*.sources' \
-exec mv -f {} "$SINK"/ \; || true
}
# STRICT verify: only fail on ACTIVE enterprise refs
verify_no_enterprise() {
local bad=0
# 1) Active lines in *.list (not commented)
if grep -RIsn '^[[:space:]]*deb[[:space:]].*enterprise\.proxmox\.com' /etc/apt/sources.list /etc/apt/sources.list.d 2>/dev/null; then
bad=1
fi
# 2) Deb822 .sources that mention enterprise AND are effectively enabled
while IFS= read -r -d '' f; do
if grep -qi 'enterprise\.proxmox\.com' "$f"; then
# treat missing Enabled as enabled, only "Enabled: no" is safe
if ! grep -qi '^[[:space:]]*Enabled:[[:space:]]*no[[:space:]]*$' "$f"; then
echo "[VERIFY] Enabled enterprise in: $f" | tee -a "$LOG"
bad=1
fi
fi
done < <(find /etc/apt/sources.list.d -maxdepth 1 -type f -name '*.sources' -print0 2>/dev/null)
(( bad == 0 )) || die "Enterprise repo still detected. Clean failed."
}
# Disabled deb822 stub WITHOUT enterprise domain (so greps never trip)
write_disabled_enterprise_sources() {
cat > /etc/apt/sources.list.d/pve-enterprise.sources <<'EOF'
Types: deb
URIs: https://example.invalid/proxmox           # placeholder to avoid enterprise domain
Suites: trixie
Components: pve-enterprise
Enabled: no
EOF
chmod 0644 /etc/apt/sources.list.d/pve-enterprise.sources
}
# --------- FIXED: robust locator for pve8to9 + debug ----------
locate_pve8to9() {
hash -r 2>/dev/null || true
local tool=""
tool="$(type -P pve8to9 2>/dev/null || true)"
[[ -z "$tool" ]] && tool="$(command -v pve8to9 2>/dev/null || true)"
[[ -z "$tool" && -x /usr/bin/pve8to9 ]] && tool="/usr/bin/pve8to9"
[[ -z "$tool" && -x /usr/sbin/pve8to9 ]] && tool="/usr/sbin/pve8to9"
[[ -z "$tool" ]] && tool="$(/usr/bin/which pve8to9 2>/dev/null || true)"
if [[ -z "$tool" ]] && command -v dpkg >/dev/null 2>&1; then
local cand
cand="$(dpkg -L pve-manager 2>/dev/null | grep -E '/pve8to9$' || true)"
[[ -n "$cand" && -x "$cand" ]] && tool="$cand"
fi
echo "$tool"
}
run_pve8to9_precheck() {
[[ "$SKIP_PRECHECK" == "1" ]] && { msg "SKIP_PRECHECK=1 set — skipping pve8to9."; return 0; }
msg "Running pve8to9 --full precheck..."
msg "PATH=$PATH"
type -a pve8to9 2>&1 | sed 's/^/[type] /' | tee -a "$LOG" || true
[[ -e /usr/bin/pve8to9 ]] && ls -l /usr/bin/pve8to9 | sed 's/^/[ls] /' | tee -a "$LOG" || true
local tool; tool="$(locate_pve8to9)"
if [[ -z "$tool" ]]; then
msg "pve8to9 not found — attempting to ensure 'pve-manager' is installed..."
apt-get update -y >> "$LOG" 2>&1 || true
apt-get install -y pve-manager >> "$LOG" 2>&1 || true
cleanup_nonlist_sources; verify_no_enterprise
hash -r 2>/dev/null || true
tool="$(locate_pve8to9)"
fi
if [[ -z "$tool" ]]; then
msg "pve8to9 still not available on this system. Continuing without precheck."
return 0
fi
msg "pve8to9 found at: $tool"
local tmp rc
tmp="$(mktemp)"
set +e
"$tool" --full | tee -a "$LOG" | tee "$tmp" >/dev/null
rc=${PIPESTATUS[0]}
set -e
if grep -qE 'FAILURES:\s*[1-9]+' "$tmp"; then
rm -f "$tmp"
die "pve8to9 reported FAILURES. Check log above."
fi
rm -f "$tmp"
msg "pve8to9 executed (rc=$rc). No FAILURES."
}
# ---------------------------------------------------------------
# ----- header / live log hint -----
echo "== Proxmox VE 8 -> 9 upgrade started: $(date) ==" | tee -a "$LOG"
echo "$$" > /run/pve8to9.pid
ln -sfn "$LOG" /root/pve-upgrade-latest.log
echo "Live log: tail -f /root/pve-upgrade-latest.log" | tee -a "$LOG"
echo "If started via nohup, also watch its file (example: /root/pve8to9.<ts>.nohup.log)" | tee -a "$LOG"
# 0) PRE-NUKE ENTERPRISE + move backups OUT of APT dir
msg "[PRE-NUKE] Backup APT lists and clean directory..."
mkdir -p "$APT_BACKUP_DIR"
cp -a /etc/apt/sources.list "$APT_BACKUP_DIR"/ 2>/dev/null || true
cp -a /etc/apt/sources.list.d "$APT_BACKUP_DIR"/ 2>/dev/null || true
cleanup_nonlist_sources
# Remove any *.sources referencing Enterprise
for s in /etc/apt/sources.list.d/*.sources; do
[[ -f "$s" ]] || continue
grep -qi 'enterprise\.proxmox\.com' "$s" && { msg " -> removing: $s"; sink "$s"; }
done
# Remove typical filenames
sink /etc/apt/sources.list.d/pve-enterprise.sources
sink /etc/apt/sources.list.d/pve-enterprise.list
# For *.list with Enterprise: comment lines or remove if Enterprise-only
for l in /etc/apt/sources.list.d/*.list; do
[[ -f "$l" ]] || continue
if grep -qi 'enterprise\.proxmox\.com' "$l"; then
if awk 'BEGIN{IGNORECASE=1} /^[[:space:]]*deb/ && $0 !~ /enterprise\.proxmox\.com/ {ok=1} END{exit ok?0:1}' "$l"; then
msg " -> commenting Enterprise lines in: $l"
sed -ri 's|^\s*deb\s+https?://enterprise\.proxmox\.com|#DISABLED-BY-SCRIPT &|I' "$l"
else
msg " -> removing Enterprise-only list: $l"
sink "$l"
fi
fi
done
# Comment Enterprise in main sources.list
[[ -f /etc/apt/sources.list ]] && sed -ri 's|^\s*deb\s+https?://enterprise\.proxmox\.com|#DISABLED-BY-SCRIPT &|I' /etc/apt/sources.list || true
# Diversions + disabled deb822 file (with example.invalid), then re-clean any .distrib/.bak
divert_add /etc/apt/sources.list.d/pve-enterprise.list
divert_add /etc/apt/sources.list.d/pve-enterprise.sources
write_disabled_enterprise_sources
cleanup_nonlist_sources
verify_no_enterprise
# 1) Sanity checks
if [[ $EUID -ne 0 ]]; then die "Run as root."; fi
if ! command -v pveversion >/dev/null 2>&1; then die "Not a Proxmox VE host."; fi
CUR_VER_RAW="$(pveversion || true)"; msg "Current pveversion: $CUR_VER_RAW"
if ! echo "$CUR_VER_RAW" | grep -qE 'pve-manager/8\.'; then
msg "Expected Proxmox 8.x. Detected: $CUR_VER_RAW"
[[ "$FORCE_UPGRADE" == "1" ]] || die "Set FORCE_UPGRADE=1 to override."
fi
# BEFORE snapshot
{
echo; echo "===== BEFORE UPGRADE ====="; date
echo "# uname -a"; uname -a || true
echo; echo "# pveversion"; pveversion || true
echo; echo "# qm list"; qm list || true
echo; echo "# pct list"; pct list || true
} >> "$LOG" 2>&1
# 2) pve8to9 precheck (robust)
run_pve8to9_precheck
# 3) Keyring + initial apt refresh
apt-get update -y >> "$LOG" 2>&1 || true
apt-get install -y proxmox-archive-keyring >> "$LOG" 2>&1 || true
verify_no_enterprise
cleanup_nonlist_sources
# 4) Switch bookworm -> trixie
msg "Switching Debian repositories: bookworm -> trixie ..."
sed -i 's/bookworm/trixie/g' /etc/apt/sources.list || true
find /etc/apt/sources.list.d -maxdepth 1 -type f -exec sed -i 's/bookworm/trixie/g' {} \; || true
# 5) Ensure single no-subscription entry
sed -ri '/download\.proxmox\.com\/debian\/pve.*pve-no-subscription/s/^/#DUPLICATE-BY-SCRIPT /' /etc/apt/sources.list || true
for l in /etc/apt/sources.list.d/*.list; do
[[ -f "$l" ]] || continue
[[ "$l" == "/etc/apt/sources.list.d/pve-no-subscription.list" ]] && continue
sed -ri '/download\.proxmox\.com\/debian\/pve.*pve-no-subscription/s/^/#DUPLICATE-BY-SCRIPT /' "$l" || true
done
cat > /etc/apt/sources.list.d/pve-no-subscription.list <<'EOF'
deb http://download.proxmox.com/debian/pve trixie pve-no-subscription
EOF
chmod 0644 /etc/apt/sources.list.d/pve-no-subscription.list
verify_no_enterprise
cleanup_nonlist_sources
# 6) Full non-interactive upgrade
msg "Running apt-get update + non-interactive upgrade/dist-upgrade..."
TMPU="$(mktemp)"
apt-get update 2>&1 | tee -a "$LOG" | tee "$TMPU" >/dev/null
if grep -q 'enterprise\.proxmox\.com' "$TMPU"; then rm -f "$TMPU"; die "APT tried to reach Enterprise during update."; fi
rm -f "$TMPU"
apt-get -o Dpkg::Options::="--force-confdef" -o Dpkg::Options::="--force-confold" upgrade -y | tee -a "$LOG"
apt-get -o Dpkg::Options::="--force-confdef" -o Dpkg::Options::="--force-confold" dist-upgrade -y | tee -a "$LOG"
# Second cleanup pass
cleanup_nonlist_sources
apt-get autoremove -y | tee -a "$LOG" || true
apt-get update -y >> "$LOG" 2>&1 || true
# 7) One-shot post-boot verification
POST_SH="/root/pve-postcheck.sh"
POST_SVC="/etc/systemd/system/pve-upgrade-postcheck.service"
cat > "$POST_SH" <<'EOS'
#!/bin/bash
set -euo pipefail
LOG_FILE="/root/pve-upgrade-post-$(date +%Y%m%d-%H%M%S).log"
{
echo "===== AFTER UPGRADE (first boot) ====="; date
echo "# uname -a"; uname -a || true
echo; echo "# pveversion"; pveversion || true
echo; echo "# apt policy (trixie check)"; apt-cache policy | sed -n '1,120p' || true
} >> "$LOG_FILE" 2>&1
systemctl disable --now pve-upgrade-postcheck.service >/dev/null 2>&1 || true
rm -f /root/pve-postcheck.sh
EOS
chmod +x "$POST_SH"
cat > "$POST_SVC" <<'EOS'
[Unit]
Description=Proxmox upgrade post-check (one-shot)
After=multi-user.target pvedaemon.service pve-cluster.service
Wants=network-online.target
[Service]
Type=oneshot
ExecStart=/bin/bash /root/pve-postcheck.sh
[Install]
WantedBy=multi-user.target
EOS
systemctl daemon-reload
systemctl enable pve-upgrade-postcheck.service >> "$LOG" 2>&1 || true
# 8) Pre-reboot snapshot
{
echo; echo "===== PRE-REBOOT SNAPSHOT ====="; date
echo "# Installed pve kernels:"; dpkg -l | grep -E '^ii\s+pve-kernel' | sort -V || true
} >> "$LOG" 2>&1
msg "Upgrade phase completed. Log: $LOG"
if [[ "$NO_REBOOT" == "1" ]]; then
msg "NO_REBOOT=1 set — skipping reboot. Please reboot manually."
else
msg "Rebooting now to complete the upgrade..."
sleep 3
reboot
fi

100

101

102

103

104

105

106

107

108

109

110

111

112

113

114

115

116

117

118

119

120

121

122

123

124

125

126

127

128

129

130

131

132

133

134

135

136

137

138

139

140

141

142

143

144

145

146

147

148

149

150

151

152

153

154

155

156

157

158

159

160

161

162

163

164

165

166

167

168

169

170

171

172

173

174

175

176

177

178

179

180

181

182

183

184

185

186

187

188

189

190

191

192

193

194

195

196

197

198

199

200

201

202

203

204

205

206

207

208

209

210

211

212

213

214

215

216

217

218

219

220

221

222

223

224

225

226

227

228

229

230

231

232

233

234

235

236

237

238

239

240

241

242

243

244

245

246

247

248

249

250

251

252

253

254

255

256

257

258

259

260

261

262

263

264

265

266

267

268

269

270

271

272

273

274

275

276

277

278

279

280

281

282

283

284

285

286

287

288

289

290

291

292

#!/bin/bash

# Proxmox VE 8 -> 9 in-place upgrade (Debian 12 "bookworm" -> Debian 13 "trixie")

# Hardened: nuke/lock Enterprise repo, move backups OUT of APT dir, ensure single no-sub,

# robust pve8to9 detection/installation, switch to trixie, non-interactive upgrade, post-boot check.

set -euo pipefail

LOG="/root/pve-upgrade-$(date +%Y%m%d-%H%M%S).log"

SINK="/etc/apt/disabled-sources" # OUTSIDE of APT scan path

APT_BACKUP_DIR="/root/apt-sources-backup-$(date +%Y%m%d-%H%M%S)"

NO_REBOOT="${NO_REBOOT:-0}"

FORCE_UPGRADE="${FORCE_UPGRADE:-0}"

SKIP_PRECHECK="${SKIP_PRECHECK:-0}"

# Ensure sane PATH for non-interactive shells

export PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:${PATH:-}"

export DEBIAN_FRONTEND=noninteractive

export APT_LISTCHANGES_FRONTEND=none

export UCF_FORCE_CONFFOLD=1

shopt -s nullglob

msg() { echo "$*" | tee -a "$LOG"; }

die() { echo "ERROR: $*" | tee -a "$LOG"; exit 1; }

ts() { date +%F-%H%M%S; }

sink() { # move file out of sources.list.d safely

local f="$1" base

[[ -e "$f" ]] || return 0

base="$(basename "$f")"

mkdir -p "$SINK"

mv -f "$f" "$SINK/$base.bak.$(ts)"

}

divert_add() {

local p="$1"

if ! dpkg-divert --list | grep -Fq "diversion of $p"; then

dpkg-divert --quiet --local --rename --add "$p" || true

rm -f "$p" || true

}

cleanup_nonlist_sources() {

mkdir -p "$SINK"

find /etc/apt/sources.list.d -maxdepth 1 -type f \

! -name '*.list' ! -name '*.sources' \

-exec mv -f {} "$SINK"/ \; || true

}

# STRICT verify: only fail on ACTIVE enterprise refs

verify_no_enterprise() {

local bad=0

# 1) Active lines in *.list (not commented)

if grep -RIsn '^[[:space:]]*deb[[:space:]].*enterprise\.proxmox\.com' /etc/apt/sources.list /etc/apt/sources.list.d 2>/dev/null; then

bad=1

# 2) Deb822 .sources that mention enterprise AND are effectively enabled

while IFS= read -r -d '' f; do

if grep -qi 'enterprise\.proxmox\.com' "$f"; then

# treat missing Enabled as enabled, only "Enabled: no" is safe

if ! grep -qi '^[[:space:]]*Enabled:[[:space:]]*no[[:space:]]*$' "$f"; then

echo "[VERIFY] Enabled enterprise in: $f" | tee -a "$LOG"

bad=1

done < <(find /etc/apt/sources.list.d -maxdepth 1 -type f -name '*.sources' -print0 2>/dev/null)

(( bad == 0 )) || die "Enterprise repo still detected. Clean failed."

}

# Disabled deb822 stub WITHOUT enterprise domain (so greps never trip)

write_disabled_enterprise_sources() {

cat > /etc/apt/sources.list.d/pve-enterprise.sources <<'EOF'

Types: deb

URIs: https://example.invalid/proxmox # placeholder to avoid enterprise domain

Suites: trixie

Components: pve-enterprise

Enabled: no

EOF

chmod 0644 /etc/apt/sources.list.d/pve-enterprise.sources

}

# --------- FIXED: robust locator for pve8to9 + debug ----------

locate_pve8to9() {

hash -r 2>/dev/null || true

local tool=""

tool="$(type -P pve8to9 2>/dev/null || true)"

[[ -z "$tool" ]] && tool="$(command -v pve8to9 2>/dev/null || true)"

[[ -z "$tool" && -x /usr/bin/pve8to9 ]] && tool="/usr/bin/pve8to9"

[[ -z "$tool" && -x /usr/sbin/pve8to9 ]] && tool="/usr/sbin/pve8to9"

[[ -z "$tool" ]] && tool="$(/usr/bin/which pve8to9 2>/dev/null || true)"

if [[ -z "$tool" ]] && command -v dpkg >/dev/null 2>&1; then

local cand

cand="$(dpkg -L pve-manager 2>/dev/null | grep -E '/pve8to9$' || true)"

[[ -n "$cand" && -x "$cand" ]] && tool="$cand"

echo "$tool"

}

run_pve8to9_precheck() {

[[ "$SKIP_PRECHECK" == "1" ]] && { msg "SKIP_PRECHECK=1 set — skipping pve8to9."; return 0; }

msg "Running pve8to9 --full precheck..."

msg "PATH=$PATH"

type -a pve8to9 2>&1 | sed 's/^/[type] /' | tee -a "$LOG" || true

[[ -e /usr/bin/pve8to9 ]] && ls -l /usr/bin/pve8to9 | sed 's/^/[ls] /' | tee -a "$LOG" || true

local tool; tool="$(locate_pve8to9)"

if [[ -z "$tool" ]]; then

msg "pve8to9 not found — attempting to ensure 'pve-manager' is installed..."

apt-get update -y >> "$LOG" 2>&1 || true

apt-get install -y pve-manager >> "$LOG" 2>&1 || true

cleanup_nonlist_sources; verify_no_enterprise

hash -r 2>/dev/null || true

tool="$(locate_pve8to9)"

if [[ -z "$tool" ]]; then

msg "pve8to9 still not available on this system. Continuing without precheck."

return 0

msg "pve8to9 found at: $tool"

local tmp rc

tmp="$(mktemp)"

set +e

"$tool" --full | tee -a "$LOG" | tee "$tmp" >/dev/null

rc=${PIPESTATUS[0]}

set -e

if grep -qE 'FAILURES:\s*[1-9]+' "$tmp"; then

rm -f "$tmp"

die "pve8to9 reported FAILURES. Check log above."

rm -f "$tmp"

msg "pve8to9 executed (rc=$rc). No FAILURES."

}

# ---------------------------------------------------------------

# ----- header / live log hint -----

echo "== Proxmox VE 8 -> 9 upgrade started: $(date) ==" | tee -a "$LOG"

echo "$$" > /run/pve8to9.pid

ln -sfn "$LOG" /root/pve-upgrade-latest.log

echo "Live log: tail -f /root/pve-upgrade-latest.log" | tee -a "$LOG"

echo "If started via nohup, also watch its file (example: /root/pve8to9.<ts>.nohup.log)" | tee -a "$LOG"

# 0) PRE-NUKE ENTERPRISE + move backups OUT of APT dir

msg "[PRE-NUKE] Backup APT lists and clean directory..."

mkdir -p "$APT_BACKUP_DIR"

cp -a /etc/apt/sources.list "$APT_BACKUP_DIR"/ 2>/dev/null || true

cp -a /etc/apt/sources.list.d "$APT_BACKUP_DIR"/ 2>/dev/null || true

cleanup_nonlist_sources

# Remove any *.sources referencing Enterprise

for s in /etc/apt/sources.list.d/*.sources; do

[[ -f "$s" ]] || continue

grep -qi 'enterprise\.proxmox\.com' "$s" && { msg " -> removing: $s"; sink "$s"; }

done

# Remove typical filenames

sink /etc/apt/sources.list.d/pve-enterprise.sources

sink /etc/apt/sources.list.d/pve-enterprise.list

# For *.list with Enterprise: comment lines or remove if Enterprise-only

for l in /etc/apt/sources.list.d/*.list; do

[[ -f "$l" ]] || continue

if grep -qi 'enterprise\.proxmox\.com' "$l"; then

if awk 'BEGIN{IGNORECASE=1} /^[[:space:]]*deb/ && $0 !~ /enterprise\.proxmox\.com/ {ok=1} END{exit ok?0:1}' "$l"; then

msg " -> commenting Enterprise lines in: $l"

sed -ri 's|^\s*deb\s+https?://enterprise\.proxmox\.com|#DISABLED-BY-SCRIPT &|I' "$l"

else

msg " -> removing Enterprise-only list: $l"

sink "$l"

done

# Comment Enterprise in main sources.list

[[ -f /etc/apt/sources.list ]] && sed -ri 's|^\s*deb\s+https?://enterprise\.proxmox\.com|#DISABLED-BY-SCRIPT &|I' /etc/apt/sources.list || true

# Diversions + disabled deb822 file (with example.invalid), then re-clean any .distrib/.bak

divert_add /etc/apt/sources.list.d/pve-enterprise.list

divert_add /etc/apt/sources.list.d/pve-enterprise.sources

write_disabled_enterprise_sources

cleanup_nonlist_sources

verify_no_enterprise

# 1) Sanity checks

if [[ $EUID -ne 0 ]]; then die "Run as root."; fi

if ! command -v pveversion >/dev/null 2>&1; then die "Not a Proxmox VE host."; fi

CUR_VER_RAW="$(pveversion || true)"; msg "Current pveversion: $CUR_VER_RAW"

if ! echo "$CUR_VER_RAW" | grep -qE 'pve-manager/8\.'; then

msg "Expected Proxmox 8.x. Detected: $CUR_VER_RAW"

[[ "$FORCE_UPGRADE" == "1" ]] || die "Set FORCE_UPGRADE=1 to override."

# BEFORE snapshot

{

echo; echo "===== BEFORE UPGRADE ====="; date

echo "# uname -a"; uname -a || true

echo; echo "# pveversion"; pveversion || true

echo; echo "# qm list"; qm list || true

echo; echo "# pct list"; pct list || true

} >> "$LOG" 2>&1

# 2) pve8to9 precheck (robust)

run_pve8to9_precheck

# 3) Keyring + initial apt refresh

apt-get update -y >> "$LOG" 2>&1 || true

apt-get install -y proxmox-archive-keyring >> "$LOG" 2>&1 || true

verify_no_enterprise

cleanup_nonlist_sources

# 4) Switch bookworm -> trixie

msg "Switching Debian repositories: bookworm -> trixie ..."

sed -i 's/bookworm/trixie/g' /etc/apt/sources.list || true

find /etc/apt/sources.list.d -maxdepth 1 -type f -exec sed -i 's/bookworm/trixie/g' {} \; || true

# 5) Ensure single no-subscription entry

sed -ri '/download\.proxmox\.com\/debian\/pve.*pve-no-subscription/s/^/#DUPLICATE-BY-SCRIPT /' /etc/apt/sources.list || true

for l in /etc/apt/sources.list.d/*.list; do

[[ -f "$l" ]] || continue

[[ "$l" == "/etc/apt/sources.list.d/pve-no-subscription.list" ]] && continue

sed -ri '/download\.proxmox\.com\/debian\/pve.*pve-no-subscription/s/^/#DUPLICATE-BY-SCRIPT /' "$l" || true

done

cat > /etc/apt/sources.list.d/pve-no-subscription.list <<'EOF'

deb http://download.proxmox.com/debian/pve trixie pve-no-subscription

EOF

chmod 0644 /etc/apt/sources.list.d/pve-no-subscription.list

verify_no_enterprise

cleanup_nonlist_sources

# 6) Full non-interactive upgrade

msg "Running apt-get update + non-interactive upgrade/dist-upgrade..."

TMPU="$(mktemp)"

apt-get update 2>&1 | tee -a "$LOG" | tee "$TMPU" >/dev/null

if grep -q 'enterprise\.proxmox\.com' "$TMPU"; then rm -f "$TMPU"; die "APT tried to reach Enterprise during update."; fi

rm -f "$TMPU"

apt-get -o Dpkg::Options::="--force-confdef" -o Dpkg::Options::="--force-confold" upgrade -y | tee -a "$LOG"

apt-get -o Dpkg::Options::="--force-confdef" -o Dpkg::Options::="--force-confold" dist-upgrade -y | tee -a "$LOG"

# Second cleanup pass

cleanup_nonlist_sources

apt-get autoremove -y | tee -a "$LOG" || true

apt-get update -y >> "$LOG" 2>&1 || true

# 7) One-shot post-boot verification

POST_SH="/root/pve-postcheck.sh"

POST_SVC="/etc/systemd/system/pve-upgrade-postcheck.service"

cat > "$POST_SH" <<'EOS'

#!/bin/bash

set -euo pipefail

LOG_FILE="/root/pve-upgrade-post-$(date +%Y%m%d-%H%M%S).log"

{

echo "===== AFTER UPGRADE (first boot) ====="; date

echo "# uname -a"; uname -a || true

echo; echo "# pveversion"; pveversion || true

echo; echo "# apt policy (trixie check)"; apt-cache policy | sed -n '1,120p' || true

} >> "$LOG_FILE" 2>&1

systemctl disable --now pve-upgrade-postcheck.service >/dev/null 2>&1 || true

rm -f /root/pve-postcheck.sh

EOS

chmod +x "$POST_SH"

cat > "$POST_SVC" <<'EOS'

[Unit]

Description=Proxmox upgrade post-check (one-shot)

After=multi-user.target pvedaemon.service pve-cluster.service

Wants=network-online.target

[Service]

Type=oneshot

ExecStart=/bin/bash /root/pve-postcheck.sh

[Install]

WantedBy=multi-user.target

EOS

systemctl daemon-reload

systemctl enable pve-upgrade-postcheck.service >> "$LOG" 2>&1 || true

# 8) Pre-reboot snapshot

{

echo; echo "===== PRE-REBOOT SNAPSHOT ====="; date

echo "# Installed pve kernels:"; dpkg -l | grep -E '^ii\s+pve-kernel' | sort -V || true

} >> "$LOG" 2>&1

msg "Upgrade phase completed. Log: $LOG"

if [[ "$NO_REBOOT" == "1" ]]; then

msg "NO_REBOOT=1 set — skipping reboot. Please reboot manually."

else

msg "Rebooting now to complete the upgrade..."

sleep 3

reboot

Below is the full content of the script for reference. It is recommended to download the latest version from the link above to ensure you have the most up-to-date fixes.

Post-upgrade verification

pveversion

1	pveversion

Expected output should look like:

pve-manager/9.x.x/xxxxxxxx (running kernel: 6.x.x-x-pve)
Check the running kernel version:

uname -a

uname -a

Review the upgrade log to confirm no errors occurred:

less /root/pve-upgrade-*.log

1	less /root/pve-upgrade-*.log

If you used the post-check service created by the script, you can view its results:

less /root/pve-upgrade-post-*.log

1	less /root/pve-upgrade-post-*.log

Dynamic Tmux Window Titles with SSH and Hostname

Posted on April 15, 2025April 15, 2025 by soban

Want your Tmux window titles to automatically show the hostname you connect to via SSH — and restore the local name after you disconnect? This guide will walk you through setting that up step by step.

1. Tmux configuration – ~/.tmux.conf

In your Tmux configuration file, set the default shell command to a custom Bash init file (.bash_tmux) that will handle window title updates.

set-option -g default-command 'bash --rcfile ~/.bash_tmux'

1	set-option -g default-command 'bash --rcfile ~/.bash_tmux'

2. Bash init script – ~/.bash_tmux

This file runs at shell startup inside Tmux. It sets the window name to your local hostname and overrides the ssh command to change the window title dynamically.

#!/bin/bash
# ~/.bash_tmux
# Custom Bash init file for Tmux sessions with dynamic tab naming
# Override the default ssh command to dynamically rename the Tmux window
ssh() {
if [ -n "$TMUX" ]; then
# Loop through arguments to find the target host (first non-flag argument)
for arg in "$@"; do
if [[ "$arg" != -* ]]; then
if [[ "$arg" == *@* ]]; then
host="${arg#*@}"  # extract host from user@host
else
host="$arg"
fi
break
fi
done
# Strip any trailing junk or whitespace
host="$(echo "$host" | cut -d' ' -f1)"
# Rename the Tmux window to the SSH target
[ -n "$host" ] && tmux rename-window "$host"
# Save the local hostname to restore later
local_host="$(hostname -s)"
# Run the actual SSH command
command ssh "$@"
# Restore the original window name after logout
tmux rename-window "$local_host"
else
# Not in Tmux — just run ssh normally
command ssh "$@"
fi
}
# Load the user's regular bash configuration
source ~/.bashrc
# On shell start, if in Tmux, set the window name to the current hostname
if [ -n "$TMUX" ]; then
tmux rename-window "$(hostname -s)"
fi

#!/bin/bash

# ~/.bash_tmux

# Custom Bash init file for Tmux sessions with dynamic tab naming

# Override the default ssh command to dynamically rename the Tmux window

ssh() {

if [ -n "$TMUX" ]; then

# Loop through arguments to find the target host (first non-flag argument)

for arg in "$@"; do

if [[ "$arg" != -* ]]; then

if [[ "$arg" == *@* ]]; then

host="${arg#*@}" # extract host from user@host

else

host="$arg"

break

done

# Strip any trailing junk or whitespace

host="$(echo "$host" | cut -d' ' -f1)"

# Rename the Tmux window to the SSH target

[ -n "$host" ] && tmux rename-window "$host"

# Save the local hostname to restore later

local_host="$(hostname -s)"

# Run the actual SSH command

command ssh "$@"

# Restore the original window name after logout

tmux rename-window "$local_host"

else

# Not in Tmux — just run ssh normally

command ssh "$@"

}

# Load the user's regular bash configuration

source ~/.bashrc

# On shell start, if in Tmux, set the window name to the current hostname

if [ -n "$TMUX" ]; then

tmux rename-window "$(hostname -s)"

3. Reload Tmux config without restarting

To apply the changes without restarting the Tmux session, run the following:

tmux source-file ~/.tmux.conf

1	tmux source-file ~/.tmux.conf

To manually reload the current shell with the new .bash_tmux configuration:

exec bash --rcfile ~/.bash_tmux

1	exec bash --rcfile ~/.bash_tmux

4. Final result

New Tmux windows automatically show the local hostname
When connecting via SSH, the window is renamed to the remote host
When disconnecting, the original local name is restored

Clean, readable, and perfect for sysadmins, devops engineers, and Tmux lovers who appreciate automatic order in their terminal tabs 💪

The most important Linux commands that every user should know

Posted on February 20, 2025February 20, 2025 by soban

The Linux system is a powerful tool that offers users tremendous flexibility and control over their working environment. However, to fully harness its potential, it is worth knowing the key commands that are essential for both beginners and advanced users. In this article, we will present and discuss the most important Linux commands that every user should know.

1. Basic Navigation Commands

pwd – Displays the current directory path you are in:

pwd

pwd

ls – Lists the contents of a directory. You can use the -l option for a detailed view or -a to show hidden files:

ls -a

ls -a

cd – Changes the directory. For example, cd /home/user will move you to the /home/user directory:

cd ~

cd ~

mkdir – Creates a new directory:

mkdir projects

1	mkdir projects

rmdir – Removes an empty directory:

rmdir old_files

1	rmdir old_files

2. File Management

cp – Copies files or directories:

cp document.txt new_directory/

1	cp document.txt new_directory/

mv – Moves or renames files/directories:

mv file.txt /home/user/new_directory/

1	mv file.txt /home/user/new_directory/

rm – Removes files or directories. Use the -r option to remove a directory with its contents:

rm -r old_data

1	rm -r old_data

touch – Creates an empty file or updates the modification time of an existing file:

touch report.txt

1	touch report.txt

3. Process Management

ps – Displays currently running processes. Use the -aux option to see all processes:

ps -aux

ps -aux

top – Displays a dynamic list of processes in real time:

top

top

kill – Stops a process by its ID:

kill 1234

kill 1234

bg and fg – Manage background and foreground processes:

fg

4. User and Permission Management

sudo – Allows a command to be executed with administrator privileges:

sudo apt update

1	sudo apt update

chmod – Changes permissions for files/directories:

chmod 755 script.sh

1	chmod 755 script.sh

chown – Changes the owner of a file/directory:

chown admin:admin file.txt

1	chown admin:admin file.txt

useradd and userdel – Adds and removes users:

useradd janek

1	useradd janek

5. Networking and Communication

ping – Checks the connection with another host:

ping 192.168.1.1

1	ping 192.168.1.1

ifconfig – Displays information about network interfaces:

ifconfig

ifconfig

ssh – Connects remotely to another computer:

ssh user@192.168.1.2

1	ssh user@192.168.1.2

scp – Copies files over SSH:

scp file.txt user@host:/home/user/

1	scp file.txt user@host:/home/user/

6. Command Usage Examples

Below is an example of using several discussed commands:

chmod – Changes permissions for files/directories:

chmod 755 script.sh

1	chmod 755 script.sh

chown – Changes the owner of a file/directory:

chown admin:developers logs.txt

1	chown admin:developers logs.txt

useradd and userdel – Adds and removes users:

useradd janek

1	useradd janek

7. Disk and File System Management

df – Displays information about disk space availability:

df -h

df -h

du – Shows the size of files and directories:

du -sh documents

1	du -sh documents

mount – Mounts a file system:

mount /dev/sdb1 /mnt/external

1	mount /dev/sdb1 /mnt/external

umount – Unmounts a file system:

umount /mnt/external

1	umount /mnt/external

8. Searching for Files

find – Searches for files in the system:
locate – Quickly searches for files in the system:
grep – Searches for patterns in files:
which – Finds the full path to an executable file:

9. Communicating with the System

echo – Displays text on the screen:
cat – Displays the contents of a file:
more – Displays the contents of a file page by page:
less – Similar to more, but offers more navigation options:
man – Displays the user manual for a command:

10. Working with Archives

tar – Creates or extracts archives:
zip – Creates a ZIP archive:
unzip – Extracts ZIP files:
tar -xvzf – Extracts a TAR.GZ archive:
gzip – Compresses files in .gz format:
gunzip – Extracts .gz files:

11. System Monitoring

uptime – Displays the system uptime and load:
dmesg – Displays system messages related to boot and hardware:
iostat – Shows input/output system statistics:
free – Displays information about RAM:
netstat – Displays information about network connections:
ss – A modern version of netstat, used for monitoring network connections:

12. Working with System Logs

journalctl – Reviews system logs:
tail – Displays the last lines of a file:
logrotate – Automatically manages logs:

13. Advanced File Operations

ln – Creates a link to a file:
xargs – Passes arguments from input to other commands:
chmod – Changes permissions for files/directories:
chattr – Changes file attributes:

Linux offers a wide array of commands that allow for complete control over the computer. Key commands such as ls, cd, cp, and rm are used daily to navigate through the file system, manage files, and directories. To effectively master these commands, it’s best to start with those that are most useful in everyday work. For instance, commands for navigating directories and managing files are fundamental and require practice to become intuitive. Other commands, such as ps for monitoring processes, ping for testing network connections, or chmod for changing permissions, are also worth knowing to fully leverage the power of the Linux system.

To learn effectively, it’s advisable to start by experimenting with commands in practice. Creating files, directories, copying, and deleting data allows for familiarity with their operation. Over time, it’s worthwhile to start combining different commands to solve more advanced problems, such as monitoring processes, managing users, or working with system logs. One can also use documentation, such as man or websites, to delve into the details of each command and its options.

Remember, regular use of the terminal allows for learning habits that make handling the Linux system more natural. Frequent use of commands, solving problems, and experimenting with new commands is the best way to master the system and fully utilize it.

Linux is indeed a powerful tool that provides great control over the system… but remember, don’t experiment on production! After all, experimenting on a production server is a bit like playing Russian roulette — only with bigger consequences. If you want to feel like a true Linux wizard, always test your commands in a development environment. Only then will you be able to learn from mistakes instead of searching for the cause of several gigabytes of data disappearance. And if you don’t know what you’re doing, simply summon your trusty weapon: man!

Enhancing Virtual Machine Management with QEMU Guest Agent on Proxmox

Posted on February 11, 2025February 11, 2025 by soban

Ever wondered how to streamline the management and monitoring of virtual machines in your Proxmox environment? QEMU Guest Agent is a game-changer, offering tools that significantly enhance the way you interact with virtual systems. Let’s dive into how this tool can transform your setup.

What Makes QEMU Guest Agent Indispensable?

Time Synchronization: Keeping time consistent across your virtual machines and the host can be tricky, but QEMU Guest Agent automates this, ensuring that time-sensitive operations run smoothly.
Power Management: Imagine being able to shut down or reboot your virtual machines right from the Proxmox panel — no need to log in to each VM. It’s not only convenient but also a time saver.
System Monitoring: Get detailed insights into file systems, network activities, and other operational parameters directly from your host. This level of monitoring allows for timely diagnostics and adjustments.
Disk Management: Handling disk operations without having to intervene directly on the VM makes backing up and restoring data more straightforward than ever.

Setting Up QEMU Guest Agent on Your Proxmox Server

Getting started with QEMU Guest Agent involves a few simple steps:

Enable the Agent: Log in to your Proxmox panel, go to the ‘Options’ section of your desired VM, and make sure the ‘QEMU Guest Agent’ option is checked.

Next up, installing it on an Ubuntu VM:

sudo apt-get install qemu-guest-agent
sudo systemctl start qemu-guest-agent
sudo systemctl enable qemu-guest-agent

sudo apt-get install qemu-guest-agent

sudo systemctl start qemu-guest-agent

sudo systemctl enable qemu-guest-agent

To check whether the qeumu-guest-agent that can make the change is working properly:

systemctl status qemu-guest-agent

1	systemctl status qemu-guest-agent

The QEMU Guest Agent doesn’t just make life easier by automating the mundane tasks — it also enhances the security and efficiency of your virtual environment. Whether you’re managing a single VM or a whole fleet, it’s an invaluable addition to your toolkit.

Automatic deletion of files on QNAP drive via SSHFS

Posted on February 7, 2025February 11, 2025 by soban

Automation of Disk Space Management in a Linux Environment

In today’s digital world, where data is being accumulated in ever-increasing amounts, managing disk space has become a key aspect of maintaining operational efficiency in systems. In this article, I will present a script that automates the process of managing space on a remote disk mounted via SSHFS, particularly useful for system administrators who regularly deal with filling storage media.

Prerequisites

Before starting, ensure that SSHFS and all necessary packages enabling its proper operation are installed on your system. SSHFS allows remote file systems to be mounted via SSH, which is crucial for our script’s operation. To install SSHFS and the necessary tools, including a package that enables password forwarding (sshpass), use the following command:

apt-get update
apt-get install sshfs fuse sshpass -y

1 2	apt-get update apt-get install sshfs fuse sshpass -y

Bash Script for Disk Space Management

Our Bash script focuses on monitoring and maintaining a defined percentage of free disk space on a remote disk mounted via SSHFS. Here are the script’s main functions:

Goal Definition:

TARGET_USAGE=70 – the percentage of disk space we want to maintain as occupied. The script will work to keep at least 30% of the disk space free.

Mount Point and Paths:

MOUNT_POINT=”/mnt/qnapskorupki” – the local directory where the remote disk is mounted. TARGET_DIRS=”$MOUNT_POINT/up*.soban.pl” – the directories where the script will look for files to delete if needed.

Function check_qnap: This function checks whether the disk is mounted and whether the mount directory is not empty. If there are issues, the script attempts to unmount and remount the disk using sshfs with a password forwarded through sshpass.

File Deletion: The script monitors disk usage and, if TARGET_USAGE is exceeded, it finds and deletes the oldest files in specified directories until the target level of free space is achieved.

#!/bin/bash
TARGET_USAGE=70
MOUNT_POINT="/mnt/qnapskorupki"
TARGET_DIRS="$MOUNT_POINT/up*.soban.pl"
# Function to check and mount SSHFS
function check_qnap {
local remote_path="/share/MD0_DATA/backup_proxmox/"
local user_remote="remote_user"
local remote_host="192.168.1.XX"
local port=22
local password='XXXXXXXXXXXXXXXXXXXXXXX'
# Check if the mounting directory exists and is empty
if [ ! -d "$MOUNT_POINT" ] || [ -z "$(ls -A $MOUNT_POINT)" ]; then
echo "Problem: The directory $MOUNT_POINT is missing or empty. Attempting to remount..."
# Unmount if anything is currently mounted
if mountpoint -q $MOUNT_POINT; then
echo "Unmounting $MOUNT_POINT..."
fusermount -u $MOUNT_POINT
sleep 5
fi
# Remount
echo "Mounting SSHFS: $user_remote@$remote_host:$remote_path to $MOUNT_POINT..."
echo $password | sshfs $user_remote@$remote_host:$remote_path $MOUNT_POINT -o password_stdin
# Check if the mounting was successful
if mountpoint -q $MOUNT_POINT; then
echo "QNAP successfully mounted."
else
echo "Error: Failed to mount $remote_host:$remote_path to $MOUNT_POINT."
exit 1
fi
fi
}
# Check and mount the disk
check_qnap
# Begin deleting files
current_usage=$(df --output=pcent "$MOUNT_POINT" | tail -n 1 | tr -d '%')
echo "Current usage: $current_usage%"
target_free_space=$((100 - $TARGET_USAGE))
# Continue deleting files until the required free space is achieved
while [[ $current_usage -gt $TARGET_USAGE ]]; do
# Find the oldest file in the target directories
oldest_file=$(find $TARGET_DIRS -type f -printf '%T+ %p\n' | sort | head -n 1 | cut -d' ' -f2)
if [ -z "$oldest_file" ]; then
echo "No files to delete."
break
fi
# Delete the oldest file
echo "Deleting file $oldest_file..."
rm -f "$oldest_file"
# Check usage again
current_usage=$(df --output=pcent "$MOUNT_POINT" | tail -n 1 | tr -d '%')
echo "New usage after deletion: $current_usage%"
done
echo "Target disk usage achieved."

#!/bin/bash

TARGET_USAGE=70

MOUNT_POINT="/mnt/qnapskorupki"

TARGET_DIRS="$MOUNT_POINT/up*.soban.pl"

# Function to check and mount SSHFS

function check_qnap {

local remote_path="/share/MD0_DATA/backup_proxmox/"

local user_remote="remote_user"

local remote_host="192.168.1.XX"

local port=22

local password='XXXXXXXXXXXXXXXXXXXXXXX'

# Check if the mounting directory exists and is empty

if [ ! -d "$MOUNT_POINT" ] || [ -z "$(ls -A $MOUNT_POINT)" ]; then

echo "Problem: The directory $MOUNT_POINT is missing or empty. Attempting to remount..."

# Unmount if anything is currently mounted

if mountpoint -q $MOUNT_POINT; then

echo "Unmounting $MOUNT_POINT..."

fusermount -u $MOUNT_POINT

sleep 5

# Remount

echo "Mounting SSHFS: $user_remote@$remote_host:$remote_path to $MOUNT_POINT..."

echo $password | sshfs $user_remote@$remote_host:$remote_path $MOUNT_POINT -o password_stdin

# Check if the mounting was successful

if mountpoint -q $MOUNT_POINT; then

echo "QNAP successfully mounted."

else

echo "Error: Failed to mount $remote_host:$remote_path to $MOUNT_POINT."

exit 1

}

# Check and mount the disk

check_qnap

# Begin deleting files

current_usage=$(df --output=pcent "$MOUNT_POINT" | tail -n 1 | tr -d '%')

echo "Current usage: $current_usage%"

target_free_space=$((100 - $TARGET_USAGE))

# Continue deleting files until the required free space is achieved

while [[ $current_usage -gt $TARGET_USAGE ]]; do

# Find the oldest file in the target directories

oldest_file=$(find $TARGET_DIRS -type f -printf '%T+ %p\n' | sort | head -n 1 | cut -d' ' -f2)

if [ -z "$oldest_file" ]; then

echo "No files to delete."

break

# Delete the oldest file

echo "Deleting file $oldest_file..."

rm -f "$oldest_file"

# Check usage again

current_usage=$(df --output=pcent "$MOUNT_POINT" | tail -n 1 | tr -d '%')

echo "New usage after deletion: $current_usage%"

done

echo "Target disk usage achieved."

Example Script Execution:

script starts working and gradually deletes files

The script will run until it reaches 70% usage as planned:

Downloading the script and adding it to crontab

Of course, the script should be adjusted to meet your specific needs. However, if you want to download it and add it to crontab, follow these steps:

wget soban.pl/bash/remove_old_files.sh
chmod +x remove_old_files.sh

1 2	wget soban.pl/bash/remove_old_files.sh chmod +x remove_old_files.sh

If you want to automate the file removal process, for example, at the end of the day, add the following entry to crontab:

crontab -e

1	crontab -e

In this case, the script will run every day at 11:55 PM:

45 23 * * * /root/scripts/remove_old_files.sh > /dev/null 2>&1

1	45 23 * * * /root/scripts/remove_old_files.sh > /dev/null 2>&1

Make sure to use the correct path to the script.

Security and Optimization

The script uses a password directly in the command line, which can pose a security risk. In practical applications, it is recommended to use more advanced authentication methods, such as SSH keys, which are more secure and do not require a plaintext password in the script. However, in the case of QNAP, we used a password when writing this script.

Conclusion

The presented script is an example of how daily administrative tasks, such as disk space management, can be automated, thus increasing efficiency and reliability. Its implementation in real IT environments can significantly streamline data management processes, especially in situations where quick response to changes in disk usage is critical.

How to automatically turn off your laptop when battery status is displayed in Linux

Posted on January 24, 2025January 24, 2025 by soban

Automatically Shutting Down Your Laptop at Low Battery Levels

Maintaining long battery life and protecting data are crucial for laptop users. In this article, we’ll show you how to create a simple Bash script that automatically shuts down your laptop when the battery level falls below 20%. Additionally, you’ll learn how to set up a crontab to run the script every 10 minutes, ensuring continuous monitoring.

Creating a Bash Script

The Bash script we have prepared will check the current battery level and compare it to a set minimum threshold. If the battery level drops below this threshold, the script initiates a system shutdown, helping to protect your data and hardware.

#!/bin/bash
# Define the minimum battery level before shutdown
MIN_BATTERY_LEVEL=20
# Get the current battery level
current_level=$(cat /sys/class/power_supply/BAT0/capacity)
# Check if the current battery level is less than or equal to the minimum level
if [[ "$current_level" -le "$MIN_BATTERY_LEVEL" ]]; then
echo "Battery level is $current_level%, which is below the threshold of $MIN_BATTERY_LEVEL%. Shutting down..."
# Shutdown command
/sbin/shutdown -h now
else
echo "Battery level is $current_level%, no need to shut down."
fi

#!/bin/bash

# Define the minimum battery level before shutdown

MIN_BATTERY_LEVEL=20

# Get the current battery level

current_level=$(cat /sys/class/power_supply/BAT0/capacity)

# Check if the current battery level is less than or equal to the minimum level

if [[ "$current_level" -le "$MIN_BATTERY_LEVEL" ]]; then

echo "Battery level is $current_level%, which is below the threshold of $MIN_BATTERY_LEVEL%. Shutting down..."

# Shutdown command

/sbin/shutdown -h now

else

echo "Battery level is $current_level%, no need to shut down."

Also you can download script:

wget https://soban.pl/bash/check_battery.sh

1	wget https://soban.pl/bash/check_battery.sh

Don’t forget to grant permissions to run it:

chmod +x check_battery.sh

1	chmod +x check_battery.sh

Crontab Configuration

Crontab is a tool that allows you to schedule tasks in the Linux system. With it, we can set up regular battery checks.

crontab -e
# Add the following line to crontab to run the script every 10 minutes
*/10 * * * * /root/check_battery.sh > /dev/null 2>&1

crontab -e

# Add the following line to crontab to run the script every 10 minutes

*/10 * * * * /root/check_battery.sh > /dev/null 2>&1

Summary

With this setup, you can rest assured about the condition of your laptop even during intensive use. Automatic shutdown at low battery levels not only protects the equipment but also helps maintain a longer battery life.

Expanding Storage Space in Linux: Step-by-Step Guide using LVM and fdisk

Posted on November 13, 2024November 13, 2024 by soban

Expanding disk space in Linux virtual machines is a key aspect of server system management. In this article, we show how to effectively increase disk space using LVM and fdisk tools, based on real system data.

Preliminary Preparations

Before making changes to partitions and volumes, it is important to check the current state of the disks in the system. We will use the lsblk command to identify available disks and partitions.

lsblk

lsblk

Here is an example of the lsblk command output on a machine:

NAME                      MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
loop0                       7:0    0 55.7M  1 loop /snap/core18/2829
sda                         8:0    0   42G  0 disk
├─sda1                      8:1    0  512M  0 part /boot/efi
├─sda2                      8:2    0    1G  0 part /boot
└─sda3                      8:3    0 40.5G  0 part
└─ubuntu--vg-ubuntu--lv 253:0    0 78.5G  0 lvm  /
sdb                         8:16   0  350G  0 disk
└─sdb1                      8:17   0   60G  0 part
└─ubuntu--vg-ubuntu--lv 253:0    0 78.5G  0 lvm  /
sr0                        11:0    1 1024M  0 rom

NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT

loop0 7:0 0 55.7M 1 loop /snap/core18/2829

sda 8:0 0 42G 0 disk

├─sda1 8:1 0 512M 0 part /boot/efi

├─sda2 8:2 0 1G 0 part /boot

└─sda3 8:3 0 40.5G 0 part

└─ubuntu--vg-ubuntu--lv 253:0 0 78.5G 0 lvm /

sdb 8:16 0 350G 0 disk

└─sdb1 8:17 0 60G 0 part

└─ubuntu--vg-ubuntu--lv 253:0 0 78.5G 0 lvm /

sr0 11:0 1 1024M 0 rom

Creating Snapshots

Before making changes to disk configurations, it is advisable to create a snapshot of the LVM volumes to ensure data can be restored in case of unexpected issues.

lvcreate -L 20G -s -n my_snapshot /dev/ubuntu-vg/ubuntu-lv

1	lvcreate -L 20G -s -n my_snapshot /dev/ubuntu-vg/ubuntu-lv

Modifying Partitions

Next, we proceed to modify the partitions using fdisk. We remove the existing partition and then create a new one that utilizes the entire available space on disk sdb.

fdisk /dev/sdb

1	fdisk /dev/sdb

Saving Changes

After properly configuring the partitions, we use the w command in fdisk to save the changes and update the partition table.

Command (m for help): w

1	Command (m for help): w

Executing pvscan

After modifying the partitions, we execute the pvscan command so the system can update information about available physical volumes.

pvscan

pvscan

Configuring LVM

After saving changes to the partition table, we need to update the LVM configuration to include the new disk space. We use the lvextend command with automatic file system resizing.

lvextend -l +100%FREE /dev/ubuntu-vg/ubuntu-lv -r

1	lvextend -l +100%FREE /dev/ubuntu-vg/ubuntu-lv -r

Summary

Expanding disk space on a Linux virtual machine enhances performance and the availability of storage space. Thanks to the steps described, managing disk space in systems using LVM becomes simpler and more efficient.

Troubleshooting Proxmox clusters and restoring the LXC container

Posted on November 13, 2024November 13, 2024 by soban

Managing Proxmox clusters can sometimes present technical difficulties, such as inconsistencies in cluster configuration or issues with restoring LXC containers. Finding and resolving these issues is crucial for maintaining the stability and performance of the virtualization environment. In this article, I present a detailed guide on how to diagnose and resolve an issue with an unreachable node and how to successfully restore an LXC container.

Before you begin any actions, make sure you have a current backup of the system.

Diagnosing the State of the Proxmox Cluster

pvecm delnode up-page-02
Node/IP: up-page-02 is not a known host of the cluster.

1 2	pvecm delnode up-page-02 Node/IP: up-page-02 is not a known host of the cluster.

and:

pct restore 107 vzdump-lxc-107-2024_11_12-03_00_01.tar.zst --storage local
CT 107 already exists on node 'up-page-02'

1 2	pct restore 107 vzdump-lxc-107-2024_11_12-03_00_01.tar.zst --storage local CT 107 already exists on node 'up-page-02'

To understand the state of the cluster, execute the following command on the node-up-page-04 node:

pvecm nodes

1	pvecm nodes

Expected output:

Membership information
----------------------
Nodeid      Votes Name
1          1 node-up-page-01
2          1 node-up-page-04 (local)

Membership information

----------------------

Nodeid Votes Name

1 1 node-up-page-01

2 1 node-up-page-04 (local)

Then check the detailed cluster information with the following command:

pvecm status

1	pvecm status

Expected output:

Cluster information
-------------------
Name:             soban-proxmox
Config Version:   4
Transport:        knet
Secure auth:      on
Quorum information
------------------
Date:             Wed Nov 13 10:40:12 2024
Quorum provider:  corosync_votequorum
Nodes:            2
Node ID:          0x00000002
Ring ID:          1.e6
Quorate:          Yes
Votequorum information
----------------------
Expected votes:   2
Highest expected: 2
Total votes:      2
Quorum:           2
Flags:            Quorate
Membership information
----------------------
Nodeid      Votes Name
0x00000001          1 <masked IP>
0x00000002          1 <masked IP> (local)

Cluster information

-------------------

Name: soban-proxmox

Config Version: 4

Transport: knet

Secure auth: on

Quorum information

------------------

Date: Wed Nov 13 10:40:12 2024

Quorum provider: corosync_votequorum

Nodes: 2

Node ID: 0x00000002

Ring ID: 1.e6

Quorate: Yes

Votequorum information

----------------------

Expected votes: 2

Highest expected: 2

Total votes: 2

Quorum: 2

Flags: Quorate

Membership information

----------------------

Nodeid Votes Name

0x00000001 1 <masked IP>

0x00000002 1 <masked IP> (local)

Removing the Container Configuration File and Cleaning Data

I discovered that the configuration file for container 107 still exists on the cluster’s file system at the path:

ls -ltr /etc/pve/nodes/node-up-page-02/lxc/107.conf

1	ls -ltr /etc/pve/nodes/node-up-page-02/lxc/107.conf

Output:

-rw-r----- 1 root www-data 235 Nov 12 21:35 /etc/pve/nodes/node-up-page-02/lxc/107.conf

1	-rw-r----- 1 root www-data 235 Nov 12 21:35 /etc/pve/nodes/node-up-page-02/lxc/107.conf

To remove this file and any remaining data associated with the detached node, execute:

rm -rf /etc/pve/nodes/node-up-page-02/

1	rm -rf /etc/pve/nodes/node-up-page-02/

Restoring the Container

After removing the configuration file, I restored the LXC container on the node-up-page-04 node using the command:

pct restore 107 /root/vzdump-lxc-107-2024_11_12-03_00_01.tar.zst --storage local

1	pct restore 107 /root/vzdump-lxc-107-2024_11_12-03_00_01.tar.zst --storage local

Output:

recovering backed-up configuration from '/root/vzdump-lxc-107-2024_11_12-03_00_01.tar.zst'
Formatting '/var/lib/vz/images/107/vm-107-disk-0.raw', fmt=raw size=59055800320 preallocation=off
Creating filesystem with 14417920 4k blocks and 3604480 inodes
Filesystem UUID: 8b707e55-5e14-4b20-8585-6cb09e0fa520
Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000, 7962624, 11239424
restoring '/root/vzdump-lxc-107-2024_11_12-03_00_01.tar.zst' now..
extracting archive '/root/vzdump-lxc-107-2024_11_12-03_00_01.tar.zst'

recovering backed-up configuration from '/root/vzdump-lxc-107-2024_11_12-03_00_01.tar.zst'

Formatting '/var/lib/vz/images/107/vm-107-disk-0.raw', fmt=raw size=59055800320 preallocation=off

Creating filesystem with 14417920 4k blocks and 3604480 inodes

Filesystem UUID: 8b707e55-5e14-4b20-8585-6cb09e0fa520

Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000, 7962624, 11239424

restoring '/root/vzdump-lxc-107-2024_11_12-03_00_01.tar.zst' now..

extracting archive '/root/vzdump-lxc-107-2024_11_12-03_00_01.tar.zst'

The restoration process was successful, and the container was ready for use. This case illustrates the importance of thorough diagnostics and configuration file management in Proxmox when working with clusters. Regular reviews of configurations are advisable to avoid inconsistencies and operational issues in the future.