xamindar

Community Developer
  • Posts

    442
  • Joined

  • Last visited

Posts posted by xamindar

  1. This autofan plugin looks like it should work similar to a script I wrote several years ago to control the fan based on hdd temps. Is that what it is supposed to do?

     

    I installed it but it will not detect my fan (/sys/class/hwmon/hwmon1/device/pwm2). Would be really nice to have this in the web gui, I guess this addon is still a work in progress? Until then I guess I'll stick with my script.

     

    Please post the result of this command:

     

    find -L /sys/class/hwmon/ -maxdepth 5 -iname "pwm[0-9]" 2>/dev/null

     

    Here you go:

    /sys/class/hwmon/hwmon1/device/pwm1
    /sys/class/hwmon/hwmon1/device/pwm2
    /sys/class/hwmon/hwmon1/device/pwm3
    

     

    Those are the three possible pwm controls from my it87 board.

     

    Ok, I need one last command output:

     

    find /sys/devices -iname "hwmon[0-9]" -exec echo {} \; -exec ls -la {} \;

     

    /sys/devices/pci0000:00/0000:00:18.3/hwmon/hwmon0
    total 0
    drwxr-xr-x 3 root root    0 Mar  2 19:57 .
    drwxr-xr-x 3 root root    0 Mar  2 07:35 ..
    lrwxrwxrwx 1 root root    0 Mar  2 08:10 device -> ../../../0000:00:18.3
    -r--r--r-- 1 root root 4096 Mar  2 08:10 name
    drwxr-xr-x 2 root root    0 Mar  2 16:33 power
    lrwxrwxrwx 1 root root    0 Mar  2 07:35 subsystem -> ../../../../../class/hwmon
    -r--r--r-- 1 root root 4096 Mar  2 08:10 temp1_crit
    -r--r--r-- 1 root root 4096 Mar  2 08:10 temp1_crit_hyst
    -r--r--r-- 1 root root 4096 Mar  2 08:10 temp1_input
    -r--r--r-- 1 root root 4096 Mar  2 08:10 temp1_max
    -rw-r--r-- 1 root root 4096 Mar  2 07:35 uevent
    /sys/devices/platform/it87.656/hwmon/hwmon1
    total 0
    drwxr-xr-x 3 root root    0 Mar  2 19:57 .
    drwxr-xr-x 3 root root    0 Mar  2 16:34 ..
    lrwxrwxrwx 1 root root    0 Mar  2 16:34 device -> ../../../it87.656
    drwxr-xr-x 2 root root    0 Mar  2 16:34 power
    lrwxrwxrwx 1 root root    0 Mar  2 16:34 subsystem -> ../../../../../class/hwmon
    -rw-r--r-- 1 root root 4096 Mar  2 16:34 uevent
    

     

    There you go, hope that helps. :)

  2. My pwm controls used to be under /sys/class/hwmon/hwmon1/device/, but sometime during the V6 beta cycle it changed to /sys/class/hwmon/hwmon2/.

     

    I mention this simply because it may be that you're loading an older driver yourself instead of using a later one as included in the unRAID image.

    This is not possible the way kernel and module versioning work, unless I want to bypass the checks which is something I would recommend never doing. In any case, it87 has been included in unraid for a while now and there is no need for me to compile my own module anymore.

  3. This autofan plugin looks like it should work similar to a script I wrote several years ago to control the fan based on hdd temps. Is that what it is supposed to do?

     

    I installed it but it will not detect my fan (/sys/class/hwmon/hwmon1/device/pwm2). Would be really nice to have this in the web gui, I guess this addon is still a work in progress? Until then I guess I'll stick with my script.

     

    Please post the result of this command:

     

    find -L /sys/class/hwmon/ -maxdepth 5 -iname "pwm[0-9]" 2>/dev/null

     

    Here you go:

    /sys/class/hwmon/hwmon1/device/pwm1
    /sys/class/hwmon/hwmon1/device/pwm2
    /sys/class/hwmon/hwmon1/device/pwm3
    

     

    Those are the three possible pwm controls from my it87 board.

  4. Slight bug in the Temp plugin. When my fan is off and should be showing 0rpm, I get "##rpm" at the bottom of the web gui. Also, while the fan is off, if I go to that plugin's settings page the fan field will show "Not Used". Othwise if I set my fan to any speed other than 0, it will show up at the bottom as well as in the settings page.

     

    It appears that the plugin is auto-hiding any fans that are powered down or appear not connected. Wouldn't it be more useful to have all possibilities listed and then let the user pick the correct one?

     

    But main issue is the "##?rpm" erroneously showing at the bottom when it should be "0 rpm".

     

    I love the work you have put in to this web interface and hope that helps!

  5. This autofan plugin looks like it should work similar to a script I wrote several years ago to control the fan based on hdd temps. Is that what it is supposed to do?

     

    Yes.

     

    I installed it but it will not detect my fan (/sys/class/hwmon/hwmon1/device/pwm2). Would be really nice to have this in the web gui, I guess this is addon still a work in progress? Until then I guess I'll stick with my script.

     

    You have to make sure that the appropriate drivers for your motherboard are loaded, then autodection should work.

     

    I'm using the plugin and it is working well for me.

     

    Thanks PeterB, as stated I am using my script still which implies I already have the module loaded and can control my fan on this system ;)  I even listed my fan device "/sys/class/hwmon/hwmon1/device/pwm2". I'll look around at this plugin and see if I can fix it because having it in the web gui is an awesome idea!

  6. This autofan plugin looks like it should work similar to a script I wrote several years ago to control the fan based on hdd temps. Is that what it is supposed to do?

     

    I installed it but it will not detect my fan (/sys/class/hwmon/hwmon1/device/pwm2). Would be really nice to have this in the web gui, I guess this addon is still a work in progress? Until then I guess I'll stick with my script.

  7. Wow thanks for all the replies guys. Got 5 people saying the same thing over and over again lol.

     

    To answer the question on why I zapped the partition tables (zap through gdisk, basically deleting it all). That disk was still showing as mbr-unaligned and it was the only way to get it aligned again as simply formatting to btrfs through the web gui did not change it. OCD I know ;) I was also thinking the web gui might change it over to gpt on a fresh new format but I was mistaken. I guess it doesn't for 2tb drives.

     

    For the other disks I'll change them as you guys state, only through the web interface, as to not invalidate parity. Thanks again!

     

    EDIT: Man, it's checking and correcting parity at 11MB/sec and will finish in 3 days. Is there no way to make it go faster? I seem to remember the initial parity build being faster.

  8. Upgraded to the 6 beta finally and love the new look. Here are a couple of issues I have noticed so far:

    -the dark theme does not show grayed out text fields in a way that you can know they are unusable.

     

    -I zapped the partition table of an empty array drive, changed it's filesystem to btrfs in the unraid interface and then started the array. As expected I needed to format it which I did. Everything came online and looks good EXCEPT....parity is still showing as "valid" which seems incorrect. Sure enough, I started a parity check and millions of errors being corrected so it looks like it is basically rebuilding parity.

     

    Shouldn't it state parity is invalid after a filesystem change in such a way? If someone doesn't run a check they may assume parity is good when it is not.

  9.  

    Is this something unraid is being designed to support down the line? Are its btrfs volumes set up as a subvolume by default to allow for snapshotting? I guess I'll find out soon enough as I am preparing my unraid system for the 6 upgrade. Will probably start eith making the cache drive btrfs.

  10. Only you who knows the secret string can link up your shares. But it does have some sort of open tracker so that your computers can connect across the internet (which I think you can even disable). I still keep my password files and vpn key files encrypted just in case. 

     

    Sent from my A510 using Tapatalk

     

     

  11. My solution in to have an ssd as the cache drive and set it to never sleep. All my other plugins save their configuration files on the cache as well and it works great. Besides, I wouldn't want the cache sleeping anyway because then I would have to wait for spin up every time I wanted to write to my unraid.

     

    Sent from my SGH-T889 using Tapatalk

     

     

  12. This parity check slow-down was a problem with simplefeatures as well. Can you please fix this bug? The parity slow-down is the most annoying thing about these custom web guis.

     

    Sent from my A510 using Tapatalk

     

    First, I don't see this as a bug in the webGui (both SF and Dynamix). It is a design decision (flaw?) in emhttp to start background disk activity upon each HTTP request made to it. That means that any button click you do in the GUI causes HDD activity. In the stock webGui this is circumvented by making it completely passive, meaning only when the user clicks on something there is interaction with emhttp. That's why people should not do  a frequent page fresh as it interferes with a parity check.

     

    Second, Dynamix can be set to "passive" or "disabled" which stops all background HTTP requests and basically turns into the same manual behavior as the stock webGui. This explains why people see a difference in parity check speed when choosing a different page refresh mode in Dynamix.

     

    Why the parity speed is different with Dynamix opened in passive or disabled mode, I can't explain. Was this tested with the stock webGui as well, I expect exactly the same results...

    Thank you for the clarification on this issue. I wasn't aware that emhttp was actually causing it with each request made.

     

    Still, you have created an amazing gui replacement. Thank you.

     

    Sent from my A510 using Tapatalk

     

     

  13. The ambient temperature can increase in a room, in turn increasing the temperature of any disks, spun down or otherwise. :)

     

    Sent from my Nexus 5 using Tapatalk

    Lol, ambient temperature will never get high enough to damage a hard drive, unless your house is on fire.

     

    Sent from my A510 using Tapatalk

     

     

  14. I have a problem with my cache drive filling up. It is only 120gb and can easily fill up if I transfer too much data over in one day.

     

    For example, I currently only have 17GB of space left on my cache drive. I start ripping a 37GB bluray to my multimedia user share which is set to use the cache drive. Makemkv warns me that there is only 17GB left on the share, I continue, and the cache drive eventually fills up causing the rip to fail.

    Note that the min free space setting is only checked when first creating a file.  Therefore the min free space setting needs to be large enough to allow for the largest file that you might create (and if you might be doing several in parallel the sum of them).  If you run out of space on the drive after creating the file as you write it there is no automatic fail-over to the array drives and you get an error about running out of space.

    I think you may have missed the example in my first post. Cache only has 17GB free, min free space is set to 30GB. Since the cache drive has less than the minimum, why is it still letting me create new files on the cache drive (in my example, the new bluray rip).

    It would seem to make more sense to me for unraid to write the next file directly to the array if the cache drive gets almost filled.

    That is what happens for me once the free space on the cache drive falls below the min free space value.

    Ok, then this is not happening for me, at least for the cache drive. As I posted above, min free space for the cache drive is set to 30GB and there is currently onlt 17GB available on the cache drive. If I attempt to write a new file it is still written to the cache drive instead of directly to the array in this case.

     

    I'm on unraid 5.0 so I am confused that mine is acting different than yours. I'm not using any split levels on the shares, should I be? There has got to be some option set somewhere else preventing my min free space setting from working.

     

    I did install the Dynamix web gui, could that be causing the issue?

  15. I have a problem with my cache drive filling up. It is only 120gb and can easily fill up if I transfer too much data over in one day.

     

    For example, I currently only have 17GB of space left on my cache drive. I start ripping a 37GB bluray to my multimedia user share which is set to use the cache drive. Makemkv warns me that there is only 17GB left on the share, I continue, and the cache drive eventually fills up causing the rip to fail.

     

    First of all, why is the user share reporting my cache drive available space instead of the entire share available space (which is several terrabytes)?

    Second, I have the cache disk "min free space" setting set to 30GB but this seems to be ignored or not do what I want. What am I doing wrong?

     

    It would seem to make more sense to me for unraid to write the next file directly to the array if the cache drive gets almost filled.

     

    Is there any way to do this? Or do I just need a bigger cache drive (or manually run the mover to make more cache space when it gets full)?

  16. Love this web gui and good job. But unfortunately, it causes emhttp to eventually crash just like simple features used to do back on the pre-5.0 versions of unraid. And once it crashes, it can not be restarted without a reboot as it seg faults until then.

     

    I have Dynamix up and running for weeks, and no emhttp crashes and - as the developer - I do a lot with Dynamix webGui and optional plugins.

     

    Are you running other plugins which are memory hungry and eventually let emhttp starve ?

     

    One workaround to prevent emhttp from being killed by the OS, is to put the following in your 'go' script (and run manually):

     

    # Set webGUI never killed off

    echo -1000 > /proc/$(pgrep -f /usr/local/sbin/emhttp)/oom_score_adj

     

    Thanks a lot! I'll give that a try. I am running btsync and dropbox plugins which I can see taking up a lot of memory (8 gigs in this box though). But why can't I re-launch emhttp once it is killed? It just segfaults which makes me think something other than OOM is the cause.

  17. Love this web gui and good job. But unfortunately, it causes emhttp to eventually crash just like simple features used to do back on the pre-5.0 versions of unraid. And once it crashes, it can not be restarted without a reboot as it seg faults until then.

  18. Thanks a lot for all you do with creating these plugins.

     

    I think I found a bug with saving the "Sync Trash (days)" setting. Before I enabled any advanced settings, this option showed 30. Once I set one of the other advanced options, this setting went to 1000. Now I try to set it to something more sane like 60 and it always reverts back to 1000 days when I apply the changes.

     

    Actually, this is happening to "Max Allowed Time Difference Between Devices (secs)" as well.

     

    It seems what ever I set "Max File Size for Versioning (MB)" to is also applied to "Max Allowed Time Difference Between Devices (secs)" and Sync Trash (days)".

  19. I have two issues that are becoming annoying:

     

    First, when I start writing to a share that is spun down and it has to spin up, the write times out and fails before the drive finishes spinning up. Is there any way to increase cache/time it waits before timing out? Why can't unraid just accept the write and then flush it all do disk once the drive is ready?

     

    Second, If I'm streaming a movie to another machine while one of the other unraid drives needs to spin up, the stream stops until that other drive finishes spinning up. Why would a completely different drive affect the current read from an already active drive?