TrueNAS doesn't set interface UP on startup

TrueNAS General
,
1

Hi,

After hardware upgrade which changed the network interfaces, TN doesn’t set the new ones UP on startup. I’m using a bridge with the new network interface and a VM one added, which worked normally before the upgrade. Now the new hardware interface, which name is different than the old one, isn’t brought up and I have to manually do it via shell. Any ideas how to fix it?

2

To add some info - the new interface isn’t in the TN database.

3

Post the output of ip a.

Also, FWIW, when I performed a transfer to new HW, I had strange issues as long as old non-existent nics were part of my bridges.

4 
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: enp7s0f0np0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master br0 state UP group default qlen 1000
    link/ether d8:43:ae:a9:9f:aa brd ff:ff:ff:ff:ff:ff
    inet6 fe80::da43:aeff:fea9:9faa/64 scope link proto kernel_ll 
       valid_lft forever preferred_lft forever
3: enp7s0f1np1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether d8:43:ae:a9:9f:ab brd ff:ff:ff:ff:ff:ff
5: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 1a:30:50:fa:9b:71 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.31/24 brd 192.168.1.255 scope global br0
       valid_lft forever preferred_lft forever
    inet6 fe80::7815:f8ff:fe90:2b32/64 scope link proto kernel_ll 
       valid_lft forever preferred_lft forever
5

Nothing criminal on the first glance.

You meant truenas gui? Are you speaking about enp7s0f0np0? Also, do you have your old interface in the gui? Perhaps screenshot would help.

6

I mean the freenas-v1.db database. enp7s0f0np0 is not there, while it is present in the UI. There were the old interfaces, but I deleted them in the UI.

7

How did you perform your hardware upgrade? Did you just move all your drives?

8

I simply swapped the motherboard.

1 Like
9

Hmm, I’m out of ideas. Perhaps someone else could help.

10

Did you try to do it locally? I mean, when you do changes via WebUI and apply, you’ll lose connection. Don’t you?

With monitor and keyboard hooked up on the CLI start screen:

[1] delete bridge
[2] delete all member interfaces
[3] reboot
[4] setup new interface(s)

Should do.

1 Like
11

For anyone reading this - the, somewhat hacky, solution was to add a description to the new interfaces which made TN add them to its database and now everything works.

1 Like