belowe

Finally got all of this solved. Seemed to stem from mavclan in docker. Switched to ipvlan and things are magically fixed.

So the thing died again today. Differently than before, this was NOT during a backup or anything. The last entry in the syslog before the failure was 'Jun 23 11:43:05 Tower emhttpd: read SMART /dev/sdb' Diagnostics from my reboot a couple of hours ago are attached. I'm sort of at a loss here. I also don't know if I should update to the newest release or should try to nail this issue down first. Thoughts? tower-diagnostics-20230623-1727.zip

Unmounting and re-mounting all cifs shares (on machines accessing my server) seems to fix the log spewing problem. Back to the original issue...? I'll keep you posted. Thanks

tower-diagnostics-20230607-2139.zip

Yep. I can still get to shares via a fstab cifs mount though. I also deleted and recreated my docker vdisk for sanity. This feels like I have multiple things at play here. Thanks for the help.

If I stop the array disable docker and disable SMB, the messages stop. As soon as I enable SMB again, they start again (even with docker stopped). Should I try another combination of actions?

Oh an apparently I'm still spewing bad SMB2 messages. Here are diagnostics after the reboot and disabling docker. tower-diagnostics-20230607-0400.zip

Hit issues again. This time after CA Backup ran. Although my docker services were up, things weren't right. Home assistant had some entities disconnected and couldn't ping google for connectivity check. All docker container versions were not available and the UI was generally slow. So I decided to try and restart docker. I disabled it in settings and suddenly the syslog started spewing SMB2 failure messages. I restarted docker and though everything started, it all looked the same with the container versions etc. SMB messages were still spewing. So I pulled diags and restarted. tower-diagnostics-20230607-0348.zip

Here ya go! Thanks tower-diagnostics-20230603-0552.zip

9.5 hours with 4 passes and no errors. Can you explain any more why that make you think memory is bad?

It's pretty new memory - only a few months old. I'm running a memtest now but I'm a few hours in already with no issues.

I keep having issues so hopefully you all can help! At this point I have pretty regular issues when doing a backup. I set it to happen in the middle of the night. I also have a user script set (for the following night) to backup my nextcloud data offsite. I can't get through 1 week without one of these two nights bringing down my server in some way. Either the whole thing freezes up and I have to hard reset it or docker refuses to start and I have to reboot the whole thing. The attached diagnostic is from an instance when docker wouldn't start. I get a message when trying to start up the docker service again via the web interface: Following another post here, I decided to delete my docker.img file. Perhaps it is corrupt. But I can't! Even trying to change the name of the file on the command line gives me an error about a read-only file system. Can anyone see in the diagnostics what's going on? A possible clue - This seemed to start happening after I set the server to be a syslog server and I used it's own address as the remote (I did this to try and debug the freezing issue). Thanks in advance! tower-diagnostics-20230602-0450.zip