EricVin

Issue happened again this morning. Output of df -h / is: Filesystem Size Used Avail Use% Mounted on rootfs 16G 2.1G 14G 14% / And I've attached another log. unraid_logs_5.txt

Same issue this morning. Output of dh -h / again is: Filesystem Size Used Avail Use% Mounted on rootfs 16G 2.1G 14G 14% / And I attatched another log. @trurl any idea what could be the problem? unraid_logs_4.txt

Happened again this morning: the output of `df -h /` is: Filesystem Size Used Avail Use% Mounted on rootfs 16G 2.1G 14G 14% / And I've attached another log from the crash. unraid_logs_3.txt

Ah, understood! Here's diagnostics after reboot. Thanks! walle-diagnostics-20230213-0725.zip

Unfortunately when the system crashes the diagnostics tool lags forever (also on an nvidia-smi command, like the pagefault), so the only way I could get the syslogs was through the terminal. Please let me know if you have an idea for how to get around this. I'll try that command next time the issue occurs!

Same error this morning, attaching new syslogs. It seems to be consistently happening after the CA Backup/Restore schedule, and that plugin is up to do date. unraid_logs_2.txt

Can do but it reproduces pretty randomly (e.g. sometimes twice in a day, sometimes a month passes), so I'm not really sure if there's a way to to tell if it's linked to plugins long term or just not appearing. Any advice?

Wanted to bump this to see if anyone could take a look at it.

I've been somewhat consistently getting a 500 error on my server, similar to the one in I can restart the webgui using the `/etc/rc.d/rc.php-fpm restart` command, but dockers and vms aren't visible and I can't gracefully restart. I'm also unable to export logs from the WebGUI (stalling forever), but I was able to manually grab the syslog which is attached. It looks like an unhandled pagefault occurred, but I'm not sure why. Any help would be appreciated! unraid_logs.txt

Sounds good, thanks for your help!

All the extended SMART checks passed and so I'm rebuilding that drive from parity. I've also attached the new diagnostics. From the other posts on this Ryzen SATA controller issue it looks like there's not much I can do to solve it, so I guess I'll just hope it doesn't happen again unless there's any other things I can try. walle-diagnostics-20221212-1454.zip

It looks like drives 1,2, and 6 had issues with only 1 being disabled. All three were not responding to SMART checks or showing temperature data. Upon reboot it looks like 2 and 6 are normal again, with all drives showing temp data and allowing SMART checks. I'm going to run an extended SMART check on all 3 devices that were behaving strangely. If drive 1 passes, is it safe to re-enable it?

I'm running 6.11.5 and I woke up to a disabled drive this morning. I stopped the array and downloaded the logs from the server, which I've attached. From what I can gather I stopped being able to read the drive, and so Unraid disabled it, is that correct? It looks like smart tests are failing on the drive as well, saying that an essential operation was unable to complete. Any advice would be really appreciated! walle-diagnostics-20221212-0722.zip