[SOLVED] Installation of SSD breaks network

[miracuru]

Hi

I have a Minis Forum MS-01 which I use as Proxmox Server.
Installed is a 1TB SSD in the first NVME slot. Proxmox works perfectly in this setup.

I have freed a NVME SSD drive which I want to use now in this machine. I have therefore installed the 2nd NVME SSD in the 2nd slot.
When I boot the machine with both SSD's installed, then I have no network anymore.

I have the output form `ip -a` in the spoiler when only 1 SSD is installed and unfortunately I can't upload a screenshot somehow. But what I see when the 2nd SSD is installed, that the 2nd SSD renames the enp88s0 network device to enp89s0. At least they have the same MAC address.

I'm not sure now, how I can proceed to become the network up again when both SSD's are installed. Maybe someone have an advise?

Please let me know if further information are needed.

Spoiler: ip a command with only 1 SSD installed

╭─root at proxmox in ~
╰─○ ip a
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 noprefixroute
       valid_lft forever preferred_lft forever
2: enp87s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 58:47:ca:76:83:89 brd ff:ff:ff:ff:ff:ff
3: enp88s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr0 state UP group default qlen 1000
    link/ether 58:47:ca:76:83:8a brd ff:ff:ff:ff:ff:ff
4: enp2s0f0np0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 58:47:ca:76:83:87 brd ff:ff:ff:ff:ff:ff
5: enp2s0f1np1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 58:47:ca:76:83:88 brd ff:ff:ff:ff:ff:ff
6: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 58:47:ca:76:83:8a brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.2/24 scope global vmbr0
       valid_lft forever preferred_lft forever
    inet6 fe80::5a47:caff:fe76:838a/64 scope link
       valid_lft forever preferred_lft forever
7: wlp89s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 4c:50:dd:9b:d6:74 brd ff:ff:ff:ff:ff:ff
8: veth101i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
    link/ether fe:a2:d6:3a:31:26 brd ff:ff:ff:ff:ff:ff link-netnsid 0
9: veth102i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
    link/ether fe:2d:75:eb:04:d8 brd ff:ff:ff:ff:ff:ff link-netnsid 1
10: veth103i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
    link/ether fe:15:b6:68:97:c9 brd ff:ff:ff:ff:ff:ff link-netnsid 2
11: veth105i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
    link/ether fe:cb:08:09:70:3f brd ff:ff:ff:ff:ff:ff link-netnsid 3
12: veth107i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
    link/ether fe:c2:87:70:8a:11 brd ff:ff:ff:ff:ff:ff link-netnsid 4
13: veth111i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
    link/ether fe:c6:65:53:22:f6 brd ff:ff:ff:ff:ff:ff link-netnsid 5
14: veth114i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
    link/ether fe:a6:7d:39:96:15 brd ff:ff:ff:ff:ff:ff link-netnsid 6
15: veth116i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
    link/ether fe:31:47:ac:1e:71 brd ff:ff:ff:ff:ff:ff link-netnsid 7
16: veth118i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr118i0 state UP group default qlen 1000
    link/ether fe:33:ee:90:c3:05 brd ff:ff:ff:ff:ff:ff link-netnsid 8
17: fwbr118i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 46:7c:ef:a9:03:eb brd ff:ff:ff:ff:ff:ff
18: fwpr118p0@fwln118i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
    link/ether 36:22:46:69:3f:76 brd ff:ff:ff:ff:ff:ff
19: fwln118i0@fwpr118p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr118i0 state UP group default qlen 1000
    link/ether 46:7c:ef:a9:03:eb brd ff:ff:ff:ff:ff:ff
20: tap202i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UNKNOWN group default qlen 1000
    link/ether 96:d6:9c:76:39:ab brd ff:ff:ff:ff:ff:ff
21: veth400i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
    link/ether fe:d6:a1:82:fc:ac brd ff:ff:ff:ff:ff:ff link-netnsid 9
╭─root at proxmox in ~
╰─○

 

[sw-omit]

It creates those names based on the devices it finds, so that is why it renames them.
There are two options to fix this:
1. Within the /etc/network/interfaces, enp88s0 with enp89s0. You could even copy /etc/network/interfaces to /etc/network/interfaces.new and replace it in there before installing, and then on the next boot it will replace them.
2. Set the name to something yourself with a .link file [1]

[1] https://pve.proxmox.com/wiki/Network_Configuration#_naming_conventions

 

[miracuru]

Hi @sw-omit
That helped. System boots normal now and network is up and running again.
Thanks for your kind help.