Leaderboard

Popular Content

Showing content with the highest reputation on 01/21/20 in all areas

  1. My apologies for long delay since the last release, for those that care about why, I'll leave it in the postscript. In this version there are some major changes in addition to the usual bug fixes. A big bug fix, is that the plugin should now be able to handle parenthesis in your VM names (thanks to squid for suggesting a solution to that). New features include the ability to have multiple configs so that you can run backups on different schedules, as well as the ability to run pre and post scripts with those configs. Compression now uses pigz for multi-threaded compression (th
    2 points
  2. Mod note: this plugin has multiple known issues, use with care. This is a beta version of a plugin I am working on to replace the unraid-vmbackup script I have been maintaining here and here. It is based off the latest version of the script (v1.3.1), and I will be maintaining both for now as there are some use-cases for the script that the plugin cannot currently replace. This is provided as-is with no guarantees. That said, and without further ado, the current version of the plugin can be found here: https://github.com/JTok/unraid.vmbackup/tree/v0.2.2
    1 point
  3. build 2020.01.21: 6.8.0-rc5 kernel with navi reset v2 vega reset patch* (used in conjunction with this script) k10temp Ryzen patches from 1/18/20 (new) Fix for onboard audio passthrough on x570 *modified to add 0x6863 in addition to 0x687f 6.8.0-rc5-Skitals-2020.01.21.zip
    1 point
  4. One more thing. Don't send mail to yourself-- Same recipient as sender. It could get tagged as Spam.
    1 point
  5. You don't have an E-mail recipient listed in the SMTP Settings.
    1 point
  6. Disabled disk rebuilt and now part of the array with a sweet green dot next to it. Just finished a parity check and have zero sync errors. Success! Thanks to everyone in this thread that helped me through this.
    1 point
  7. If you can't boot and it stops before unraid is loaded, the issue is not unraid. If your bios is from 2016 it is about time you update it.
    1 point
  8. Yes! I received the Intel E-2278G a week ago, and 4 no. 32Gb ECC UDIMMS. I just booted for the first time into ESXi showing 128Gb of memory. the DIMMS are: 4 no. "32GB (1x32GB) Samsung M391A4G43MB1-CTD DDR4 ECC UDIMM, PC4-21300 (2666)" I'll carry on with the build now.
    1 point
  9. Open the container settings (edit) and change to advanced view. Check the setting for "WebUI" --> http://[IP]:[PORT:8888]
    1 point
  10. If the RAM is good (I'd reseat both DIMMs by swapping them over for good measure) I'd check the power connections to the motherboard, both the main ATX power and the CPU power. Try a different PSU, if you have one.
    1 point
  11. Hi there, Looks like you need to update your forum signature as your hardware has changed from AMD to Intel ;-). That said, I'm not seeing any events in the logs themselves that show a problem. And I'm not sure what this is supposed to mean: Also hoping that you removed this container while troubleshooting this: At this point, I would suggest hooking up a monitor and keyboard to the system and tailing the log (command is tail /var/log/syslog -f). This will begin printing the log out to the screen. Then try to get the system to crash again and capture what
    1 point
  12. I have had the same problem since I installed Nextcloud over six months ago and have asked a few times and not got any answers so I don't think anyone knows! I did get one answer over on Nextclouds forum and they seemed to think it was a bug! A bad one in my opinion, makes it unusable for me and effects downloads or uploads to the server the same! I can't have a system that crashes all my docckers when someone downloads a file! So I leave it off until I find a solution! If you find one please post here and I'll do likewise! Cheers, Tim
    1 point
  13. If you type ls -l /dev/disk/by-id you will see what the symlinks actually point to. Instead of using /dev/sdX in your configuration, use /dev/disk/by-id/Y where Y is the symlink (shown in light blue/cyan) that points to your /dev/sdX. If what I wrote doesn't make sense then post a screenshot of the ls -l command, above and confirm which sdX you are currently using (from your screenshot above it looks like you're using /dev/sde).
    1 point
  14. Thanks for your answer for the moment a restart of the radarr docker solve the problem ^^
    1 point
  15. Depends on where the bulk of the traffic is headed. If it's headed out the WAN port, then the router is the obvious choice to connect that specific switch. If it's staying local, then keeping it off the router is better. With the equipment you originally specced out, it really wouldn't make a whole lot of difference. This is the correct answer at this point in time for your layout IMHO. A single unit feeding all data lines, with uplink ports connecting to the POE branch. Now all you need is a real router and some Unifi access points hanging off that POE switch along
    1 point
  16. Any audio transcoding is still handled by the CPU, but that would be significantly lower. All video is GPU. I don't have a P2000, but there are a few videos where people have got about 12/13 4K transcodes simultaneously (although 4K transcoding doesn't look right yet). If it's 1080p stuff, more. I have the 1231 processor, and I find it's now only taxed if one of the other dockers has a moment. Plex just works, and if I get any holdups, it's usually either a system pause whilst a drive spins up or network congestion.
    1 point
  17. It's not crazy. You are assuming perfect scaling (i.e. more core = better performance) but in real life, it's rarely ever like that. 44 (logical) cores sounds like a lot but they are hyperthreaded. An extra hyperthreaded core adds only about 30% performance (at best!) so 44 logical cores is roughly equivalent to 33 non-HT cores at best and 22 non-HT cores at worst. So now you only have to really "explain" the diff between my 24 non-hyperthreaded "odd-bank" config vs 33 non-hyperthreaded (at best) config. Firstly, there's diminishing return (i.e. performance) as you add co
    1 point
  18. You need to move the data to another disk, with Krusader, mc (midnight commander), etc, then shrink the array, there are two options, both described below, 1st one is probably the best for this case, at least it would be the fastest. https://wiki.unraid.net/Shrink_array
    1 point
  19. You probably need to google some reviews I guess. I generally prefer PSU reviewed by jonnyguru. I would not be too concerned about the single-rail vs multi-rail argument, especially considering your load. It was a rather archaic argument (for tech stuff) back in the early 2000. It's more important that the PSU comes from a reputable brand and has at least decent review. PS 1: the Unraid wiki has to take into account people running 20+ HDD array. Those guys probably would prefer single rail. PS 2: the Unraid wiki is also quite old (for tech stuff) so back when it wa
    1 point
  20. Multiple arrays are not possible although I believe it is a roadmap item, but with no ETA. Having the 8TB as parity is over-kill at the moment, but it does mean you are in a position to add 8TB data drives going forward.
    1 point
  21. Thanks, I updated the guide. That error means that you hit the Discord Server Role Limit which I had not accounted for until now. Go ahead and check for updates and you should have bot version 1.2.1. I adjusted the code to work around the limit so it should be functional but you will still have that error in your logs. By the way, !notifications preview is a new command that can be used in place of !notifications list when experimenting, I created it because the bot now tracks the most recent call of !notifications list and updates the emoji reactions on bot startup to re
    1 point
  22. The fun never stops, I uploaded a new 6.8.0-rc5 kernel today that incorporates a bunch of goodies for this board. Brand new k10temp patches for Ryzen, and a fix for passing through onboard audio!
    1 point
  23. Updated to add flr kernel patch. You can now pass through 1022:1487 [AMD] Starship/Matisse HD Audio Controller on x570 boards! I haven't tested, but you should also be able to pass through the cursed isolated 1022:149c [AMD] Matisse USB 3.0 Host Controller. I believe you are best off using that controller for your unraid usb/keyboard/mouse/ups and passing through the other two controllers, however.
    1 point
  24. Parity has none of your data. Parity PLUS ALL remaining disks are required to calculate the data for a missing disk. Doesn't matter at all how large any of the disks are except none can be larger than parity. So single parity only allows one disk to be rebuilt. Dual parity allows 2. Here is the wiki on parity: https://wiki.unraid.net/UnRAID_6/Overview#Parity-Protected_Array
    1 point
  25. So...I have a feeling the kernel panic was due to the upgrade to 6.8.1. For my part only 6.8 was stable. I say this because when I remade the USB stick with the old backup (6.7.2) and used the config files from the original stick, it booted up with the correct configuration and everything. I don't know if the guys at Unraid are aware of this issue but I won't be migrating to 6.8 until this gets fixed. All in all, thanks @PeteAsking. The config migration solution worked. Not sure why I didn't think of that. Much appreciated. I was freaking out a bit, I'll be honest.
    1 point
  26. Okay, thanks. Does this mean the redirect will only work on the non-SSL port? I would've figured the cert issue wouldn't have been an issue if it redirected to where I told it to go. Yes, the way the default page is configured in nginx makes it apply to non-SSL port only.
    1 point
  27. bingo, i had to edit the xml instead of using the form view. The port was set to -1, I assume that means auto but I changed the websocket to 5703 and then it started. Thanks.
    1 point
  28. Some folks, when setting up an unRAID server, will load the data to than array without assigning a Parity drive. Of course, the data on the array will have no protection in the event of a disk failure but often the data is still on the original source drives so there is a backup. After the data is moved, the Parity drive is added and parity will have to be built. Moving massive amounts of data to an array is always a time consuming process. The actual transfer rate has many factors involved. Some of the most significant have to do with the characteristics of the hard drives the
    1 point
  29. I generally recommend Gigabyte mobo for new users because its BIOS allows you to pick which of the PCIe x16 slots as Initial Display Output (i.e. what Unraid boots with). Given you want to pass through a RTX 2080, chances are you will need a 2nd GPU (a cheapo single-slot like GT710 would work) to dump vbios and avoid error code 43. Having the ability to pick any PCIe x16 for Unraid to boot with allows you put the cheapo on the slowest slot (e.g. the one running at PCIe x4 speed) and reserve the fast slot (1st) slot for the RTX 2080.
    1 point
  30. got the firmware updated. Didn't get greeted w/a ton of udma crc errors (fingers crossed). Currently rebuilding array due to the disabled disk. Hope this works.
    1 point
  31. For the Metadata part please do the following (taken from Plex Forums that worked for me) 1. Stop PMS 2. Delete the HTTPCookies file under the Plug-in Support (the agents) 3. Start PMS 4. Refresh All Metadata 5. Give it time to walk through. For me the HTTPCookies files are in Plug-in Support/Data folder. Delete only the HTTPCookies files that are located in each folder. After doing that the Movies and TV shows Posters started populating. Sent from my iPhone using Tapatalk
    1 point
  32. Hmmm, Going to be honest, I didn't even realise realtek oot drivers were needed on this release, I must have missed that in the release notes. I'll build a new release, not a big problem. Sent from my Mi A1 using Tapatalk
    1 point
  33. Thanks, these confirm my suspicions, the quad NIC isn't being detect after a reboot, so nothing LT can do about this, look for a bios update (and/or reset bios to defaults) or try a PCIe different slot if available.
    1 point
  34. Is it possible there was a regression for the RTL8125 driver in the Unraid Nvidia 6.8.1 build? I am running into the identical issue I had on the 8.8.0-rc5 build. Reverting to Unraid Nvidia 6.8.0 has my NIC working correctly again. Thanks again for all the work put into this project.
    1 point
  35. I have blue iris running in a windows 10 vm (igpu passthrough to that vm) and can transcode several 1080p plex streams without much of a sweat. You've got the k version so an extra 400mhz(?) to your base clock speed will do better. There's a also a 30 day trial, so you could just try it lol.
    1 point
  36. Possibly because of and your solution was to which didn't actually address the issue
    1 point
  37. Awesome! Bring on 6.9 with that new 5.4 kernel
    1 point
  38. I like the virtualisation feature and I would like to see overclocking features added in the future. This was a fun way to set up a competition!
    1 point
  39. I will update for 6.9 rc1 when it's out. 6.8 final reverted to a 4.x kernel. 6.9rc1 will be identical to 6.8 final with the addition of the 5.x kernel.
    1 point
  40. @alturismo Create "/etc/modprobe.d/snd-hda-intel.conf" inside the VM with the following content and restart the VM. options snd-hda-intel enable_msi=1 Crackling sound should be gone with this.
    1 point
  41. Good to know, thank you for the clarification!
    1 point
  42. Ok so what exactly is your top score for space Invaders? [emoji16] Sent from my CLT-L09 using Tapatalk
    1 point
  43. If you're on latest release it's much easier, just click on the flash drive and change it here:
    1 point
  44. Basically, Unraid uses a even-parity calculation across all the data drives to be able to reconstruct the failure of a single data drive. See here for how it works: https://wiki.unraid.net/index.php/UnRAID_Manual_6#Parity-Protected_Array Raid is faster in data writing and retrieval operations. However if two drives fail in a RAID configuration, you lose all of the data in the array. Also all drives must be the same size. With Unraid, writing is much slower and the read process is limited to the read speed of the data drive which contains the actu
    1 point
  45. Hello Unraid community. I am curious if I am able to limit the amount of resources a docker has access too. I recently installed the Handbrake docker and start my first job. I have a fairly decent servers for unraid with '2 x E5-2670's'. When I fired up my first handbrake job I saw all CPU cycles get consumed. As sexy as this is I have a VM that is my main base of operation also running on the server and its is very unresponsive with handbrake eating all cycles. Is there a way to restrict which cores Handbrake docker can use? Or at least limit how many cores it h
    1 point
  46. https://forums.lime-technology.com/topic/57181-real-docker-faq/?page=2#comment-566088 https://forums.lime-technology.com/topic/57181-real-docker-faq/?page=2#comment-566087
    1 point
  47. I've add some script files to the method speed up the process. Updated Files - https://mega.nz/#!bp1lwAwZ!qrQics2qslPxCRFSI7pCaL-JECCauM_xqp00GQPloSg MIRROR - https://file.io/K3Hhyrpt Steps Create DOS USB using RUFUS and copy these files to the USB. GUIDE link Each task has 2 commands you can do. The first one saves you typing the commands by using script/bat files. Recommendations Unplug all drives but the USB, helps with the EFI shell bit Plug D2607 in to the first x16 slot, even if it means unplugging another car
    1 point
  48. How do I limit the CPU resources of a docker application? Two methods: The first is the easiest and doesn't involve much thought about what's going on under the covers: Pin the application to one or more cores of the CPU. This way the application will only execute on that particular core(s), leaving the other cores open for other applications / vms / etc On 6.6+ on the Settings - CPU Pinning you can select which core(s) the docker application will run on Alternatively, you can also prioritize one docker app over another: eg: You're running the folding@home app and ple
    1 point
  49. Please see Why do I see csrf errors in my syslog?
    1 point
  50. Why do I see csrf errors in my syslog? Starting with 6.3.0-rc9 unRaid includes code to prevent CSRF vulnerabilities. (See here) Some plugins may have needed to be updated in order to properly work with this security measure. There are 3 different errors that you may see logged in your syslog: missing csrf_token - This error happens if you have plugins that have either not been updated to conform to the security system or the version of the plugin you are running is not up to date. Should you see this error, then check for and install updates for your plug
    1 point