@t.lamprecht - I have to take that back. I had tried to replace RAID controller and in the process I had different number of disks between, so that was false positive. I tried to compare the last entries in dmesg output but they look identical - so I guess some libraries / binaries got upgraded...
@t.lamprecht - i have found one interresting thing. On 5.3 iso, the loader is searching for cdrom on /dev/sdd and its working. On 5.4 its trying to find cdrom on /dev/sdc and that fails - maybe its not related, but it seems odd to me.
I have upgraded all hardware components before trying to install Proxmox. I want to use ZFS so I am using the Legacy mode. The server isnt newest but still has support for 2 more years though.
I will try to switch to EFI for testing.
I have been banging my head for last 3 hours trying to install Proxmox using the ISO 5.4-1 on Fujitsu Primergy RX200 S7 - every time I ended up on screen saying no cdrom found. I tried Ether, rufus, Easy2Boot - nothing has worked.
Then I have stumbled onto this page...
So unfortunately it has happened again. This time we managed to get the stack trace:
[223849.690311] kernel BUG at mm/slub.c:296!
[223849.690345] invalid opcode: 0000 [#1] SMP PTI
[223849.690368] Modules linked in: tcp_diag inet_diag ebtable_filter ebtables ip6t_REJECT nf_reject_ipv6...
It has happened this morning again even with older version. of the kernel
So I have found there was outdated BIOS. Other components are up to date. I have upgraded the BIOS to the latest version and I see there was a new version of the kernel 4.15.18-9 available so I have installed it also...
Its Fujitsu PRIMERGY RX2530M1 with PRAID EP400i - 8 Seagate ST900MM0018 drives put in JBOD mode so Proxmox sees all the drivers - one of them is a hot spare.
We have attached two M2 SSDs (Samsung 970 PRO 512GB and Samsung 860 EVO M.2 250GB) for ZIL / L2ARC using I-TEC PCI-E 2x M.2 Card - we were...
I have upgraded the kernel to this version just yesterday and today our hypervisor showed kernel panic and journald was complaining that it cant write anything. VMs were running, but when i tried to write anything to the disk it froze. After 10 more minutes VMs stopped responding.
Well, if I recall correctly apt-get upgrade should install just fixes and shouldn't break anything. dist-upgrade can change versions and dependencies.
I just wanted to install all security fixes and nothing new - so maybe you should think about following the standard implied by apt creators...
During apt-get upgrade I got following error:
root@xxxx:~# apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
libpve-common-perl proxmox-ve pve-container pve-manager...
we are comparing different products for our new servers. We really like Proxmox, but there is one problem that we are not even sure what does it mean.
Every time we try to run Debian graphical installation on VM, we get an error saying "cpu0 unhandled rdmsr: 0x345". It's happening only when...