unr41dus3r

Would it be possible to move the license from an single USB to the Internal Boot Devices (which are 2 USB for me) or one of the USB devices in the new USB Pool?

One thing i want to mention and i also could not find this information in the announcement? The internal boot Pool will count in to the License of maximal Array devices. I only was informed after moving to dedicated internal boot pool, that i can't start my array anymore as i do not have the correct license... I would understand if i use a NON dedicated boot pool, but i moved from 1 USB device to the 2 USB device pool. @JorgeB maybe you could implement an check that checks the current array count with the planned boot pool count and verifys the current license if its enough afterwards. Went now from Pro to Plus (or the other way arround) as i really needed the array but yeah, sucks a little bit (again, probably i overead it anywhere) Or overthink the decision that an dedicated boot pool will be added to the license count. Edit: Found the mentioning in this thread from JorgeB about the license count, but nothing official?

Hey, i am in the same boat ;) I installed thors Kernel and the is "better" recognized, but is nearly working the same as before. SR-IOV is not working. I thought the kernel is missing some features, for my understand what would be necessary for the unraid team to update to get SR-IOV working?

About your experience with the FAN, did you try to plug something into the Display Port? I plugged in an Monitor first (now an DP Dummy) and the FAN is completely normal and i can't hear it in daily tasks. As you mentioned, it is really buggy at the moment, still i got it running in Jellyfin and also in the Ollama Arc Version, which was one of my main reasons to get a B50. At the moment i don't use ollama, because of the crashes if the GPU is mounted in different containers.

An Jellyfin integration is not planned as i guess? It would be really aweseome, if this would be possible

Thanks for your response, but this is exactly what i did. You can reproduce it yourself if you want, create an new container (does not matter which one or from app store) Set the container to autostart (check mark in the Docker GUI) and remove the container with the webgui. If you check now the "/var/lib/docker/unraid-autostart" file, the autostart config for this container name is still there. Now, you add the same container in your Compose File and if you use the same container name, this setting is still persistent. So after an reboot (if the container exist while array starting) the container will still be started, as the container was set to autostart in the autostart file. The problem, Unraid is not updating this file if you remove an container from the web gui. I disabled the autostart for all containers in the GUI before removing, but for some it did not stick and was not edited into the file, but this is a different problem with unraid. As i remember i tried this already and i can see in the syslog it writes in the Log "docker compose starting stack 12345" (not exactly the log) but the containers does not start and i see not more output. I will try it again, and report back if i see more. Edit: this is my log with debug enabled, i only obscured the names of compose names. All stacks are only have compose files and only one uses and ENV. The /config/ folder is on my cache drive If i use a userscript to start the containers while array start it works without any problem. ... Sep 25 09:16:48 tower emhttpd: nothing to sync Sep 25 09:16:48 tower root: Starting compose stack: stack0 Sep 25 09:16:48 tower root: docker compose -f '/mnt/user/config/docker/stack0/docker-compose.yml' -f '/mnt/user/config/docker/stack0/docker-compose.override.yml' -p stack0 up -d Sep 25 09:16:48 tower root: Starting compose stack: stack1 Sep 25 09:16:48 tower root: docker compose -f '/mnt/user/config/docker/stack1/docker-compose.yml' -f '/mnt/user/config/docker/stack1/docker-compose.override.yml' -p stack1 up -d Sep 25 09:16:48 tower root: Starting compose stack: stack12 Sep 25 09:16:48 tower root: docker compose -f '/mnt/user/config/docker/stack12/docker-compose.yml' -f '/mnt/user/config/docker/stack12/docker-compose.override.yml' -p stack12 up -d Sep 25 09:16:48 tower root: Starting compose stack: stack123 Sep 25 09:16:48 tower root: docker compose -f '/mnt/user/config/docker/stack123/docker-compose.yml' -f '/mnt/user/config/docker/stack123/docker-compose.override.yml' -p stack123 up -d Sep 25 09:16:48 tower root: Starting compose stack: stack1234 Sep 25 09:16:48 tower root: docker compose -f '/mnt/user/config/docker/stack1234/docker-compose.yml' -f '/mnt/user/config/docker/stack1234/docker-compose.override.yml' -p stack1234 up -d Sep 25 09:16:48 tower root: Starting compose stack: stack12345 Sep 25 09:16:48 tower root: docker compose -f '/mnt/user/config/docker/stack12345/docker-compose.yml' -f '/mnt/user/config/docker/stack12345/docker-compose.override.yml' -p stack12345 up -d Sep 25 09:16:48 tower root: Starting compose stack: stack123456 Sep 25 09:16:48 tower root: docker compose -f '/mnt/user/config/docker/stack123456/docker-compose.yml' -f '/mnt/user/config/docker/stack123456/docker-compose.override.yml' -p stack123456 up -d Sep 25 09:16:48 tower usb_manager: Info: virsh called VM12345 005 002 Device attached successfully ... My Userscript i set at "Array Start" which works without any problem echo "START CONTAINERS START" sleep 15 #stack0 cd /mnt/user/config/docker/stack0 docker compose start

