[SOLVED] VLAN Problems

floh · Feb 3, 2020

Hello Community!

I'm currently having a problem with the network settings. I've already a working cluster with server-hardware (using VLAN taggs).

Now I'm trying to setup a second cluster (with consumer hardware) to test new updates and to play around without being afraid to break something on the important cluster.

I first focused on creating a bond and next creating vmbridges onto that bond but I couldn't figured it out to work properly. So I just tried to get vlans working on just the interfaces itself.

Here's the output of ip a:

Code:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: enp6s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether bc:ae:c5:22:8f:8f brd ff:ff:ff:ff:ff:ff
    inet6 fe80::beae:c5ff:fe22:8f8f/64 scope link
       valid_lft forever preferred_lft forever
3: enp5s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether bc:ae:c5:22:8c:1c brd ff:ff:ff:ff:ff:ff
4: enp8s1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UP group default qlen 1000
    link/ether 00:0e:0c:bc:a4:39 brd ff:ff:ff:ff:ff:ff
5: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 00:0e:0c:bc:a4:39 brd ff:ff:ff:ff:ff:ff
    inet 192.168.10.23/24 scope global vmbr0
       valid_lft forever preferred_lft forever
    inet6 fe80::20e:cff:febc:a439/64 scope link
       valid_lft forever preferred_lft forever
6: vmbr1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000
    link/ether 66:b9:a6:06:55:aa brd ff:ff:ff:ff:ff:ff
    inet 192.168.10.24/24 scope global vmbr1
       valid_lft forever preferred_lft forever
    inet6 fe80::64b9:a6ff:fe06:55aa/64 scope link
       valid_lft forever preferred_lft forever

and here is /etc/network/interfaces:

Code:

# 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' directives to do
# so.
# PVE will preserve these directives, but will NOT read its network
# configuration from sourced files, so do not attempt to move any of
# the PVE managed interfaces into external files!

auto lo
iface lo inet loopback

iface enp5s0 inet manual

iface enp6s0 inet manual

iface enp8s1 inet manual

iface enp6s0.40 inet manual
#iface enp5s0.40 inet manual

iface enp8s1.40 inet manual

auto vmbr0
iface vmbr0 inet static
    address  192.168.10.23
    netmask  255.255.255.0
    gateway  192.168.10.17
    bridge-ports enp8s1
    bridge-stp off
    bridge-fd 0

auto vmbr1
iface vmbr1 inet static
    address  192.168.10.24
    netmask  24
    bridge-ports enp6s0.40
    bridge-stp off
    bridge-fd 0

enp8s1 is currently plugged in to a network configured with the vlan tag 40.
enp6s0 is currently plugged into the same network but untagged (just for debugging purposes).

So I'm trying to get this node working with any interface with the vlan-tag 40.

Best regards
Floh

wolfgang · Feb 4, 2020

Hi,

sorry but I miss the question?

floh · Feb 19, 2020

Hi!

Sorry for the lack of timely response.

I figured something (hopefully) useful out:

The machine was not able to enslave it's interfaces to create a working bond(found this error with "systemctl status networking")

After a while of troubleshooting I found that the bonding module isn't loaded and cannot be found on the server - which is very strange in my opinion.

