Search results

Hi! If it happens only on one server, then it'd be most likely the fault of the connection to the server. How is the network setup? What is the performance of the link between your host and the Proxmox VE server? Is there any packet loss?

Hi! Could you post the exact request (e.g. with curl) you're making and the permissions that the API token / user has? There's not much information about which permissions the role "Download" permits and it is important that the API token / user has the Sys.Audit permission for the ACL /nodes...

One way you could do this, even though I do not encourage it, is to add the syslog capability CAP_SYSLOG to the container. Another much less secure way is to set /proc/sys/kernel/dmesg_restrict on the host to 0, which allows any user on the host system, including any container, access to the syslog.

Hi! Could you elaborate a little bit more on your hardware and how you installed Proxmox VE? Is there any more output when booting/in grub? This is just an informational message from fsck about the root filesystem's state.

Hi! Are there any BIOS firmware upgrades available for your mainboard? Have you modified any BIOS settings on the machine?

Hi! There's documentation for the PVE HA Manager in our admin guide at [0]. It's designed so that virtual machines and containers can be setup as highly available services, which will be automatically recovered to other nodes, e.g. in case of a failing node. [0]...

Is there a specific use case or reason why you need noatime on procfs? procfs in itself is a special file system, where there are no IO operations on reads anyway since the content of the files are either in-memory or generated on demand. Pretty much the same applies to sysfs as well.

Welcome to the Proxmox forum, Agasnine! Another simple suggestion, have you tried another flash drive to install from? Is there a RAID controller and do you know which it is?

Hi! I assume that this is an unprivileged LXC container, then this behavior is normal since unprivileged containers map the container's root user to an unprivileged user outside of the container. Therefore the root user in the container cannot perform any actions, which need the usual root...

Interessant, sehe auch gerade, dass die zitierte Code-Zeile den Marvell 88SE9170 nur als Sub-Device registriert. Könntest du einen Output von lspci -nnk mitsenden?

Hm, dieser RAID Controller sollte eigentlich bereits korrekt erkannt werden, da dieser seit Kernel Version 3.13 in der Gerätetreiber-Tabelle des AHCI Controller-Treibers eingetragen ist [0]. Der Patch betrifft nur den Marvell SATA Controller von dem im Blog-Artikel genannten DawiControl RAID...

Welcome to the Proxmox forum, YamiGhor! First, these should probably be lxc.idmap and second these id mappings say, that the container's uid and gid 100000 should be mapped to the host's uid and gid 100000, which is probably not what you want. These high-numbered ids are usually reserved...

Hi @firsak! Could you share the configuration of your LXC container (i.e. pct config 102), the contents of /etc/fstab and the output of pct start 102 --debug?

Hi! Proxmox VE doesn't use pacemaker, but has its own high availability solution called HA Manager. Is there a reason that you have set it up on the cluster?

Hi! Der beschriebene Patch ist nun upstream für die Kernel Version 6.15 vorgesehen. Sobald dieser im Mainline-Kernel ist cherry-picke ich den Patch in den Proxmox VE Kernel, sodass das Gerät verwendet werden kann. Außerdem ist gerade ein Patch [0], der auf diesen aufbaut, vorgesehen und...

Das tut mir leid zu hören, jedoch muss der Fehler nicht zwingend fatal sein. Wenn SMART "PASSED" meldet, bedeutet dass das das NVMe insgesamt in einem guten Zustand ist. Das kann aber trotzdem bedeuten, dass es einen Bad Block [0] auf dem Speichermedium geben kann, was aber relativ normal ist...

Hi! This is unrelated to Proxmox VE directly, but from a quick glance it seems that nixmoxer has a own option for import-form at [0]. Apart from that, the task log you added shows that there is no space left on the device: qemu-img: error while writing at byte 19797114880: No space left on...

Hi and welcome to the Proxmox forum, philtao! These ACPI errors could be anywhere in between informational to suggesting a hardware failure. Do you have the latest BIOS firmware for your mainboard installed? Does (temporarily) booting the opt-in 6.11 kernel change anything on these error...

Hi! Könntest du einen Auszug von dem Syslog (dmesg/journalctl --system) posten während das Backup dieser VM fehlschlägt? Eine Vermutung wäre, dass es zu Lesefehlern an der Quelle gekommen ist, aber der Syslog würde mehr Information geben.

Welcome to the Proxmox forum, ushiromawashi! Which problems did you encounter with Ceph Reef exactly? Do you have the Ceph log of the previous installation available? If so, please post it. If I understood it correctly, downgrading Ceph and using the disks is not really possible and not...