I had some more problems with the migration to docker-compose on unraid. I will leave some more information here, because this problem cost me hours of debug and searching for the solution in the wrong place. After moving all my containers to compose, i still had some containers who did an autostart while everything was disabled. I disabled before moving to compose all autostart flags in the webgui. After moving to compose, i moved all templates-user files (unraid docker xml files) to a new place, to be sure that they are not the problem. Then i searched hours, in the compose as i thought i removed all old settings. I was wrong, in unraid the container autostart are saved in a different file, after removing them from this place, the autostart stopped. /var/lib/docker/unraid-autostart Another problem, some containers never stopped automatically while disabling the docker service or array stop. I could find the following line in the logs: Sep 25 08:43:17 server root: Stopping compose stack: I have much more compose files and normally it looks like this: Sep 25 08:43:17 server root: Stopping compose stack: compose1234 So something was not correct running with the compose stack and the plugin. My simple solution at the end was, backup the compose, delete the compose stack in gui and reconfigure it. My last and still existing problem Not a single of my Docker-Compose Stacks is auto starting, so this is not related to one container or one stack, same for all. After reboot all stopped. The only idea i have is that my config files are not in the default folder, but who knows. I will probably fix this with an userscript and have one benefit i can also control the order when a compose start.

I am so blind, yes you are right, thanks!

Little feedback from my side. Jellyfin works fine. Tested ollama specially for arc https://github.com/eleiton/ollama-intel-arc Which also works fine, BUT i experienced now already 2 times my unraid server completly crashed in the moment i shared the GPU with different containers. When i used jellyfin OR ollama, everything fine, if both uses the GPU, it is a matter of time till the server was stuck and had to do a hard reboot. As mentioned before, when i add the GPU to my Virtual Maschine, the GPU also will be removed from /dev/dri what could cause problems. So for me it is OK, but if you want use different services with the GPU at the same time, there could be problems. About Plex, i can't add anything as i don't use it.

Another finding, a maybe a little bug fix worth. If Docker is disabled and the array starts, as i can see in the logs docker compose still trys to start the compose stacks, but docker host is not running. Could be checked before. Still have the problem that my compose files are not starting all containers and still searching what is causing this. Is it a problem if the compose folder is on the array instead of the USB drive? thanks for the work and the great plugin!

As it looks like, jellyfin is working fine, tried now also immich and nextcloud/go-vod There i get no streams, will see whats going on, but already great use jellyfin is running

Your command shows a stream and i think this is the same as the gpu_stat is doing. In GPU stat i have not much data but i can see if a app uses the card

I make a new post because i can report back, for me transcoding looks like it is working fine with Jellyfin ! I am still on 7.1.4 and installed the intel_gpu_top plugin, no other special changes. Mapped the card to jellyfin and as i can interpret the logs it is transcoding fine. As intel_gpu_top is not working i am not 100% sure how to verify. As my testing skills are limited, to verify the Intel GPU is doing something, i tried HDR tonemapping and it also works. If i would point the QSV device mapping to my IGPU it fails correctly (to verify it is really the doing of the intel card) Next step will be to try a different container, to check QSV is working (on my AMD CPU/APU system)

How is the fan on your side? For the moment it would fine for me if i could use one container with the card, but at the moment i need to connect it to the VM and can't use it anywhere else. Sadly i will send the card back if the fan can't be fixed, because i have no idea how long i would have to wait. Edit: Found a fix for my problem, i had no display plugged in into the Intel Arc Pro and set my onboard GPU to default. I still have my onboard GPU set to default but plugged in an dongle into the Intel Arc Card and now it stays silent. Which looks for me like an bug, as long the card has no output, the fan spins 100% I really have to say, i am really "shocked" that such basic problems are still here. Will test now transcoding and report back if anything works

