fixing truenas new mobo network and web interface reconfigure

a bit of a tricky post to title, but before i get to that, let me confirm, that yes indeed, you can change every single piece of a working nas system and be fineTM. i have changed my motherboard, my cpu, my ram, my case, and psu (and even the order the hard drives were connected), and everything continued to work. changing the motherboard did cause a slight hiccup, which i want to address.

the setup (and reason for the change):

changing from a gigabyte a520i ac itx to asrock b450 fatality itx motherboard. the reason for this change is my previous network adapter was realtek, which in the documentation says is not as well supported as intel network adapters. the biggest issue i was having is that with larger transfer files, my truenas would "soft crash". basically remain powered on, but no longer visible or reachable on the network. i could physically press the power button, and it would safely power off, and then press it again to power it on like normal without any immediate alerts/errors.

the error:

upon plugging everything in, no truenas available on my network. connecting my truenas to a display said that it detected a motherboard change. you can just hit 'yes' and let it continue and it'll start the truenas bootup. hopefully it works for you, but for me, it landed on the options (1-11) with a message saying:

entering panic mode, i tried to do option 1, which was reconfigure the network adapter. i hit 'yes' and deleted the existing one, and it tried to restart the web interface, but again, same error.

doing some google-ing, i found some options, something along the lines of

• dmesg | less
• pciconf - lv
• man less

to try and figure out if their is a driver. i'm quite unfamiliar and foreign to freebsd, so i apologize if these aren't the right commands, but from here i "found out" some line of code that said

not to worry! i went down this path of worry and google-ing already, but i found online that this board is compatible. the other saving grace is that when i did option 1, i could see the network adapter that it wanted to reconfigure.

the solution:

using the official documentation here (who woulda thought), i got an idea to try re-configuring the network adapter from option 1, but using different settings. the first option i did was 'no', and that led to a few other prompts. unforunately, i don't remember what i tried exactly, as i was just trying things on a whim, but if you know your hardware is compatible, and you can see the network adapter (mine was called igb0), then it's just a matter of configuring it via option 1 in the right way, and then you may see that the web interface is available at 0.0.0.0. from there, i could connect to it and adjust my ip reservations, and everything was back on track.

alhamdulillah.