Search results

I have a Supermicro server with and X12SPM-TF motherboard with as network controller a dual LAN with 10 GBase-T with Intel X550. Running Proxmox PVE enterprise latest. Running on BIOS v1.6 or lower the 10GB ethernet connection is working as expected. However after an update to BIOS v1.9 or...

Issue solved. Rebooted the Node.

It started with questions marks everywhere in the cluster but I managed to limite the question marks to the 3th node of the cluster (see below). I tried to stop and start the pvestatd service. When starting the service I get the following error: Job for pvestatd.service failed because the...

Solved by deleting the reservation.

I have a 3 Node Proxmox cluster with one ZFS pool on all Nodes. When I try to replicate VM111 to Node 2 I get the following error: zfs error: cannot create snapshot 'TEAPHOME-Storage/vm-111-disk-0@__replicate_111-0_1704310144__': out of space The results of zpool ist and zfs list for all...

I agree. But in that case I can not explain that number of unsafe shutdowns. The Node is connected to an UPS. And after a kernel update I type "reboot"

That should than happen when a kernel update is applied as this is almost the only reason to restart. Shutdown will almost never happen.

These are at least not from power loss as there is an UPS. If I assume that a shutdown will cause also shutdown of the Node it looks like it relates to Proxmox kernel updates.

It is indeed a cluster (with in total 3 Nodes). See in this thread also the results of the smartmontools. It seems a failing NVMe.

Using smartmontools: My conclusion is that the NVMe should be replaced. According to Samsung I have 5-Year Limited Warranty or 600 TBW Limited Warranty The NVMe is 3 Years old and less than 600TBW (180 TB). Is the best way forward to do a fresh install or clone this NVMe?

When I try to refresh (under updates) I get the following error: starting worker failed: unable to create output file '/var/log/pve/tasks/F/UPID:TEAPHOMEPVE02:00001E64:00025ADC:6578CB3F:aptupdate::root@pam:' - Read-only file system (500) The journal showed. the following: It seems that the...

@deanfourie do you have a link to an older version of the ISO? --- John

@t.lamprecht Adding a HDMI dummy solves the issue so it seems a kernel issue.

That fixed it. Luckily all three nodes has an enterprise license. --- John

Under repositories I have the following warning: When I run apt update I will get the following Ignoring file 'pve-enterprise.listapt' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension How to resolve? --- John

Updated my cluster (3 Nodes) to Proxmox 8.0.3. One of the Nodes is an Intel NUC kit NUC7i7DNHE. This Node dies within a couple of minutes. Than it will restart a number of times and in then it is fully dead. I updated the BIOS to the latest version but the behavior did not change. When I pin...

Thanks, did forget that I pinned (due to some issues).

I updated to Proxmox 8. However it seems that the kernel is not updated. pve-manager/8.0.3/xxxxxxxxxxxxxxxx (running kernel: 5.15.39-3-pve-guest-fpu) WARN: a suitable kernel (pve-kernel-6.2) is intalled, but an unsuitable (5.15.39-3-pve-guest-fpu) is booted, missing reboot?! The Proxmox boot...

@martin-g-it Do you know why the version number of the Proxmoxbackupserver is given as 2.3 in Node-RED while the version is 2.3.2? For the Proxmox VE the correct number of decimals is given for the version#. I assume it is in the Proxmox API. --- John

Hi @martin-g-it That is great. Thanks for letting me know. Much appreciated. The Proxmox subflow (https://flows.nodered.org/flow/f445ca36af1e4f3097986f9095982a67) also has added the functionality. Will have a look at it this weekend.