Here is the output of a fresh installed version of the machine with the latest iso (without updates, because they didn't resolve the problem before the fresh installation):

Code:

root@srv-eg-beta3:~# uname -r
5.0.21-5-pve
root@srv-eg-beta3:~# modprobe bonding
modprobe: ERROR: ../libkmod/libkmod.c:586 kmod_search_moddep() could not open moddep file '/lib/modules/5.0.21-5-pve/modules.dep.bin'
modprobe: FATAL: Module bonding not found in directory /lib/modules/5.0.21-5-pve
root@srv-eg-beta3:~# cd /lib/modules
root@srv-eg-beta3:/lib/modules# ls
5.3.10-1-pve
root@srv-eg-beta3:/lib/modules#
root@srv-eg-beta3:/lib/modules#

root@srv-eg-beta3:/lib/modules# pveversion
pve-manager/6.1-3/37248ce6 (running kernel: 5.0.21-5-pve)

So the problem is that I cannot even make a working bond - even without thinking any further (vlan tags, ...)

Any idea what could be wrong with this installation?

wolfgang · Feb 19, 2020

Please upgrade to the current version and try again.
It makes no sense to debug outdated versions.

https://pve.proxmox.com/wiki/Package_Repositories

floh · Feb 19, 2020

Hi wolfgang!

I've updated to the latest version - I just thought it's an useful information for you and your team that I'm currently facing a problem on the latest version you provide as an .img

Anyway...
I'm currently facing two problems and I don't want to confuse you so I'm not sure if it's useful to provide all information at once.

Problem 1: I cannot create a working bond.
Problem 2: vlans aren't working.
Maybe both problems exist because of one failure.

Infos for Problem 1 (bonding):

Code:

root@srv-eg-beta3:~# pveversion
pve-manager/6.1-7/13e58d5e (running kernel: 5.0.21-5-pve)

Code:

root@srv-eg-beta3:~# uname -r
5.0.21-5-pve
root@srv-eg-beta3:~# modprobe bonding
modprobe: ERROR: ../libkmod/libkmod.c:586 kmod_search_moddep() could not open moddep file '/lib/modules/5.0.21-5-pve/modules.dep.bin'
modprobe: FATAL: Module bonding not found in directory /lib/modules/5.0.21-5-pve
root@srv-eg-beta3:~# ls -al /lib/modules/
total 16
drwxr-xr-x  4 root root 4096 Feb 19 09:56 .
drwxr-xr-x 63 root root 4096 Feb 19 09:56 ..
drwxr-xr-x  4 root root 4096 Feb 19 09:23 5.3.10-1-pve
drwxr-xr-x  4 root root 4096 Feb 19 09:56 5.3.18-1-pve

Problem 2 (vlans):
When I'm trying to use vlans directly at NIC-level I get the error-message "interface enp6s0.40 does not exist!".
I'll provide some more details:
Here is the network config - just to clarify that: enp8s1 is plugged into a network which is untagged (to access the server; let's say for debugging purposes)
enp6s0 is plugged into to wanted network - here is nothing untagged, only vlan 40 is tagged there.

Code:

root@srv-eg-beta3:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback

iface enp8s1 inet manual

auto vmbr0
iface vmbr0 inet static
    address 192.168.10.23
    netmask 255.255.255.0
    gateway 192.168.10.17
    bridge_ports enp8s1
    bridge_stp off
    bridge_fd 0

iface enp6s0 inet manual
iface enp6s0.40 inet manual

iface enp5s0 inet manual

auto vmbr40
iface vmbr40 inet static
        address 192.168.10.24
        netmask 255.255.255.0
        bridge_ports enp6s0.40
        bridge_stp off
        bridge_fd 0

Next is the output where I found the error message provided above:

Code:

root@srv-eg-beta3:~# systemctl status networking
● networking.service - Raise network interfaces
   Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled)
   Active: active (exited) since Wed 2020-02-19 10:09:57 CET; 14min ago
     Docs: man:interfaces(5)
  Process: 746 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=0/SUCCESS)
Main PID: 746 (code=exited, status=0/SUCCESS)

Feb 19 10:09:57 srv-eg-beta3 systemd[1]: Starting Raise network interfaces...
Feb 19 10:09:57 srv-eg-beta3 ifup[746]: Waiting for vmbr0 to get ready (MAXWAIT is 2 seconds).
Feb 19 10:09:57 srv-eg-beta3 ifup[746]: Error: Unknown device type.
Feb 19 10:09:57 srv-eg-beta3 ifup[746]: interface enp6s0.40 does not exist!
Feb 19 10:09:57 srv-eg-beta3 ifup[746]: Waiting for vmbr40 to get ready (MAXWAIT is 2 seconds).
Feb 19 10:09:57 srv-eg-beta3 systemd[1]: Started Raise network interfaces.

