Proxmox Reboot for no reason, then stuck in a bootloop

phil9309

New Member
Oct 1, 2024
2
0
1
Hi friends,

I had Proxmox randomly shutdown/try to reboot at night, then stuck in a bootloop for a few minutes and then die for the second time now in the last week.

I can only restart the server by cutting power, then it'll reboot normally. My proxmox server has been running more than fine on a Lenovo m720q with an i5 8400t and 64gb of ram for months now.

The logs prior to the first shutdown/reboot are nothing special it seems:

Code:
Oct 01 02:18:22 schmangstlbase postfix/qmgr[1130]: 159121A0793: from=<root@schmangstlbase.local>, size=716, nrcpt=1 (queue active)
Oct 01 02:18:22 schmangstlbase postfix/qmgr[1130]: 45FA31A0C9A: from=<root@schmangstlbase.local>, size=716, nrcpt=1 (queue active)
Oct 01 02:18:22 schmangstlbase postfix/qmgr[1130]: 4F48C1A105E: from=<>, size=3627, nrcpt=1 (queue active)
Oct 01 02:18:22 schmangstlbase postfix/local[675756]: error: open database /etc/aliases.db: No such file or directory
Oct 01 02:18:22 schmangstlbase postfix/local[675756]: warning: hash:/etc/aliases is unavailable. open database /etc/aliases.db: No such file or directory
Oct 01 02:18:22 schmangstlbase postfix/local[675756]: warning: hash:/etc/aliases: lookup of 'root' failed
Oct 01 02:18:22 schmangstlbase postfix/local[675759]: error: open database /etc/aliases.db: No such file or directory
Oct 01 02:18:22 schmangstlbase postfix/local[675759]: warning: hash:/etc/aliases is unavailable. open database /etc/aliases.db: No such file or directory
Oct 01 02:18:22 schmangstlbase postfix/local[675759]: warning: hash:/etc/aliases: lookup of 'root' failed
Oct 01 02:18:22 schmangstlbase postfix/local[675756]: 159121A0793: to=<root@schmangstlbase.local>, orig_to=<root>, relay=local, delay=214716, delays=214716/0.01/0/0.01, dsn=4.3.0>
Oct 01 02:18:22 schmangstlbase postfix/local[675756]: warning: hash:/etc/aliases is unavailable. open database /etc/aliases.db: No such file or directory
Oct 01 02:18:22 schmangstlbase postfix/local[675756]: warning: hash:/etc/aliases: lookup of 'root' failed
Oct 01 02:18:22 schmangstlbase postfix/local[675759]: 45FA31A0C9A: to=<root@schmangstlbase.local>, orig_to=<root>, relay=local, delay=29875, delays=29875/0.01/0/0.01, dsn=4.3.0, >
Oct 01 02:18:22 schmangstlbase postfix/local[675756]: 4F48C1A105E: to=<root@schmangstlbase.local>, relay=local, delay=260912, delays=260912/0.02/0/0, dsn=4.3.0, status=deferred (>
Oct 01 02:25:01 schmangstlbase CRON[684919]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Oct 01 02:25:01 schmangstlbase CRON[684920]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Oct 01 02:25:01 schmangstlbase CRON[684919]: pam_unix(cron:session): session closed for user root
Oct 01 02:28:22 schmangstlbase postfix/qmgr[1130]: 287D91A0A26: from=<>, size=3637, nrcpt=1 (queue active)
Oct 01 02:28:22 schmangstlbase postfix/local[689475]: error: open database /etc/aliases.db: No such file or directory
Oct 01 02:28:22 schmangstlbase postfix/local[689475]: warning: hash:/etc/aliases is unavailable. open database /etc/aliases.db: No such file or directory
Oct 01 02:28:22 schmangstlbase postfix/local[689475]: warning: hash:/etc/aliases: lookup of 'root' failed
Oct 01 02:28:22 schmangstlbase postfix/local[689475]: 287D91A0A26: to=<root@schmangstlbase.local>, relay=local, delay=88632, delays=88632/0.01/0/0.01, dsn=4.3.0, status=deferred >
Oct 01 02:30:01 schmangstlbase CRON[691750]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Oct 01 02:30:01 schmangstlbase CRON[691751]: (root) CMD (systemctl restart mnt-onlinebackup.automount)
Oct 01 02:30:01 schmangstlbase systemd[1]: mnt-onlinebackup.automount: Deactivated successfully.
Oct 01 02:30:01 schmangstlbase systemd[1]: Unset automount mnt-onlinebackup.automount.
Oct 01 02:30:01 schmangstlbase systemd[1]: Stopping mnt-onlinebackup.automount...
Oct 01 02:30:01 schmangstlbase systemd[1]: Set up automount mnt-onlinebackup.automount.
Oct 01 02:30:01 schmangstlbase systemd[1]: Stopped target remote-fs.target - Remote File Systems.
Oct 01 02:30:01 schmangstlbase systemd[1]: Stopping remote-fs.target - Remote File Systems...
Oct 01 02:30:01 schmangstlbase systemd[1]: Reached target remote-fs.target - Remote File Systems.
Oct 01 02:30:01 schmangstlbase CRON[691750]: pam_unix(cron:session): session closed for user root
Oct 01 02:35:01 schmangstlbase CRON[698498]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Oct 01 02:35:01 schmangstlbase CRON[698500]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Oct 01 02:35:01 schmangstlbase CRON[698498]: pam_unix(cron:session): session closed for user root
-- Boot 094058eca19b49db802f84cef8c14cee --
Oct 01 02:43:07

I can't see why the boot fails either:

Code:
Oct 01 02:43:07 schmangstlbase systemd[1]: Inserted module 'autofs4'
Oct 01 02:43:07 schmangstlbase systemd[1]: systemd 252.30-1~deb12u2 running in system mode (+PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT -GNUTLS +OPENSSL +ACL +BLK>
Oct 01 02:43:07 schmangstlbase systemd[1]: Detected architecture x86-64.
Oct 01 02:43:07 schmangstlbase systemd[1]: Hostname set to <schmangstlbase>.
Oct 01 02:43:07 schmangstlbase systemd[1]: Queued start job for default target graphical.target.
Oct 01 02:43:07 schmangstlbase systemd[1]: Created slice system-getty.slice - Slice /system/getty.
Oct 01 02:43:07 schmangstlbase systemd[1]: Created slice system-modprobe.slice - Slice /system/modprobe.
Oct 01 02:43:07 schmangstlbase systemd[1]: Created slice system-postfix.slice - Slice /system/postfix.
Oct 01 02:43:07 schmangstlbase systemd[1]: Created slice system-systemd\x2dfsck.slice - Slice /system/systemd-fsck.
Oct 01 02:43:07 schmangstlbase systemd[1]: Created slice user.slice - User and Session Slice.
Oct 01 02:43:07 schmangstlbase systemd[1]: Started systemd-ask-password-console.path - Dispatch Password Requests to Console Directory Watch.
Oct 01 02:43:07 schmangstlbase systemd[1]: Started systemd-ask-password-wall.path - Forward Password Requests to Wall Directory Watch.
Oct 01 02:43:07 schmangstlbase systemd[1]: Set up automount proc-sys-fs-binfmt_misc.automount - Arbitrary Executable File Formats File System Automount Point.
Oct 01 02:43:07 schmangstlbase systemd[1]: Expecting device dev-disk-by\x2duuid-DAE8\x2d74AB.device - /dev/disk/by-uuid/DAE8-74AB...
Oct 01 02:43:07 schmangstlbase systemd[1]: Expecting device dev-pve-swap.device - /dev/pve/swap...
Oct 01 02:43:07 schmangstlbase systemd[1]: Reached target ceph-fuse.target - ceph target allowing to start/stop all ceph-fuse@.service instances at once.
Oct 01 02:43:07 schmangstlbase systemd[1]: Reached target ceph.target - ceph target allowing to start/stop all ceph*@.service instances at once.
Oct 01 02:43:07 schmangstlbase systemd[1]: Reached target cryptsetup.target - Local Encrypted Volumes.
Oct 01 02:43:07 schmangstlbase systemd[1]: Reached target integritysetup.target - Local Integrity Protected Volumes.
Oct 01 02:43:07 schmangstlbase systemd[1]: Reached target paths.target - Path Units.
Oct 01 02:43:07 schmangstlbase systemd[1]: Reached target slices.target - Slice Units.
Oct 01 02:43:07 schmangstlbase systemd[1]: Reached target time-set.target - System Time Set.
Oct 01 02:43:07 schmangstlbase systemd[1]: Reached target veritysetup.target - Local Verity Protected Volumes.
Oct 01 02:43:07 schmangstlbase systemd[1]: Listening on dm-event.socket - Device-mapper event daemon FIFOs.
Oct 01 02:43:07 schmangstlbase systemd[1]: Listening on lvm2-lvmpolld.socket - LVM2 poll daemon socket.
Oct 01 02:43:07 schmangstlbase systemd[1]: Listening on rpcbind.socket - RPCbind Server Activation Socket.
Oct 01 02:43:07 schmangstlbase systemd[1]: Listening on systemd-fsckd.socket - fsck to fsckd communication Socket.
Oct 01 02:43:07 schmangstlbase systemd[1]: Listening on systemd-initctl.socket - initctl Compatibility Named Pipe.
Oct 01 02:43:07 schmangstlbase systemd[1]: Listening on systemd-journald-audit.socket - Journal Audit Socket.
Oct 01 02:43:07 schmangstlbase systemd[1]: Listening on systemd-journald-dev-log.socket - Journal Socket (/dev/log).
Oct 01 02:43:07 schmangstlbase systemd[1]: Listening on systemd-journald.socket - Journal Socket.
Oct 01 02:43:07 schmangstlbase systemd[1]: Listening on systemd-udevd-control.socket - udev Control Socket.
Oct 01 02:43:07 schmangstlbase systemd[1]: Listening on systemd-udevd-kernel.socket - udev Kernel Socket.
Oct 01 02:43:07 schmangstlbase systemd[1]: Mounting dev-hugepages.mount - Huge Pages File System...
Oct 01 02:43:07 schmangstlbase systemd[1]: Mounting dev-mqueue.mount - POSIX Message Queue File System...
Oct 01 02:43:07 schmangstlbase systemd[1]: Mounting sys-kernel-debug.mount - Kernel Debug File System...
Oct 01 02:43:07 schmangstlbase systemd[1]: Mounting sys-kernel-tracing.mount - Kernel Trace File System...
Oct 01 02:43:07 schmangstlbase systemd[1]: auth-rpcgss-module.service - Kernel Module supporting RPCSEC_GSS was skipped because of an unmet condition check (ConditionPathExists=/>
Oct 01 02:43:07 schmangstlbase systemd[1]: Starting keyboard-setup.service - Set the console keyboard layout...
Oct 01 02:43:07 schmangstlbase systemd[1]: Starting kmod-static-nodes.service - Create List of Static Device Nodes...
Oct 01 02:43:07 schmangstlbase systemd[1]: Starting lvm2-monitor.service - Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling...
Oct 01 02:43:07 schmangstlbase systemd[1]: Starting modprobe@configfs.service - Load Kernel Module configfs...
Oct 01 02:43:07 schmangstlbase systemd[1]: Starting modprobe@dm_mod.service - Load Kernel Module dm_mod...
Oct 01 02:43:07 schmangstlbase systemd[1]: Starting modprobe@drm.service - Load Kernel Module drm...
Oct 01 02:43:07 schmangstlbase systemd[1]: Starting modprobe@efi_pstore.service - Load Kernel Module efi_pstore...
Oct 01 02:43:07 schmangstlbase systemd[1]: Starting modprobe@fuse.service - Load Kernel Module fuse...
Oct 01 02:43:07 schmangstlbase systemd[1]: Starting modprobe@loop.service - Load Kernel Module loop...
Oct 01 02:43:07 schmangstlbase systemd[1]: systemd-fsck-root.service - File System Check on Root Device was skipped because of an unmet condition check (ConditionPathExists=!/run>
Oct 01 02:43:07 schmangstlbase kernel: pstore: Using crash dump compression: deflate
Oct 01 02:43:07 schmangstlbase systemd[1]: Starting systemd-journald.service - Journal Service...
Oct 01 02:43:07 schmangstlbase systemd[1]: Starting systemd-modules-load.service - Load Kernel Modules...
Oct 01 02:43:07 schmangstlbase systemd[1]: Starting systemd-remount-fs.service - Remount Root and Kernel File Systems...
Oct 01 02:43:07 schmangstlbase systemd[1]: Starting systemd-udev-trigger.service - Coldplug All udev Devices...
Oct 01 02:43:07 schmangstlbase systemd[1]: Mounted dev-hugepages.mount - Huge Pages File System.
Oct 01 02:43:07 schmangstlbase systemd[1]: Mounted dev-mqueue.mount - POSIX Message Queue File System.
Oct 01 02:43:07 schmangstlbase systemd[1]: Mounted sys-kernel-debug.mount - Kernel Debug File System.
Oct 01 02:43:07 schmangstlbase systemd[1]: Mounted sys-kernel-tracing.mount - Kernel Trace File System.
Oct 01 02:43:07 schmangstlbase systemd[1]: Finished keyboard-setup.service - Set the console keyboard layout.
Oct 01 02:43:07 schmangstlbase systemd[1]: Finished kmod-static-nodes.service - Create List of Static Device Nodes.
Oct 01 02:43:07 schmangstlbase systemd[1]: modprobe@configfs.service: Deactivated successfully.
Oct 01 02:43:07 schmangstlbase systemd[1]: Finished modprobe@configfs.service - Load Kernel Module configfs.
Oct 01 02:43:07 schmangstlbase systemd[1]: modprobe@dm_mod.service: Deactivated successfully.
Oct 01 02:43:07 schmangstlbase systemd[1]: Finished modprobe@dm_mod.service - Load Kernel Module dm_mod.
Oct 01 02:43:07 schmangstlbase systemd[1]: modprobe@drm.service: Deactivated successfully.
Oct 01 02:43:07 schmangstlbase systemd[1]: Finished modprobe@drm.service - Load Kernel Module drm.
Oct 01 02:43:07 schmangstlbase systemd[1]: modprobe@fuse.service: Deactivated successfully.
Oct 01 02:43:07 schmangstlbase systemd[1]: Finished modprobe@fuse.service - Load Kernel Module fuse.
Oct 01 02:43:07 schmangstlbase systemd[1]: modprobe@loop.service: Deactivated successfully.
Oct 01 02:43:07 schmangstlbase systemd[1]: Finished modprobe@loop.service - Load Kernel Module loop.
Oct 01 02:43:07 schmangstlbase systemd[1]: Mounting sys-fs-fuse-connections.mount - FUSE Control File System...
Oct 01 02:43:07 schmangstlbase systemd[1]: Mounting sys-kernel-config.mount - Kernel Configuration File System...
Oct 01 02:43:07 schmangstlbase systemd[1]: systemd-repart.service - Repartition Root Disk was skipped because no trigger condition checks were met.
Oct 01 02:43:07 schmangstlbase systemd[1]: Mounted sys-fs-fuse-connections.mount - FUSE Control File System.
Oct 01 02:43:07 schmangstlbase systemd[1]: Mounted sys-kernel-config.mount - Kernel Configuration File System.
Oct 01 02:43:07 schmangstlbase kernel: EXT4-fs (dm-1): re-mounted 5440b6e0-8b52-4c78-8cb5-bb6252980da0 r/w. Quota mode: none.
Oct 01 02:43:07 schmangstlbase kernel: spl: loading out-of-tree module taints kernel.
Oct 01 02:43:07 schmangstlbase kernel: pstore: Registered efi_pstore as persistent store backend
Oct 01 02:43:07 schmangstlbase systemd[1]: Started dm-event.service - Device-mapper event daemon.
Oct 01 02:43:07 schmangstlbase systemd[1]: modprobe@efi_pstore.service: Deactivated successfully.
Oct 01 02:43:07 schmangstlbase systemd[1]: Finished modprobe@efi_pstore.service - Load Kernel Module efi_pstore.
Oct 01 02:43:07 schmangstlbase systemd[1]: Finished systemd-remount-fs.service - Remount Root and Kernel File Systems.
Oct 01 02:43:07 schmangstlbase systemd[1]: systemd-firstboot.service - First Boot Wizard was skipped because of an unmet condition check (ConditionFirstBoot=yes).
Oct 01 02:43:07 schmangstlbase systemd[1]: systemd-pstore.service - Platform Persistent Storage Archival was skipped because of an unmet condition check (ConditionDirectoryNotEmp>
Oct 01 02:43:07 schmangstlbase systemd[1]: Starting systemd-random-seed.service - Load/Save Random Seed...
Oct 01 02:43:07 schmangstlbase systemd[1]: Starting systemd-sysusers.service - Create System Users...
Oct 01 02:43:07 schmangstlbase systemd[1]: Finished systemd-sysusers.service - Create System Users.
Oct 01 02:43:07 schmangstlbase systemd-journald[487]: Journal started
Oct 01 02:43:07 schmangstlbase systemd-journald[487]: Runtime Journal (/run/log/journal/dbc3514cb5e0456788080c37454e91ef) is 8.0M, max 641.7M, 633.7M free.
Oct 01 02:43:07 schmangstlbase systemd-modules-load[488]: Inserted module 'vhost_net'
Oct 01 02:43:07 schmangstlbase dmeventd[497]: dmeventd ready for processing.
Oct 01 02:43:07 schmangstlbase dmeventd[497]: Monitoring thin pool pve-data-tpool.
Oct 01 02:43:07 schmangstlbase kernel: zfs: module license 'CDDL' taints kernel.
Oct 01 02:43:07 schmangstlbase kernel: Disabling lock debugging due to kernel taint
Oct 01 02:43:07 schmangstlbase kernel: zfs: module license taints kernel.
Oct 01 02:43:07 schmangstlbase systemd[1]: Starting systemd-tmpfiles-setup-dev.service - Create Static Device Nodes in /dev...
Oct 01 02:43:07 schmangstlbase systemd[1]: Started systemd-journald.service - Journal Service.
Oct 01 02:43:07 schmangstlbase systemd[1]: Finished systemd-random-seed.service - Load/Save Random Seed.
Oct 01 02:43:07 schmangstlbase systemd[1]: first-boot-complete.target - First Boot Complete was skipped because of an unmet condition check (ConditionFirstBoot=yes).
Oct 01 02:43:07 schmangstlbase systemd[1]: Starting systemd-journal-flush.service - Flush Journal to Persistent Storage...
Oct 01 02:43:07 schmangstlbase systemd-journald[487]: Time spent on flushing to /var/log/journal/dbc3514cb5e0456788080c37454e91ef is 20.233ms for 877 entries.
-- Boot 721e075f35e4444fa6dab40edda9e4e9 --

Is there anything else I can do to troubleshoot?
 
Last edited:
It happend again today, again the logs show no sign of anything unusual. Really nobody has an idea?

The system NVME shows no SMART problems, it is quite new anyways (< 4 months)

I had my server and an additional Raspi 5 Server with 2 big HDDs on a Tapo WiFi Switch maxing out at 2300W, may this be the problem? But the Raspberry Pi was running fine the whole time, only the m720q is shutting down, and then just slowly blinking yellow until I take it off power, I can't hold down the power button to reboot it like usual. Do you guys think this is a hardware related problem?
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!