Can't access GUI after reboot - scale

TrueNAS General
,
1

Can’t access gui and system doesn’t seem to boot completely.

I need help with that, I can’t access the gui over local network, ssh doesn’t work either same for the VM that’s on there (home assistant). When I plug a monitor and keyboard on the system, I see briefly a “terminal ‘serial’ not accessible (or found)” error but too quick to read, then a blue rectangle with either boot to truenas, advanced and go to UEFI. And then I have options 1 through 9 with network configuration, shutdown, etc (I added a photo of it). what am I missing? It gets an IP from the router and I see both in my router clients list and in the network config option.

PXL_20241228_172907889
PXL_20241228_1729078891920×2550 361 KB

2

Go into option 7, the linux shell (type in ‘7’ then hit ‘enter’)

Can you Ping your default gateway? If not, what is the output of ip link show and ifconfig

Do you have a bridge setup? Any other details of your hardware, truenas version, network config, etc, etc, etc can help. Otherwise we’re guessing blindly.

3

So, I did try to ping and host is un reachable. I’m running truenas-scale-24.04.2.1 on a lenovo m920 I have one VM to run home assistant (overkill I know but that’s the only thing it does).

Here’s what’s given to me
https ://imgur.com/gallery/36RqMEA

4

Oh and yes there’s a bridge, br0 for the VM

5

Alrighty… time for attempting lazy fixes:

ip link set br0 down
ip link set eno1 down

##if you’re very cautious for some reason, wait 30s

ip link set eno1 up
ip link set br0 up

Then try to ping the gateway away to see if that works - if it does, GUI should be up.

If possible would be good to see specifically the output of ifconfig br0 and ifconfig eno1 if just bouncing the links doesn’t do the needful.

Would also be good to confirm on router that nothing else got the NAS’ IP due to DHCP & lease expiry if just bouncing the links doesn’t fix anything.

6

That didn’t do it…

http s://imgur.com/gallery/DaEjdZY

The link is the ifconfig return for eno1 and br0. I’ve also went on the router (er7206 with the oc200 controller) trying to clear the ARP table but can’t for the life of me find it, I tried changing the DHCP range, I tried assigning a fixed IP that is different from the one it automatically gives it and put it on a different VLAN. Nothing did it, the static IP isn’t being used it still keeps the same adress when the VLAN has a different dhcp range… I’ve restored a back from two weeks ago when it was working fine, that also isn’t working. I’m thinking about resetting the entire network now…

7

Please do not post links to external hosting.

If you have a configuration backup, and you should, go for option 5; otherwise, there should be a reset the network configuration or similar inside option 2.

This however feels like a network issue.

8

Am I crazy or eno1 has the ips setup instead of br0? Shouldn’t it be the other way around…?

Try clearing the ips on eno1 & instead setting them up on br0. br0 just has a ipv6 ip.

Make sure to remove ipv4 & ipv6 from eno1

9

For the link it doesn’t let me put pictures yet and it’s pretty much the only way outside of retyping the entire thing, but I’ll keep that in mind.

With what I’ve tried today it gives me the same feeling but I’ll try what @Fleshmauler suggested and see.

10

When setting up a bridge the bridge should have the IPs & the members should have nothing assigned to them. For example, here you can see enp37s0 is assigned to bridge br0. Both are up, br0 has the IP, while enp37s0 has nothing.

3: enp37s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master br0 state UP mode DEFAULT group default qlen 1000
    link/ether 00:23:a4:0e:01:82 brd ff:ff:ff:ff:ff:ff
6: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether ae:90:9d:e0:43:76 brd ff:ff:ff:ff:ff:ff

br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 10.0.0.149  netmask 255.255.255.0  broadcast 10.0.0.255
        ether ae:90:9d:e0:43:76  txqueuelen 1000  (Ethernet)


enp37s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        ether 00:23:a4:0e:01:82  txqueuelen 1000  (Ethernet)

You on the other hand have an ipv6 address assigned to your bridge, and an ipv4 & ipv6 address assigned to eno1 - I randomly have issues where after a reboot, enp37s0 assigns itself an ipv6 address for some stupid reason & I can’t access my server until I delete it enp37s0’s rando ipv6 address, because life sucks. I’m guessing you have a similar problem to what I face.

Edit: another simple test would be to just temporarily delete the bridge & see if that fixes things. At least afterwards you can set it back up properly if I’m on the right track.

11

That did the trick! I have no idea why it was the way it was because I don’t remember having touched that since the moment I created the vm but, seems like I did which is weird because it wouldn’t have been accessible before the reboot… Anyway, it’s fixed, caused it’s own oddities on the network but all is good.

Thanks a bunch

Edit: oh just saw the previous comment about random changes after reboot, now it makes a bit more sense (not really).

1 Like