Hello, I recently replaced my flash drive after the prior USB failed. I created a new USB drive from a flash backup and got it all up and running. Since then I can only seem to keep the server online for several hours before it crashes and has to be reset - no way to access without forcefully shutting down and rebooting. I have attached the syslog here. It was enormous.. fixed that now, but I copied and pasted the most recent parts from the last two crashes into textedit and attached that instead of the 500mb .log file. 

 

Any ideas why this may be happening? Almost looks like a failure mounting a disk or a CPU issue? But I am fairly new to this.. any help is greatly appreciated. Many thanks in advance. 

 

Edit - I noticed one of my cache drives is completely MIA.. looks like it's failed. I had two separate cache pools - one for standard cache and one for dynamic storage... really for plex downloads only. That one is gone. 

 

Jim 

syslog-atlantis.rtf

Edited December 5, 20232 yr by JimmyL
new information

Attach Diagnostics to your NEXT post in this thread. 

See diagnostics attached, many thanks. 

atlantis-diagnostics-20231205-1853.zip

Quick update - 

 

The SSD that I was using as cache pool 2 (plex downloads, and the 'quick swap' network share we use) did in fact fail. I pulled it and tried it in another machine and its completely dead - no life at all. I replaced it, formatted it, added to the array. Seems to work. 

 

I also found that the config file on one of my shares was corrupt, I shut down, pulled the USB and deleted the corrupt config file, and restarted the server. I was able to rebuild the config for the share, and the error is gone. Everything seems to be normal for now, I will leave it running overnight and see if it crashes again. 

 

Next move I think will be to boot into safe mode and leave it be for a day and see what happens. 

Here are the most current syslog and diagnostics files after the fixes I tried. atlantis-diagnostics-20231205-2056.zipsyslog dec5.rtf

There are Macvlan related call traces, and these will usually end up crashing the server, switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)), then reboot.

Hi JorgeB, I switched to ipvlan this morning, unfortunately it's already crashed again. Wondering if docker image is corrupt maybe? Here are the current syslog and diagnostics files from just now after rebooting again. atlantis-diagnostics-20231206-1456.zipsyslog-10.0.0.189-3.log

 

Thank you for your help 

Unfortunately there's nothing else relevant logged, this usually points to a hardware issue, one thing you can try is to boot the server in safe mode with all docker/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.

Well, it appears to have run overnight without issue now, and I have been able to complete a parity check - wasn't able to run that long without crashing before. Seems healthy today.. will see if it lasts. If it crashes again I will run it in safe mode for a while and see what happens. Thank you for your help. 

Seems to still be going strong. Thank you for your help.