Hi, i also got an Arc Pro B50 and experience some problems. As i can see the device is correctly recognized and i also find it under /dev/dri/renderD128. My main problem at the moment is, after starting Unraid the FAN of the GPU spins to 100% and i have no idea how to tune it down. Do you experience the same? In BIOS the FAN is fine. I have the GPU Statistics, Intel_GPU_TOP and an AMD GPU Plugin (for onboard APU) installed. The only way to get the GPU FAN slowing down, was for the moment to install an Windows VM and attach it to the Windows VM and install the Intel Arc Pro Driver. I recognized the GPU is missing (in /dev/dri/renderD128) after adding it to the WIndows VM, which should not happen ( SR-IOV Support in BIOS enabled) but this is at the moment the minor problem. The fan noise is not bearable at the moment without the windows VM, including i can't use it when its attached to windows (i did not bin the IOMMU device) Syslog: Sep 16 23:39:45 rserver kernel: xe 0000:03:00.0: [drm] Found BATTLEMAGE (device ID e212) display version 14.01 stepping B0 Sep 16 23:39:45 rserver kernel: xe 0000:03:00.0: [drm] Using GuC firmware from xe/bmg_guc_70.bin version 70.44.1 Sep 16 23:39:45 rserver kernel: xe 0000:03:00.0: [drm] Using GuC firmware from xe/bmg_guc_70.bin version 70.44.1 Sep 16 23:39:45 rserver kernel: xe 0000:03:00.0: [drm] Using HuC firmware from xe/bmg_huc.bin version 8.2.10 Sep 16 23:39:45 rserver kernel: xe 0000:03:00.0: [drm] Finished loading DMC firmware i915/bmg_dmc.bin (v2.6) Sep 16 23:39:45 rserver kernel: xe 0000:03:00.0: [drm] VISIBLE VRAM: 0x0000007800000000, 0x0000000400000000 Sep 16 23:39:45 rserver kernel: xe 0000:03:00.0: [drm] VRAM[0, 0]: Actual physical size 0x0000000400000000, usable size exclude stolen 0x00000003fb000000, CPU accessible size 0x00000003fb000000 Sep 16 23:39:45 rserver kernel: xe 0000:03:00.0: [drm] VRAM[0, 0]: DPA range: [0x0000000000000000-400000000], io range: [0x0000007800000000-7bfb000000] Sep 16 23:39:45 rserver kernel: xe 0000:03:00.0: [drm] Total VRAM: 0x0000007800000000, 0x0000000400000000 Sep 16 23:39:45 rserver kernel: xe 0000:03:00.0: [drm] Available VRAM: 0x0000007800000000, 0x00000003fb000000 Sep 16 23:39:46 rserver kernel: xe 0000:03:00.0: [drm] ccs1 fused off Sep 16 23:39:46 rserver kernel: xe 0000:03:00.0: [drm] ccs2 fused off Sep 16 23:39:46 rserver kernel: xe 0000:03:00.0: [drm] ccs3 fused off Sep 16 23:39:46 rserver kernel: xe 0000:03:00.0: [drm] vcs1 fused off Sep 16 23:39:46 rserver kernel: xe 0000:03:00.0: [drm] vcs3 fused off Sep 16 23:39:46 rserver kernel: xe 0000:03:00.0: [drm] vcs4 fused off Sep 16 23:39:46 rserver kernel: xe 0000:03:00.0: [drm] vcs5 fused off Sep 16 23:39:46 rserver kernel: xe 0000:03:00.0: [drm] vcs6 fused off Sep 16 23:39:46 rserver kernel: xe 0000:03:00.0: [drm] vcs7 fused off Sep 16 23:39:46 rserver kernel: xe 0000:03:00.0: [drm] vecs2 fused off Sep 16 23:39:46 rserver kernel: xe 0000:03:00.0: [drm] vecs3 fused off Sep 16 23:39:46 rserver kernel: xe 0000:03:00.0: [drm] gsccs disabled due to lack of FW Sep 16 23:39:46 rserver kernel: [drm] Initialized xe 1.1.0 for 0000:03:00.0 on minor 0 Sep 16 23:39:46 rserver kernel: xe 0000:03:00.0: [drm] Cannot find any crtc or sizes Sep 16 23:39:46 rserver kernel: xe 0000:03:00.0: [drm] Cannot find any crtc or sizes

I removed now a big part of my comment, as the confusion with moving the projects to another folder is fixed Thanks for your fast response. Sorry if i dont make my question more clear. I still experience 2 problems, i dont have a indirect file in my project folders (if necessary) and the autostart is not working. I can see 4 files in the compose project folder, but no indirect file "autostart , docker-compose.override.yml , docker-compose.yml , name" I tried now many things, the only way to start my compose-containers at Unraid boot (docker enable) is when i set it to "restart: always" but i think this is not because of compose, it is a default docker behavior. I tested now different settings (recreate containers at boot) different restart options, nothing helped. When i checked the logs while i enable docker, i don't see any log entry with "<host> root: Starting compose stack: test" When i check the project folders, i see a autostart file with value true in it. No idea what i could still debug. Ok, forget everything, found out now if i reboot the server the compose start will be triggered... thought it is the same as containers that they will start if i disable/enable the service. Edit: Still not working Additional feature request incoming 😅, Could we have an setting to enable auto start when enabling docker container? A Button to "Compose Up All", "Compose Down All", "Update Stack All" would be interesting

