Leaderboard

Popular Content

Showing content with the highest reputation on 03/11/21 in all areas

  1. People with specific Seagate Ironwolf disks on LSI controllers have been having issues with Unraid 6.9.0 and 6.9.1. Typically when spinning up the drive could drop off the system. Getting it back on would require checking, unassigning, reassigning and rebuilding its contents (about 24 hours). It happened to me three times in a week across two of my four affected drives. The drive in question is the 8TB Ironwolf ST8000VN004, although 10TB has been mentioned, so it may affect several. There have been various comments and suggestions over the threads, and it appears tha
    3 points
  2. Came from 6.9-beta-35 I had some issues where my drives wouldn't spin down using 6.9.0 with Auto Fan. Updated to 6.9.1 and I haven't had any issues that I can notice. I made sure all my dockers and plugins are up to date along with the Nvidia plugin and shut everything down, rebooted and so far everything is green or spun down just like I like it.
    2 points
  3. Again not Asus, if you are man enough then go pfsense, I'm using a Qotom silent passively cooled unit and it is simply fantastic! I believe it can do symmetrical gigabit encrypted, best £280 aid I've ever spent £180.12 16%OFF | Qotom Mini PC with Core i3 i5 i7 processor and 4 Gigabit NICs, AES-NI, RS232, Fanless Mini PC PFSense Firewall Router https://a.aliexpress.com/_m0fcObV Sent from my iPlay_40 using Tapatalk
    2 points
  4. I think you get me wrong... Use the iGPU (QuickSync - this is also Hardware transcoding) not the CPU (this is Software transcoding), simply install my Intel-GPU-Top Plugin that will enable the iGPU and then you have to add a device to the Plex/Jellyfin/Emby container template with the path '/dev/dri' and remove the Nvidia entries: That should be no problem as long as you don't transcoding only 4K files (but 8x 4K transcodes is also too much for the P2000). This is completely off topic here, eventually start another thread and mention me there, or look for
    2 points
  5. To second this, I tried it last night and it seems to be going well. It was easier than I was expecting. I'm just creating a General Support post collating the entries spread across the 6.9.0 & 6.9.1 topics and including the resulting step-by-steps that I took if you don't mind.
    2 points
  6. After doing some digging I believe I have solved my issue. It seems like it is somewhat a known bug on Asus X99 motherboards. Mine is an Asus X99-WS/IPMI. I am on the latest BIOS so updating was not an option. The solution was to add "pcie_aspm=off" to my syslinux configuration. After a reboot I appear to no longer be getting errors. Fingers crossed it stays fixed. If anyone has anything to add feel free to chime in. If I don't have any errors tomorrow morning I'll mark this solved.
    2 points
  7. Done and done. And yeah - totally a 1% problem to have. It's just such a pretty card though...
    2 points
  8. You have a old template and it will always add the ports on a container update. Eventually try to delete the container (note your existing settings down) and pull a fresh copy from the CA App and set it to the same values as before so this won't happen any more...
    1 point
  9. Well, carp. It appears that my front-of-case USB3 ports are non-functional. I plugged the dock into the USB2 port and it showed right up. Now to wriggle around behind the case and plug it in the back - I am not waiting for an 8TB drive to preclear via USB2...
    1 point
  10. I'd heard of unRAID from various places, but had been rocking a Synology NAS since about 2016. It suited my needs absolutely fine, but I had been pushing it more and more as of late. The final straw came when some docker containers stopped working due to the kernel being too old. I had thought about building a new NAS myself off and on over the years, but this felt like the right time. I looked into several solutions and settled on giving unRAID a go. The trial made it an easy choice. I built my new machine and fired up unRAID last night to play about with it. This
    1 point
  11. @ich777 Okay so i figured out the issue so plex was working the whole time its only the some of my stuff was being transcoded and some was not depending on codec.
    1 point
  12. Okay so jellyfin works but cant figure out plex. Ill try binhex.
    1 point
  13. This is what I said. OK will try later. (made the file and folder, just waiting for reboot) I did not run any beta (for this beta cycle) - my server was too busy these last few months.
    1 point
  14. cool ill give that a try
    1 point
  15. I'm not running a b550, but a x570 board. It's my second x570 board. I also had a few conversations with b550 users. From my expierence, take a look on different boards and look for the ones that do seperate the devices in iommu groups in a good way. But keep in mind that a bios update can change everything in that matter. Also I don't recommend to bind usb controllers to vfio on boot. Just leave them as they are and attach your usb devices as you want. Then, take a look on the site for system devices and make sure that all devices needed for vm's are seperated from the c
    1 point
  16. Never noticed. But, any/all files I've got that are over 4GB would be media files, and I'm not too worried about anything infecting them since it would simply cause display corruption. I do worry about executable files, and if they're over 4GB in size then there's obviously something very wrong with how they're programmed.
    1 point
  17. Yeah, there is a partial outage over the last 2 days.
    1 point
  18. You also have to install ValheimPlus to your local game installation, instructions on how to that are here: Click
    1 point
  19. Or just disable the built-in nic in the BIOS, unless your switches support failover, bonding etc.
    1 point
  20. I noticed Zombie Panic! Source is now on the CA list! Thank you so so much @ich777
    1 point
  21. I didn't know SATA1 wasn't supported, good catch though. Make sure to try all the breakout cable ports, check the drive works in both 2 SAS ports and each breakout sata works. If it does then the SBR you've got flashed is the correct one.
    1 point
  22. Die Auflösung von VNC erhöhst du, in dem du den Treiber installierst. Der ist in dem libvirt Paket, was du vermutlich als CD Laufwerk siehst.
    1 point
  23. I threw the card into the other computer (an old oem machine with a motherboard from 2011!) along with a fresh unraid on a spare usb and am gettting the same message in the plugin and logs. I think there's either a problem with the card itself or maybe, as some digging online suggests, requires a way older nvidia driver to function (can't find the link but I think it was for quadros older than kepler). Or maybe the motherboards I'm using are just way too old. Is it possible to use a driver older than those select-able in this plugin? I never changed any VM settings and was refer
    1 point
  24. No I'm not responsible for this part of unRAID but I'm happy to help.
    1 point
  25. You can install my Intel-GPU-TOP Plugin from the CA App.
    1 point
  26. Yea, I got busted by the permissions cop too.
    1 point
  27. I upgrade to 6.9.1 from 6.8.3 and it went well using the above process from @NAStyBox! Thanks unRaid Devs! However, I think step 3 moved my VMs off of the SSD cache and into the array. Can I just move them back to the SSD?
    1 point
  28. Just an update. Tested both 2 x 16gb on there own no issue.. Had a friend of mine said to increase voltage on memory. WIll test again tomorrow see if i get the issue then up the voltage and try again. Fingers crossed.
    1 point
  29. i was thinking through what you said and you might get away with just the rebuild! after the rebuild completes the contents of the rebuilt data drive will agree with what parity plus all the other data drives contain, but the contents are likely to be badly corrupt at best. However since you said you were not worried about preserving the drives contents, if you now follow the procedure for Reformatting a drive the fact that the contents may currently be invalid is not relevant as the format operation will create a new empty file system and update parity accordingly. Note that
    1 point
  30. Normally I would have, but I just didn't have a chance to yet. My life is still a bit of a mess after moving (I'm currently sitting on the floor while I type this because most of my furniture won't arrive for another week haha). I'm planning on incrementing the version later today though, but I wanted to get the quick and dirty fix out sooner rather than later.
    1 point
  31. Have you tried to load the Intel module for your onboard graphics card? You can also try to: Press CTRL+ALT+F1 this should bring you back to the command line Log in with your root user and password Then type in 'modprobe i915' (without quotes) Then type in '/etc/rc.d/rc.4' (without quotes) And please report back.
    1 point
  32. Yup, also worked without configuration changes for me as well.
    1 point
  33. 1 point
  34. Thx for the fast Update (6.9.1)! My HDD´s spin down as they should, now (with enabled AutoFan).
    1 point
  35. Thank you very much! It works pertfectly! Problem solved for me.
    1 point
  36. So, Sonarr v3 is FINALLY here, its out of beta and is now the latest release, if you want to switch from Sonarr v2 to v3 then simply pull down the 'latest' tagged image. However, if you want to stick on Sonarr v2 then please do the following:- Go to unRAID Web UI/Docker/left click Sonarr/Edit and change the value for 'Repository' to:- binhex/arch-sonarr:2.0.0.5344-1-04 Click apply to pull down v2 image. Note:- There will be NO further development on v2 going forward. If you are using the tag name of 'v3' then please do the following to
    1 point
  37. Hey, As for default image I don't see why not, I'll look into it. I currently have no plans to provide a https end point so I would recommend using a proxy for now. I will also look at adding progress for the parity check and mover, shouldn't be a massive change. Let me know if there is anything else Cheers
    1 point
  38. Not sure if this is the correct place to add some general thanks but i think it's the most general place to express my gratitude specifically. The latest builds including the various GPU drivers have me chuffed and appreciative. I use an old Powercolor HD3540 GPU for local admin of my unraid box that I'm extremely reluctant to get rid of as it's a rare PCIe*1 GPU which leaves all my other PCIe slots open for the usual high-bandwidth stuff. I've been struggling along with the resolution of the HD3450 for around a couple of years now since a release (can't rem
    1 point
  39. Fixed the issue. Not sure if this is already documented somewhere. The /storage mount point is strictly configured to be read-only (and a safe thing to do for security). In order to restore files back, you need to create a new mount point in the container configuration. In my case, I just added /restore and mapped to /mnt/user/scratch/restore. Provided destination /restore to restore job and it worked just fine.
    1 point
  40. This tweak has nothing to do with your RAM usage. The source of your problem must be something else (or you used a path, that targeted your RAM). Do you use transcoding to RAM and use the /tmp or /shm folder? Than this is your problem. Next time you should investigate the RAM usage before restarting your server / containers. Use this command: ps aux | awk '{print $6/1024 " MB\t\t" $11}' | sort -n In addition check the sizes of your Ramdisks as follows: df -h -t tmpfs And finally you could check the size of your tmp folder which is even located in your RAM: du -sh
    1 point
  41. Thanks @KptnKMan and @SpaceInvaderOne. I will be using this information to overhaul my old unraid build. I too think it would be amazing if Unraid devs decide to add all sorts of advanced VM configuration in the Web UI.
    1 point
  42. Check the settings of all of your docker containers, one (or more) of them is configured wrongly.
    1 point
  43. Thanks @SpaceInvaderOne I appreciate the compliment. Just hoping that this helps someone else. I really hope that we could get a VM advanced UI for configuring the PCIe settings when using graphics card or sound card: - multifunction on/off - bus - slot - function These are PCIe devices, so it seems to be a common setting, that would translate to the XML like the other UI settings, overwriting the default. This would go a long way to making this easier to fix.
    1 point
  44. Great write up. Thanks for taking the time for posting what worked for you.
    1 point
  45. Sounds like you need to watch some videos from Space Invader, they helped me a lot... He has some other updated videos after this one if it doesn't fully solve your issue... Some key points though, change you VM machine type from the default that UnRaid gives (i440fx) and change it to Q35... If you can reinstall the VM with that, that is best, but if you have to keep your current VM than make sure to do some backups, then create a new VM but point it at the old image file (Don't skip the backups)... If you have an nVidia card that you are trying to passthrough, you wi
    1 point
  46. I also recently had this issue, right as i was about to try the manual way, i renamed the usb to "UNRAID" as per what it requires, i had forgot to close the usb installer, and as soon as i renamed it, it worked. In my case, the usb drive had no name at all, and adding a name fixed it. hope this helps someone!
    1 point
  47. Thanks to thomast_88 for setting up this docker I've set it up and muddled through learning git at the same time and just wanted to post a config I've came up with to let you use the "Linuxserver.io - letsencrypt" docker to reverse proxy the this (gitlab-ce) docker without having to use SSH etc to edit the gitlab.rb config file or any other suggestion I've seen here that involves a workaround of sorts like Gizmotoy's port workaround (although it did work). ##### How to use reverse proxy gitlab-ce with the letsencrypt docker Summary: I use the letsencryp
    1 point