Anubclaw

attached diagnostics zip dellnas-diagnostics-20221128-1858.zip

Dear Community, I think I am not alone with this - I noticed issues when opening PDF files (and other files too) if they contain äöü or that have spaces in the names inside or if they are longer. It helps most of the time if I rename the files to shorter names and avoid spaces from the unraid command line. Outside the command line I will receive that the file does not exist for the Mac. It is no issue on the Windows side I think. It's a bit odd - I am running the latest MacOS Ventura and the user is accessed the same. I thought at first the files were damaged in some way but the same files downloaded and stored on the share display ok on the windows side. It's just one of the odd things that I noticed and I wonder if other unraid users experience also inaccessible files. Same files have issues when trying to access from iOS via the files App.

I have followed your guide and excluded the system share from the integrity plugin as well as made it cache mostly it seems to work. I also updated to 6.11 today on both of the systems now. Thank you for helping-

I have set the system share now to cache preferred. stopped and started the docker and VM Engine (docker was unable to start until I stopped and started the array) then removed the Plex binhex docker and reinstalled that one. if there a way to exclude the docker-img from the file integrity plugin ?

Strange is also that it seemed to happen to all updated docker images and it seems always after an update.

Yes all containers worked flawless before , it started happening a few days ago . I thought this was strange and deleted the docker apps and reinstalled one (binhex Plex) which did also work but a day ago or so there was an update and as I checked today docker said again that the images are orphaned. I thought it was better to post this as it seems kind of an odd issue. I have a second unraid server with almost identical hardware that does not show this behavior

Thank you for the unrelated answer, the issue is not affecting a specific container but all docker containers. I install the apps/docker apps, they run usually but once there is an update it seems to become orphaned after a day Or two the docker stops and shows the message that the image is orphaned and is stopped.

added diagnostics z1nas-diagnostics-20220917-0917.zip

Dear Support, on my z1nas unraid server I get the following display: Version: 6.10.3 Betriebszeit 2 Tage 21 Stunden 39 Minuten • Unraid OS Basic Media server•z1nas Anubclaw Docker Container ANWENDUNGVERSIONNETZWERKPORT ZUORDNUNGEN (APP ZU HOST)VOLUMENZUORDNUNGEN (APP ZU HOST)PROZESSOR/SPEICHER AUSLASTUNGAUTOSTARTBETRIEBSZEIT (verwaistes Abbild) GestopptAbbild ID: 8daed943dbb5 binhex/arch-plexpass:latestErstellt 1 day ago I can deinstall the container but it seems if there is an update then 1 day later it returns to the same display with stopped and old image .... update docker container does not help. I will add diagnostic data as well

I did rebuild the setup on the USB Stick so far this worked , just wonder why the GUI Access got lost before

it tries to jump to https://0a2ffae1a8ec35265c5f42f09a7e3cff92e2ff13.unraid.net/ instead of the local address

Dear Support, I have the issue that one of my unraid servers webgut is no longer reachable. I can restart it and it will come up again but the webgui just comes back with a ngnx Error 404 or jumps to the unraid.net Webadress and shows unavailable . The my servers plugin shows the server online and even the backup is current. what would be the best steps to recover the access to the webgui ? Thank you for your help in advance

Thank you I disabled audio for now - will have a look if the other solution yields a result later . Thank you

I have an issue creating VMs on my Unraid Server - I have added 32GB RAM to my DELL T30 but I get the following error when creating a VM: internal error: qemu unexpectedly closed the monitor: qxl_send_events: spice-server bug: guest stopped, ignoring 2022-06-11T07:43:52.752062Z qemu-system-x86_64: -device vfio-pci,host=0000:00:1f.3,id=hostdev0,bus=pci.0,addr=0x6: vfio 0000:00:1f.3: group 7 is not viable Please ensure all devices within the iommu_group are bound to their vfio bus driver. I am pretty new to VMs on Unraid but it looked straight forward. Can you give me some advice ? or point me in the right direction ? Thank you in advance, Best regards, Harald dellnas-diagnostics-20220611-0947.zip