Chriexpe

I noted that too, mine is online, so there's always the alarm of 'UPS is in Converter Mode', and when it looses connection (very frequently) it initiate shutdown, if I 'sudo systemctl restart nut-server' where NUT server is running, my unraid will go down as well. Apr 12 14:00:15 Tower upsmon[66261]: Communications with UPS [email protected] lost Apr 12 14:00:15 Tower upsmon[66261]: UPS [[email protected]] was last known to be in an ALARM state and currently is not communicating, assuming dead. Apr 12 14:00:15 Tower upsmon[66261]: Executing automatic power-fail shutdown I tried adding ALARMCRITICAL 0 on upsmon.conf but didn't seem to do anything (after restarting nut-server).

I'm aware, but shouldn't Unraid be more "resilient" to it (like not depending on disks)? It hangs during reboot/shutdown and I have to manually reset the server (thank god I have PiKVM). Also, please take a look at diagnostics, specifically at syslog-previous as Unraid just mysteriously died some hours after the ZFS pool getting suspended, there wasn't any log or video output at all, I've read even some error with my SAS card too. Interestingly enough, after a fresh reboot everything works fine (note that there is a NVR recording to this pool 24/7), tho one disk (sdd) lags behind in R/W. Not only that but looking at the logs, that disk (sdd) has some more log that I couldn't comprehend right. Do you have any idea on what could be? If it's actually one disk failing I may be able to get warranty on it (all HDDs are identical, Seagate Exos 7e8 8TB). Some years ago I also got some I/O error and changing the SAS Sata cable solved it (I'm even considering getting one from Aliexpress), but even after swapping to the old cable I also got this issue on (possibly) the same HDD. tower-diagnostics-20250106-2111.zip

I have one RaidZ1 pool with 3 HDDs, recently one is supposedly dead (usually after rebooting it kinda works for some time), anyway, with this pool suspended Unraid doesn't turn off or reboot, it stops at "Unmounting local file systems:" requiring manually to shut it down. also this is the zpool status: pool: nasa state: SUSPENDED status: One or more devices are faulted in response to IO failures. action: Make sure the affected devices are connected, then run 'zpool clear'. see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-HC scan: resilvered 576M in 00:00:07 with 0 errors on Sun Jan 5 19:14:50 2025 config: NAME STATE READ WRITE CKSUM nasa DEGRADED 0 0 0 raidz1-0 DEGRADED 7 150 0 sde1 REMOVED 0 0 0 sdd1 ONLINE 12 182 0 sdb1 ONLINE 8 0 0 errors: 70 data errors, use '-v' for a list

Thanks for helping! Just for closure, updating to Unraid 7.0.0 Beta solved it, so it might been some bug from an older ZFS/Kernel.

My bad, I thought it enabled it too, but now I remember I also have Intel Graphics SR-IOV plugin that replaces it with i915 driver. So only Intel Arc is currently supported? I thought SVT-AV1 encoding worked on 12th+ Intel CPUs too, but can't find anything online about it. (or is it like 5x slower than HW HEVC encoding?) I did use HW QSV h.265 to transcode all my media on Immich, but Firefox can't play it (at least on Linux), with AV1 it should work fine.

Does Intel GPU TOP plugin supports SVT-AV1 encoding? My CPU is i5 12500. I get this error when transcoding to AV1 on Immich: (with QSV is the same) An error occurred while configuring transcoding options: UnsupportedMediaTypeException: VAAPI acceleration does not support codec 'AV1'. Supported codecs: h264,hevc,vp9

Thanks, I did try 6.12.10 and also going back to 6.12.8 and the error was still "the same", where it would output those kernel errors, and containers crash (but not my HAOS VM), the GUI kinda works but ignores any attempt of rebooting/shutdown. Either way, there is some things that I don't comprehend like why only some cores are at 100% even if top reports VM and python (I didn't install it) using 9%. You did mention possible ZFS crash, but I can still access both shares through SMB and Dynamix File Manager plugin. In case you need to take another look, here is my diagnostics file: tower-diagnostics-20240419-1151.zip And memtest went fine (but now that I'm looking at it, wait is the memory timing at 76?)

Yeah but this problem always comes back after some time, and randomly some containers break and I can't even restart it due to "server error". But what about these kernel error.txt? What are the odds of it being related to my motherboard?

Doesn't work

This started right after downloading and installing this update, where I was asked to reboot the server to complete the install but no matter what I tried, it just ignored both commands from UI and console. Curiously after trying to reboot/shutdown this happens with CPU, and all dockers and VM keeps working fine. This is the diagnostics file: tower-diagnostics-20240328-2011.zip

How do you guys handle Databases containers? I've set it to do backups of everything once a day but I have a feeling that somewhat it's breaking some containers (in a sense of stopping/starting it all the time).

This is odd, I created the dataset "users" and later "user_files" through UI (just like all others), they're recognized by zfs but when I try copying anything to them they don't show up... And if I manually add the folder name after /nasa/ DFM gives an "invalid target" error. I already tried creating these datasets with commands, restarted the server, updated to stable 6.12 and yet this bug persists.