Hello there!

I've noticed a slow transference speed, and not being sure about what can it be, i restarted my Unraid machine. After the reboot, i wasn't able to make the server get an IP.

This is not the first time that it happens. I replaced my flashdrive for one with a better quality, but it seems that it wasn't doing well. I tried to reboot, not connecting to the second router but directly to the main one, putting an HDMI to see the output and .. nothing. No HDMI output, no IP, not even lights in the ethernet port.

 

I removed the assigned IP for the server, and it booted, but when i went to my PC to see how was everything i didn't have an IP anymore. I tried to restore a month-old backup, and same problem. 

 

I tried the USB in my main PC and it doesn't boot. New USB, same backup copied... it works!
So i thought: The USB was not a good one, let's replace it.

I moved the new USB to the Unraid machine and no boot. Same for the old one. After a few reboots, i noticed that my MSI MoBo has turned on the "No OS" light, so i keep trying until i don't see the light anymore, and it booted again, but when i moved the server back in place, no ip again

 

I opened the server, removed and put the RAM again and, after a few tries, it booted again, and now it has been 15 minutes and i still have my IP

 

What could go wrong? I'm gonna order one of the USB reccomeneded in the SpaceInvaderOne video, because i used a new one that i had laying around, but i'm not sure if that is the issue (And it seems that i can't move my key anymore, should i ask support?)

 

I'm not sure about how to debug this, i will need to open the case again to add more fans now that i've found a splitter for the old connector, but any thoughts or ideas will be appreciated. Thanks!

I've ran the diagnostics file just in case, but i'm guessing that the old boots won't be there

littlekraken-diagnostics-20240924-1737.zip

There are some difficulties getting an IP, but apparently it got one in the end after a few tries:

 

Sep 24 17:28:33 [1086]: br0: probing address 192.168.1.3/24
Sep 24 17:28:36 [1086]: br0: carrier lost
Sep 24 17:28:44 [1086]: br0: carrier acquired
Sep 24 17:28:45 [1086]: br0: soliciting a DHCP lease
Sep 24 17:28:50 [1086]: br0: probing for an IPv4LL address
Sep 24 17:28:51 [1086]: br0: carrier lost
Sep 24 17:28:54 [1086]: br0: carrier acquired
Sep 24 17:28:56 [1086]: br0: soliciting a DHCP lease
Sep 24 17:29:01 [1086]: br0: carrier lost
Sep 24 17:29:02 [1086]: br0: carrier acquired
Sep 24 17:29:02 [1086]: br0: soliciting a DHCP lease
Sep 24 17:29:07 [1086]: br0: offered 192.168.1.3 from 192.168.1.1
Sep 24 17:29:07 [1086]: br0: probing address 192.168.1.3/24
Sep 24 17:29:11 [1086]: br0: leased 192.168.1.3 for 86400 seconds
Sep 24 17:29:11 [1086]: br0: adding route to 192.168.1.0/24
Sep 24 17:29:11 [1086]: br0: adding default route via 192.168.1.1

 

 

Try different NIC, cable, or router.

Sorry, i was swamped with the job and i totally forgot about this. Router shouldn't be the issue (More devices there), changing port is the same issue and the same cable with my phone and an type-c Ethernet adapter works, so it's weird. Today i rebooted after a week to switch one bad fan, and same issue. I'll switch cables just in case

Now it worked on the 4th reboot, after plugging and unplugging the Ethernet cable, but that was probably just a coincidence. Router (OpenWRT) says 100mb until it really boots, and then it says 1GB. Parity check started, so i'm guessing that it had SO booted but no IP. Could it be something about the reserved IP for the device?

 

12 minutes ago, Kivaj said:

after plugging and unplugging the Ethernet cable, but that was probably just a coincidence.

In storytelling, this is called foreshadowing.

It happened again. i buy some more fans to lower the temperature and i shutdown the server (I was missing a cable, so i will do it again when i have it).

Last time i needed to restore a backup, and i modified the network from fixed ip to DHCP and did the IP reservation at router level (like before), but not fixing the IP in Unraid, so i can discard if its the server, the network or what. The USB now is one of the reccomended ones, and it's new

 

littlekraken-diagnostics-20241016-1257.zipAny idea?

Im trying to check the syslog.txt, but im not sure about what i should be looking for

Looks like it got an IP:

 

Oct 16 12:54:08 [1087]: br0: leased 192.168.1.3 for 86400 seconds

 

Any reason there are 4 NICs in a bond? I only see one NIC.

Yeah, i only get the diagnostic file when it boots, not sure if you can get it otherwise. It only should be one NIC yes, how can i check that? @JorgeB

Inside the Ethernet adapter is where only i can see 4 items related to networks, not sure if you mean that:

 

Edit: Yup, for some reason i have bound active in my NIC, a nonsense because i only have one physical controller, and when i plug another one is an USB for debugging. Removed. Could this be related?

I was just supposed to have some virtual networks for the *ARR services

Edited October 17, 20241 yr by Kivaj

The bond should not be the reason for the issues, but you can delete/rename /boot/config/network,cfg to go back to defaults.

 

 

I did, probably is not what it broke it, but its also not helping. Thanks!
Still clueless, but every little thing is a thing that could be causing problems and its not there anymore

So it's still getting an IP or not? It was in the second diags as mentioned.

I mean, now it's working, yes, but its never after the first reboot, but after a few, that's what i'm trying to fix

Post the diags when it doesn't work.

7 hours ago, Kivaj said:

I mean, now it's working, yes, but its never after the first reboot, but after a few, that's what i'm trying to fix

That sounds like some sort of address assignment problem.  Have a look at DHCP settings and also verify all other devices on network have unique IP addresses.