Crashes about once every 1-2 weeks, any suggestions

[mikesp18]

orcrist-diagnostics-20220911-1049.zipsyslog-192.168.86.113.log.7z

I get a crash about once every 1-2 weeks.  It's a little frustrating. When it happens, I lose the WebGui, and I cannot SSH into the server. I cannot see any of the shares anymore. But the power is still on.  Can you kind and helpful souls please offer me any suggestions?

[trurl]

What do you get from command line with this?

df -h /

 

[JorgeB]

If you don't use the iGPU block it from loading the driver, it could be this issue:

 

 

[mikesp18]

21 hours ago, trurl said:

What do you get from command line with this?

df -h /

 

root@Orcrist:~# df -h /
Filesystem      Size  Used Avail Use% Mounted on
rootfs           32G  909M   31G   3% /

 

[mikesp18]

8 hours ago, JorgeB said:

If you don't use the iGPU block it from loading the driver, it could be this issue:

 

 

Thank you for the reply. You have been very helpful to me on many occasions, and I wanted to make sure to express my appreciation.  With regard to the "iGPU block it from loading", you could explain a little futher.  I see 2 comments in that linked thread.

commenting out the "# modprobe i915" line go file

recreated i915.conf with the 'touch' method
From the terminal type 'touch /boot/config/modprobe.d/i915.conf'

I then see many more comments about blacklisting the i915

“blacklist i915” should be the content of that file 

I will admit I find that thread confusing.  I think you referenced that thread for me once before, and I'll admit (shamefully) that I gave up reading it.  It is many pages and gets confusing and little contradictory.  I wish there was a summary on the first page.

 

Could you confirm for me that the GO file should have no reference to the i915 (or # commented out) and that the i915.conf should be created with the content "blacklist i915"?  Also, the thread makes numerous reference to the intel-gpu-top, but I don't believe this is something I ever installed.

 

Now just have to wait 11 more hours to complete the 33 hour parity check, then I can reset

Edited September 12, 2022 by mikesp18

[JorgeB]

Just type in the console:

echo "blacklist i915" > /boot/config/modprobe.d/i915.conf

 

and reboot

[mikesp18]

10 minutes ago, JorgeB said:

Just type in the console:

echo "blacklist i915" > /boot/config/modprobe.d/i915.conf

 

and reboot

Thank you so much.  I did notice that my GO file has this line, I'm not sure if I added myself some time ago.  Should I remove this?

modprobe i915

 

[JorgeB]

Yep.

[mikesp18]

Just now, JorgeB said:

Yep.

You rock for all the quick replies and attention.  I appreciate it.  I made it through all 9 pages of that thread, and it was difficult to follow.