velourfogg

Sure, not sure if they're different from the ones included in the diagnostics. Thanks for your help! syslog.zip

My unraid server has been crashing sporadically over the last few months before and after recent 7 update. I've tried to understand what's going on using the logs to no avail. Hoping someone could take a look at the diagnostics and see if anything going on that I missed. The crashes seem to be random and I won't know about them until I try and use a service and I can't access the unraid GUI or other docker apps. I've tried to ssh and tried to login using physical keyboard and monitor when this happens which doesn't help. I end up having to hard reset. mercury-diagnostics-20250213-2202.zip

Hi all, I ended up needing to do a hard reboot do to a few things not responding on my server, after this one of my disks shows as unmountable and my main VM disappeared. I'm really not sure what happened. Maybe a drive failed was my first thought, though I can't figure out why that would affect this VM i had running, and why the drive just shows as unmountable. I did a soft reboot that didn't help. I'm at a loss. Any suggestions would be appreciated. I attached diagnostics. mercury-diagnostics-20240720-0313.zip

oh good to know, maybe i'll look into an alternative.

Okay thanks very much. I appreciate the help. I'll keep an eye on Frigate, though it's been stable for a while. The VM runs Home Assistant.

Hi, I've been having the "Out Of Memory errors detected on your server" on and off for almost as long as I've had my server. Haven't been able to figure it out. Does get solved by restarting, but was hoping the community could help figure out the cause. As far as I can tell no services or other issues occur because of it. Thanks for your time. See attached diagnostics. mercury-diagnostics-20240714-1001.zip

no overclocking, but older ram. thanks for all your help. I'm gonna buy replacement ram.

Running memtest now at least 200 errors. I guess I need new ram?

just seeing this will do.

If a hardware problem how can I pinpoint if it's RAM or the drive? That error on the nvme is the main cache drive does that mean it is the broken bit?

Sorry if this is a duplicate I had issue posting...This is what I got for running these commands. root@Mercury:~# ls -lah /mnt/cache/system total 16K drwxrwxrwx 1 nobody users 48 Jan 7 2022 ./ drwxrwxrwx 1 nobody users 136 Jan 1 04:30 ../ drwxrwxrwx 1 nobody root 142 Apr 4 2021 custom_ovmf/ drwxrwxrwx 1 root root 0 Apr 17 2022 docker/ drwxrwxrwx 1 root root 0 Jan 7 2022 libvirt/ root@Mercury:~# ls -lah /mnt/disk1/system total 0 drwxrwxrwx 3 nobody users 21 Jan 7 2022 ./ drwxrwxrwx 17 nobody users 318 Jan 8 22:45 ../ drwxrwxrwx 2 root root 25 Jan 7 2022 libvirt/ root@Mercury:~#

Hey thanks very much for you r response and help! The mover took a while. I'm unsure why I had a docker image that large. I've done what you've said, made the docker.img setting smaller to 20GB and you can see attached diagnostics. I have not restarted VM manager or docker yet. mercury-diagnostics-20230109-0857.zip

Hi all, My docker service has crashed and won't restart. I get the following error: Warning: stream_socket_client(): unable to connect to unix:///var/run/docker.sock (Connection refused) in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 712 Couldn't create socket: [111] Connection refused Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 898 Warning: stream_socket_client(): unable to connect to unix:///var/run/docker.sock (Connection refused) in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 712 Couldn't create socket: [111] Connection refused Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 967 I have tried going into settings -> docker and enable docker no then yes to restart the service and I get the same error. I haven't changed anything recently with the server so I don't think I changed anything to cause this to happen. I appreciate any help I have attached diagnostics. mercury-diagnostics-20230108-2300.zip