Latest activity
-
Ddavidlynch replied to the thread [SOLVED] Proxmox crashing, hardware issue?.You can swap the RAM with one of your known-good servers first and see if the errors follow the DIMMs. The logs make me think it's more likely a memory issue than the microcode, especially with another system using the same Nemix RAM showing...
-
Why is there a Proxmox VE v8.4.19 running? What CPU Type do you use? So get the lshw programm with apt install lshw. for the Asrock X470D4U you can download the English manual. and on Page 22 you find: So your 2666 MT/s is normal with 4x DDR4... -
TI like to use this: https://github.com/VoltKraft/PBS_Chunk_Checker
-
Mmeyergru replied to the thread Problem with rsync mtime preservation since update to kernel 6.17.13-6-pve (solved by avoidance of nfs 4.2).Me too, similar situation: an "rsync -a" syncs the timestamps of the original files first and after a short while the mtime of the file switches to the time of copy. Falling back to NFS version 4.1 on the mount fixes the problem.
-
Mmeyergru reacted to raipvs's post in the thread Problem with rsync mtime preservation since update to kernel 6.17.13-6-pve (solved by avoidance of nfs 4.2) with
Like.
I have the same problem on Proxmox 9.2.4 with kernel 7.0.14-3-pve as NFS-Server and NFS-clients running 7.x kernels. A workarround for me is to mount the filesystem with NFS version 4.1: mount -o vers=4.1 SERVER:/DIR /mnt I guess it is a kernel bug. -
DDerPaddy posted the thread PVE 9.1/9.2 installer + kernel 7.0 fail on Intel H97 SATA — 9.0-1 and kernel 6.14 work! in Proxmox VE: Installation and configuration.Preface: I just registered to share my almost week long suffering chasing imaginary hardware issues and the very simpel software bug/limitation that caused it. A few weeks ago I used Claude.ai to cobble together a comprehensive manual to get...
-
Vvluxh replied to the thread Proxmox + Pocket ID + OIDC.hello, glad it works for you. just leaving this link here for others using caddy + pocketid + pve: https://forum.proxmox.com/threads/proxmox-ui-caddy-and-reverse-proxy.83198/ cheers!
-
VHi, I have only registered in order to post my solution to the problem. The working entry in my Caddy config file is as follows: proxmox.lan { reverse_proxy 192.168.1.200:8006 { transport http {...
-
Llethuer replied to the thread Proxmox Oberfläche nach Stromausfall nicht mehr erreichbar.Anders gefragt: gibt es noch Dinge die ich tun kann oder bin ich mit dem BIOS Update am technischen Ende angekommen ?
-
Wweconnect replied to the thread PMG behind Proxmox DNAT - real sender IP not visible, SPF checks failing.Hello, The reason you are seeing the internal gateway IP (10.0.0.1) instead of the real public IP is usually due to Source NAT (SNAT) or Masquerading being applied on the Proxmox Host alongside the DNAT rule. When masquerading is active for the...
-
Wwaltar reacted to raipvs's post in the thread Problem with rsync mtime preservation since update to kernel 6.17.13-6-pve (solved by avoidance of nfs 4.2) with Like.
I have the same problem on Proxmox 9.2.4 with kernel 7.0.14-3-pve as NFS-Server and NFS-clients running 7.x kernels. A workarround for me is to mount the filesystem with NFS version 4.1: mount -o vers=4.1 SERVER:/DIR /mnt I guess it is a kernel bug.
-
Wwaltar reacted to Onslow's post in the thread Problem with rsync mtime preservation since update to kernel 6.17.13-6-pve (solved by avoidance of nfs 4.2) with Like.
Hi, @skraw I wonder if you really mean atime... Though you wrote "atime" both in the subject and inside the post. But by default, rsync's decision whether to copy a file or not, doesn't depend on atime. It depends on mtime (and the size). From...
-
EEAnushan replied to the thread Problem with rsync mtime preservation since update to kernel 6.17.13-6-pve (solved by avoidance of nfs 4.2).I can confirm I'm running into the same bug. root@proxmox:~# pveversion pve-manager/9.2.4/5e5ae681198514d4 (running kernel: 7.0.14-4-pve) I was using rclone to sync some files to an NFS share hosted on my Proxmox node. After a sync, running a...
-
TTarzoq reacted to fabian's post in the thread Receiving "pipelined request failed: update atime failed for chunk/file" when backing up to backup proxmox server? with Like.
I don't know how unraid handles that. the command would be "chown -R backup:backup /backups", but it might require some changes on the unraid side as well before that works..
-
Aa3a replied to the thread [SOLVED] NVIDIA DKMS driver failure on Proxmox VE 9.2.4 with kernel 7.0.x (Quadro P2000) — seeking guidance.I haven't had good luck using the distribution bundled drivers. Howwever, I am succesfully using 580.173.02 downloaded directly from NVidia on my venerable GTX1080 I used: ./NVIDIA-Linux-x86_64-580.173.02.run --no-install-compat32-libs...
-
Bbindi replied to the thread [SOLVED] NVIDIA DKMS driver failure on Proxmox VE 9.2.4 with kernel 7.0.x (Quadro P2000) — seeking guidance.Nice AI post. Too old drivers for too new of a kernel. EOL hardware.
-
news replied to the thread [SOLVED] Proxmox crashing, hardware issue?.Why is there a Proxmox VE v8.4.19 running? What CPU Type do you use? So get the lshw programm with apt install lshw. for the Asrock X470D4U you can download the English manual. and on Page 22 you find: So your 2666 MT/s is normal with 4x DDR4... -
-
NNevadaTech posted the thread [SOLVED] Proxmox crashing, hardware issue? in Proxmox VE: Installation and configuration.Hello, I have a server crashing and I'd like some help. Please! Over the last couple weekend I've had a small maintenance window where I could take it offline for a couple hours. This weekend is a longer window so I'd like to get as much testing...
-
CCycloneB replied to the thread WebUI Syslog Font.No add-on in the browser, but totally possible I tweaked a setting over the years. No tweaks on the new node as that's how it looked from the first login to the web UI.
-
NNevadaTech replied to the thread [SOLVED] No /boot after PVE 8 to 9 upgrade.Oy, bit by this bug also. Extra input... I wasn't sure which disk was my booter, other posts say 'EFI BIOS' partition, I have 'BIOS boot' and 'EFI System' partitions, so which is it? for me it was the EFI System partition my guessing was based...
