Search results

No CX3: Jun 12 07:04:51 pve kernel: Linux version 6.8.4-2-pve (build@proxmox) (gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC PMX 6.8.4-2 (2024-04-10T17:36Z) () Jun 12 07:04:51 pve kernel: DMI: To Be Filled By O.E.M. X570D4U-2L2T/X570D4U-2L2T, BIOS...

I installed the CX3 Pro on Juli, 6th. Reboots occured on August, 26. So i don't see a direct relation there.

Interesting. I'm using the same (40G) with the system. No problem with X570, only with B650

After my second board started randomly rebooting after several weeks, i had enough. Also other people mention that even H5 REV 4.01 has the Post-Code-00-Problem... I dont know

You are also using the B650D4U? The board seems to be the problem. Many people switched to the H13SAE-MF from supermicro and the problem with sudden reboots (mine) has been solved. Really disappointed by asrock and the seller seems to not want to take the board back. Having the third exchange...

Same issue here. Any solutions or updates so far?

On my AMD-cpu? seems like a good idea! ;-)

Doesn't fit to my cases. I'm using a mellanox nic in the system. Seems to be a widely known problem: https://forum.proxmox.com/threads/proxmox-mystery-random-reboots.125001/page-2

Damn it. Turns out the reason on my customers epyc system was the RAM and not the kernel. Had to downclock the ram to 1866MHz to get it stable until i have time to change the defective stick :-( Horay for mce eventlog!

I'm having the same problem. It first appeared on my new 7950x homelab-server with an AsrockRack Board. Board was swapped by the distributor, problem persisted. Yesterday i had to move an entire rack at a customer site and updated the proxmox-server at this point. This morning the system had...

Hallo, leider finde ich in den Docs keine Infos darüber, welche Rechte ein User benötigt, um per API auf Cluster/Firewall zugreifen zu können. Auch im Proxmox unter roles/permissions/paths finde ich nichts dergleichen. Kann mir jemand auf die Sprünge helfen? Mfg Stephan

Similar problem here. Haven't been able to exactly pinpoint it yet. Did you get any further?

Where exactly did you put this in your config? I pasted it at the end and the error still persists. EDIT: Despite this thread being nearly 2 years old now, i encountered this bug just recently. Can't see exactly when because i don't look in the syslog every day on the logging machine. But can...

Thanks for your analysis. I must admit, i don't had the problem since months. Afair since Proxmox 8.0/8.1 or Kernel 6.5 ? Can't remember exactly...

Ok, nevermind. Hab's anders gelöst! Bin per Shell auf den Datastore-Ordner, habe einen neuen Ordner für ein Backup angelegt (vm/199) und dort die Metadaten des gewünschten Snapshots reinkopiert. So konnte ich das Backup per Gruppe selektieren.

Hi, ich stehe gerade vor dem Problem, nur einen bestimmten Snapshot per Backup-Job einmalig auf Band zu sichern. Bei "Group Filter" kann ich als Typ "Regex" auswählen. Aber was muß dann ins Feld "Filter Value"? Das letzte Backup bringt mir nichts, es muß ein ganz spezifisches von einer VM sein.

Hab das Update gerade eingespielt, läuft! Vielen Dank!

@fabian : Gibt es schon eine Info, wann die Änderungen in die Releases reinkommen? Aktuell muß ich immer eine 7.4er PVE-VM hochfahren, nur um Dateien aus einem Backup zu holen. Geht, ist aber natürlich suboptimal.

Ok, mit dem non-debug-paket geht es tatsächlich. Wieso das debug nicht ging - k.a. Problem behoben! Wäre nett, wenn der Fix in künftige Releases wandern könnte, ansonsten muß man jedesmal das Testpaket installieren.

Ich habe jetzt in dem Debug-Image geschaut, ist da wirklich ntfs-3g drin? / # find / -name ntfs /sys/module/ntfs / # / # cat /proc/filesystems nodev sysfs nodev tmpfs nodev bdev nodev proc nodev devtmpfs nodev sockfs nodev pipefs nodev ramfs nodev devpts reiserfs ext3 ext4...