Network Issue with new NIC

TrueNAS General
,
1

My existing motherboard seemingly died, so I’m trying to use some old hardware as a stop gap.

I was previously running a Xeon 1230v2 on a Supermicro X9SCM-F and am now temporarily trying to use a 4670k on an MSI Z87m Gaming board. My recollection is that the Z87m Gaming uses a Qualcomm NIC.

I was hoping to avoid having to re-install and re-setup everything and just carry over my existing install/config. TrueNAS boots up and prompts me with the IP for the web interface, but when I open a local shell (on TrueNAS) I am unable to ping the gateway. Running arp -an spits out the following:

? (192.x.x.2) at MAC_ADDR on bridgeX permanent [bridge]
? (192.x.x.1) at (incomplete) on bridgeX expired [bridge]

Is there a way to sort out this bridge issue so I can quickly get things back and running and get into the web GUI?

2

I’d delete the previous bridge & remake it with the new NIC - if I had to guess the old bridge has the no-longer present NIC as a member & is therefor failing.

3

I found this post on the old TrueNAS forums that talks about removing a bridge:

Show : remove the bridge and set an IP on the NIC

ifconfig bridge666 remove
ifconfig | grep flags
igb0: flags=8863<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
igb1: flags=8863<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
cxgb0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
ifconfig cxgb0 1.1.1.1/24


Show : remove member and set IP on the NIC

ifconfig bridge666 | grep member
        member: cxgb0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
ifconfig bridge666 deletadm cxgb0
ifconfig bridge666 1.1.1.1/24

But, is there a way to disable the existing bridge instead of deleting it entirely?

I plan to continue playing around with my old hardware to see if there’s something else going on causing it to not post that I’m able to work around. Or I might try to buy a used X9SCM-F board off ebay and hope to do a drop-in replacement. So to the extent that I can minimize “damage” to the existing configuration, the better. I unfortunately, and very stupidly, don’t have a recent copy of the configuration.

4

I mean - you could, but if you are running a local shell on TrueNAS, then why not just edit the network config from the interface option (uhh, I think option #4 when you have a display connected physically to the NAS, you can type exit to leave the shell to do that).

Otherwise, you could do something like:

ip link set br0 down (br0 or whatever your bridge name is)

ifconfig NIC_HERE 192.x.x.x netmask 255.x.x.x

That’d shut down (but not delete) the bridge, then you’d assign the relevant ip/subnet to the nic you’re using.

I’d still find it easier to delete the bridge & remake it later with GUI or the network options thing locally on NAS.

5

I ended up doing:

iconfig bridgeX remove
ifconfig alc0 192.x.x.3/24

but I still can’t reach the gateway.

6

does ifconfig support slash notation? I thought it has to be dotted decimal & invoke the netmask argument…

try

ifconfig alc0 192.x.x.x netmask 255.255.255.0

then for fun

ip link set alc0 up

7

ip link doesn’t seem to be installed.

ifconfig does support slash notation, but I get the same result using the explicit netmask 255….

I can ping the alc0 IP address (locally), but still not the gateway. The same is actually true for the bridge as well.

8

…What version of TrueNAS we working with here?

Also, again, any reason to not use this stupid thing if you have a keyboard/monitor connected to the NAS?

image
image337×174 6.25 KB

(sorry, it was option#2 not 4 like I claimed in a previous post)

9

I’m running TrueNAS 12.2.

I already tried to configure the default route to 192.x.x.1 using “Configure Default Route” option.

10

Ahhh - Core, sorry man, I was thinking we’re in full Scale mode. I’ll be honest, I’m not sure if Core even supports Qualcomm NICs… I don’t think I can be of further particular use :frowning:

11

I’ll be upgrading to TrueNAS 25 once I get everything sorted, so I’ll at least be on something not ancient. But I’m hoping I’ll be able to find a way to get this working with what I have so I can pull off some configs. I’m tempted to buy a replacement motherboard off ebay, but I’m reluctant since I don’t know for certain where the issue lies – I’m only guessing the MB is the issue since there is no post and no error beeps regardless of memory config.

12

It’s very likely that you have to redo the very thing you are doing now when you upgrade because the interface names are different in SCALE vs CORE.

13

I’m fine with redoing everything eventually. I really would just like to get this working as a temporary solution so I can 1) pull off some config files and 2) have access in the interim.

14

Is that the board that doesn’t POST or beep?

To me, no beeps or POST suggests a PSU-issue, a damaged motherboard or possibly an issue with the monitor/cable.

Double-check jumper JPG1 for the VGA setting and JSPK for the speaker setting. Verify that they are set as you would expect according to the manual.

It would also be of interest to know if any LEDs on the board light up when power is applied.

15

Can’t help with the existing Core boot file - but you could make a temporary boot drive (even a boot usb for short term is fine) of Scare & see if Scale works with your specific NIC. If it does, beauty - set the IP, make a quick & dirty SMB share & have access to your files.

…This does nothing to get you back the original config files though, but is a quick & dirty to get your NAS working in the short term?

16

The BIOS doesn’t come up and there are also no beeps. The cpu fan spins up and will stay on.

I tried a different PSU and that had the same result. I also swapped the z87/4670k into my server chassis and it boots up (so PSU is fine) and monitor is fine. Technically I did have to use a DVI to HDMI cable to connect to the new motherboard compared to a VGA cable with the X9SCM-F, but that seems wildly unlikely to be the issue since that would mean both the cable (that didn’t move and wasn’t touched) failed AND the server became unreachable over the network simultaneously.

IPMI heartbeat LED flashes and power standby LED is on. I’ll go double check the jumpers, but again, the server hasn’t been opened in years.

17

Okay, so in theory you can connect to the IPMI maybe get more information.
IPMI on those old boards was often a pain though, requiring Java (IPMIView specifically).

Hopefully the IPMI happens to be set to use DHCP to grab an IP, if not things get a bit more complicated.

18

More complicated further – I stopped using IPMI a couple years back since it seemed to have stopped working at some point.

19

I always give fixing things a genuine attempt, but with everything you’ve told I will at this point concede that replacing that board is likely the best use of your time.

Maybe you can find a used Supermicro X10 or ideally X11 board on Ebay or equivalent site.

20

I ordered an X9SCM-F earlier for $35. That way I don’t also have to replace the CPU and/or RAM. So hopefully that will solve the issue.

1 Like