Solverz

Members
  • Content Count

    27
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Solverz

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Ahh that's great news then! That reassures me that the P16 IT firmware should be fine for use, I am going to flash it now and install the controller in my system. Can finally move my SSD's from the petty 3Gbps onboard sata ports to 6Gbps using the 9207-8i controller on the P16 IT firmware. Appreciate you both sharing your expereince using the P16 It firmware, I am sure many will read these posts which will help others make their decision
  2. @JorgeB @ezhik Is the 9207-8i P16 firmware still the only firmware that allows for trim with the latest mpt3sas driver in UNRAID 6.9.1? Or have they decided to allow it again in the driver? Ezhik - Have you noticed any issues with the P16 firmware e.g. stability, data corruption etc? I understand it has been about 2 years since you started using the P16 firmware on the 9207-8i controller so if anyone can answer this question it would be yourself haha If not, does anyone have any recommendations on a good controller that supports TRIM?
  3. Is it reccommeded to back up your flash drive, docker appdata, libvirt & domain folder directly with Crashplan? or is there a more reccommended method to do this but still backing up to crash plan?
  4. Just out of curiosity, try and do a fresh install of unraid on a spare USB, unplug your original unraid usb and put in the spare one. (Don't start the array or anything or assign any drives as if you assign them incorrectly you could lose data) Then install unraid nvidia. Now see if that boots okay and if it does you definitely know that there's something on your original unraid install that is causing an issue. Just to rule out anything hardware related possibly?
  5. Thank you for this helpful information! I will give this a try However, mapping to /tmp or /tmp/example/ also started to cause issues, so I have edited my previous post... Anyway, I am going to stop discussing this here as it is going to get off the topic of this UD thread
  6. Mapping to a sub folder worked! Thank you so much for all the help!!! EDIT: After testing for a while, mapping to a sub folder in /tmp also started to cause issues.... So based on this I do not think it is a good idea to map to /tmp in any way
  7. That makes sense, the only reason I mapped it to /tmp is because it is a temp directory in the memory which seems a perfect place for on the fly transcodes and I read everyone else was doing it so thought it was fine to do so but this shows that it is not a good idea. I do not fully understand how it all fundamentally works but I will try and map it to a sub folder in /tmp to see if that makes a difference as I assume it wont interfere with any of the other stuff that is loaded in the root /tmp that way? I could be wrong about this though. Thank you for the help again!
  8. I do not have any UD devices being passed through to any dockers but your mention of mappings got me thinking, so I checked them all and decided to re create the Jellyfin docker step by step identically until I ran into the issue. I found out that mapping the dockers transcode folder to /tmp on the host was causing the issue! So after removing this mapping the UD error was no more even with auto start enabled on the Jellyfin Docker. So now the question is why would this mapping cause this error
  9. Thank you for testing that, I just found some important information to add below as soon as your post came through! I just done some more testing and I found out that the issue only occurs when the jellyfin docker has auto start enabled. This happens on the stock and the nvidia unraid build. (I was incorrect in saying it was the unraid nvidia build causing the issue before Sorry!) So to explain what happens: if the jellyfin docker has auto-start enabled and I reboot the server I get the errors (on stock and nvidia unraid). If i disable autostart on the jellyfin docker a
  10. I see, thank you for the help by the way I appreciate it Would you think this issue is being caused by an issue with the unraid build or unassigned devices itself? or any ideas on what I could do to figure out what is going on?
  11. Just did some more testing. This only happens with the nvidia unraid build as when using stock unraid, I get no errors at all! Have you heard of this issue before?
  12. Thank you for getting back to me! I just tried this in the order you wrote it and the errors are still there after the reboot
  13. Hi all, hope you can help! I have a clean nvidia unraid install and I have unassigned devices installed. When I first installed UD it worked great. However after a reboot of the server I now get the below errors: Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 1106 Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 1298 I have uninstalled UD and deleted /flash/config/plugins/unassigned.devices/ and then inst
  14. I know, jellyfin only makes it disappear when jellyfin is set to autostart and the server reboot with this setting on. The gpu is assigned to the jellyfin container so not sure if anything is going on when the server boots with jellyfin autostarting? Maybe? 😅