SlinkyBiest

Sorry for the delay, I was waiting for it to fail again. I started my machine in safe mode (plugins disabled) and it ran fine for a few days. Then, restarted it normally and uninstalled all plugins and it's been running with no issues for about a week; even after reinstalling a Community Applications and User Scripts since those are "crucial" to my current setup. I may start slowly reinstalling plugins once the new HDDs have been installed, but so far, it seems one of the plugins I had installed was the culprit. It would still be nice to have a better error code (or a list of possible meanings somewhere) so users can more easily diagnose their systems on their own. It almost seems like 135 is just a catch-all - not knowing whether it's at least a hardware or software issue without digging heavily into logs is fairly problematic.

Any updates on this error? I've been dealing with it for the past few days as well; server will run for about 24 hours fine, then no WebGUI, CLI/SSH, or access to Docker containers till a hard reboot and I remove/reinsert the USB boot drive. I've tried setting up syslog to write to the array and mirror to flash, but nothing meaningful writes since, once Exit Status 135 occurs, the array and flash drive are no longer accessible (checking through terminal on the actual device). I don't have another server setup, so writing externally isn't really an option. For me, this seems to have started when I attached 2 external drives through USB and set them up as a new pool (my array is nearly full, I don't have room for more internal drives, and don't want to include USB drives in the main array for obvious reasons). I want to expand my array with larger drives (already purchased, just need testing), but I'm afraid this will happen during the resilvering process and that'll be yet another issue. ran memtest overnight (~9.5 hours); 12 passes; 0 errors; I'm fairly certain this is not a memory issue here) uninstalled & reinstalled plugins docker is set to use ipvlan So, I guess the main question is: what does this exit status actually mean? Once we have that, we should have a better idea of how to fix it.