Search results

I figured out, the the kernel 6.5.13-5-pve works, tty is just not shown. So there must be an issue with 6.8 kernel.

Hi, sadly, the Proxmox Kernels (6.8.8-3-pve,6.5.13-5-pve) all stuck at "Loading initial ramdisk". The Debian amd64 kernels (6.1.0-23-amd64) work just fine and asks for the LUKS passphrase. HW: - CPU: AMD Epyc 4584PX - MB: MSI D3051 What I did: I installed Debian bookworm with LVM + LUKS...

Found the issue. MTU rate 9000 was set on the TrueNAS host, while the switch had "Jumbo Frames" disabled somehow.

Hi, i restared my Proxmox host and since then I cannot connect to NFS nor CIFS shares. The state of the storage is "Unknown". When I open the storage device I get unable to activate storage 'truenas' - directory '/mnt/pve/truenas' does not exist or is unreachable (500). Well it is reachable and...

I booted VMWare ESXi up and hoped for easier understandable logs. I found out that only PCPU8 and PCPU9 are faulty. VMWare gives me these logs: MCA: 150: UC Excp G5 B0 Sb20000000010005 A0 M0 P0/0 Internal Parity Error. Now the question is if I can disable/ignore core 8 and 9 in Proxmox

Mcelog: mcelog: failed to prefill DIMM database from DMI data Hardware event. This is not a software error. MCE 0 not finished? CPU 4 BANK 0 TSC 2123decdcd77 RIP !INEXACT! 10:ffffffffac0ff117 TIME 1608143383 Wed Dec 16 19:29:43 2020 MCG status:RIPV MCIP MCi status: Error overflow Uncorrected...

What can I do? I tried cleaning the CPU and reinserting RAM but it won't help.

It crashed again: https://termbin.com/hb6hi(full logs) Edit 20:24: It frezzes again: https://termbin.com/9ubu In the logs it says "-- Reboot --"

There are only logs after I rebooted the system after freeze. https://termbin.com/bn86x

It again crashed with the last syslog messages; Dec 16 12:58:27 pve pvedaemon[1416]: <root@pam> successful auth for user 'root@pam' Dec 16 13:11:30 pve systemd[1]: Starting Cleanup of Temporary Directories... Dec 16 13:11:30 pve systemd[1]: systemd-tmpfiles-clean.service: Succeeded. Dec 16...

Proxmox died today and it didnt reboot. The server was still on, but proxmox wasn't active anymore(black screen) Here are the last syslogs: c 16 03:52:03 pve vzdump[16817]: INFO: Starting Backup of VM 140 (qemu) Dec 16 03:52:48 pve pvestatd[1453]: status update time (5.363 seconds) Dec 16...

It's an older network card. It can't do more. But how can I hide this warning for the link 2 on node 2?

https://pastebin.com/HEHQ474c It won't do more than 4060.

https://pastebin.com/LcbE06u2

https://pastebin.com/XET3tygK

8972 works

root@pangolin:~# cat /etc/network/interfaces # network interface settings; autogenerated # Please do NOT modify this file directly, unless you know what # you're doing. # # If you want to manage parts of the network configuration manually, # please utilize the 'source' or 'source-directory'...

Which link? I have only two nodes. On the node with the warnings I have 2x 10Gbit activated at 9000MTU. Intel says that Intel Corporation Ethernet Connection X557 have jumbo frames....

I get this on boot: Jun 30 01:02:30 pangolin corosync[2308]: [KNET ] pmtud: PMTUD link change for host: 2 link: 1 from 469 to 6021 Jun 30 01:02:30 pangolin corosync[2308]: [KNET ] pmtud: Global data MTU changed to: 6021 Jun 30 01:02:34 pangolin pmxcfs[2297]: [status] notice: received log...

Yes. I have the UniFi Switch PRO 24 POE and enabled jumbo frame. There are also some new errors: Jun 29 17:14:20 pangolin iscsid[2012]: connect to 192.168.1.46:3260 failed (Connection refused) Jun 29 17:14:23 pangolin iscsid[2012]: connect to 192.168.1.46:3260 failed (Connection refused) Jun...