RaidUnnewb

Don't forget to swap the render node for Jellyfin/Plex and any other containers needing the GPU.. Whether this is working, I still dont know, havent had time/ability to test.

Well, had to restart Unraid and the render devices swapped... Now my B580 is RenderD128 instead of D129. Since the physical slot is still /dev/dri/by-path/pci-0000:03:00.0-render the AI is telling me to change the Extra Parameters in the Tdarr docker. Since colons cant be used without errors, a hardlink needs to be made: Type this in unraid CLI: ln -s /dev/dri/by-path/pci-0000:03:00.0-render /dev/dri/intel_b580 Now, we need to make that a script so it runs every reboot: Do this in User Scripts, running every first array start. Finally: Change the extra parameters to: --device=/dev/dri/intel_b580:/dev/dri/renderD128 Now that were back to using D128, have to go back into the Flows Custom Arguments and change it to D128 from D129: And it finally works again... Moral of the story: Just buy Nvidia since thats the default people code stuff for...

Okay, so I was still having transcoding errors but that was all fixed in my flows and docker extra parameters now. Successful transcodes with the below settings! I did these 2 commands in Unraid CLI per AI instructions, dont know if I messed anything up: chmod 777 /dev/dri/* setfacl -m u:99:rw /dev/dri/* In the custom arguments section of Tdarr, i had to do some inputs and outputs on suggestions with AI. I did some extra stuff but that wouldnt work without running the docker in privleged mode, which I didnt want to do past testing. Here is how I got the B580 working without having a privileged docker: Input: -hwaccel qsv -hwaccel_output_format qsv -qsv_device /dev/dri/renderD129 Output: -max_muxing_queue_size 1024 -global_quality {{{args.variables.user.qual}}} -extbrc 1 -async_depth 4 -look_ahead 1 -look_ahead_depth 30 -extra_hw_frames 30 -b_strategy 1 -adaptive_i 1 -adaptive_b 1 Some of that output above is needed, some isnt. I don't know which is required due to the B580 and what is needed per the flow instructions. The RenderD129 part is again, because 128 is my AMD igpu, 129 is the Intel Arc GPU. Also in the Video Encoder options, set your codec, in my case av1, and AI says its very important to use "veryfast" due to specifically the Arc or B580 compared to how igpu's handle this. Also qsv as hardware type is important. In the Docker settings (for both Jellyfin and Tdarr), I got rid of all the extra stuff, and now just have: --memory=16g --cpu-shares=512 --device /dev/dri:/dev/dri The latter part is what matters, and matches what others have said. I was just missing the stuff inside the docker itself. For Jellyfin, I also made a specific device mapping just in case: Not 100% sure its needed. I don't know how to actually test Jellyfin transcoding properly since gpu tops arent working in unraid right now. In Jellyfin I specified QSV and typed the D129 device path.

Ok, so I spent a bit of time with google AI and seeeeeem to have my B580 working on my 9950x platform. This is Unraid version 7.2.2 if it matters. Havent fully tested yet, wish GPU Statistics was working... Trick is to pass "--device /dev/dri/card1:/dev/dri/card0 --device /dev/dri/renderD129:/dev/dri/renderD128" to all your dockers that you want to use in 'extra parameters'. I found other tips to use "--device=/dev/dri", but this passes through both GPU's, and I really only want the actual discrete card passing through so I can use the igpu for a VM or something later. BUT FIRST you have to make sure that card0 and renderD128 are the right ones. I have my igpu enabled and that takes up card1/D129 on my system. Steps: Get plugins "Intel GPU TOP", "NVTOP" (I use this for the top in CLI, you may not need?), "GPU Statistics" (this one is bugged until the kernel updates and supports ARC and then Unraid adopts that, but at least its a quick check to see if it even recognizes my card) In unraid CLI, use these commands: ls -l /dev/dri This should print out your card0, card1, and renderD128/D129 and whatever else. readlink /sys/class/drm/card0 This will print out some stuff, what you want is right before /drm/card0 readlink /sys/class/drm/card1 This will print out some stuff, what you want is right before /drm/card1 lspci -nnk | grep -i vga -A3 This will let you match your actual video card to your card1/renderD129 or whathaveyou, for the above "--device /dev/dri/card1:/dev/dri/card0 --device /dev/dri/renderD129:/dev/dri/renderD128" Now, in my case I want to use card1 which is my B580, and not card0 which is my igpu. What this actually means, I have no clue. Actually, scratch that (just asked AI, editing post). You want card0 and D128 to be on the RIGHT side of the above command, whatever your left sides are. Just so happened that mine were this way. Ask AI why, it can explain somewhat easily. Pic example: I do the extra CPU resources and RAM settings for each docker, doesnt matter for this guide. Hope it helps!

Tried #!/bin/bash chmod +x /boot/config/plugins/user.scripts/scripts/00001/script echo "Script 1 done" echo "" chmod +x /boot/config/plugins/user.scripts/scripts/'0 isos snap and replication'/script echo "Script 2 done" echo "" chmod +x /boot/config/plugins/user.scripts/scripts/"0 system snap and replication"/script echo "Script 3 done" echo "" /boot/config/plugins/user.scripts/scripts/'0 VMs snap and replication' echo "Script 4 done" echo "" /boot/config/plugins/user.scripts/scripts/"appdata snap and replication"/script echo "Script 5 done" echo "" got So it looks like it mostly worked (made them all different so I could text syntax because I added spaces...) But I checked the Iso snaphsot admin, and no new snapshots. Went and ran that script directly, and it did change the snapshot admin. So none of the scripts actually ran from the main script. Saw itimpi's comment that I got sh pathname wrong lol (I am new to this) tried: #!/bin/bash sh /boot/config/plugins/user.scripts/scripts/00001/script echo "Script 1 done" echo "" sh /boot/config/plugins/user.scripts/scripts/'0 isos snap and replication'/script echo "Script 2 done" echo "" sh /boot/config/plugins/user.scripts/scripts/"0 system snap and replication"/script echo "Script 3 done" echo "" sh /boot/config/plugins/user.scripts/scripts/'0 VMs snap and replication' echo "Script 4 done" echo "" sh /boot/config/plugins/user.scripts/scripts/"appdata snap and replication"/script echo "Script 5 done" echo "" And now its running sequentially which is GREAT. well, it ran script 1, script 2, script 3, failed script 4 due to syntax, and then ran script 5, which is what I expected! Fixed the failed script, and boom! Good to go! Thank you for both of your help! I have scoured this website search and google and couldnt find. Hope this is useful to others in the future.

I tried the sh pathtoscript first since that looked easiest lol. #!/bin/bash sh pathtoscript /boot/config/plugins/user.scripts/scripts/00001/ sh pathtoscript /boot/config/plugins/user.scripts/scripts/0 isos snap and replication/script.sh sh pathtoscript /boot/config/plugins/user.scripts/scripts/"0 system snap and replication" sh pathtoscript /boot/config/plugins/user.scripts/scripts/'0 VMs snap and replication' sh pathtoscript /boot/config/plugins/user.scripts/scripts/"appdata snap and replication"/script also did a quick test with sh pathtoscript /boot/config/plugins/user.scripts/scripts/00001/script.sh same result.. I dont understand what to write in the main script for foo_fighter's comments. (And apparently forgot how quoting works on this forum). Do I use the CLI to make a copy somewhere, put the command in the main script to make a copy daily then run that, something else? Welp, I learned the hard way that I really do need to figure out this main script, because I was running one of the backups when my 'restart once a week' script ran. Ended up in an unclean shutdown so doing a 2-day parity check, when I just finished building parity yesterday (made some drive changes) lol. Now I have the 5 schedules running AFTER the weekly reboot.

Actually, I'm stuck again. Been trying different options for the last 30 minutes. Keep getting errors trying to run the script. So far my script is: #!/bin/bash /boot/config/plugins/user.scripts/scripts/'00001' /boot/config/plugins/user.scripts/scripts/"0 isos snap and replication" /boot/config/plugins/user.scripts/scripts/"0 system snap and replication"/script.sh /boot/config/plugins/user.scripts/scripts/"0 VMs snap and replication"/script.sh /boot/config/plugins/user.scripts/scripts/"appdata snap and replication"/script.sh Ive tried using quotes, apostrophes, no punctuation, adding and removing .sh to the end. In each script directory, there are only 3 files: description, name, and script. I assume that I want to call out the script file to run, but I don't know the proper syntax. (also future note to anyone searching for this, the script files are on the flash drive) Edit: after some more process of elimination: Looks like a few of them are seeing the script, but getting permission denied...? Doesnt seem to make a difference between " and ' for the below scripts. But need to have one of them, and a /script at the end. #!/bin/bash /boot/config/plugins/user.scripts/scripts/00001/script /boot/config/plugins/user.scripts/scripts/0 isos snap and replication/script.sh /boot/config/plugins/user.scripts/scripts/"0 system snap and replication".sh /boot/config/plugins/user.scripts/scripts/'0 VMs snap and replication'/script /boot/config/plugins/user.scripts/scripts/"appdata snap and replication"/script Im thinking that the answer is in here, but I don't understand any of it and have been going at this for a couple hours now... https://www.baeldung.com/linux/shell-call-script-from-another Thank you for your patience/help.

Thanks! Was thinking it was more complicated with waits and whatnots (closest to coding I've come is editing macros in keyboard/mouse software). If the script waits for the previous line to be done before moving onto the next, then it solves itself. Awesome!

Hello, I am relatively new to scripting (I use other people's scripts, not creating my own) and would love help creating a script to run other scripts in order. I have 5 instances of SpaceInvadors 'snap and replication' script for my various zfs cache drives (appdata, system, vm's, iso storage, ect) running daily backups to a single zfs drive I have on my array. These are creating daily/weekly/monthly backups for all of the datasets and storing them on my drive, which then gets parity protection. Works great so far. But, I am worried that having so many scripts running timer'd is 1) Inefficient (I want my disk to spin down instead of kept active for extra hours), and 2) I am worried that if I do a big change to one of my folders (adding gigabytes of LLM files or something) that one of the backups could take long enough to interfere with the timing of another, and stop it from running, or catch my server/house/me on fire or something. I haven't been able to find (and dont want to test) what happens with trying to run multiple scripts at once. Does anyone know to write a script that will do what this reddit post suggests? Apparently it should be simple, I just cant find an example to copy/alter haha. Solution is to have a script that will start each script right after the previous one finishes. The 'master script' will be set to run daily and all other scripts will have their schedule disabled. Thank you!

Mods, don't know if this belongs here since its not a current issue. I just wanted to give others examples of random problems and a possible solution. If it helps you, please go through my past diagnostics for my other support threads/tickets, as I believe the solution was found below, may help you diagnose future issues with other systems? To be clear, Unraid has largely been perfect for the past 2 months solid now. I still have a weekly reboot setup, may try to get monthly uptime. This is fine for now. Its now always ready to go when I need to access server. Its been a while since Ive been having constant Unraid problems. Ive opened a couple of threads, done a bunch of research and the problems kept happening. Terrible server uptime/reliability since Dec 2022 until May 2024. I now believe that I had a couple older SSD's (OCZ Vertex 3 120gb is oldest, also had a Samsung 500gb, and a 64gb one from a steam deck) that may have just been throwing weird edge case errors that I was never able to track down. I have spent thousands of dollars on replacing hardware (cpu, ram (3 sets), mobo, psu, drives, ect) before just removing a couple of older drives that had 90+% life remaining according to SMART data. If this helps someone else, I am posting my error log that I started recording a year into the errors in hopes of finding a solution. If you get random errors that happen to match some of mine, take a look at any older hardware? Below are my notes for personal use and have spelling errors or abbreviations. Figured I would share if it helps, sorry for not being 100% thorough.

Jesus, this took me a couple hours to troubleshoot.... I couldn't figure out what you were talking about by adding a second video card. Theres a tiny easily missed plus button to add more cards in the VM settings: I kept getting a Guest not initialized error, so had to go into XML view (top right of VM settings), and switch the bus to 0 from 7: to It gave me an error for slot 1 so I switched it to slot 2. I have to manually edit this every time I change a setting. Anyone know a fix? Now I can start the VM using VNC in unraid, as well as by using remote viewer of your choice. Was having a hell of a time getting Nvidia drivers installed, had to go back and forth to VNC like 15 times. Now I have the VNC drivers and Nvidia drivers installed and showing up in device manager. Now even loads Star Citizen which was my entire reason for making this VM. Edit: After a single restart the VM keeps losing the Nvidia drivers (device manager has question mark). Nvidia control panel wont open. Task manager doesnt have a GPU tab even right after reinstalling the gpu driver (and shows up in device manager). anymore.

I would like the new pool to be 1 device. Snips showing each step below: Current config, array started. Crazy, I don't think I missed this before, but found this as I was stopping the array for the 20th time today lol. I formatted, and its now apparently working. I knew it should be this easy, it has been this easy in the past. I don't know why the option wasnt there before, or why I missed it (more likely). I did format a few times while it was unassigned, just havent been able to do it when it was in the pool and assigned. Transferring appdata and system back to array from other SSD using mover. Took about 15 minutes vs the 18 hours (before I gave up) on the old SSD. Hung up transferring back just now, so I let mover run overnight. Server crashed again during the night's auto-restart but recovered and Parity was going again I guess. Cancelled that, used MC to transfer over the system share that mover missed. Turned off the array for docker shares, and all seems to be working, except for 1 of my dockers. No biggie, just restore from a backup. Sorry for the false alarm, dont know why it wasnt there or I didnt see it.

Hello, I have months/years of problems with my server that I am slowly trying to diagnose. My lastest efforts have been to replace an older sata SSD with a new NVME one for my dockers and eventually VM's (dont have any VM's yet). I told mover to move everything off the SSD onto the array. Mover bugged out and stayed "working" forever. I used MC and manually moved over the data. Something is up though, the dockers are all funky. I may have lost everything. Not the end of the world. I am now in process of removing the SSD from the Pool and adding a new NVME to the pool but I keep getting other problems. The Pool is zfs with compression and autotrim set to on. Every time I start my array I get: "Unmountable: Unsupported or no file system" I have cleared and formatted the drive, and cleared the Pool. I even deleted the pool and made a new one with the same name. I added back the old drive plus the new one, and it auto mirrored (it should have zero bytes on it, but w/e) and appeared to work. I then remove the old drive from the array and it goes back to 'Unmountable'. Running "zpool import" gives: I dont really care about the data. I just want the drive to work, so I can put the data back on it. I have many backups using 'ZFS Master'. The reason for running a zfs cache drive is to do daily/weekly/monthly backups onto the single zfs hard disk in my array. The only thing I can think of is I still see the new NVME drive under "Historical Devices" where I had it unmounted since installation a while ago (never used, never put data, never mounted). Any ideas? I will eventually open another topic to discuss the myriad of troubleshooting steps taken over the past few months to try and get my server to stop randomly crashing every few days. I am hoping a bad drive running my dockers is the culprit. Diagnostics included. gigavault-diagnostics-20240403-1051.zip Thank you!

Hello, Is there any guides on how to get Mattermost Docker to work for a beginner? I am reading that I need other dockers or something to act as a database, but under Mattermost docker in the "Additional Requirements" field there is: "None Listed" Without know what to change, my Mattermost Docker is running and when I try to use the WebGui, I get "This site cant be reached". I try clicking on all the container settings and there arent any help-tips. I am assuming I am missing whatever needs to be changed in the 'DATASOURCE' and 'APP_HOST' settings since it has some username/password/ip stuff there but...... My IT/computer background is as advanced as: Watch youtube guide, download whatever docker, change the two settings the guide says to, and.... it works.. There just doesnt exist a how-to for this thing yet, unless I missed me. Thanks! Edit a couple weeks later: I gave up. Running Nextcloud instead of mattermost because there are guides in how to set up the database for it.

Yes. Thank you, you summed up my dilemma perfectly lol. Though, I am further screwed because I want to add my old 1070 gpu to the 16x slot for VM use. So having 4 slots working at x4 speeds is all I need. They just don't make em. But the key to all this, and I hope it helps other people googling, is a PCI 3.0 x8 (or whatever) device hooked to a PCI 4.0 x1 speed slot, will only work at PCI 3.0 x1 speeds.