Just some additional info: When I comment out vmbr40 and enp6s0.40 (so everything related to the vlan) there are no error messages.

So now I provided all infos to let you build yourself a big picture of the problem - please tell me if you want to focus one problem fist.
As said above: This machine is newly installed today and updated to the latest version. The only change made by me is in /etc/network/interfaces where I added the interface with ".40" at the end and I added vmbr40

best regards
Floh

Edit:
Here is the output of a simple ping-test:

Code:

root@srv-eg-beta3:~# ping -I vmbr0 192.168.10.254
PING 192.168.10.254 (192.168.10.254) from 192.168.10.23 vmbr0: 56(84) bytes of data.
64 bytes from 192.168.10.254: icmp_seq=1 ttl=128 time=0.485 ms
64 bytes from 192.168.10.254: icmp_seq=2 ttl=128 time=0.380 ms
64 bytes from 192.168.10.254: icmp_seq=3 ttl=128 time=0.347 ms
^C
--- 192.168.10.254 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 46ms
rtt min/avg/max/mdev = 0.347/0.404/0.485/0.058 ms
root@srv-eg-beta3:~# ping -I vmbr40 192.168.10.254
PING 192.168.10.254 (192.168.10.254) from 192.168.10.24 vmbr40: 56(84) bytes of data.
^C
--- 192.168.10.254 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 55ms
pipe 3
root@srv-eg-beta3:~#

wolfgang · Feb 19, 2020

You have to reboot the host to load the new kernel.
You still use the old one.
What Nic Hardware do you use?

floh · Feb 19, 2020

I've rebooted the host after the upgrade.

I just rebooted the machine again:

Code:

root@srv-eg-beta3:~# uname -r
5.0.21-5-pve
root@srv-eg-beta3:~#

I use one onboard nic (intel - asus board) and an additional external (PCI-Slot) NIC, because it wasn't working with the onboard nics - but the result is the same.

Edit:
Here are some additional infos:

Code:

root@srv-eg-beta3:~# dpkg --list | grep kernel
ii  ipset                                6.38-1.2                    amd64        administration tool for kernel IP sets
ii  kmod                                 26-1                        amd64        tools for managing Linux kernel modules
ii  libaio1:amd64                        0.3.112-3                   amd64        Linux kernel AIO access library - shared library
ii  pve-firmware                         3.0-5                       all          Binary firmware code for the pve-kernel
ii  pve-kernel-5.3                       6.1-4                       all          Latest Proxmox VE Kernel Image
ii  pve-kernel-5.3.10-1-pve              5.3.10-1                    amd64        The Proxmox PVE Kernel Image
ii  pve-kernel-5.3.18-1-pve              5.3.18-1                    amd64        The Proxmox PVE Kernel Image
ii  pve-kernel-helper                    6.1-4                       all          Function for various kernel maintenance tasks.
ii  rsyslog                              8.1901.0-1                  amd64        reliable system and kernel logging daemon
root@srv-eg-beta3:~# ls /lib/modules
5.3.10-1-pve  5.3.18-1-pve
root@srv-eg-beta3:~# uname -r
5.0.21-5-pve

wolfgang · Feb 19, 2020

floh said:
I've updated to the latest version - I just thought it's an useful information for you and your team that I'm currently facing a problem on the latest version you provide as an .img

The kernel 5.0 is from the PVE 6.0 the latest image is 6.1.

Do you have a grub kernel binding because in der default setting it loads always the newest kernel?

floh · Feb 19, 2020

Hey Wolfgang!

I've installed 6.1 today - how can I check if a kernel binding is configured?

floh · Feb 19, 2020

I don't know if that's the correct file - and I'm not familiar with it but I couldn't find 5.0.x hardcoded.

Code:

root@srv-eg-beta3:~# cat /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
  set have_grubenv=true
  load_env
