DoeBoye

Sounds like a plan! Did you find you had to populate specific SAS ports first (The ones at the back of the card)? I'm a bit concerned that maybe the front ports might be bad... Also, why does it not like having 2 'incoming' connections from my Controller? I assumed it would double my available bandwidth and would be a good thing... Thanks again! You've been a great help

Ok. So more info. I moved both breakout cables to the same group of sas ports at the back of the card (The 7 internal ports are grouped 4 at the back of the card, and 3 at the front). With the 2 breakout cables and 1 controller to Expander cable, all the drives appeared!! A soon as I added a second controller cable, drives disappeared... So either the second port is bad, or maybe it's only used if the second 'group' of sas ports are needed... Thanks again for your help @Vr2Io! Though I'm still not clear as to the issue, at least i got all my drives to show up!!

Well that's interesting! I removed one cable from controller to expander, and moved one forward breakout cable to a different port, and now one of the drives is appearing! It's [1:1:31:0] disk ATA WDC WD30EZRX-00M 80.0 /dev/sdr 3.00TB. Why would only one drive appear? Progress of sorts! The firmware on the HBA is the most current, but not sure about the expander as I can't see it to check/flash it... Regarding the cables. The SFF-8643 to SFF-8643 cables are both new (never tested), but the SFF_8643 to SATA cables were in use before on my controller and worked without issue. I've uploaded a new diagnostic bundle, just in case something changed. Thanks again! I really appreciate your help!!

Ok. Diagnostic attached. Thank you so much for looking!

Hello! So Sorry about the extended delay on this question. I must have missed the email that there was a response to this thread! My 72405 is set to 'HBA' mode. See screenshot for what the manual has to say. To me, it sounds like 'HBA' is the correct choice for Unraid... As for parity speeds, hard to say. Some of my drives are ancient, so slow things down quite a bit, but I have seen speeds range from low 90 MB/s to maxing out my fastest drives. With all 24 ports occupied, I believe the technical max speed would be 4800 MB/s / 24, (Based on this very thorough post) but I don't believe I've ever seen 200 MB/s during parity checks. I have 14 sata ports on my board, but 4 of them are Marvell and I learned the hard way a few years ago that Marvell and Unraid do not play well together. So 10 sata ports from the board, and now that I'm experimenting with Chia farming, all 24 ports on my controller are occupied (I actually bought an expander to increase the number of available drives, but I'm having some issues getting it running... Hopefully my foolishness, and not a bad card... TBD ). In a 4x slot, your max speed would be 2400 MB/s, so you might be limited a bit on parity checks, but for regular usage when not all drives are being read, I'm sure it would still be decent. Boot time: Hmmmm... Good question. Boot time has always been slow for me, but if I had to guess, I'd guess another 30 seconds or so? I hope that helps somewhat. Apologies again for the delayed response :).

Yup. 2 sas ports connected from controller to expander. Note: I am using power from a molex connection and do not have it plugged into the motherboard, but everything I've read in their documentation seems to say that's fine... And it does appear in the controller's utility at boot, just no drives and no device in Unraid...

Hey folks, I have no experience with SAS expanders, so I'm not sure what to expect. I purchased an Adaptec 82885T expander to work with my Adaptec 72405, but though the expander shows in the Adaptec utility during boot, the drives do not appear in Unraid (and they don't show up in the Adaptec utility either), and the expander does not show up in the devices list. Do I have a bum expander card, or am I missing something?

Also, to confirm, it works without issue for me. Just to rule out the obvious, you have identified those paths (/plots and /plotting) inside the docker template, right?

Thank you so much!!! This is perfect! Exactly what I was looking for. I followed your steps and I have Swar humming along nicely inside this docker!! Now I can actually see what the docker is doing!! As an aside, this is also a great roadmap for me on how to get other scripts running inside other dockers!!!! Super helpful!!!

