my ASRock Fatal1ty Professional motherboard has 2 onboard NIC's.  I'd previously run with network bonding, but due to some issues I've been having, it was suggested that I turn it off.  (honestly, it bonding probably provides me no benefit, so it's fine to disable it).

 

However, with 2 ethernet cables plugged in, I'm still having issues where some bandwidth floods my router, and kills all internet availability to all machines connected to the router.  If I disconnect the ethernet cables from the server, I get my internet back for all other machines.

 

If I just plug one ethernet cable into one NIC, unRAID initializes the other one about 1/2 the time (race condition), so I have to physically move the cable to the other NIC, or reboot, and hope the one with the cable 'wins' on the next bootup.

 

On top of all this, I don't normally boot the server very often (assuming I can fix my other issues), so when these things happen, I don't always remember these quirks at the time, and think something else has gone wrong, which often causes me to hard boot the server, causing more issues.

 

So, how do I get reliable network service, considering all the above issues?  What's the solution?

Possibly too simple of an answer, but can you disable one in BIOS? Some motherboards also have physical jumpers to enable or disable ports.

Actually, no, not too simple.  I'm not sure why I didn't think of it before posting, but I just finished rebooting the server after doing this very thing.

 

I just confirmed it booted back up, and I have access, and was just about to update this thread.

 

I guess the server had officially knocked me stupid

 

good news is that I'm hopeful this resolves my 'server' dieing' issues.  Last time it died, I tried disconnecting both ethernet cables, waited about a minute, then reconnected, and sure enough, server was just fine.

 

Something about the VM causes the network to crap itself it seems.

 

Anyway, more testing to come.

 

thanks.

I know this is of little help but with my supermicro board the has two nic's i've never experienced this issue. Unraid just bound to a nic#1 al the time.