Drives Spin-Down, Unable to Connect [Unraid 7 beta 2]

[stry8993]

So this has been happening since I moved to Unraid 7 beta, and switched to ZFS. I thought by switching the Docker back to a cache drive, as that was having problems in the notes, it would fix it... but... it hasn't.

 

I haven't been able to catch it when it had just happened recently enough to get a good diagnostics zip from it, but I finally have it! Any and all support would be appreciated, because I have no idea whats going on, nor how to interpret the diagnostics.

zima-diagnostics-20240802-1149.zip

[itimpi]

The syslog in the diagnostics is the RAM copy and only shows what happened since the reboot.   It could be worth enabling the syslog server to get a log that survives a reboot so we can see what happened prior to the reboot. The mirror to flash option is the easiest to set up, but if you are worried about excessive wear on the flash drive you can put your server’s address into the Remote Server field.

[stry8993]

3 hours ago, itimpi said:

The syslog in the diagnostics is the RAM copy and only shows what happened since the reboot.   It could be worth enabling the syslog server to get a log that survives a reboot so we can see what happened prior to the reboot. The mirror to flash option is the easiest to set up, but if you are worried about excessive wear on the flash drive you can put your server’s address into the Remote Server field.

Okay, awesome, I've got that done. I'll get back to you fine folks when it crashes again. Its intermittent, but the way that it crashes is consistent.

[stry8993]

Just dropping this here while I remember:

I ran the unraid live memory test, and everything came out fine. But, still, on a hunch, thought I'd run Memtest, and everything turned out well/passed.

 

I'm still waiting for the server to S.T.B., and I've got the Syslog server set; I'll post as soon as I have the results from that.

DIMMResults-20240803-072520.bmp DIMMResults-20240803-072529.bmp MemTest86-20240803-010227.log MemTest86-Report-20240803-010911.html

[stry8993]

Welp, it happened, finally. See attach @itimpi

 

wasn't sure which one was necessary, so, attached the syslog and syslog-previous.

syslog syslog-previous

[JorgeB]

Unfortunately there's nothing relevant logged, this can be a hardware issue, one thing you can try is to boot the server in safe mode with all docker containers/VMs disabled, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one.

[stry8993]

10 hours ago, JorgeB said:

Unfortunately there's nothing relevant logged, this can be a hardware issue, one thing you can try is to boot the server in safe mode with all docker containers/VMs disabled, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one.

Hmm... makes me wonder if its the Realtek 2.5Gbps USB NIC I'm using... it always seems to choke when theres a lot hitting the 'net'. Like I'll lose the ability to connect, but the hard drives will still show activity.

[stry8993]

Yeah, there might be something up with the Realtek r8152 NIC Driver on Unraid 7 beta 2's kernel. I suppose I'll wait and see. Thank you again both of you, for getting back to me on this. Its very much appreciated.