fi
if [ "${next_entry}" ] ; then
   set default="${next_entry}"
   set next_entry=
   save_env next_entry
   set boot_once=true
else
   set default="0"
fi

if [ x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
else
  menuentry_id_option=""
fi

export menuentry_id_option

if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z "${boot_once}" ]; then
    saved_entry="${chosen}"
    save_env saved_entry
  fi
}
function load_video {
  if [ x$feature_all_video_module = xy ]; then
    insmod all_video
  else
    insmod efi_gop
    insmod efi_uga
    insmod ieee1275_fb
    insmod vbe
    insmod vga
    insmod video_bochs
    insmod video_cirrus
  fi
}

if [ x$feature_default_font_path = xy ] ; then
   font=unicode
else
insmod part_gpt
insmod lvm
insmod ext2
set root='lvmid/pOm47W-UN4d-tUa2-QA4g-zSEG-ALkJ-SQBRKz/p5uT1c-qDHn-6oNf-FeSY-AiXh-fNqT-i6bElc'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint='lvmid/pOm47W-UN4d-tUa2-QA4g-zSEG-ALkJ-SQBRKz/p5uT1c-qDHn-6oNf-FeSY-AiXh-fNqT-i6bElc'  88fcdf69-ca10-41c0-816c-1af31f8dfcf9
else
  search --no-floppy --fs-uuid --set=root 88fcdf69-ca10-41c0-816c-1af31f8dfcf9
fi
    font="/usr/share/grub/unicode.pf2"
fi

if loadfont $font ; then
  set gfxmode=auto
  load_video
  insmod gfxterm
  set locale_dir=$prefix/locale
  set lang=en_US
  insmod gettext
fi
terminal_output gfxterm
if [ "${recordfail}" = 1 ] ; then
  set timeout=30
