longer's latest activity
-
Llonger replied to the thread ceph 1 daemons have recently crashed.Okay, so 10.10.10.2 is still listed at the end of the mon_host line inside the [global] section. You can use your preferaed editor and delete the ip: 10.10.10.2. make a copy of the file before making any change.
-
Llonger replied to the thread ceph 1 daemons have recently crashed.can you share: ~# cat /etc/pve/ceph.conf
-
Llonger replied to the thread ceph 1 daemons have recently crashed.Please try without the -k option: root@pve2 :# journalctl --since "2026-07-27 22:00:00" --until "2026-07-27 23:30:00" > /tmp/syslog.txt.gz
-
Llonger replied to the thread ceph 1 daemons have recently crashed.You can attempt again after couple of minutes, if still same issue check: - Check the Active Mon Map ceph mon dump
-
Llonger replied to the thread Proxmox doesn't have internet access.As @daanw said, you network interfaces are all down, double check the Physical server cables connections and also on the switch side.
-
Llonger replied to the thread Cant acces to webGUI after trying to change the node/hostname name.Just posting Proxmox wiki: https://pve.proxmox.com/wiki/Renaming_a_PVE_node
-
Llonger replied to the thread VirtIO Block or IDE.Oh you already have thread about this: https://forum.proxmox.com/threads/migration-of-windows-server-2003.185331/
-
Llonger replied to the thread ceph 1 daemons have recently crashed.So at the moment, the daemon successfully restarted, and running for more than hour. Looking at journalctl may provide related information, so the last crash from shared crash info was at 2026-07-27 23:21, therefore take look what happend before...
-
Llonger replied to the thread Proxmox VE 9.1 installation process does not recognize keyboard and mouse.Not really sure, but did you verify different port portv2 and v3 to see if any differences? Just my 2 cent, Do you have IPMI/iDRAC? maybe you can attempt from IPMI console and check this issue after booting.
-
Llonger replied to the thread VirtIO Block or IDE.The recommendation is to use virtio dirvers for best performance: https://pve.proxmox.com/wiki/Windows_2003_guest_best_practices In the wiki its also mentioned: "the latest VirtIO iso do not include drivers for Windows 2003. You need to download...
-
Llonger replied to the thread ceph 1 daemons have recently crashed.Is it always mon.pve2 ? You could attempt to destroy and create this mon in case other mon are fine. Could you also share: ~# ceph status
-
Llonger replied to the thread Server 2025 High CPU.Is the high CPU usage showing up inside the Windows Guest (Task Manager), or on the Proxmox Host GUI? If inside the Windows VM What specific process is consuming the CPU? I would suggest to test to: - Increase the assigned core to e.g 8 cores...
-
-
Llonger replied to the thread Server 2025 High CPU.hmmm there currently known issue explained in: https://forum.proxmox.com/threads/windows-server-2025-cpu-suddenly-at-100.184763/post-861490 Where its recommended to use CPU type other than host CPU. So you can roll out this and keep CPU type as...
-
Llonger replied to the thread VMs and LXCs are frequently 'unknown status'.I have not experienced this issue before. are you still observing this problem? The journalctl log during the issue time might contain a clear reason for the problem.
-
Llonger replied to the thread EFI disk0 snapshot problem.Happy for you. Thanks for sharing the fix.
-
Llonger replied to the thread EFI disk0 snapshot problem.Please share the vm config: qm config [VMID]
-
Llonger replied to the thread Intermittent I/O errors on SAN-backed VM disks (Proxmox VE 9.2).My first thought was if there's backup running during that time, and I kept on reading until spotting it: "Our backup infrastructure uses Bacula, and backups are executed on Fridays, so I'm wondering if increased I/O load could somehow expose an...
-
Llonger replied to the thread After deleting the lun and applying "multipathd reconfigure" the gui is not working correctly. D exit_a [vgs].If the process is shown D → the process in an uninterruptible sleep. This state cannot be interrupted by signals. For more details please refer to the PROCESS STATE CODES in man ps[0]. In such cases, it is not possible to resolve the issue...
-
Llonger replied to the thread Everything working after power outage except one VM which lost internet connection. Different from the other similar issue..Which Linux distribution running on the affected VM?
-
Llonger replied to the thread Everything working after power outage except one VM which lost internet connection. Different from the other similar issue..Thanks, it looks the config correct, so the issue seems on the VM. The network config on the VM doesn't sees to include auto start (auto) [0]; could you try to bring the interfacr up on the VM: ~# ifup enp6s18 [0]...
