Search results

Hi! It depends on how you setup your Proxmox VE installation, but by default (if installed with ext4), there are two storages configured for PVE: a directory storage in /var/lib/vz and a LVM-based storage (which the first is part of). If you're running out of disk space, there is the du(1) tool...

What kernel version were you running before? Which kernel version have you upgraded to? Can you boot the server with an older kernel or does it not boot at all? Is the boot process just stuck at the first screenshot or are there more details on the problem?

Welcome to the Proxmox forum, gdeshun! Could you provide further information about your IOMMU groups and the hardware that was enumerated with the loaded kernel modules (e.g. lspci -nnk)? These errors seem to be logged by a check for Intel-based machines, which was introduced with this patch...

Welcome to the Proxmox fourm, GalacticPrez! That's right, and there is already a bug report about this on our BugZilla [0]. If you're interested in the feature, you can join the discussion there and/or subscribe to the bug report to see if there are updates on this. For now, you can safely...

Welcome to the Proxmox forum, parc-network! Have you found a solution to your problem in the mean time?

Have you already found a solution to this problem? If not, NMIs (non-maskable interrupts) are CPU-related and other posts have suggested [0], that this could be caused by specific power saving modes. Have you changed the power savings in the BIOS? Does disabling the C-states and/or enabling...

Hi! Welche PCI NICs hat das System? Wie werden diese mit dem Kernel 6.5.13-6 enumeriert (lspci -nnk | grep -A2 -E "(Network|Ethernet)")? Könntest du einen vollständigen Log eines Boots mit dem neuen Kernel (6.8.12-4) posten (journalctl -b <boot-nummer>)?

Thanks for getting back and great that the system runs stable now! Cheers!

Welcome to the Proxmox forum, Harry! Could you provide further details on the erratic disk I/O? What does exactly happen? In general, ZFS on a hardware raid controller is not recommended nor supported as described at [0] and other spots in the Proxmox VE admin guide. Does this hardware RAID...

Zusätzlich zu meiner obigen Frage bezüglich Hardware und Backup Fleecing (obwohl hier relativ viel zusätzlicher Speicher benötigt werden würde, da die Disk images relativ groß sind), wie wurde der Proxmox Backup Server aufgesetzt (VM, eigene Node)? Wie sind das PVE und das PVE verbunden?

Hi! Wie schaut denn die Config dieser VM aus (qm config <vmid>) und könntest du einen Log von dem Backup Job posten? Welche Hardware ist bei den PVE und PBS Installationen im Einsatz? Wenn die VM während dem Backup weiterhin viele Schreiboperationen ausführt -- besonders wenn diese relativ...

Danke für das schnelle Feedback @devaux und @spacefreak! Ich konnte den Fehler nun reproduzieren und melde mich, wenn eine Lösung in Sicht ist. Ich würde die Diskussion zu diesem Thread hauptsächlich auf den älteren Thread [0] und den Bug Report [1] verschieben, sodass mehr Personen (in...

Thanks for the quick answer @spacefreak! I could reproduce the issue on my local setup now. I'll work on this and update this thread and the original bug report [0] with further details for a possible fix. [0] https://bugzilla.proxmox.com/show_bug.cgi?id=5430

Thanks for sending a crash log! It is important to point out that the RCU preemption stalls are preceded by a protection fault in the kernel for the same process (pve-firewall). Oct 29 07:26:21 pve3 kernel: general protection fault, probably for non-canonical address 0x2c8cf81df5d70a56: 0000...

Thanks for pointing this out in the referenced thread! As you mentioned, it seems like the problem hasn't been fully fixed with the patch in io_uring. As for the mentioned thread, it would help to have a more exact reproducer (hardware setup, ocfs2 mount options, vm config) to have a clear...

Diese Fehlernachricht wird ausgegeben, wenn bei einem Direct I/O auf einem ocfs2 filesystem auf dem Kernel block layer ein I/O-Fehler auftritt (-EIO == -5) [0]. Ich konnte diesen Fehler jedoch sowohl mit der Kernel-Version 6.8.12-2, als auch der gepatchten Kernel-Version 6.8.12-3 nicht...

Were there any changes in the VM configuration or were they during runtime? Checking the syslog could also give further conclusions why that happened. How is the VM configured (qm config <vmid>)? Anyway, using the partition UUIDs is a good way if drives/udev should change the device names again.

Are the packages the same version for all nodes? I can only see the versions for pve1 now. It would be interesting which kernel version is running on pve3, the node that crashed, and if they're as up-to-date as on pve1. The stacktrace in the RCU stall warning seems rather generic to me. The...

Could you provide more information about the failed boot (e.g. logs, screenshots)? I'm not familiar with Nagios VMs, but a quick forum search suggests that Nagios VMs seem to depend on their drive to use the IDE bus [0]. [0]...

You can convert a disk from IDE to SCSI by shutting down the VM, detaching the disk at ide0 and reattaching the used disk at scsi0. You could also change the SCSI controller to "VirtIO SCSI single". If the VM doesn't find the boot device, enable and add scsi0 in the VM's bootorder option. In my...