SixFive7
Members
-
Joined
-
Last visited
-
I now have: - Included appdata path. - Global exclusion on same appdata path. - Notifications on warnings disabled. - Tar verify disabled. - Disable container shutdown enabled. This seems to work. Thank you! If you'd consider a "What do you want to backup?" list of checkboxes (vms, containers, flash, etc) for the someday maybe future, that would be beyond all expectations. Thank you for thinking through this workaround with me š
-
Hi, does anybody know of a way to disabled docker containers and appdata backup? These are already on a synced zfs volume. I would like to only backup the flash drive and the vm config data. Things I have tried already: - Just disable a specific container backup. -> I add remove containers every day. There is no "new containers do no backup" option. - Disable container shutdown. -> Works. - Leave appdata path empty. -> This is not allowed. - Add appdata path but also add the same path to the global exclusion list. -> Tar verify errors. Any help would be much appreciated!
-
I'm hoping someone can help with this ā I want to keep all my usual notifications, but I manage Docker updates outside of Unraid. The issue is, every time a new container (especially with a new name) gets added, I get spammed with emails saying an update is available. My Fix Common Problems ignore list is getting massive because I have to manually ignore each one. It's becoming unmanageable. Is there a way to: Ignore all Docker update warnings globally? Or maybe ignore containers based on a wildcard pattern in the name? Iād love a clean solution that lets me still receive useful warnings, just not for Docker updates I handle manually. Any ideas?
-
Hi, I just ran into the same issue. Had a few shares that I could not delete whatever I tried. Uninstalling ZFS Master fixed it. Once I knew this I found this thread and reinstalled ZFS Master. Enabling destructive mode does indeed fix it. Why ZFS Master is leaving my dataset "busy" I don't know. Could be I have some browser tab on some machine somewhere that has the ZFS Master gui open and that this is locking the dataset preventing share deletion?
-
Hi, I'm managing docker with Portainer (because I prefer compose files) and container updates with watchtower. This works perfectly. I do still use the Unraid interface by specifying net.unraid.docker.icon and net.unraid.docker.webui. Beautiful. If Unraid detects a possible update for a container I get a notification. All good, for all containers. Actually updating containers from Uraid for my containers made with Portainer does not work ending in a "Configuration not found." error. This is expected of course, as Unraid has no configuration for said container. However, if I update the said container with Watchtower something strange happens. The container updates, but Unraid keeps signalling that there is an update available, even though this is no longer the case. Manually running "Check updates" from Unraid does not seem to solve this. Recreating the container also does not work. Unraid just keeps saying there is an update even though there is no longer the case. The only way to solve this is by deleting /var/lib/docker/unraid-update-status.json forcing a reset. This seems to be a regression from and earlier fixed bug: https://forums.unraid.net/topic/93399-683-custom-docker-stuck-on-apply-update/. It seems Unraid is once again only checking for newly available updates and not checking for containers that are no longer out of date. Should be an easy fix for some conditional? Hope this bug report helps, Kind regards, Jori Huisman
-
Hi there, new user running Unraid on a AMD Ryzen 9 5950X. When I install FCP and let it run I always get this error: FCP notification: Machine Check Events detected on your server Output of mcelog: root@unraid:~# mcelog mcelog: ERROR: AMD Processor family 25: mcelog does not support this processor. Please use the edac_mce_amd module instead. CPU is unsupported Hourly repeats in the syslog: Aug 7 15:47:04 unraid root: Fix Common Problems: Error: Machine Check Events detected on your server Aug 7 15:47:04 unraid root: mcelog: ERROR: AMD Processor family 25: mcelog does not support this processor. Please use the edac_mce_amd module instead. Aug 7 15:47:04 unraid root: CPU is unsupported However, I'm unsure if there actually is an error as running mcelog doesn't ever yield any more details. I know the line Please use the edac_mce_amd module instead is harmless. But is FCP tripping over the line after that? Or is there really something wrong with my (otherwise very stable) hardware?
