Jump to content

HarryMuscle

Members
  • Posts

    40
  • Joined

  • Last visited

Posts posted by HarryMuscle

  1. On 5/7/2022 at 4:44 AM, Trunkton said:

    hey @HarryMuscle just tried to load this driver into my unRAID QNAP TS-873A by doing the following:

    • Place qnap-ec-1.0.0-x86_64-1.txz into /boot/extra/
    installpkg qnap-ec-1.0.0-x86_64-1.txz
    depmod --quick
    modprobe qnap-ec

     

    Getting the following after manually moving qnap-ec.ko.xz from the hard-coded directory

    /lib/modules/5.10.28-Unraid/extra/

    to the only other directory under /lib/modules:

    /lib/modules/5.15.37-Unraid/extra/

    Output from 'modprobe qnap-ec' command:

    modprobe: ERROR: could not insert 'qnap_ec': Exec format error

     

    Casual searches about this kind of error say that the binary must be compiled against the current kernel in order to get past that error. I'm sorry to bother you @ich777, is there any chance to compile this for latest RC7 version of unRAID?

     

    Additional information shown during pkgremove which is where I got the idea to move that binary.

      --> Deleting /lib/modules/5.10.28-Unraid/extra/qnap-ec.ko.xz
      --> Deleting /usr/lib/libuLinux_hal.so
      --> Deleting /usr/sbin/qnap-ec
      --> Deleting empty directory /lib/modules/5.10.28-Unraid/extra/
      --> Deleting empty directory /lib/modules/5.10.28-Unraid/

     

     

    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

    • Like 1
  2. @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

  3. 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

  4. 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

  5. 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

  6. 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

  7. 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

  8. 11 minutes ago, Squid said:

    The linux kernel does not natively support ZFS due to licensing issues.

    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.

  9. 6 hours ago, ich777 said:

    Why would you do that?

    Try it andy you will se what happens... If nothing happens, the next reboot will be funny... :D

     

    Jokes asside, no that is not possible currently, you also will have no benefit if you format it in ZFS, or what do you think would be the benefit? ZFS won't be quicker than with XFS because the Parity data is always calculated. It will always prompt you that one disk is not formated in the right filesystem.

     

    Why don't you create a zpool outside from the array/cache like most people do it including myself. I have one drive as a cache installed and the zpool holds my Docker path (I'm not using a image), my appdata folder, libvirt.img and so on and it works really nice on RC2.

     

    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.

     

     

  10. 18 hours ago, BeardElk said:

    I´m gonna apologize for my previous language, was frustrated as hell! 
    Min temp value does not matter what I set it to, min pwm does not matter what I set it to. 
    If I set my fans 100% in bios, as soon as I "detect fan", and it detects it, my selected fan turns of. 
    Does not matter what I set min temp or min pwm to, can not get selected fan to turn on again. 

    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

  11. On 11/5/2021 at 3:55 AM, JorgeB said:

    Not for now, likely it will be possible in the future.

    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

  12. 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.

     

     

     

  13. 13 minutes ago, ich777 said:

    Should I create a plugin for this where the package is compiled every time a new unRAID version is released, like it is for my Nvidia Driver, DVB Driver, NCT Driver Plugin,...

    I also compile packages for other community developers like ZFS for @steini84 and USBIP & iSCSI for @SimonF.

     

    The process is automated and executed every time a new unRAID version is released.

    Just hook me up with a short PM.

    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.

     

  14. 8 minutes ago, ich777 said:

    @HarryMuscle any news on the QNAP packages? Do they work?

     

    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.

  15. 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

     

     

  16. 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

  17. 8 hours ago, ich777 said:

    The script for the container is copied over to the root directory if you enable the custom build mode, this is basically a Debian Bullseye container that cross compiles everything and packs it up in custom images, keep in mind I will be deprecating the container soon because I will move away from custom images since you can integrate now nearly everything with plugins.

     

    Made a package for you from where it is possible to create a plugin:

    Compiled the linked Github repo and attached the files for you to test, please keep in mind these files will only work on unRAID v6.9.2:

    qnap_it8528-plugin-5.10.28-Unraid-1.txz 645.67 kB · 0 downloads

    qnap_it8528-plugin-5.10.28-Unraid-1.txz.md5 33 B · 0 downloads

     

    To install the files first place it somewhere on unRAID, navigate to the folder where you've put the files and issue these commands:

    installpkg qnap_it8528-plugin-5.10.28-Unraid-1.txz
    depmod -a
    modprobe qnap-ec

    I can't test these files since I've got no QNAP hardware, I also don't know if you need to run 'qnap-ec' in order that everything is working.

     

     

    May I also recommend that you change the Makefile a bit so that it respects DESTDIR?

    Since Slackware has a little different layout where the share libraries are I would also recommend to change the 'LIBRARY1_PATH' & 'LIBRARY2_PATH' to '/usr/lib64' (those are 64 bit libraries I think or am I wrong, if not the path should be '/usr/lib') and the last thing that I recommend would be to change the 'HELPER_PATH' to '/usr/bin'.

     

    Feel free to contact me again if you got further questions. :)

    Awesome.  Thanks.  I'll look into making the suggested changes.

    • Like 1
  18. Today we got the driver fully working. Currently the development and testing is being done on Debian and Ubuntu but it works great. You can view temps, fan RPMs, and view and adjust fan PWM values. Code needs a tiny amount of cleanup still and a few odds and ends but it should be ready for prime time pretty soon. Need to write some more documentation about it and figure out how to compile it for Unraid too still.

    • Like 1
×
×
  • Create New...