Hey All! Loving this docker! Thanks @Partition Pixel! I've been trying for days to make a Plot Manager work with this docker, but I think/agree that the only solution is to integrate it into the docker. If we're taking votes on Plot Manager integration, I'm a big fan of Swar. I find it a bit more user friendly then Plotman, and can be used in all OSes if you're running more than just the docker (I'm using my MacBook as well as a Windows machine). Here's a screenshot of the interface to try and make the sale .

Hey Folks, For anyone running out of ideas, many of these issues sound exactly like what I was experiencing. CPU usage normal, plenty of ram and disk space. Set to Performance and Turbo enabled. My VM was so slow and experienced so much lag that it was pretty much unusable. It came down to Interrupts in my Win10 VM getting messed up in 6.9+. This is what I did to fix it. You can probably skip right to step 5, as I'm pretty sure that's what fixed it, but if you want to be extra careful, it doesn't hurt to clean up all the video drivers as well (I had a bunch of different video cards/drivers in the system, which is why I thought steps 1 to 4 might help as well).

I had a similar issue. This is what I did to solve the problem. You probably can skip right to the msi_util step, but I outlined everything I did, just in case...

My pleasure! I'm glad you got it working!!

Success! :). I finally had some time to take a good hard look at this issue, and with patience and perseverance, my VM is running again the same as it was in 6.8.3! Here's what I did, but I suspect these steps may not all be necessary. Download DDU (Display Driver Uninstaller) on another pc and copy it over to a shared drive on the server. I made sure it was unzipped and ready to go, as doing anything in my VM took FOREVER. Boot your VM Set it to boot into Safe mode Hit the windows key. Type 'msconfig' (without the brackets) Select Safe boot (I added networking just in case I need network access). Reboot into safe mode and run DDU. Remove all drivers (AMD, then Intel, finally Nvidia). I may have had bits and pieces of Radeon drivers in there, as I had a Radeon card running in the VM at some point. I wanted to make sure I removed all potential issues. Download MSI Util v2 on another pc (I already had it, but the link can be found from the wiki. I noticed there's a v3 version as well, but I used the one I had already. Copy it over to a shared drive . Prep it the same as DDU. My VM is extremely slow right now. Go back to VM, go back into msconfig and set boot back to normal Reboot VM. VM should perform normally at this point (video will be stuck at 800x600 with no drivers). Grab the msi util app from the shared drive and save to desktop. Go to nvidia and grab the current drivers Install current drivers and reboot. Performance will degrade to virtually unuseable again. Right click on msi util and RUN AS ADMIN. Now. Get up, get a coffee/grab a beer/Make lunch for your kids. This part took over an hour for the app to launch and find all the devices in my system. Once it stops adding things to the list, look for anything related to audio/video. I had 2 a/v entries that did not have msi checked, and no interrupt priority set. I checked the msi box and set them to high priority. MAKE SURE TO HIT APPLY in the top right corner. Reboot and enjoy the sweet sweet speed of your Windows 10 VM Of course, our issues may be completely unrelated. My VM never crashed/permanently froze. But any inputs from the mouse were extremely delayed (about 10 seconds between moving the mouse and having it register). Apps also took at least 10 times as long to load. Completely unuseable. The funny thing is I had already run this utility when I first built the VM. It usually takes care of any stutter or audio artifacts you might find in your Win10 VM. Odd that I had to re-run it, and it had never behaved so poorly before. Usually I might just have a bit of a stutter or audio weirdness. Finally, as I mentioned at the start, more than likely most people could skip to just running MSI Util and checking 'msi' and setting interrupts to high priority for any a/v entries, but I thought I would provide exactly what I did in case that is not enough. Good Luck!

Can you try without passing through your rtx2080? Just use VNC. Obviously not a solution, but may help isolate the issue. I have the same problem, but if I don't pass through my video card, stability returns.

Update: Updated to 6.9.1 with no improvement. VM Performance with Nvidia card passed through is still unuseable.

No worries! It was a good suggestion. One more thing confirmed not to be the issue

I have a ASRock EP2C602-4L/D16. Also, as an aside, the script didn't work for me either, but I did it the old fashioned way and the vBios export worked (but didn't solve the issue)

Good idea! Unfortunately, I tried, and even with the vBios file, no change. The VM loads, but everything is extremely slow. I'll type in my login and it takes about 10 seconds to appear. Thanks for the suggestion though! It looked promising on the surface!

Note: Tried running MSI Util inside Windows to see if something changed with interrupts etc (I ran it before to take care of some performance and sound issues and it worked great), and it tries to load but gets stuck halfway and ends up 'Not responding'.... interesting.

For the record, I have the same problem passing through a Nvidia GT 710. I tried the script above in user scripts at boot. No change. I tried binding the GT 710 to the vfio-pci driver at boot using the new system devices checkbox feature, but no luck... Very odd. Worked flawlessly in 6.8.3

I moved to an Adaptec 72405 more than a year ago, and though the initial setup was a bit of a pain, it's been working without issue since. Here's a thread documenting the situation. https://forums.unraid.net/topic/83895-please-explain-what-is-happening-with-my-adaptec-72405/?tab=comments#comment-777570

Thanks again! This has been a minor irritant for me for years. Anytime I wanted to preclear an external drive, I would have to shut down my Windows VM, remove the usb 3.0 card from the xml, add a usb 2 controller and reboot. When done preclearing, I would re-add the USB3 controller. This card allows me to dedicate one USB3 controller (port) to my VM, and the remaining three are still available to Unraid! They all show up separate and easy to identify in their own IOMMU groups. Can't ask for better than that!! IOMMU group 24:[1912:0015] 04:00.0 USB controller: Renesas Technology Corp. uPD720202 USB 3.0 Host Controller (rev 02) IOMMU group 25:[1912:0015] 05:00.0 USB controller: Renesas Technology Corp. uPD720202 USB 3.0 Host Controller (rev 02) IOMMU group 26:[1912:0015] 06:00.0 USB controller: Renesas Technology Corp. uPD720202 USB 3.0 Host Controller (rev 02) IOMMU group 27:[1912:0015] 07:00.0 USB controller: Renesas Technology Corp. uPD720202 USB 3.0 Host Controller (rev 02) This is on an ASRock EP2C602-4L/D16 motherboard. Note: In my case, the top port was 06:00.0. You would think it would have gone in order (4, 5, 6, 7), but instead it went 6, 5, 4, 7.

Installed and working great in 6.8.3! Funny story. I'm testing out Tdarr to batch convert old .ts files to .mp4 files, and I've been running 'watch nvidia-smi' to keep an eye on my 1660ti when I thought to myself "It would be neat if I could see this in the dashboard". I went to the nvidia plugin support thread, started reading the last few comments, and someone linked to this plugin that does exactly what I was looking for! Thank you!! :)

Awesome Docker! Thank you so much!!! One thing I noticed: While using an nvidia card to transcode, if I cancel all workers mid-transcode, the streams do not seem to get released until I stop the docker. If I let them finish, they release as expected. (watching using 'watch nvidia-smi' in Putty)