Proxmox 8.0.1 - several service in failed

G

gibil

New Member
Aug 15, 2023
2
0
1
Hello everyone,

I need help with my Proxmox VE setup. Following a power outage, all my virtual machines encountered a fatal error.
Additionally, after trying to modify a setting in the BIOS to address the issue, I lost all network connectivity. Furthermore, the web server on port 8006 is also down and maybe some others.
Details :
  • Server with an Intel 82579V Ethernet controller.
  • After the bios modification, the Proxmox environment does not recognize the network card, which appears as "UNCLAIMED" in lshw -class network.
  • The only network interfaces visible are lo and vmbr0. The physical network interface (e.g., eno1, eth0) is missing.
Steps Taken:

  1. Checked lspci and confirmed the Intel Ethernet controller is listed and associated with the e1000e kernel module.
  2. Manually attempted to load the e1000e driver using sudo modprobe e1000e, but this did not resolve the issue.
  3. Ensured that the bridge configuration in /etc/network/interfaces is correct, but still no network access.
My /etc/network/interfaces configuration

Code: 
auto lo
iface lo inet loopback

iface eno1 inet manual

auto vmbr0
iface vmbr0 inet static
address 192.168.1.93/24
gateway 192.168.1.1
bridge-ports eno1
bridge-stp off
bridge-fd 0

systemctl status networking.service

Code: 
proxmox systemd[1]: Starting networking.service - Network initialization...
proxmox networking[738]: networking : configuring network interfaces
proxmox networking[846]: error: vmbr0: bridge port eno1 does not exists
/usr/sbin/ifup : error: vmbr0: bridge port eno1 does not exist

Your advice or assistance would be greatly appreciated to resolve this issue.
 
First, you should consider updating. PVE6.2 is End-of-Life for a long time and isn't receiving security patches. So your server is running with unpatched vulnerabilities for years.

Then I would check with ip a if the NIC got renamed and now isn't matching your netwoek config any longer.

You didn't told us what storage is used, so its hard to give advice on how to try to fix filesystems or rescue data.

PS: Not unusual to corrupt filesystems on a power outage. Thats why you shouldn't run a server without an UPS.
Those aren't that expensive, starting at 50€ and worth it.
 
Last edited:
Thanks for your feedback,

I made a mistake in my previous post about the version number; it's actually the kernel version that is 6.2, not the Proxmox version. I'm running the system with Proxmox-VE 8.0.1.

This is my first time installing Proxmox, which I did back in August. I'm aware of the risks as I haven't set up proper backups or a UPS yet. Originally, I intended to use this setup to learn Proxmox, but I started using it to store some data because I didn't have space elsewhere. While the data isn't critical, it would be a significant time waste to rebuild everything from scratch, specially for my work.

I'm hoping to set up my network properly so that I can continue investigating or perhaps try to restore the LVM to another Proxmox installation. I have a new SSD, I can consider trying a fresh installation while possibly mounting this current one.

Additionally, I've gathered more information. For example, using ifquery -c -a, I found that my network interface is in error.

I notice that IPv6 is enabled, and I've seen in another topic that a "bindipv6only" something* setting might cause such issues, but in my case, it's already turned off.

Here you can have an overview of my storage and the output of ip -a.

https://imgur.com/a/8uZpuPU
 
You must log in or register to reply here.
Top Bottom
Back