syslog-previous.txtmilkyway-diagnostics-20240629-1931.zip

 

I recently had another unresponsive webGUI that I couldn't get to.  I had to do a hard reboot.  I do have the syslog mirroring to the flash drive.  I have attached what I believe is the last log before the unclean shutdown, as well and a diagnostics after reboot.

 

Just wondering if someone can help me look through these and decipher what could be the problem.

 

Thank you!

Rhuarc

The last thing in the syslog-previous file appears to be a crash

Jun 29 16:53:25 MILKYWAY kernel: general protection fault, probably for non-canonical address 0x98e2664600152ec0: 0000 [#1] PREEMPT SMP NOPTI
Jun 29 16:53:25 MILKYWAY kernel: CPU: 14 PID: 9047 Comm: update_3 Tainted: P        W  O       6.1.79-Unraid #1

Have you done a memtest recently?

 

FYI:  If using the "mirror to flash" option then the syslog server file is automatically included in the diagnostics so then not necessary to provide it separately.

I have not done a memtest recently.  I also just had another crash and had to hard reboot.

 

I have attached the logs from this one as well.  If this one contains the same fault as shown previously would this point for sure towards a memory issue?  

 

Is there a best practice way of running unraid with memtest?

 

Thanks for all the help!

 

milkyway-diagnostics-20240630-1118.zip

14 hours ago, Rhuarc said:

Is there a best practice way of running unraid with memtest?

It's an option in the boot menu

So I ran a memtest for several hours and got 0 errors after 5 or so full tests. I am still getting occasional freezes. I managed to catch this screen while the server was unresponsive. I ahve no idea what this means or what it was doing. Any ideas? 

 

 

 

Would it be possible that my flash drive is going out at this is causing it? I purchased a new flash drive just for unraid thay is a tiny one barely bigger than the port. 

 

This is the drive I purchased. 

SanDisk 32GB USB Flash Drive (SDCZ430-032G-A46) https://a.co/d/0e2FTsEe

 

I will pull another diagnostics as soon as i can that will hopefully have info on the crash I had last night. 

 

Thanks again for all of the help! 

 

Edit: Added latest diagnostics. 

milkyway-diagnostics-20240702-0754.zip

Edited July 2, 20242 yr by Rhuarc
Added latest diagnostics

There are NIC related crashes logged, do you have a different NIC you could try with?

 

Also, memtest is only definitive if it finds errors, if you have multiple sticks try using the server with just one, if the same try with a different one, that will basically rule out bad RAM.

 

 

I am currently using a USB 2.5gbe nic. 

Any recommendations for a good quality replacement? 

 

I love the idea of unraid but it does feel like it is a house of cards sometimes. 🤔😅

Realtek NICs can sometimes be a pain with Linux, Intel NICs are usually more reliable, first you can also try the Realtek driver plugin, worth a shot.

In doing some research it doesn't seem like Intel has ever made a USB NIC.  I want to keep it at or over 2.5GbE, but currently have no leftover pci-e lanes on my MB as far as I am aware.

 

In looking at the logs does it seem pretty solid that the NIC is what is causing the no responsive web gui?  Also, if the web gui becomes unresponsive due to the NIC, if I have my server set to boot into the GUI on the connected Mouse, Monitor, and Keyboard that should theoretically still work, correct?

 

I really need to figure out these crashes so I can get some stability back in my server.

 

Thanks again!

25 minutes ago, Rhuarc said:

if I have my server set to boot into the GUI on the connected Mouse, Monitor, and Keyboard that should theoretically still work, correct?

Yep.

Is there any chance that these crashes are related to the KVM that I have hooked up?  

 

https://www.amazon.com/gp/product/B092Q2DVC2/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1

 

I believe it acts as a hub or something like that.  It has a video cord plugged in to the graphics card and a USB plugged in for mouse and keyboard support.

 

I don't know. may be worth trying without it.