else
  if [ x$feature_timeout_style = xy ] ; then
    set timeout_style=menu
    set timeout=5
  # Fallback normal timeout code in case the timeout_style feature is
  # unavailable.
  else
    set timeout=5
  fi
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
    set gfxpayload="${1}"
}
set linux_gfx_mode=
export linux_gfx_mode
menuentry 'Proxmox Virtual Environment GNU/Linux' --class proxmox --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-88fcdf69-ca10-41c0-816c-1af31f8dfcf9' {
    load_video
    insmod gzio
    if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
    insmod part_gpt
    insmod lvm
    insmod ext2
    set root='lvmid/pOm47W-UN4d-tUa2-QA4g-zSEG-ALkJ-SQBRKz/p5uT1c-qDHn-6oNf-FeSY-AiXh-fNqT-i6bElc'
    if [ x$feature_platform_search_hint = xy ]; then
      search --no-floppy --fs-uuid --set=root --hint='lvmid/pOm47W-UN4d-tUa2-QA4g-zSEG-ALkJ-SQBRKz/p5uT1c-qDHn-6oNf-FeSY-AiXh-fNqT-i6bElc'  88fcdf69-ca10-41c0-816c-1af31f8dfcf9
    else
      search --no-floppy --fs-uuid --set=root 88fcdf69-ca10-41c0-816c-1af31f8dfcf9
    fi
    echo    'Loading Linux 5.3.18-1-pve ...'
    linux    /boot/vmlinuz-5.3.18-1-pve root=/dev/mapper/pve-root ro  quiet
    echo    'Loading initial ramdisk ...'
    initrd    /boot/initrd.img-5.3.18-1-pve
}
submenu 'Advanced options for Proxmox Virtual Environment GNU/Linux' $menuentry_id_option 'gnulinux-advanced-88fcdf69-ca10-41c0-816c-1af31f8dfcf9' {
    menuentry 'Proxmox Virtual Environment GNU/Linux, with Linux 5.3.18-1-pve' --class proxmox --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-5.3.18-1-pve-advanced-88fcdf69-ca10-41c0-816c-1af31f8dfcf9' {
        load_video
        insmod gzio
        if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
        insmod part_gpt
        insmod lvm
        insmod ext2
        set root='lvmid/pOm47W-UN4d-tUa2-QA4g-zSEG-ALkJ-SQBRKz/p5uT1c-qDHn-6oNf-FeSY-AiXh-fNqT-i6bElc'
        if [ x$feature_platform_search_hint = xy ]; then
          search --no-floppy --fs-uuid --set=root --hint='lvmid/pOm47W-UN4d-tUa2-QA4g-zSEG-ALkJ-SQBRKz/p5uT1c-qDHn-6oNf-FeSY-AiXh-fNqT-i6bElc'  88fcdf69-ca10-41c0-816c-1af31f8dfcf9
        else
          search --no-floppy --fs-uuid --set=root 88fcdf69-ca10-41c0-816c-1af31f8dfcf9
        fi
        echo    'Loading Linux 5.3.18-1-pve ...'
        linux    /boot/vmlinuz-5.3.18-1-pve root=/dev/mapper/pve-root ro  quiet
        echo    'Loading initial ramdisk ...'
        initrd    /boot/initrd.img-5.3.18-1-pve
    }
    menuentry 'Proxmox Virtual Environment GNU/Linux, with Linux 5.3.10-1-pve' --class proxmox --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-5.3.10-1-pve-advanced-88fcdf69-ca10-41c0-816c-1af31f8dfcf9' {
        load_video
        insmod gzio
        if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
        insmod part_gpt
        insmod lvm
        insmod ext2
        set root='lvmid/pOm47W-UN4d-tUa2-QA4g-zSEG-ALkJ-SQBRKz/p5uT1c-qDHn-6oNf-FeSY-AiXh-fNqT-i6bElc'
        if [ x$feature_platform_search_hint = xy ]; then
          search --no-floppy --fs-uuid --set=root --hint='lvmid/pOm47W-UN4d-tUa2-QA4g-zSEG-ALkJ-SQBRKz/p5uT1c-qDHn-6oNf-FeSY-AiXh-fNqT-i6bElc'  88fcdf69-ca10-41c0-816c-1af31f8dfcf9
        else
          search --no-floppy --fs-uuid --set=root 88fcdf69-ca10-41c0-816c-1af31f8dfcf9
        fi
        echo    'Loading Linux 5.3.10-1-pve ...'
        linux    /boot/vmlinuz-5.3.10-1-pve root=/dev/mapper/pve-root ro  quiet
        echo    'Loading initial ramdisk ...'
        initrd    /boot/initrd.img-5.3.10-1-pve
    }
}

### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_linux_xen ###

### END /etc/grub.d/20_linux_xen ###

### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry "Memory test (memtest86+)" {
    insmod part_gpt
    insmod lvm
    insmod ext2
    set root='lvmid/pOm47W-UN4d-tUa2-QA4g-zSEG-ALkJ-SQBRKz/p5uT1c-qDHn-6oNf-FeSY-AiXh-fNqT-i6bElc'
    if [ x$feature_platform_search_hint = xy ]; then
      search --no-floppy --fs-uuid --set=root --hint='lvmid/pOm47W-UN4d-tUa2-QA4g-zSEG-ALkJ-SQBRKz/p5uT1c-qDHn-6oNf-FeSY-AiXh-fNqT-i6bElc'  88fcdf69-ca10-41c0-816c-1af31f8dfcf9
    else
      search --no-floppy --fs-uuid --set=root 88fcdf69-ca10-41c0-816c-1af31f8dfcf9
    fi
    linux16    /boot/memtest86+.bin
}
menuentry "Memory test (memtest86+, serial console 115200)" {
    insmod part_gpt
    insmod lvm
    insmod ext2
    set root='lvmid/pOm47W-UN4d-tUa2-QA4g-zSEG-ALkJ-SQBRKz/p5uT1c-qDHn-6oNf-FeSY-AiXh-fNqT-i6bElc'
    if [ x$feature_platform_search_hint = xy ]; then
      search --no-floppy --fs-uuid --set=root --hint='lvmid/pOm47W-UN4d-tUa2-QA4g-zSEG-ALkJ-SQBRKz/p5uT1c-qDHn-6oNf-FeSY-AiXh-fNqT-i6bElc'  88fcdf69-ca10-41c0-816c-1af31f8dfcf9
    else
      search --no-floppy --fs-uuid --set=root 88fcdf69-ca10-41c0-816c-1af31f8dfcf9
    fi
    linux16    /boot/memtest86+.bin console=ttyS0,115200n8
}
menuentry "Memory test (memtest86+, experimental multiboot)" {
    insmod part_gpt
    insmod lvm
    insmod ext2
    set root='lvmid/pOm47W-UN4d-tUa2-QA4g-zSEG-ALkJ-SQBRKz/p5uT1c-qDHn-6oNf-FeSY-AiXh-fNqT-i6bElc'
    if [ x$feature_platform_search_hint = xy ]; then
      search --no-floppy --fs-uuid --set=root --hint='lvmid/pOm47W-UN4d-tUa2-QA4g-zSEG-ALkJ-SQBRKz/p5uT1c-qDHn-6oNf-FeSY-AiXh-fNqT-i6bElc'  88fcdf69-ca10-41c0-816c-1af31f8dfcf9
    else
      search --no-floppy --fs-uuid --set=root 88fcdf69-ca10-41c0-816c-1af31f8dfcf9
    fi
    multiboot    /boot/memtest86+_multiboot.bin
}
menuentry "Memory test (memtest86+, serial console 115200, experimental multiboot)" {
    insmod part_gpt
    insmod lvm
    insmod ext2
    set root='lvmid/pOm47W-UN4d-tUa2-QA4g-zSEG-ALkJ-SQBRKz/p5uT1c-qDHn-6oNf-FeSY-AiXh-fNqT-i6bElc'
    if [ x$feature_platform_search_hint = xy ]; then
      search --no-floppy --fs-uuid --set=root --hint='lvmid/pOm47W-UN4d-tUa2-QA4g-zSEG-ALkJ-SQBRKz/p5uT1c-qDHn-6oNf-FeSY-AiXh-fNqT-i6bElc'  88fcdf69-ca10-41c0-816c-1af31f8dfcf9
    else
      search --no-floppy --fs-uuid --set=root 88fcdf69-ca10-41c0-816c-1af31f8dfcf9
    fi
    multiboot    /boot/memtest86+_multiboot.bin console=ttyS0,115200n8
}
### END /etc/grub.d/20_memtest86+ ###

### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/30_uefi-firmware ###
### END /etc/grub.d/30_uefi-firmware ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries.  Simply type the
# menu entries you want to add after this comment.  Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###

### BEGIN /etc/grub.d/41_custom ###
if [ -f  ${config_directory}/custom.cfg ]; then
  source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f  $prefix/custom.cfg ]; then
  source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
root@srv-eg-beta3:~#

... and some additional infos I found which seems also strange to me:

Code:

root@srv-eg-beta3:~# ls /boot ; uname -a
config-5.3.10-1-pve  efi   initrd.img-5.3.10-1-pve  memtest86+.bin          pve               System.map-5.3.18-1-pve    vmlinuz-5.3.18-1-pve
config-5.3.18-1-pve  grub  initrd.img-5.3.18-1-pve  memtest86+_multiboot.bin  System.map-5.3.10-1-pve  vmlinuz-5.3.10-1-pve
Linux srv-eg-beta3 5.0.21-5-pve #1 SMP PVE 5.0.21-10 (Wed, 13 Nov 2019 08:27:10 +0100) x86_64 GNU/Linux

wolfgang · Feb 19, 2020

please send the output of

lsblk

floh · Feb 19, 2020

Code:

