January 25, 20206 yr Hello All. Finally upgrading an HP Proliant Micro Gen-7 from Unraid 5.4 to the latest image (starting over). Made new flash drive using Windows utility. Boots just fine, but was returning a 169 IP...not interacting with NIC? router has fixed IP set to MAC of NIC, so I set Network.cfg to the same address as a fixed value, but now getting a "not responding" error when I run ifconfig. diagnostics zip attached...is the box too old to get NIC driver support? tower-diagnostics-20110728-1734.zip
January 26, 20206 yr Community Expert Also, what version Unraid do you really have? 6.8.1 according to your diagnostics.
January 26, 20206 yr Author Very good question on the date, given I had set the date in BIOS to today at the start of this process. UPDATE: I'm thinking CMOS battery is toast, or something similar, as date setting at BIOS UI is not holding/sticking. It thinks it is July of 2011 every time I reboot. Working on that. Any thoughts on the lack of connectivity to the NIC, based on the diagnostics? Edited January 26, 20206 yr by k_allhands New Info
January 26, 20206 yr Author Date issue resolved...good there...no change in result of boot sequence in regards to NIC interaction. Not seeing any big hits in the diagnostics. Exact same config worked with older UNRAID version less than 24 hours ago. thoughts?
January 26, 20206 yr Community Expert The NIC is being detected correctly, delete/rename network.cfg (also network-rules.cfg if it exists) on the flash drive config folder, reboot, post new diags after boot (use default network settings).
January 26, 20206 yr Author re-imaged thumb drive...back to complete stock. rebooted. 169 address. Diagnostics attached. tower-diagnostics-20200126-2248.zip
January 26, 20206 yr Author So I see that the log shows ETH0 identified internally, but no address. Strange. Same cable used, same port on switch. Same machine that still gets an address with other (older) flash drive. Thoughts?
January 26, 20206 yr Community Expert The syslog shows that Unraid is getting a timeout attempting to contact a DHCP server! If your router is meant to be acting as the DHCP server then maybe you should try rebooting it?
January 26, 20206 yr Author Curious as it just assigned addresses to two test devices on the same subnet, from the same switch. Will continue to investigate.
January 27, 20206 yr Community Expert Like mentioned the problem appears to be the router not assigning an IP address, but if have one try with a different NIC just to rule that out.
January 30, 20206 yr Hi, Not sure if I should start a version 2 of this thread. I have the same IP Address/NIC Issue w/6.8.2. UnRAID will not recognize NIC. I have attached my diagnostics file if someone could kindly have a look. Thanks in advance tower-diagnostics-20200129-1336.zip
January 30, 20206 yr Community Expert 4 hours ago, SteelBrigade said: Hi, Not sure if I should start a version 2 of this thread. I have the same IP Address/NIC Issue w/6.8.2. UnRAID will not recognize NIC. I have attached my diagnostics file if someone could kindly have a look. Thanks in advance tower-diagnostics-20200129-1336.zip 53.49 kB · 0 downloads Update to v6.8.2 since there's a known issue with Intel NICs on v6.8.1, also disable bonding, if still issues please post new diags.
January 31, 20206 yr Thanks Tee-tee Jorge, Strange, I was sure I had created a bootable USB using 6.8.2. I will recheck that Thanks
Archived
This topic is now archived and is closed to further replies.