Lost network access shortly after boot

Do you still think it is worth checking out?

 

At first, I would have said probably not, especially if you meant that you did not have the wireless dongle plugged in.  But when I look at the chronology of events recorded in the syslogs, it almost looks like a possible correlation, some rather tight windows and almost too coincidental timings there.

 

In all of the syslogs and syslog excerpts, one of the very last statements recorded is the final avahi statement immediately after all drives are mounted and it announces the array is started, the same whether in safe mode or in normal mode with Plex starting.  Crashes appear to happen extremely soon after that.  In the previous syslog tail, it's the very last line logged.  In this syslog piece, it happens at 17:03:34, then 3 seconds later the network links up, then about 17 seconds later the Logitech driver is loaded.  That's about 20 seconds for it to crash, you recognize it's crashing, then quickly connect or enable the wireless device (you are fast!).  Does that sound correct to you?  Then there are about 11 minutes where I assume you were trying to diagnose what worked and what didn't, then the keyboard is disconnected.  Just 3 seconds later, we have a kernel Oops, but the system was still somewhat operational for almost a minute, then the keyboard is reconnected and the syslog terminates for good, I assume with a hard crash.  Sound right?

 

I cannot assume much of anything here.  I cannot conclude it's the Logitech's fault, or it's not its fault, but it looks like it *may* be related, or it is forcing the issue somehow.

Ah right. So in the last syslog the process was the following:

• Turn on server and select safe mode.
  
• (Assuming logitech driver loads up after the server starts)
  
• I spent a short amount of time checking plex wasn't loaded, ran 'top' etc, then left it alone. At this point it had not crashed.
  
• 11 mins of it just sitting there not crashed but not doing anything either, might have accessed a drive on the server remotely (can't remember)
  
• I disconnected the keyboard and shortly afterwards the crash occurred
  
• Reconnect the keyboard to see if it is responding to input - it does. Try to save a copy of the syslog with the error messages it spat to the screen. During this it completely died and I shut it down
  

Hope that makes sense.

UPDATE: after 1 hour off, and with a different ram stick, it has now been stable for ~20 mins. I shall give it the rest of the evening to see if it is stable, then turn it off overnight to see if it crashes in the morning or not. Hopefully a new RAM stick will be the solution!