Another question, i want to migrate the compose files to a different folder. What would be the correct way? I can move the files and also in the Compose settings set a new default path, but how i can import the files into the gui again? I could create each project new and replace the files then in the new created folders, but for example, an import/export feature only for the .env and .yml files would be nice

I have an feature request but i am not sure this is for Unraid or needs to be done in the plugin. On the docker page, i can see under the "Version" Tab that it is handled by compose. Would it be possible to show in the docker tab in which compose file the container is running?

Hi all, i really like the plugin, one question about the Autostart. When is the Autostart triggered? Is did triggered before or after the normal container autostart? Would it be possible to configure between which containers the compose start? In general, how is the autostart activated? I set all compose files to autostart but only 1 of 7 really starts Edit: Found it out, i need to set the restart parameter in the compose restart: always After that it works fine for the containers. Also after testing, i think the compose container starts at the same time as the normal containers.

Hey all, i have a problem with the "System AutoFan" Plugin, i really like it but since v7 i think it stopped working to run on Boot. Any way to fix this? I tried to set it in /boot/config/go, but i did not work. #Auto Fan Control Start /usr/local/emhttp/plugins/dynamix.system.autofan/scripts/rc.autofan ‘start’ &>/dev/null The plugin is set enabled on PWM Controller 3 and disabled on 1+2, i read this could be the problem, but i don't need it for 1+2

I dont know if it was the reseating or the double arrows. But i did the reseating, format the drive, mount still greyed out. Pressing the double arrows. It works now! Thanks

Hey, i have a problem with mounting an NVME drive. I have the drive installed for a long time without an file system and wanted to format it now and mount it. Sadly the mount button is greyed out all the time. Did a server reboot, renamed mount point, set default script settings, cleared script settings, reformat in different filesystems and a drive clear, nothing helped. Maybe someone has an idea. Disk Log: Sep 1 11:23:42 tower unassigned.devices: Removing all partitions from disk '/dev/nvme0n1'. Sep 1 11:35:01 tower unassigned.devices: Format device '/dev/nvme0n1'. Sep 1 11:35:02 tower unassigned.devices: Device '/dev/nvme0n1' block size: 2000409264. Sep 1 11:35:02 tower unassigned.devices: Clearing partition table of disk '/dev/nvme0n1'. Sep 1 11:35:04 tower unassigned.devices: Reloading disk '/dev/nvme0n1' partition table. Sep 1 11:35:04 tower unassigned.devices: Reload partition table result: /dev/nvme0n1: re-reading partition table Sep 1 11:35:04 tower unassigned.devices: Creating Unraid compatible mbr partition on disk '/dev/nvme0n1'. Sep 1 11:35:06 tower unassigned.devices: Reloading disk '/dev/nvme0n1' partition table. Sep 1 11:35:06 tower kernel: nvme0n1: p1 Sep 1 11:35:06 tower unassigned.devices: Reload partition table result: /dev/nvme0n1: re-reading partition table Sep 1 11:35:06 tower unassigned.devices: Formatting disk '/dev/nvme0n1' with 'xfs' filesystem. Sep 1 11:35:06 tower unassigned.devices: Format drive command: /sbin/mkfs.xfs -f '/dev/nvme0n1p1' 2>&1 Sep 1 11:35:29 tower unassigned.devices: Format disk '/dev/nvme0n1' with 'xfs' filesystem: meta-data=/dev/nvme0n1p1 isize=512 agcount=4, agsize=62512726 blks = sectsz=512 attr=2, projid32bit=1 = crc=1 finobt=1, sparse=1, rmapbt=0 = reflink=1 bigtime=1 inobtcount=1 nrext64=0 data = bsize=4096 blocks=250050902, imaxpct=25 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0, ftype=1 log =internal log bsize=4096 blocks=122095, version=2 = sectsz=512 sunit=0 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 Discarding blocks...Done. Sep 1 11:35:32 tower unassigned.devices: Reloading disk '/dev/nvme0n1' partition table. Sep 1 11:35:32 tower kernel: nvme0n1: p1 Sep 1 11:35:32 tower unassigned.devices: Reload partition table result: /dev/nvme0n1: re-reading partition table

Hi, i am searching for a backup tool, which can be triggered on a remote server. with dedup and versioning. For example Remote Server -> SSH -> Local Server I dont want to trigger the backup from the local server, example "Local Server" -> Borgmatic Docker with Repo Destination Remote Server Why i want this, in case my local server gets compromised i dont want to allow any access from my local server to the remote backup, because of that i want my remote server connect to my local server. I would like to use something like borgmatic, kopia etc. but as i see the repo can be configured remote but not the source files.

No sadly not, but i think with latest unraid and netdata version, i dont see the error anymore.