MinisForum MS-01 Problems Installing Proxmox 8.2

[Zwitscher_Tom]

Hi,

I tried to install Proxmox 8.2 on a brand new MinisForum MS-01 system.
After the installation of Proxmox 8.2, I am able to reach the Web Gui at port 8006 for some minutes.
After some minutes the ports 22 and 8006 are closed.

I installed Windows 11 on the MS-01 and found that Windows 11 doesn not install network drivers.
I had to install the network drivers by hand.

Does Proxmox 8.2 not support MinisForum MS-01 systems?

Thanks.

 

[justinclift]

In theory, Proxmox should work ok with that system. So it's strange that it's not.

As a first step, I'd probably reboot the system when it stops being available on the network, then I'd collect the kernel logs from the previous boot.

There's a command for doing that and saving them to a file:

journalctl -b -1 > somefile.txt

The -1 there means "the previous boot". You can do -2, -3, -4 (etc) to get the runs before that too if you ever need to.

Anyway, I'd probably try looking through the end of that saved file to see if it says what happened. If you're unsure, you can try attaching the file here for people to look at.

 

[Zwitscher_Tom]

Thanks for your answer.
Here are the setps I performed just recently:
- Installed proxmox-ve_8.2-1.iso
- Installed no updates
- Checked from another system if ports 22 and 8006 are closed
- Both ports are closed
- Reboot the system
- Run journalctl -b -1 > boot.txt

Please find boot.txt attached

 

[justinclift]

Looking through that, the bootup piece of that looks all very standard through to about here:

Jun 29 09:10:12 pm1 kernel: sd 0:0:0:0: [sda] No Caching mode page found
Jun 29 09:10:12 pm1 kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through
Jun 29 09:10:12 pm1 kernel: sda: sda1
Jun 29 09:10:12 pm1 kernel: sd 0:0:0:0: [sda] Attached SCSI removable disk

After that though, the log starts showing a lot (hundreds?) of network related errors:

Jun 29 09:11:30 pm1 kernel: vmbr0: received packet on enp88s0 with own address as source address (addr:58:47:ca:77:5b:55, vlan:0)
Jun 29 09:11:31 pm1 kernel: vmbr0: received packet on enp88s0 with own address as source address (addr:58:47:ca:77:5b:55, vlan:0)
Jun 29 09:11:31 pm1 kernel: vmbr0: received packet on enp88s0 with own address as source address (addr:58:47:ca:77:5b:55, vlan:0)
Jun 29 09:11:31 pm1 kernel: vmbr0: received packet on enp88s0 with own address as source address (addr:58:47:ca:77:5b:55, vlan:0)
Jun 29 09:11:31 pm1 kernel: vmbr0: received packet on enp88s0 with own address as source address (addr:58:47:ca:77:5b:55, vlan:0)
Jun 29 09:11:37 pm1 kernel: net_ratelimit: 22 callbacks suppressed
Jun 29 09:11:37 pm1 kernel: vmbr0: received packet on enp88s0 with own address as source address (addr:58:47:ca:77:5b:55, vlan:0)
Jun 29 09:11:37 pm1 kernel: vmbr0: received packet on enp88s0 with own address as source address (addr:58:47:ca:77:5b:55, vlan:0)

After several minutes of that, the kernel is showing a reboot has been triggered so it goes through the reboot process:

Jun 29 09:14:58 pm1 kernel: vmbr0: received packet on enp88s0 with own address as source address (addr:58:47:ca:77:5b:55, vlan:0)
Jun 29 09:14:58 pm1 kernel: vmbr0: received packet on enp88s0 with own address as source address (addr:58:47:ca:77:5b:55, vlan:0)
Jun 29 09:14:58 pm1 kernel: vmbr0: received packet on enp88s0 with own address as source address (addr:58:47:ca:77:5b:55, vlan:0)
Jun 29 09:14:58 pm1 kernel: vmbr0: received packet on enp88s0 with own address as source address (addr:58:47:ca:77:5b:55, vlan:0)
Jun 29 09:15:02 pm1 systemd-logind[715]: The system will reboot now!
Jun 29 09:15:02 pm1 systemd-logind[715]: System is rebooting.
Jun 29 09:15:02 pm1 systemd[1]: Stopping session-1.scope - Session 1 of User root...
Jun 29 09:15:02 pm1 systemd[1]: Removed slice system-modprobe.slice - Slice /system/modprobe.
(etc)

From the above, it's pretty clear the network problems are related to the errors in that middle section. I'm not a super in-depth networking person, so may not be the right person to sort that out.

But to my initial reading of that duplicated message it seems like you either have some other network adapter on your network with the same MAC address, or your network configuration is screwed up in some fashion to the point where the Proxmox kernel thinks you do.

As to "why?"... that's a good question. Any idea if there's other stuff on your network that could be causing that?

 

[meyergru]

I do not know if that helps, but I have two pieces of info on that machine:

1. One of the interfaces is shared with an Intel AMT port. That could lead to the strange messages, because the Intel AMT adapter may send DHCP requests or something of that sort with the same MAC.

2. The Intel NICs are known to be unstable unless one disables the ASPM (see this).

I have no explanation for the reboot, though.

 

[justinclift]

I have no explanation for the reboot, though.

The reboot is manual (or that's my understanding anyway) due to the server no longer being available over the network.

 

[Zwitscher_Tom]

I have enabled the Intel AMT.
Therefore the kernel messages came from.
I rebooted the proxmox server manually.

 

[justinclift]

It sounds like disabling ASPM might be the next thing to try then.