GFOviedo Posted September 22, 2022 Share Posted September 22, 2022 I have not used my unraid server for several years. I've had it in storage for a while. Today, I've decided to turn it on, check parity, and update the OS and possibly the hardware, but I cannot get it to get an IP. Attached is the log file I had to download via command line, which is something I've never done before, but I had to learn. I've also Googled this issues, but none of the things others have done have helped me. tower-diagnostics-20220922-0153.zip Quote Link to comment
GFOviedo Posted September 22, 2022 Author Share Posted September 22, 2022 I was reading a different post where they recommended to delete the network file since unraid would create a new. So, I deleted mine, but didn't backed it up. So, this is the log file from that. tower-diagnostics-20220922-0219.zip Quote Link to comment
Solution JorgeB Posted September 22, 2022 Solution Share Posted September 22, 2022 NIC problems: Sep 22 02:16:58 Tower kernel: e1000 0000:03:01.0 eth0: Detected Tx Unit Hang Sep 22 02:16:58 Tower kernel: Tx Queue <0> Sep 22 02:16:58 Tower kernel: TDH <1000001> Sep 22 02:16:58 Tower kernel: TDT <1000001> Sep 22 02:16:58 Tower kernel: next_to_use <1> Sep 22 02:16:58 Tower kernel: next_to_clean <0> Sep 22 02:16:58 Tower kernel: buffer_info[next_to_clean] Sep 22 02:16:58 Tower kernel: time_stamp <fffbd99a> Sep 22 02:16:58 Tower kernel: next_to_watch <0> Sep 22 02:16:58 Tower kernel: jiffies <fffbe940> Sep 22 02:16:58 Tower kernel: next_to_watch.status <0> Sep 22 02:17:00 Tower kernel: e1000 0000:03:01.0 eth0: Detected Tx Unit Hang Sep 22 02:17:00 Tower kernel: Tx Queue <0> Sep 22 02:17:00 Tower kernel: TDH <1000001> Sep 22 02:17:00 Tower kernel: TDT <1000001> Sep 22 02:17:00 Tower kernel: next_to_use <1> Sep 22 02:17:00 Tower kernel: next_to_clean <0> Sep 22 02:17:00 Tower kernel: buffer_info[next_to_clean] Sep 22 02:17:00 Tower kernel: time_stamp <fffbd99a> Sep 22 02:17:00 Tower kernel: next_to_watch <0> Sep 22 02:17:00 Tower kernel: jiffies <fffbf140> Sep 22 02:17:00 Tower kernel: next_to_watch.status <0> Sep 22 02:17:01 Tower dhcpcd[1478]: br0: probing for an IPv4LL address Sep 22 02:17:02 Tower kernel: e1000 0000:03:01.0 eth0: Detected Tx Unit Hang Sep 22 02:17:02 Tower kernel: Tx Queue <0> Sep 22 02:17:02 Tower kernel: TDH <1000001> Sep 22 02:17:02 Tower kernel: TDT <1000001> Sep 22 02:17:02 Tower kernel: next_to_use <1> Sep 22 02:17:02 Tower kernel: next_to_clean <0> Sep 22 02:17:02 Tower kernel: buffer_info[next_to_clean] Sep 22 02:17:02 Tower kernel: time_stamp <fffbd99a> Sep 22 02:17:02 Tower kernel: next_to_watch <0> Sep 22 02:17:02 Tower kernel: jiffies <fffbf940> Sep 22 02:17:02 Tower kernel: next_to_watch.status <0> Sep 22 02:17:04 Tower kernel: ------------[ cut here ]------------ Sep 22 02:17:04 Tower kernel: NETDEV WATCHDOG: eth0 (e1000): transmit queue 0 timed out Do you have a different one you could try with? Quote Link to comment
GFOviedo Posted September 22, 2022 Author Share Posted September 22, 2022 I’ve got the mobo NIC. I’ll try it out. I had to get this Intel NIC because it’s more reliable. Quote Link to comment
GFOviedo Posted September 22, 2022 Author Share Posted September 22, 2022 @JorgeB I've enable the LAN for my mobo, and it worked. Thank you for the help! Now, I need to order a new NIC, but I can at least access my server! 1 Quote Link to comment
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.