Leaderboard

Popular Content

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

  1. Let's work together to repair this relationship. I love this community and what unRAID has become. Seeing it evolve over a decade shows the strength of this one united large family. Let's fix this, we are better than that. I have re-read the comments and although they are good points, this does not help us re-unite. @limetech, came through and did the initial steps with a public apology attempting to repair the relationship and yes, wounds do not heal overnight, but it is a two-way street. I cannot repair it, but from a community member perspective, it hurt
    6 points
  2. Please point one of these out to me. FWIW I haven't received any email or PM from someone trying to be a Comm Dev with unanswered technical questions. I don't have a lot of time to monitor the entire forum. Mostly these days I monitor Prerelease and any topics which are specifically brought to my attention. Also I've always said that Unraid is not for everyone. We really have tried hard though to remain friendly and cooperative. If you feel like you have not been treated fairly, I apologize for that and suggest perhaps a different server solution would be better for you to be
    3 points
  3. Tom has done all he could be expected to do in this situation. Unfortunately, the genie is out of the bottle and cannot be put back. He has acknowledged that the rift was entirely of his making and has outlined every misstep he made which caused the situation. Some of the LSIO guys impacted by this are probably taking a break to let things simmer down and consider what, if anything, should be their public response post-apology. It may in fact be best to let it alone publicly for a while. If the schism is repaired behind the scenes and (and as alluded to by Jon P.) steps are tak
    3 points
  4. Those following the 6.9-beta releases have been witness to an unfolding schism, entirely of my own making, between myself and certain key Community Developers. To wit: in the last release, I built in some functionality that supplants a feature provided by, and long supported with a great deal of effort by @CHBMB with assistance from @bass_rock and probably others. Not only did I release this functionality without acknowledging those developers previous contributions, I didn't even give them notification such functionality was forthcoming. To top it off, I worked with a
    2 points
  5. If your data is sensitive and valuable, I wouldn't transport 3.5" spinning hard drives like that. If you want some flexibility and ruggedness, it would be worth your while to use SSD's and have spinning drives for backups at an offsite, stationary location. It'll significantly lower the weight of your system as well as require far less room.
    2 points
  6. Although I can't speak for my fellow team members, decisions like these usually aren't taken by a single event, in most cases it's just the final drop...not saying it was like that in this case....but don't start "expecting" stuff in return just because a cheap apology was made. Some new developers trying to get into the Unraid community are belittled and left hanging without a proper response, you don't see them getting an apology.... IMO, the backlash was just too big in this case and that's why you get this nice apology, just simple business damage control at its fin
    2 points
  7. In a world where most of the people are even unable to admit mistakes and never apologize for anything I highly appreciate @limetech statement. Everybody doing mistakes on a daily basis and nobody is protected against that - PERIOD! IMHO -- True stature shows itself in small things and an apologize was stated. Now its time that the devs show true greatness and accept Toms apologize.
    2 points
  8. Just a little feedback on upgrading from Unraid Nvidia beta30 to beta35 with Nvidia drivers plugin. The process was smooth and I see no stability or performance issue after 48h, following these steps : - Disable auto-start on "nvidia aware" containers (Plex and F@H for me) - Stop all containers - Disable Docker engine - Stop all VMs (none of them had a GPU passthrough) - Disable VM Manager - Remove Unraid-Nvidia plugin - Upgrade to 6.9.0-beta35 with Tools>Update OS - Reboot - Install Nvidia Drivers plugin from CA (be patient and wait
    2 points
  9. Nvidia-Driver (only Unraid 6.9.0beta35 and up) This Plugin is only necessary if you are planning to make use of your Nvidia graphics card inside Docker Containers. If you only want to use your Nvidia graphics card for a VM then don't install this Plugin! Discussions about modifications and/or patches that violates the EULA of the driver are not supported by me or anyone here, this could also lead to a take down of the plugin itself! Please remember that this also violates the forum rules and will be removed! Installation of the Nvidia Drivers (this
    1 point
  10. DVB-Driver (only Unraid 6.9.0beta35 and up) This Plugin will add DVB Drivers to Unraid. Please note that this Plugin is community driven and if a newer version of Unraid is released the drivers/modules has to be updated (please make a short post here or see the second post if the drivers/modules are already updated, if you update to a newer version and the new drivers/modules aren't built yet this could break your DVB support in Unraid) ! Installation of the Plugin (this is only necessary for the first installation of the plugin) : Go to the Communit
    1 point
  11. Please note: The author of the application is aware that the software needs rework. This is ongoing at the moment, so if you find the application to be a bit hard to work with, maybe you want to be a bit patient and wait for the rework progressing. As it is now, with fiddling the app can be made to work, but it's not very smooth. I still think this application provides a great benefit to the community of doujinshi collectors and am not going to pull the (marked as beta in CAs as before) template for it. Thank you and happy reading! ___________________
    1 point
  12. Mit Hilfe von @ich777 und @zspearmint freue ich mich, unraid.net auf Deutsch zu enthüllen. 😀
    1 point
  13. I'd buy this service right now. I only go near my Unraid once every few years and waste far too much time trying to relearn stuff. I'd much rather just hand money to someone to solve it for me. If you want some paid support work, please contact me +6421742634 Current problem, can't format a newly installed drive
    1 point
  14. You found APCUPSD conflict with Corsair iCue 👍 Would you provide the exactly hardware info. so other member could quickly identify the problem device next time. Edit : Got it .... Commander Pro
    1 point
  15. It is expected. NUT show realtime power usage ? I don't think so, my first UPS BE-550G-UK won't show that in NUT nor APCUPSD, it is hardware limitation not software issue. I just try troubleshoot why APCUPSD not work.
    1 point
  16. OK Seems relate Corsair iCue, could you try disconnect it ? Oct 31 11:18:19 tower kernel: hid-generic 0003:1B1C:0C10.0001: hid_field_extract() called with n (128) > 32! (swapper/5) https://forum.corsair.com/v3/showthread.php?t=189994&page=6
    1 point
  17. Thank you for sharing that link. I added a question to that thread.. There maybe could be a specific problem with non reference cards or something like that. At least I hope that 🙈 "Doable" sounds pretty good to me 🤪 Have a nice weekend!!!
    1 point
  18. FYI Important Security update to fix potentially vulnerable passwords: https://forum.rclone.org/t/rclone-1-53-3-release/20569
    1 point
  19. Unlikely that any filesystem resize will work due to being damaged, you can resize the partition by creating a new one on top of the existing one, same start sector but using the full disk.
    1 point
  20. Except that every feature added directly to the OS consumes RAM, whether you use it or not. Unraid isn't like pretty much any other OS that runs from a drive, everything is installed into fresh into RAM at boot time. That's why Unraid doesn't include drivers for everything normally supported in linux, because all that space in RAM would be wasted for 90% of users. Every feature that is included in the stock base of Unraid must be carefully evaluated whether or not the increase in RAM required to store the files used is worth it. It's kind of a double whammy, the files consume space
    1 point
  21. I think this is doable but be aware that someone posted already an Github issue that this doesn't work on Kernel 5.8> with an 5700XT... Unraid 5.9.0beta35 is already on Kernel version 5.8.18 and will be upgraded to 5.9.x EDIT: Forget to include the link to the Github issue.
    1 point
  22. ATM I'm using 6.9.0-beta1, every step is appreciated in this direction as it is for all of us. Take your time, I stay on my current version until either the community or unraid itself gets this implemented. BTW, thank you for your provided containers 🙋‍♂️
    1 point
  23. For the utilisazion in Containers it's too old because the driver won't support it. No this should be fine since you can install a older driver inside the VM so that your card will work.
    1 point
  24. Yep, all good and devices configured in Plex
    1 point
  25. An update on this to close it out. After replacing the SATA cable, and switching the SATA port the btrf errors continued after rebuild of the filesystem and docker image multiple times. I removed the suspect SATA SSD drive and went to a single cache drive and errors stopped. I have concluded that that SSD has failed and replaced it. All is restored and back to normal now.
    1 point
  26. Hi ICH777 I've worked it out. Turns out that a lot of the older TBS cards don't like anything other than PCIe Gen1. My server had all slots configured for Gen2. Switched these down to Gen1 in the BIOS and can confirm its all working. Thanks again for you hard work on this.
    1 point
  27. Welcome! I also use OMV on my old N36L. Great boxes...... paid £110 for mine and it's still happily chugging along after nearly 10 years.
    1 point
  28. Could be, maybe my welcome party has given me a bad aftertaste, then again it's just your opinion and we all have one. Having said that, it doesn't make it any less true.
    1 point
  29. Unhelpful, inflammatory, provoking and downright unnecessary. Also, if I was to define the set of values that makes this community group so strong I would say there isn’t a word in your post that would align with them.
    1 point
  30. Sounds pretty similar to my issue with the binhex plex container. After switching to binhex plexpass everything worked fine.
    1 point
  31. Hi! thank you for your fast reply. You are absolutely right!!! That makes sense, because only SATA connected devices are affected. 08.00.0 was my Nvidia 2060 GPU I have added to the vfio config. After the install of the PCI device on the second 16x slot seems to change the IOMMU numeric order of these devices, as the following screenshot shows: Now my GPU has the number 09.00.0 (before 08.00.0). So I changed the config as you mentioned and now it works. Thank you so much for your help!!!! Have a nice day! Best regards, Reini
    1 point
  32. @ljm42 Thanks for your input. Will consider the zero value problem in a future release. I will publish this script only on github if I find the time to write it as a plugin. "frag -f" is sadly nearly useless as described in this post. As an example all my HDDs return a high fragmentation factor although no defragmentation is possible (as they mainly contain huge movies). Maybe it would be possible to calculate the real fragmentation factor by counting files and their sizes and devide them through 8GB while finally comparing this value with the value returned by "fr
    1 point
  33. As others have mentioned, we are actually growing as a company. When I started out early last year, I was the 4th FTE. We are now almost double that and I can assure you we are all working very hard to get this Stable release out. We also have some exciting things in store so please stay tuned! This has been a tough year for a variety of reasons. Even in the best of times, it's not easy growing as an all remote company but rest assured, we aren't going anywhere and have big plans for the future!
    1 point
  34. Acting uncharacteristically extreme sometimes when we get hurt is very human and understandable and my personal opinion is that is what a few of the fellas at @linuxserver.iodid after the exchanges on the previous thread. I have no reason to doubt the sincerity of this post by @limetech and therefore was hoping there would be some return comms from @linuxserver.io to do their part in repairing this bridge. It might be nice if those who “retired” or decided they were now “out” or were “quitting unRAID work” came back. It might also be nice that if some of the support threa
    1 point
  35. I had typed and re-read and re-typed what I said below because I wanted to make sure I said what I meant. I’d like to 100% agree with you on this, but I can’t completely, but I do to a point. You have to remember unRAID is partially open source which allows the community to add on to it. Those addons make unRAID very appealing and more popular than most mass storage options and at one time addons were mostly considered hacks. @limetech has spent 1000’s of hours improving security, improving the interface and implementing many many requests alongside what the community has don
    1 point
  36. Added psutil. Should be able to install using pip3 now
    1 point
  37. You mean like this? Yeah you can install the Ultimate UNRAID Dashboard I developed. It has this functionality and more. You can find it here: https://forums.unraid.net/topic/96895-ultimate-unraid-dashboard-uud/
    1 point
  38. This is true. Unfortunately communicating development plans like this (ad hoc, not centralized) is probably not the best way to go about it. Rest assured that Tom's post here was only the first step. Him and I have been having conversations about how we can better engage with the community beyond just this issue. Expect to see another post from me sometime this week with more details on this. At the end of the day we all realize how vital our community is to our continued success. I just hope that everyone can appreciate how big this community really is now, because managing expectations
    1 point
  39. It's not as if they've been very welcoming to new community developers wanting to get in on the unraid action....so something like this was bound to happen to older highly respected community developers....just my 2 cents. Luckily time heals all wounds and in 6 months time a new unraid user has no idea this even happened. Burning bridges is a thing and people will keep doing it.
    1 point
  40. I’ve been around a little while. I always follow the boards even though I have very little life time to give to being active in the community anymore. I felt the need to post to say I can completely appreciate how the guys at @linuxserver.io feel. I was lucky enough to be apart of the team @linuxserver.iofor a short while and I can personally attest to how much personal time and effort they put into development, stress testing and supporting their developments. While @limetech has developed a great base product i think it’s right to acknowledge that much of the
    1 point
  41. @trurl Please lock this thread. Due to an unexpected announcement from @limetech this is no longer required. I'm quitting Unraid work.
    1 point
  42. Great news. Crazy how they constantly focus on features benefiting more than 1% of the maximum userbase, right. 🤪
    1 point
  43. I think I figured this out from the binhex delugevpn log. https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md See Question 19. I used the new PIA files from the link therre and now NZB get is working again with VPN. PIA must have disabled their old servers. I am getting much better speed now in torrents and usenet. craigr
    1 point
  44. The shutdown option is now available in the version of the Parity Check Tuning plugin i released today. I would be interested in any feedback on how I have implemented it or any issues found trying to use the shutdown feature.
    1 point
  45. I personally like UnFire myself. Certainly better than UnOven, UnCool, UnBBQ, UnLava et al. Either way, this plugin may become the UnSun hero for some people in 2020/2021
    1 point
  46. After unsuccessfully changing the branch from 'latest' to 'dev' and running chmod -R 777 /mnt/user/appdata/pihole/ I found a solution: In my docker config I changed /mnt/cache/appdata/pihole/pihole/ to /mnt/user/appdata/pihole/pihole/ and /mnt/cache/appdata/pihole/dnsmasq.d/ to /mnt/user/appdata/pihole/dnsmasq.d/ All the error message seem to have gone away.
    1 point
  47. I've just realised I have/had the EAC3 'issue'. i.e. any video file with EAC3 audio requiring audio transcode down to 2 channgels (most of my client apps) won't play the file, I get the following log entry: "ERROR - [Transcoder] [eac3_eae @ 0x7e9840] EAE timeout! EAE not running, or wrong folder? Could not read '/tmp/pms-198c89ec-c5fa-4ceb-99dc-409b57434d00/EasyAudioEncoder/Convert to WAV (to 8ch or less)/C02939D8-5F8B-432B-9FD9-6E7F76C40456_522-0-21.wav'" I found a solution in this thread, just deleting the appdata\plex\..\Codecs folder and restart so it recreates it and everything see
    1 point
  48. Any plans for adding support for LTO backup? Speaking as a data hoarder, I know my server has grown to a size such-that a catastrophic failure would be almost impossible to recover from, yet 1:1 backup options are limited IF you want LONG TERM storage. Hard drives don't last for decades in cold storage, and I suspect many of us are only one good power surge away from disaster. A UPS and power conditioner transformer only protect you so far.
    1 point
  49. Turn on help on the cache settings. Cache: No means new files written to the share will go directly to the array, and the mover won't touch files already on the cache for that share What you want is Cache:Yes and run the mover, then make sure no new files are written to the cache by turning it back to Cache:No.
    1 point