krodami

Ok I will try that and see how it goes.

i am only running a 3 docker containers but for the past several days something has been causing all things docker containers to become unresponsive, during this time i cannot stop docker via the settings UI it says its going to stop but then on page refresh its still running and confirmed this via terminal and still seeing docker service running. i have also deleted my docker img a few times and things are still crashing. This time around I have switch to ipvlan, so we'll see if that changes anything however I would appreciate if someone could take a look at my logs and see if they can find anything interesting. I have attached 2 logs 1 is pre-restart the other is post-restart. unraid-diagnostics-20240212-2350.zip unraid-diagnostics-20240212-2306.zip

I noticed a similar issue today; after I updated to version 2024.01.11.1434, a new log file was created. However the old log was still there, maybe this is the same thing you are seeing, and maybe try the fix noted here to see if that fixes your issue.

I actually just updated to 2024.01.11.1434 after I posted this as I saw there was a pending update and I see the log has rotated now. The old log is still there; I assume it should be safe to clear out the old log now that I have updated to the latest version. > /var/log/unraid-api/stdout.log.1 I don't think a reboot is required.

i did a quick search and unraid-api logs should not exceed 10MB however mine is currently 118MB. Is this limit configured somewhere that I may have accidentally changed? How should I go about cleaning this up?

the crashing stopped so i guess its fixed for now...

Right these logs came after the crash, so maybe they are not helpful? I will enable syslog server and repost the next time it happens.

I have had the server become unresponsive two times in the past 4 days. Unclear why. unraid-diagnostics-20231201-1235.zipunraid-diagnostics-20231205-2022.zip

I just wanted to circle back to this and let you know that the second check ran and reports 0 errors upon completion, thanks. I'm still not sure what the first set of errors was all about but I guess everything should be in an ok and healthy state?

this is after running the correcting check, i will run another non-correcting check next.

unraid-diagnostics-20231108-1539.zip

It has not finished yet but i do see this on the dashboard "Sync errors corrected: 1605"

No memtest errors

No unclean shutdowns. I will run a memtest shortly and post another update

I ran my first parity check after adding 1TB of data to it, and it returned 1605 errors. I see a lot of references to gdrive and dropbox which are rclone mounts. Nov 5 23:33:41 UNRAID emhttpd: error: malloc_share_locations, 7193: Operation not supported (95): getxattr: /mnt/user/gdrive Nov 5 23:33:42 UNRAID emhttpd: error: malloc_share_locations, 7193: Operation not supported (95): getxattr: /mnt/user/dropbox Is it an issue when they are mounted to '/mnt/user/'? Should rclone mounts go under the '/mnt/remotes/' folder or somewhere else? There are also a fair amount of these types of logs Nov 5 16:39:41 UNRAID kernel: md: recovery thread: P incorrect, sector=9143051688 What should be my next steps at this point? unraid-diagnostics-20231106-0823.zip