root@srv-eg-beta3:~# lsblk
NAME                        MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
sda                           8:0    0  1.9T  0 disk
├─sda1                        8:1    0 1007K  0 part
├─sda2                        8:2    0  512M  0 part
└─sda3                        8:3    0  1.9T  0 part
  ├─pve-swap                253:2    0    8G  0 lvm  [SWAP]
  ├─pve-root                253:3    0   96G  0 lvm  /
  ├─pve-data_tmeta          253:4    0 15.8G  0 lvm 
  │ └─pve-data              253:6    0  1.7T  0 lvm 
  └─pve-data_tdata          253:5    0  1.7T  0 lvm 
    └─pve-data              253:6    0  1.7T  0 lvm 
sdf                           8:80   1  2.7T  0 disk
├─sdf1                        8:81   1    1M  0 part
├─sdf2                        8:82   1  256M  0 part
└─sdf3                        8:83   1  2.7T  0 part
  ├─pve--OLD--E6EE598B-swap 253:0    0    8G  0 lvm 
  └─pve--OLD--E6EE598B-root 253:1    0   96G  0 lvm 
sr0                          11:0    1 1024M  0 rom 
root@srv-eg-beta3:~#

best regards,
Floh

wolfgang · Feb 20, 2020

You boot from the old PVE partition.
This is why you load the old 5.0 kernel.
this kernel does not work because it has no modules.

Set the correct boot device in the Bios and then you boot in the correct kernel and everything will work.

floh · Feb 21, 2020

Hello Wolfgang!

Thank you! I couldn't believe that it was such a dumb thing...

Code:

root@srv-eg-beta3:~# modprobe bonding
root@srv-eg-beta3:~# lsblk
NAME               MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
sda                  8:0    0  1.9T  0 disk
├─sda1               8:1    0 1007K  0 part
├─sda2               8:2    0  512M  0 part
└─sda3               8:3    0  1.9T  0 part
  ├─pve-swap       253:0    0    8G  0 lvm  [SWAP]
  ├─pve-root       253:1    0   96G  0 lvm  /
  ├─pve-data_tmeta 253:2    0 15.8G  0 lvm
  │ └─pve-data     253:4    0  1.7T  0 lvm
  └─pve-data_tdata 253:3    0  1.7T  0 lvm
    └─pve-data     253:4    0  1.7T  0 lvm
sr0                 11:0    1 1024M  0 rom
root@srv-eg-beta3:~# ping -I vmbr40 192.168.10.254
PING 192.168.10.254 (192.168.10.254) from 192.168.10.24 vmbr40: 56(84) bytes of data.
64 bytes from 192.168.10.254: icmp_seq=1 ttl=128 time=1.13 ms
64 bytes from 192.168.10.254: icmp_seq=2 ttl=128 time=0.393 ms
^C
--- 192.168.10.254 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 2ms
rtt min/avg/max/mdev = 0.393/0.759/1.125/0.366 ms
root@srv-eg-beta3:~# ping -I vmbr0 192.168.10.254
PING 192.168.10.254 (192.168.10.254) from 192.168.10.23 vmbr0: 56(84) bytes of data.
64 bytes from 192.168.10.254: icmp_seq=1 ttl=128 time=0.325 ms
64 bytes from 192.168.10.254: icmp_seq=2 ttl=128 time=0.339 ms
^C
--- 192.168.10.254 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 26ms
rtt min/avg/max/mdev = 0.325/0.332/0.339/0.007 ms
root@srv-eg-beta3:~#

Bonds and VLANs are now working fine.

Thanks,
Floh

Search

Search

[SOLVED] VLAN Problems

floh

Active Member

wolfgang

Proxmox Retired Staff

floh

Active Member

wolfgang

Proxmox Retired Staff

floh

Active Member

wolfgang

Proxmox Retired Staff

floh

Active Member

wolfgang

Proxmox Retired Staff

floh

Active Member

floh

Active Member

wolfgang

Proxmox Retired Staff

floh

Active Member

wolfgang

Proxmox Retired Staff

floh

Active Member