sdcp73

Thank you, I must have missed those posts. Plex official was the only thing that got it working. I appreciate your help!

I recently installed a Tesla P4 from eBay (fake?) and have attempted to pass through to plex docker. Best I can tell everything is good but the card is not showing as a transcode option and it isn't showing in watch nvidia-smi as being utilized, P8. I've been reading the past few evenings through all kinds of posts and have made no progress. HPE DL360 Gen9 Installed in slot 3 (x16) Latest HP Bios P89 v3.30 (09/21/2023) 64bit BAR support enabled -I couldn't find anything about 4g Unraid 6.12.4 Nvidia Driver Installed (535.129.03) -Shows Tesla P4 as Installed GPU persistenced in go file -I couldn't find exactly how to do this other than adding 'nvidia-persistenced' to the last line of go file at boot\config\go unraid booted in normal and gui mode LSIO docker image --runtime=nvidia NVIDIA_DRIVER_CAPABILITIES all NVIDIA_VISIBLE_DEVICES matches UUID from nvidia Driver I hope this is enough information to help out. The only thing I haven't tried is switching the card to slot 1. I don't know how to do that since my cache pool is sitting on slot one on two bifurcated nvme drives. Bios only allows bifurcation on slot one, but it's also showing the card in slot 3 at x16. Diags and screens attached. The bios screen is example I pulled and not my exact settings. Thanks in advance. mikey-diagnostics-20231118-2250.zip

Thank you. It still won't let me type a space. It will let me paste the path in with spaces though.

I am trying to add my Plex/metadata folder to the excluded folders list but I can't add paths with spaces. So as far as I can get is up to 'Application Support'. I see in a much earlier post that it should allow this. I have tried in chrome, IE, and edge. Have I missed the solution to this? On 6.8.2 and 2019.10.27. Thanks!

I have replaced the ram and tried different combinations of HBA and cables and always the same result. When either of the HGST drives spins down it goes to unassigned devices. If I manually spin the drive up it comes back as disabled with a read error. I still think it is odd that it is my only two deskstar drives and they started doing this at the same time. Looking for advice on my next move. I've also attached diags, just in case. I can replace the drives. Try more cables. Should I try these drives in different bays? Anything else? Thanks! donnie-diagnostics-20190905-0200.zip

I've gone back to the H310 mini with the new firmware installed. I made it through parity with no crc errors. It took much longer, reporting 70MB/s average... about 20 hours longer. After my two HGSTs spun down it dropped them to unassigned devices with read errors, just like before. I seem to have made no progress so started testing the ram, one came out with an error, so working on swapping out the suspect stick. Found a post that may help my speed issue, enabling write cache. Has anyone else done this? Had issues with it? Is this still relevant? Drive write speeds really slow Thanks donnie-diagnostics-20190826-1821.zip

I have not had a chance to verify the card yet, I hope to accomplish that soon. I have found documentation on how to flash the integrated H310, seems to be a fairly recent post. H310 Flash Procedure for anyone else looking. Will report back. Johnnie, thanks for all the advice.

Hey Johnnie, thanks for the input. I've tried to add some more detail to accompany your comments. To support my previous statement about the H310, here is the article I read regarding queue depth. Admittedly, I don't fully understand this. http://www.yellow-bricks.com/2014/04/17/disk-controller-features-and-queue-depth/ Well, I've tried a few things today and had a few issues pop up. Unraid disabled a disk, I'm not sure why. This keeps me from during a parity check and makes me think something might really be wrong. new diags attached After the disk was disabled I changed the following, one at a time, with the same errors. To test it I could no longer do a parity check so I transferred from the emulated disk to another machine. enabled the H310 Mini Rolled back to P19 firmware per newegg review deleted the bios per firmware review Also, I've taken some pictures of the card. From what I can tell it doesn't look like a fake but I can't tell for sure. What are my best next steps? Thanks! Edit....Forgot to ask: Can I revert back to my 310 now that I have a disabled disk? Was the 310 just not reporting these problems? donnie-diagnostics-20190821-0128.zip

Setup: R720xd w/ 6.7.2 PERC H310 Dell branded LSI 9207-8i (04TMJF and 0F4DPW cables) Several assorted disks Story: System was running stable until it was time for a parity check. Apparently the H310 can't handle running all 12 disks along with a cache pool and other operations. I thought it would be a good idea to replace the H310 with the LSI 9207-8i, since it was supported by Dell there should be no issue. Wrong. Now during parity I get tons of CRC errors. Also, my only two HGST drives drop to unassigned devices when they spin down. Attempted remedies: Updated LSI f/w and bios to latest P20. Same issues Replaced SAS cables with used SAS cable that came with the LSI (connectors angled incorrectly, no dell tag). I do not know if these cables are good. Same issues. Other thoughts: I learned from another post that the 310 doesn't report any SMART info, so I don't know if my drives have issues or other historical issues. Also, the cable for the 310 has the SAS connector molded together, so I can't try that cable. I find it odd that my two HGST drives behave differently than other brands. I've also noticed that the HDD lights aren't operating as they did on the 310, not sure if this is anything. My next path is a memtest to rule out bad RAM. I have attached my diagnostics, in case I'm maybe missing something. donnie-diagnostics-20190819-2255.zip

Thanks for the info! I'm looking into flashing the 310 but got it up and running for now. I'll report back with results.

did "new config" reassigned my drives in the proper slots. all is working well. 310 mini is not raid only, does pass through on latest firmware.

I just ran across a thread suggesting "new config" that sounds like my answer. Any advice on this is appreciated. https://forums.unraid.net/topic/66673-drive-identification-wrong-on-some-disks-after-634-to-64-upgrade/ Thanks

Hi all, did a quick search and didn't find anything quickly. The short of it is after I moved from an AMD build with an LSI HBA that displayed the full disk ID I swapped everything over to a Dell 720 with a 310 mini. The mini seems to be passing the disks through with the middle part of the disk ID truncated. Because of this unraid is showing missing disks. My first thought is to just edit a config file to match the name the new controller is passing, but I'm not sure where to do that at. I'm looking in to updating the firmware on the controller to hopefully rectify the issue. Screenshot attached. I can attach diagnostics if needed, but hoping this is an easier fix. Thanks in advance..... EDIT: in a rush to find a fix realized I didn't mention needed info. Unraid 6.6.5, 310 mini f/w 20.13.3-001, bios v 2.6.1. diagnostics attached. donnie-diagnostics-20181227-1117.zip

I replaced the two cables on the cache drives just because I had a stack of fresh ones. Everything is stable for just over an hour now.... And I haven't been exactly going easy on it. So far so good, thanks!

Grasping for a solution, I have tried a few more things. fixed permissions (docker safe) nuked docker image increased image from 50gb to 80gb (probably unnecessary, reports 7gb used) rebalanced cache scrubbed cache reloaded all dockers but stopped them all. turning dockers on one by one with a few hours between I'm hoping that I'll blindly find the solution but afraid I won't learn from it. Looking at the docker log this was everywhere for all containers: Everything is fine so far, just hit 14 hours. I don't expect it to be fine for long.