HarryMuscle

Members
  • Posts

    40
  • Joined

  • Last visited

Everything posted by HarryMuscle

  1. Hi, sorry for the late reply. I've moved away from using Unraid, but ich777 and I have connected and he's currently providing this driver as an actual plugin for Unraid so it should be available going forwards for the various versions of Unraid. Thanks, Harry
  2. @hotio or @binhex any chance one of you guys would create one of your great Docker containers for Transmission? Looks like there's no solution out there for Transmission with VPN (preferably WireGuard). Thanks for considering this. Harry
  3. Can anyone recommend a good Transmission with WireGuard VPN Docker container? I don't believe binhex or hotio make one unfortunately. Thanks, Harry
  4. @binhex Since rTorrent by itself doesn't have a web GUI, would you consider making a Docker container with rTorrent and use Flood (https://flood.js.org) as the GUI (instead of ruTorrent that is used currently). Flood looks like a very nice looking modern GUI with a responsive interface that's great for all devices including mobile. Thanks, Harry
  5. The shutdown/reboot page doesn't match the rest of the Unraid user interface theme. I find it such a stark contrast to the rest of the interface that it actually bugs me. It would look so much nicer if it included the header and the page background color matched the theme's background color. Thanks, Harry
  6. Has anyone attempted to have the Shutdown/Reboot page match the theme of the rest of the Unraid user interface? I find it such a stark contrast to the rest of the interface that it actually bugs me :). It would look so much nicer if it included the header and the page background color matched the theme's background color. Thanks, Harry
  7. Does anyone know the GitHub repo for this plugin? I'd like to look though the source code. Thanks, Harry
  8. I really like the concept of an OS running fully from RAM in a business situation (like what Unraid does) because that keeps the configuration settings very well defined and easy to troubleshoot and revert if/when issues arise. Also generally the OS is kept very minimal and simple (to minimize RAM usage) minimizing the exposure to possible issues or mistakes as compared to a regular full OS installed onto a hard drive. Unfortunately, I'm only aware of three such OS solutions in the storage space, Unraid, XigmaNAS, and sort of Vmware ESXI. ESXI has very limited hardware support and even though we will be using business level hardware along with enterprise level drives it doesn't seem to have all the needed drivers for our setup (and developing new drivers seems to be next to impossible since it's a custom kernel with no public information available). XigmaNAS is also fairly limited with drivers since it runs on FreeBSD. That leaves Unraid which has good driver availability since it's based on Linux. However, I'm wondering if Unraid can be considered a business quality solution. It feels like we're mixing business hardware, enterprise drives, with a home use OS. However, maybe that's just a misconception. Is anyone using Unraid in a business situation? How stable has it been? Edit: a few more details. This would be for a small business. Lack of vendor support is not considered a problem cause it's usually either too slow or too expensive in my experience for a small business. I think the main concern is stability. Having the server crash and corrupt data in the process would be the biggest thing we need to avoid. Thanks, Harry
  9. Any recent reports of which card readers work and don't work? Unfortunately most if not all of the ones mentioned here that would work are impossible to get now since they have been discontinued. Thanks, Harry
  10. Using a brand new Unraid USB key if you go to Settings -> FTP and change the FTP server from Enabled to Disabled then reboot the machine the server will revert back to Enabled. Doing a comparison between the configuration files before the FTP server is set to Disabled and after it's set to Disabled shows that nothing is actually written to any configuration file in the config folder when this setting is changed in the GUI.
  11. Is anyone using a Corsair MP510 NVME drive for their cache that is BTRFS formatted? I've read some old posts about this causing issues (only when BTRFS formatted though) but there doesn't seem to be anything recent with the latest version of Unraid. If you are using this drive as your cache and are using BTRFS please let us know if you have any issues reported in your logs. Thanks, Harry
  12. Interesting. Any idea how Unraid reads the temperatures (via smartctl, hddtemp, sysfs attribute, etc)? Cause everything I've read so far about reading drive temperatures in general states that reading the temperature is considered drive activity and will prevent the drives from falling asleep if the temperatures are read often enough (for example if they are read every 5 minutes and the drives are configured to sleep after 10 minutes of inactivity they will never fall asleep cause the drive will think there is activity ever 5 minutes). Thanked, Harry
  13. Does Unraid without any plugins show hard drive temperatures? If not, which plugin is usually used? Lastly does reading/showing hard drive temperatures prevent the drives from sleeping? Thanks, Harry
  14. Bad choice of words on my part ... I mean the kernel supports it because there's a module loaded into the kernel either manually or via the ZFS plugin. End result is the same though.
  15. My ideal setup would be using ZFS (for it's checksumming ability, snapshots, etc. and most importantly greater maturity than BTRFS) as individual disks (ie: pools of one disk each) all part of the Unraid array so that they are protected against disk failure. Which is why I'm trying to understand the technical side of things as to why they can't be part of the array. Obviously this isn't supported via the GUI, but as far as I understand it the parity created on the party drive(s) is file system agnostic. Now if the GUI is designed to complain if it doesn't recognize the file system of a disk (even though the kernel supports it) then I could understand that being an annoyance or even a deal breaker depending on what the GUI prevents from working under such a situation.
  16. I've looked through the source code for the Auto Fan Control plug-in and for some reason they turn off PWM functionality in the main loop and then turn it back on (they also assume two optional sysfs fan/pwm attributes always exist which prevents it from working with lots of configurations). According to the sysfs docs when PWM is turned off the fan should go full speed but it's technically dependant on the actual chip controlling the PWM, so I wouldn't be surprised that because they turn off PWM momentarily it turns your fans off. Unfortunately the way the plug-in is designed it will only work with a fairly limited number of configurations. I've put in a bug report on their GitHub repo but I think the developers are not maintaining the code at all at this time. I've thought about rewriting it to be more universal but honestly it's just easier and faster to write a script to manually control my fans directly since my configuration too doesn't work with the Auto Fan Control plug-in. Harry
  17. What would happen if a person formatted a drive that is part of the array as ZFS via the command line? Would it be removed from the array or cause an error or would it stay in the array? Thanks, Harry
  18. I've read that there are two ways that ZFS can be supported in Unraid, one is via the ZFS plugin which specifically mentions that ZFS formatted drives cannot be part of the array, and the second is apparently via native ZFS support in the kernel itself that Unraid uses. If adding a ZFS drive via the second route, can it be part of the array (I assume if it can it will most likely be done via the command line which is perfectly fine)? Also, any guides on how to add a ZFS formatted drive that is natively supported by the kernel? All the guides I'm finding are related to the plug-in cause that was the initial way of adding ZFS to Unraid. Thanks, Harry P.S. When referring to ZFS drives, I'm referring to individual ZFS formatted drives, not a ZFS pool made of multiple drives with its own redundancy, etc.
  19. I might take you up on that. I'm having trouble figuring out exactly who supports the Auto Fan Control related code (according to the Dynamix GitHub page it's no longer a plugin but part of Unraid but according to the Unraid response to my bug report it's still a plugin) so we might add a "solution" to the driver itself to deal with the issue to allow Unraid to control the fan speeds not just read them. I'd like to hold off until that is figured out before we make it widely available.
  20. According to the GitHub page for Dynamix (https://github.com/bergware/dynamix) the plugins are now part of Unraid. This was also confirmed in the Dynamix support thread: So we seem to be getting conflicting information. Any way to confirm who exactly supports the Auto Fan Control related code and how to get in touch with them? Thanks, Harry
  21. We had to make some changes to the driver code so the original packages you created became outdated but your Docker build script was very helpful in creating a new package (we based a simplified packaging workflow on how your build script does things ... current package can be found here: https://github.com/Stonyx/QNAP-EC/releases/tag/1.0.0) which does indeed work for reporting the fan speeds to Unraid. However we came across a bug in the Auto Fan Control code in Unraid that prevents it from being able to control the fans (https://forums.unraid.net/bug-reports/stable-releases/auto-fan-control-assumes-pwm-enable-sysfs-attribute-exists-r1617) so we're working on a possible solution for that.
  22. This is a bug report for the Auto Fan Control functionality. The code (in the include/SystemFan.php file and possibly others) is hard coded to assume that the pwmX_enable sysfs attribute exists, however, this is an optional attribute that some drivers do not implement. For example, we're working on developing a driver for an embedded controller chip used in many QNAP NAS devices so that Unraid and other Linux based OSes can read and control fan speeds, however, this embedded controller chip doesn't provide a enable/disable PWM function (PWM is always enabled) therefore according to the hwmon/sysfs standards our driver should not be creating a PWM enable sysfs attribute. However, without that attribute we get the following error from Auto Fan Control: <br /><b>Warning</b>: file_get_contents(/sys/devices/platform/qnap-ec/hwmon/hwmon2/pwm7_enable): failed to open stream: No such file or directory in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>40</b><br /><br /><b>Warning</b>: file_put_contents(/sys/devices/platform/qnap-ec/hwmon/hwmon2/pwm7_enable): failed to open stream: Permission denied in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>42</b><br /><br /><b>Warning</b>: file_put_contents(/sys/devices/platform/qnap-ec/hwmon/hwmon2/pwm7_enable): failed to open stream: Permission denied in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>50</b><br /> Is it possible to change the code to check if this attribute exists before trying to open it and if it doesn't exist assume PWM is enabled? Or is the concern that without this attribute the code doesn't know if PWM is enabled and the developers don't feel comfortable assuming that it is enabled? There are also reports of the same issue with other drivers. Here's one just for reference: Thanks, Harry
  23. Also wanted to clarify, according to the Dynamix plugin GitHub page (https://github.com/bergware/dynamix) the Dynamix plugins are now part of Unraid 6.x, so does that mean that the Unraid development team is now responsible for any bug fixes in those plugins (I guess that are no longer plugins if they are part of Unraid 6.x). Is there a GitHub page where we can submit issues and pull requests for what used to be the Dynamix plugins? The original GitHub page seems to be abandoned from an issues and pull request aspect. Thanks, Harry
  24. I'm hoping the developers of the Auto Fan Control plugin can weigh in on this question. Is there a reason why the plug-in is hard coded to look for the pwmX_enable sysfs attribute? We're working on developing a driver for a embedded controller chip used in many QNAP NAS devices so that Unraid and other Linux based OSes can read and control fan speeds, however, this embedded controller chip doesn't provide a enable/disable PWM function (PWM is always enabled) therefore according to the hwmon/sysfs standards (at least the way we currently understand them) our driver should not be creating a PWM enable sysfs attribute. However, without that attribute we get the following error from the Auto Fan Control plugin: <br /><b>Warning</b>: file_get_contents(/sys/devices/platform/qnap-ec/hwmon/hwmon2/pwm7_enable): failed to open stream: No such file or directory in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>40</b><br /><br /><b>Warning</b>: file_put_contents(/sys/devices/platform/qnap-ec/hwmon/hwmon2/pwm7_enable): failed to open stream: Permission denied in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>42</b><br /><br /><b>Warning</b>: file_put_contents(/sys/devices/platform/qnap-ec/hwmon/hwmon2/pwm7_enable): failed to open stream: Permission denied in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>50</b><br /> Is it possible to change the plug-in to check if this attribute exists before trying to open it and if it doesn't exist assume PWM is enabled? Or is the concern that without this attribute the plug-in doesn't know if PWM is enabled and the developers don't feel comfortable assuming that it is enabled? Thanks, Harry