letrain 2 Posted March 30 Share Posted March 30 i recently moved so server has been off for 14 days. for some reason unraid is showing eth0 and eth1 and i only have one eth port. i've deleted network.cfg a couple of times, and it works after one reboot, then fails on the next. and gives me two eth again. i don't have internet access unless i enable bonding..which doesn't make since as i have only one eth. Quote Link to post
John_M 375 Posted March 30 Share Posted March 30 Post your diagnostics. You can have a bond with only one member. That's how Unraid is set up by default. Quote Link to post
Hoopster 743 Posted March 30 Share Posted March 30 5 minutes ago, letrain said: i recently moved so server has been off for 14 days. for some reason unraid is showing eth0 and eth1 and i only have one eth port. i've deleted network.cfg a couple of times, and it works after one reboot, then fails on the next. and gives me two eth again. i don't have internet access unless i enable bonding..which doesn't make since as i have only one eth. You should attach your diagnostics to a new post (Tools --> Diagnostics from the GUI). Quote Link to post
letrain 2 Posted March 30 Author Share Posted March 30 (edited) i also had an issue with some dockers saying they don't exist. Here is diagnotics. tower-diagnostics-20210330-0810.zip edit : just rebooted and its showing one eth again...i'm not sure whats going on. i didn't do anything. Edited March 30 by letrain Quote Link to post
letrain 2 Posted March 30 Author Share Posted March 30 and after that reboot its back again... eth0 and eth1... Quote Link to post
John_M 375 Posted March 30 Share Posted March 30 According to your diagnostics you have five Ethernet ports installed. Unraid is only using one of them, eth1, the rest are stubbed and presumably being used by your pfsense VM. Your problem is that Unraid expects to use eth0 for its GUI. You need to rearrange your NICs so that the 2.5gb NIC is eth0, not eth1. You can do that on the Settings -> Network Settings page of the GUI in the Interface Rules section. Quote Link to post
John_M 375 Posted March 30 Share Posted March 30 You also have read errors on your cache: Mar 30 07:57:21 Tower kernel: BTRFS info (device sdd1): bdev /dev/sdd1 errs: wr 0, rd 26, flush 0, corrupt 0, gen 0 which may explain your Docker problem. See this post for how to deal with it, how to reset the counters and how to monitor it in the future: Quote Link to post
letrain 2 Posted March 30 Author Share Posted March 30 (edited) 3 hours ago, John_M said: According to your diagnostics you have five Ethernet ports installed. Unraid is only using one of them, eth1, the rest are stubbed and presumably being used by your pfsense VM. Your problem is that Unraid expects to use eth0 for its GUI. You need to rearrange your NICs so that the 2.5gb NIC is eth0, not eth1. You can do that on the Settings -> Network Settings page of the GUI in the Interface Rules section. Rules section? i'm not seeing that. just both interfaces, and eth0 has no mac address...just a yes / no for mac address. if i change it to yes, it offers bonding modes...eth1 is the correct mac address for the 2.6gbps ethernet... i've had a server with two nics before i could switch them around by mac address. i still don't understand why i have eth0 and eth1... Quote Edited March 30 by letrain Quote Link to post
John_M 375 Posted March 30 Share Posted March 30 5 minutes ago, letrain said: Rules section? i'm not seeing that. It's immediately above the Routing Table section: but since you're not seeing it you'll have to free up those other NICs temporarily so that Unraid can see them, then that section should appear. So go to Tools -> System Devices and un-stub them (you'll need to stop the VM that uses them first, of course). Then re-boot, navigate to the Settings -> Network Settings page again and reassign eth0 to the appropriate MAC address. Then you can go back and re-stub them, re-boot and start the VM. Quote Link to post
letrain 2 Posted March 30 Author Share Posted March 30 2 minutes ago, John_M said: It's immediately above the Routing Table section: but since you're not seeing it you'll have to free up those other NICs temporarily so that Unraid can see them, then that section should appear. So go to Tools -> System Devices and un-stub them (you'll need to stop the VM that uses them first, of course). Then re-boot, navigate to the Settings -> Network Settings page again and reassign eth0 to the appropriate MAC address. Then you can go back and re-stub them, re-boot and start the VM. that sounds good. i will try that and report back. Quote Link to post
10 posts in this topic Last Reply
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.