Q4OS Forum

chisli

Member

Registered: 2025-12-26

Posts: 1

No power off when shut-down after upgrade from gemini to aquarius

I've upgraded my WUBI bullseye (gemini) installation to bookworm (aquarius). The upgrade process went quite good, but the shut-down process does not power off the PC and shows the folowing last entry: Reached target poweroff.target System Power Off.

I've tried to change the shut-down parameters in grub, but that does not solve the problem. At least I solved the "kernel panic - not syncing" error with this settings.
GRUB_CMDLINE_LINUX_DEFAULT="quiet loglevel=3 systemd.log_color=0 systemd.show_status=1 acpi=off apm=power_off"

Does anyone know what to do that the PC power off as before on bullseye.

swarfendor437

Member

Registered: 2024-11-06

Posts: 64

Re: No power off when shut-down after upgrade from gemini to aquarius

Hi chisli. I cheated and used Brave A.I.:

"Upgrading from Debian Bullseye to Bookworm can sometimes lead to issues with virtual machine power management, such as the inability to properly shut down or reboot a system. In one reported case, a virtual machine (VM) with ID 107, originally created by cloning a Bullseye template and upgraded to Bookworm using standard APT commands, exhibited problematic behavior where it would not power off or reboot normally through the Proxmox interface. The VM would only shut down successfully when using the force commands poweroff -f or reboot -f, indicating a potential issue with the shutdown sequence or service management during the upgrade process.

This issue may be related to configuration problems or lingering dependencies from the previous Bullseye installation, especially if the system was not fully cleaned up after the upgrade. For example, some users have reported that packages from older releases remain installed and functional unless explicitly removed, which can lead to unexpected behavior.
Additionally, the upgrade process itself may leave behind transitional packages or misconfigured services, particularly if third-party repositories were used or if system services were not properly managed during the upgrade.

To resolve such issues, it is recommended to ensure that the system is fully updated and cleaned after the upgrade. This includes running apt --purge autoremove to remove obsolete packages and configuration files.
It is also important to verify that all services are properly configured and that no lingering configuration files from Bullseye are interfering with the shutdown process. If the problem persists, checking the system logs (e.g., journalctl or dmesg) may help identify which service or process is preventing the shutdown.

Furthermore, Debian officially supports upgrades only from one stable release to the next, such as Bullseye to Bookworm, and recommends backing up critical data and configuration files before proceeding.
While the upgrade process is generally reliable, hardware-specific configurations or third-party software may introduce complications. For remote systems, it is advisable to use a serial console or rescue mode to recover if the system fails to boot after the upgrade.

AI-generated answer. Please verify critical facts."

---

ASUS PRIME X470-PRO, AMD Ryzen 7 1700X 8 Core, 16 Gb RAM, Asus GT1030 2 Gb DDR-5  Q4OS 5.9 (Aquarius)