Don't get me wrong, but this should not be a very hard task.
So, the logical conclusion would be, that you either have defective hardware, or that you are doing something wrong.
You could also have a look at the output on the COM-header of your...
No it should not.
I agree, the most likely explanation is something very stupid going on. Probably with the User :p. I just fail to see what exactly ...
This Week I'm completely under Water at work, so no Time to play around with Scopes. But...
Well, it say quorate, so it should be fine. Is this after unplugging the Cable on pve1 and pve2 also rebooted ? Are you sure it's a reboot and not some e.g. Network IP Address conflict due to reconfiguration or something along those Lines ? Does...
Are you sure you set a different "weight" (number of Votes) for the "remaining" Node ?
What is :ffff:172.16.1.20 and :ffff:172.16.1.21 ? It looks like 2 Hosts are down, not only 1 ... But who is monitoring/pinging them then ? Do you have another...
I'm not sure if that is the Issue.
As I said, when I connected the DB9 on the Back of one of these Supermicro Motherboards to a Zyxel GS1910-24 Switch, I could get it to work without Issues with minicom. Since RS232 seemed fine there, why do you...
Alright ...
Sometimes the OEM / BIOS Vendor either puts them in Places that are impossible to find, or they are altogether hidden.
You may need to patch BIOS (using a NEW Version of uefitool to extract the BIOS, ifrextractor to dump that to...
Still thanks for checking :)
Everything clean in IPMI / Event Log - no issues at all. Also compared the RAM again, their performance specs are 1:1 the same.
Yep, I did.
Me too. ^^
Chrony is already installed and configured - it was the...
It could indeed by a stubborn Firmware Quirk :( . I got no direct Experience with this specific one, only LSI 2118/3008 Series Chipsets so far.
I doubt that is an Issue *per se*, unless it would prevent you from booting at all, which clearly is...
Thanks for your reply. I had another freeze this saturday, so checking again...
Mainboard
it's a H12DSU-iN mainboard in all servers, same version 1.01. BIOS on the failing server is newer (was the same as failing servers when issues started...
This thing is not intuitive or documented (and I also looked for it arriving here), I think it is useful to add a "help" link to the documentation that specifies it as there is for other fields but not for this one.
Alright, Fingers crossed :).
I think I added a debug Parameter too (also used to debug Initramfs), but it might well be that there is quiet Parameter that I missed. Thanks for the Tip. Let me check that :).
That's surely NOT an Issue in my Case...
The screenshot you posted is from PCI(e) initialization. There should be a lot of output before that.
So no, I doubt, that the kernel crashes "that fast". "0.34 seconds" (according to your screenshot) might sound early, but in terms of kernel...
Thank you for your Reply :) .
When I was in BIOS the other Day, I am pretty sure it was under the Advanced Features Submenu, NOT the IPMI one.
COM1 was set to COM by Default, whereas COM2 was set to SOL by Default.
Logically COM1 would be the...
According to the blockdiagram, that Supermicro provides, your UARTs are both coming directly from the Aspeed AST2400 BMC. Plus there seems to be a suspicious "Serial Mux" BIOS setting in the "IPMI" Submenu.
Might be, that both UARTs are...
Any Idea ?
EDIT 1: back several Months for a similar Issue (digging through my Emails since Forum Search is quite Bad), @t.lamprecht suggested adding Options earlyprintk=vga,keep to Kernel Command Line, so I might as well try that.
Weird that...
Sorry for the late Reply, but I'm facing the Issue now on another System.
I tried both the Null Modem Cable and using Supermicrom SOL (Serial over LAN) but in both Cases, probably due to misconfiguration, it won't do anything at all.
I...
I tried both with SOL (Serial over LAN) and a local Null-Modem Cable connected between the DB9 Serial Port of one Host and the DB9 Serial Port of the other Host.
Nothing is working :( .
I tried with: minicom --device /dev/ttyX --baudrate 115200...
I can observe several Issues (NOT only related to Proxmox VE 9 / Debian Trixie) but rather also e.g. Kernel 6.8 or even Kernel 6.5 on multiple Xeon E3 v3 Systems based on Supermicro X10SLL-F / X10SLM-F Platforms.
This is what it looks like...
I don't think you can really convert them. The Conversion, if any, might be done the other Way around (VM -> CT), but also in that Case it's probably easier to just install from Scratch and restore/migrate from Backup.
You need to DEPLOY a new...
That's what I usually do indeed.
However I cannot do that for some Hosts because of these **** IOMMU Groups: I CANNOT pass only the Hailo PCIe Accelerator to the VM, but instead it would pass the entire Chipset PCIe Devices (NIC, SATA...