This system runs just fine whilst it has the dual port ethernet nic installed, configured as a linkagg. the web GUI is accessible via the 192.168.0.140 address.
alc0 is used for wake on lan
I bought an Intel x520-SR2 which I tested working in another computer and a basic truenas 12 build.
Today I installed the x520 in this truenas box and booted. When the cli menu was presented on screen I was greeted with “the web interface could not be accessed. Check network config”
If I select option 1 it listed both fibre ports and I can assign IP addresses to them. But I still get the same message. I have tried deleting the ix interface config and re assigning IP’s.
If I put the dual port 1GiB card back in and boot everything is working and the GUI shows the fibre interfaces and the IP’s I assigned.
Anyone any idea’s why TrueNAS can bind the IP’s to the web interface?
So I was able to look more into this, this evening.
Couldn’t find any logs to help. dmesg didn’t seem to show any errors etc
Shutting down the VM and un ticking power on at startup didn’t help
Still didn’t get any IP bound to HTTP.
I now resorted to a sledge hammer approach. With the dual ethernet nic installed so I could get to the GUI, as nothing seemed to work from the cli.
I deleted the lagg and the em interfaces.
Next removed the dual nic from the system and rebooted.
I now got the 10.1.10.10 address bound to http and was able to access the GUI.
Next I shutdown, re inserted the x520 and rebooted. 10.1.10.10 was still accessible
Via the gui i could see both ix interfaces. Both showing down
configured ix0 with 192.168.0.140, tested network config, saved and rebooted
Now I could access the NAS via fibre and the 192.168.0.140 address. However, the VM wouldn’t start. This was due to the VM still being configured to use the old network interface. Changed it to use ix0 and it now started and was accessible.
Happy Days.
Given the above, if anyone could confirm.
Was the original problem due to the VM being bound to the interface which was removed and, knowing what I know now, if I had removed/changed the nic the vm was in the beginning would I not have had this problem?
I would rather not revert tonight’s changes to find out. So appreciate if anyone with more XP could confirm?
