Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 09/13/19 in all areas

  1. 6 points
    Sneak peak, Unraid 6.8. The image is a custom "case image" I uploaded.
  2. 2 points
    So I have installed a 6.6.7 unRAID with freshly formatted HDD. I tested around 10 movies hosted on rclone mount and NO ISSUE so far !!! It seems to be working flawlessly, I am so relieved
  3. 2 points
    There is an rc4, but it doesn't fix the slow array problem.
  4. 2 points
    The URLs missing is because of the multitude of mistakes the guys were making on that field, ca is now filling it out for them. Hit apply fix on each of them The update available constantly is due to a change at dockerhub. Install or update the auto update plugin which will patch the OS for this Sent from my NSA monitored device
  5. 2 points
    HOW TO TEMPERATURES VOLTAGES FANS - Go to http://unraid:19999/netdata.conf (change unraid for your unraid servername or ip, my case is called unraid) - Paste the contents in a text editor - Find the [plugins] section - Change the line where says # python.d = yes for python.d = yes (so remove the # at the beginning of that line) - Copy the content of your text editor and paste the content in a new file called netdata.conf in /mnt/user/appdata/netdata (or wherever you have configured the data of your unraid) - Now copy and paste the content of this: https://raw.githubusercontent.com/netdata/netdata/master/collectors/python.d.plugin/python.d.conf in a text editor - Find the line # sensors: yes and change it for sensors: yes (remove the # at the beginning of that line) - Save this file as python.d.conf in /mnt/user/appdata/netdata - Create a folder python.d in /mnt/user/appdata/netdata - Copy the contents of https://raw.githubusercontent.com/netdata/netdata/master/collectors/python.d.plugin/sensors/sensors.conf in a text editor - Check the lines that starts with types: and add a # at the beginning of each sensor that you DON'T want to have in netdata - Save this file as sensors.conf in /mnt/user/appdata/netdata/python.d - Restart the Docker of netdata, and you will see a new section called Sensors and there all your temperatures and voltages and more If after all of this, still not works, I recommend to install Dynamix System Temperature and configure it properly, you should be able to see temperatures in the footer of unraid admin web, as that tool configures the command sensors to work as expected and therefore the plugin for netdata can read those sensors too. Hope this Helps
  6. 2 points
    Personally I wouldn't ever trust any IOT device to be on the same network as everything. Security isnt the highest priority for the manufacturers as they try and gain market share. Sent from my NSA monitored device
  7. 1 point
    Yes, that's right: the man, the myth, the legend Spaceinvader One has graciously agreed to sit down for an interview with us. If you could ask him something, what would it be? Best questions will make it in to an upcoming interview blog. Fire away!
  8. 1 point
    Posted the same thing on the unRAID Users & Help page on FB, but here's my status: Upgraded to the new release 2 days ago, on 9/19/2019. Have a Sonarr container. Rebuilt the DB from scratch last night. Using the path /mnt/user/... DB is already corrupt, with Sonarr logs showing "yesterday" as the time. Have a Radarr container. Using the last good backup I could find. Using the path /mnt/disk*/.... DB is also corrupt. first error shows as 3:51PM today (CST), so made it a little longer. If there's anything else I can do to help or test... *please* let me know. I'd love to get this resolved. Attached diagnostics file... drogon-diagnostics-20190920-2109.zip
  9. 1 point
    It’s definitely a compatibility with the 10Gtek intel modules and the X520, no link flaps since I installed the genuine intel module. i just migrated my esxi server to Proxmox, using a thunderbolt 3 enclosure with another 10Gtek module plugged into an x520, after it installed I was pinging hosts on the network and it was was down up and down like nobodies business, had a 60% loss rate on ping. went searching in my magic networking box as I knew I had another intel module (but wasn’t sure what type it was), luckily it was a also MMF SR module, switched that in and straight away ping was behaving and the link stopped flapping. i’ve not Had any issues with the 10Gtek modules in MikroTik, UniFi or Aquantia devices, just the intel ones. you live and learn.
  10. 1 point
    What his real job is, Because his video's are top quality and great knowledge passed onto this community. How does he find the time. Much appreciated
  11. 1 point
    Currently unRAID uses basic auth to enter credentials for the web gui, but many password managers don't support this. Would be great if we could get a proper login page. Examples This kind of login page always works with password managers. This does not
  12. 1 point
    I’m ready for a 6.8-rc1
  13. 1 point
    I just don't think it's the card, especially if you have gone through three so far. Mathematically/Statistically speaking, you are out of bounds for thinking it's the card at this point 🙂 Unless, of course they are all using the same ix driver, and you are triggering a bug somewhere (I have seen things like tcpdump trigger port flapping in LACP bonds before. But that was a Cisco switch and a Broadcom SR-IOV card).. But with that said, I have intel based NIC's and never had an issue..... Do you have any other 10Gb switches other than the Mikrotik? What's the opposite 10Gb device you have on your network? If I look at your topology correctly, your gigabit everything else except for your link between the Mikrotik and your server? 10Gb won't help you if your link from your unifi switches (which appear to be all 1Gb) are 1Gbe. Unless you are using the SFP1 and 2 on your 16 port PoE as a bonded pair (that needs to be setup properly in your UCK as well, and the Mikrotik would also need to support it) into your Mikrotik? But even then, the rest of your devices are 1Gbe, so even if all your clients were saturating the bond, you would max out a 2Gb since those are not SFP+ ports. Sorry, I know I am more looking at your layout then answering your question, but I am curious how you have it all hooked up....
  14. 1 point
    Try this http://thinlinx.com/. I'm running VM Win10 on unRaid which is in the basement and use rPi as a thin client. Works perfect.
  15. 1 point
    I think that there is a problem with the unraid tool that checks upgrades.....lots of people seeing it with linuxserver dockers. There were some threads about it. Just boarding flight so cant look! Sent from my SM-N950F using Tapatalk
  16. 1 point
    You can just upgrade/replace the two efi files (EFI/CLOVER/CLOVERX64.efi and EFI/BOOT/BOOTX64.efi, they are the same file) which download from github instead of install whole directory by pkg or iso.
  17. 1 point
    There have been a couple of problem areas that LimeTech is addressing to fix before releasing the 6.8-rc series. https://forums.unraid.net/bug-reports/stable-releases/sqlite-db-corruption-testers-needed-r598/page/7/?tab=comments#comment-5428 and https://forums.unraid.net/bug-reports/stable-releases/67x-very-slow-array-concurrent-performance-r605/page/8/?tab=comments#comment-5448 They were hoping at the time that these problems could be quickly resolved and that a 6.7.3 stable could be released first but they both have proven to be quite difficult to solve. There was a post some place where Tom provided more details on what their initial thinking was but I can't find it at this point.
  18. 1 point
  19. 1 point
    Now thats a constructive reply!
  20. 1 point
    The fix that Auto Update is applying is the same fix that is in the up coming (soon) 6.8
  21. 1 point
    Due to a change at docker hub unraid always reports an update is available. Installing the auto update plugin (even if it's not enabled will fix this for you) Sent from my NSA monitored device
  22. 1 point
    Just found those instructions myself and jumped over here hoping to find that the @ symbol have been fixed or was about to be fixed... Guess not. Any hint on where I would look to find the reason the @ symbol is verboten?
  23. 1 point
    Yes. -rc4 doesn't fix the issue, during testing was fooled by caching. Thought I accounted for that but it was late at night. The Linux block layer has undergone significant changes in last few releases, and I've had to do a lot of re-learnin'.
  24. 1 point
    It is not clear if there will ever be a 6.7.3 stable release or whether the next stable release will be 6.8.
  25. 1 point
    unraid really needs a better way of browsing files than using a docker file manager, using the command line or using another pc on the network. would be great to have a simple file browser built into the web ui that allowed you to browse your local files and do simple functions like copy, move, delete, rename, and open some files (documents, videos, music, and text files for example). Basically something like dissident.ai built right into the webui.
  26. 1 point
    nope, its been requested a number of times by users on the plex forum but its apparently a bit 'tricky', at this time you have two options:- 1. as previously mentioned, roll back to 6.6.7 and/or 2. buy yourself a cache drive and relocate plex config to the cache. im assuming you are running unraid 6.7.x and im also assuming you have /config for plex defined as /mnt/user/appdata (which will target array) and dont have a cache drive, right?
  27. 1 point
    Hi @robsch, I will have to think about how to do that and test it out. Right now it can only move the final video to "/output". Also, I kinda like everything for me to be in the root of /output so I would have to make it an optional setting at startup. I'll let you know what I come up with. My first guess would be to end the script with "mv $1 /output$1". Easiest way I can think of right off hand, it would move for example "/watch/movie/movie.mp4" to "/output/watch/movie/movie.mp4" would that work for you? The comskip.ini is only for comskip settings like commercial detection schemes, cpu threads, etc.
  28. 1 point
    You can get LSI cards from many different vendors on E-bay and the cost is quite reasonable-- <$90US. Read the offers carefully and vet the vendors with care as there are some 'bad' actors selling counterfeit cards. I believe that many of the LSI cards that Johnnie listed are discontinued as that should be a clue when someone is selling 'new' ones. If you are uncomfortable with flashing (or crossflashing), some vendors will provide cards with it already done. Be care on E-bay with the LSI Model numbers. Some vendors will list the card model number based on the hardware but the LSI part number also refers to the software/firmware installed on the card and LSI RAID software/firmware versions may not work with Unraid.
  29. 1 point
    actually even for the appdata on cache, there will be 2 setup 1. map directly to /mnt/cache/xxx 2. map to user share /mnt/user/xxx with setup "use cache disk" only by testing on this 2 setup, we might be able to isolate if the issue is fuse related or not
  30. 1 point
    If you're curious, here is the bug report regarding this (even though it's not a bug since you're bypassing the system)
  31. 1 point
    9th Gen QSV is not yet supported by Unraid. The next version will include the necessary kernel/drivers to support the newer CPU’s.
  32. 1 point
  33. 1 point
    go into your bios set primary display as the geforce 210
  34. 1 point
    I wanted to summarize how I got Mullvad working with DelugeVPN as I had to piece together several "solutions" from different comments in this thread and there was some incorrect info; likely old. First go to https://mullvad.net/en/download/config/?platform=linux (you may have to sign into your Mullvad account first), select a region, leave "Use IP addresses" and "Connect via our bridges." left unchecked, then click "Download". This will download a .zip file with all your config and cert files. The .zip file will contain a folder with the following files: mullvad_ca.crt (the cert file) mullvad_<whatever region you selected>.conf (the config file) mullvad_userpass.txt (a text file with your account number) update-resolv-conf (some file with no file extension that I have no idea what it does lol) You will extract these files later after we do the initial set up for Deluge VPN. Next grab binhex-delugevpn from Community Applications (you've probably already done this if so just click "edit" on the binhex-delugevpn docker container) and adjust the following container settings: Host Path 2 (Container Path: /data) set this to your downloads location; usually a share you created. Mine is /mnt/user/Downloads. If you are using Sonarr or Radarr it should be the same /data path they use. Key 1 (VPN_ENABLED) should be set to "yes" Key 2 (VPN_USER) should be your Mullvad account number; a 16 digit number you received when you set up your Mullvad account which also can be found in mullvad_userpass.txt. Do not include the "m" as shown in the .txt file, just the 16 digit account number. Key 3 (VPN_PASS) same account number as Key 2, no "m". Key 4 (VPN_PROV) set to "custom" Key 6 (STRICT_PORT_FORWARD) set to "yes" Key 8 (LAN_NETWORK) put the first 3 numbers of your routers IP (most likely 192.168.1) followed by .0/24 (example "192.168.1.0/24") Everything else can be left alone. Click apply. It will pull the container and run it. Open a file explorer and navigate to <your server>/appdata/binhex-delugevpn/openvpn/ Now extract the files: mullvad_ca.crt mullvad_<whatever region you selected>.conf mullvad_userpass.txt update-resolv-conf from the .zip you downloaded from Mullvad into <your server>/appdata/binhex-delugevpn/openvpn/ change the file extension of mullvad_<whatever region you selected>.conf to mullvad_<whatever region you selected>.ovpn Open mullvad_<whatever region you selected>.ovpn with a text editor and add the following lines to the bottom: pull-filter ignore "route-ipv6" pull-filter ignore "ifconfig-ipv6" Save the file. Restart the binhex-delugevpn container That should do it. I hope this helps.
  35. 1 point
    hello , reinstalled the plugin, it worked now. i thinks the reason not working first time is download error.
  36. 1 point
    You can delete the Plus key. It will have been blacklisted when you upgraded to Pro so cannot be used elsewhere.
  37. 1 point
    That's a new one for me. Check that file /config/etc/letsencrypt/renewal/website.com.conf to make sure it contains all the parameters including this line: dns_cloudflare_credentials = /config/dns-conf/cloudflare.ini
  38. 1 point
    Can confirm CA Auto Update resolves everything.
  39. 1 point
    I wish you luck. When you find a solution, would you please write it up and post it in one of the FAQ stickies on this subforum-- General Support. It will probably help some other person in the future.
  40. 1 point
    Take a look at the Tips and Tweaks Plugin. You can play with settings there to influence how Unraid handles its RAM and when it writes to disk. Definitely read the thread for suggestions.
  41. 1 point
  42. 1 point
    Today's update to CA Auto Update will automatically apply the fix for this issue on affected systems (Whether or not the plugin is even enabled). You will though have to check for updates manually once to clear out the old update available status. If you are running @ljm42's patch script, you can safely remove it, as the Auto Update will not install the patch once 6.8+ is released.
  43. 1 point
    Alright- I'm going to experiment with taking away "Upvote", leaving "Like" and adding a "Haha" and "Thanks" to keep things positive around here. As always, if you have feedback or comments on this, feel free to respond here or DM me! Cheers
  44. 1 point
    Best way forward is to backup cache data, re-format and restore. Those connection issues with SSDs are usually cable related, Samsung SSDs especially can be very picky with connection quality, also keep in mind that trim won't work when connected to that LSI, so if possible use the Intel SATA ports instead for both.
  45. 1 point
    Do you see any advanced virtualization tools coming to unraid such as VM cloning, snapshots, IP management of VM’s, oversee other VM’s of other unraid machines, and managing those?
  46. 1 point
    same issue ubtunu 18.04 by running: sudo dhclient enp3s0 I was able to get a connection again
  47. 1 point
    Zombie thread but it wasn't answered and I haven't found a current one that does yet. Anyway its first page on google results so here goes. braaaaaains! This is unfortunately incorrect, at least in 2018 it is. A Microsoft Account is not an email account. It is a Microsoft Account that is registered to your device and software licenses (for MS products), your Store account, your Skype acct and it links your user profile experience across Windows machines. That is why every time you log in with your MS account on a new PC, you have to authorize that by multi-factor auth and lo and behold you have the same desktop image and other stuff. You can and should use your MS account with your unRAID shares because it's The Right Way and it's easy. But there is no integration to MS directly; you will have to update your password on unRAID when you change it with MS. This is actually how it's done on every NAS on the market that I've seen, because its been supported by Samba for years. Unfortunately the GUI on unRAID has not caught up with the times. You can use your Microsoft Account with unRAID; you just need to know how to edit a few config files, and you need to restart samba (i.e. stop/start the array). - In the GUI, create a user with the short name for your account. e.g. in my case I called the account 'dude'. Set a password for dude that matches your MS account. This will create a unix account and a matching samba account - edit /etc/passwd (and /boot/config/passwd probably - I did) and change "dude" to "youraccount@yourdomain.com" to match your MS acct - edit /etc/shadow (and /boot/config/shadow) likewise - edit /boot/config/smbpasswd as well, to change the unix username to your MS account Now when you restart the array its going to restart samba. You can probably bounce samba manually; I've not tried to see if unRAID handles that gracefully yet. Someone else might chime in the confirm. Once samba is restarted, the new account is enabled. Okay now on the client machine you are connecting from, I'm assuming that you are logging in with a standard Microsoft Account. You should have no drives mapped (especially with credentials saved) and you can always restart the Workstation service to clear any open sessions to the server. Once you've done this, if you navigate to the unRAID server in your Windows Explorer network browser, it should not prompt you for credentials ASSUMING that you configured basic permissions for the user account to access your shares. This works fine because its TOTALLY SUPPORTED BY SAMBA and standard on almost every NAS product I've seen but unRAID. I'm just going to push a feature request to add the ability for the GUI and the supporting scripts to eat a proper email address for a MS account. BTW the form of a MS account in SMB protocol is MicrosoftAccount\you@domain.com If the target was a windows box, it would need to have that MS account created locally and have been logged in once before. Samba is not so picky because it has SAVED the password that you gave it. The difference is that real Windows 8 or 10 host knows how to ask Microsoft if the credentials are valid (and it caches it for a time, which you could look up - I've forgotten). I find it hilarious when people say oh this is not standard or supported when it's a Microsoft protocol so what they say and do is the standard. Cheers from your friendly neighborhood MCSE.
  48. 1 point
    I solved this on my system: Asus Rampage IV Formula / Intel Core i7-4930k / 4 x NVIDIA Gigabyte GTX 950 Windforce, with all graphics cards passed through to Windows 10 VMs. The problem I was having was that the 3 cards in slots 2, 3 and 4 pass though fine, but passing through the card in slot 1, which is being used to boot unRAID, freezes the connected display. I explored the option to add another graphics card. A USB card won't be recognized by the system BIOS to use for POST. The only other card I could add would be connected by a PCIe 1x to PCIe 16x riser card (which did work by the way for passthrough, but a need to pass through a x16 slot), but it would require modding the mainboard BIOS to get it use it as primary. So I looked for another solution. The problem was caused by the VBIOS on the video card, as mentioned on http://www.linux-kvm.org/page/VGA_device_assignment: To re-run the POST procedures of the assigned adapter inside the guest, the proper VBIOS ROM image has to be used. However, when passing through the primary adapter of the host, Linux provides only access to the shadowed version of the VBIOS which may differ from the pre-POST version (due to modification applied during POST). This has be been observed with NVDIA Quadro adapters. A workaround is to retrieve the VBIOS from the adapter while it is in secondary mode and use this saved image (-device pci-assign,...,romfile=...). But even that may fail, either due to problems of the host chipset or BIOS (host kernel complains about unmappable ROM BAR). In my case I could not use the VBIOS from http://www.techpowerup.com/vgabios/. The file I got from there, and also the ones read using GPU-Z is probably a Hybrid BIOS, it includes the legacy one as well as the UEFI one. It's probably possible to extract the required part from the file, but it's pretty simple to read it from the card using the following steps: 1) Place the NVIDIA card in the second PCIe slot, using another card as primary graphics card to boot the system. 2) Stop any running VMs and open a SSH connection 3) Type "lspci -v" to get the pci id for the NVIDIA card. It is assumed to be 02:00.0 here, otherwise change numbers below accordingly. 4) If the card is configured for passthrough, the above command will show "Kernel driver in use: vfio-pci". To retrieve the VBIOS in my case I had to unbind it from vfio-pci: echo "0000:02:00.0" > /sys/bus/pci/drivers/vfio-pci/unbind 5) Readout the VBIOS: cd /sys/bus/pci/devices/0000:02:00.0/ echo 1 > rom cat rom > /boot/vbios.rom echo 0 > rom 6) Bind it back to vfio-pci if required: echo "0000:02:00.0" > /sys/bus/pci/drivers/vfio-pci/bind The card can now be placed back as primary, and a small modification must be made to the VM that will use it, to use the VBIOS file read in the above steps. In the XML for the VM, change the following line: <qemu:arg value='vfio-pci,host=01:00.0,bus=pcie.0,multifunction=on,x-vga=on'/> To: <qemu:arg value='vfio-pci,host=01:00.0,bus=pcie.0,multifunction=on,x-vga=on,romfile=/boot/vbios.rom'/> After this modification, the card is passed through without any problems on my system. This may be the case for more NVIDIA cards used as primary adapters!
  49. 1 point
    As long as both network cards follow GB specs, crossover cables aren't necessary. Auto-MDIX is part of the GB spec, so the cards will figure out automatically what pairs to use. Real question is what is the end goal, because writing to a parity protected array with current common hardware can't even saturate 1 GB connection.
  50. 1 point