Jump to content

_0m0t3ur

Members
  • Posts

    353
  • Joined

Posts posted by _0m0t3ur

  1. 2 minutes ago, aptalca said:

     

    No, the container doesn't need any ports mapped because there are no incoming connections to this container. 

     

    You can just set networking mode to bridge and not map any ports

    Ok.  I'll change to bridge mode.  There were no pre-set options in the container for paths, etc.  I wasn't sure if you meant that I should be adding them.  Some containers that have paths specified, I've also been able to specify additional paths for other purposes.  For example in Plex specifying a path for movies.  Then creating another for tv shows.  Thanks for your help.

  2. 1 minute ago, aptalca said:

     

    I'm guessing because there are no ports mapped

    Are you saying that I, in the container, should map local and host ports.  And then open ports in my router to match the host ports listed in the DuckDNS container?

     

    I ask because the setup that @gridrunner put together on his Youtube channel didn't specify those steps.  DuckDNS seems to be working.  I'm new here.  Any advice would be appreciated.

     

    Thank you.

     

  3. This DuckDNS docker appears to be working.  I learned about it from watching a video by Spaceinvader One on Youtube.  I'm able to ping successfully.  But when setting up another docker, I noticed that under "Docker Allocations" that in place of a port, there are several question marks.  I'm curious why?  Image below:

     

     

    DuckDNS.jpeg

  4. 2 hours ago, CSIG1001 said:

    Thanks can you give me a model number what I should look for on ebay? I am thinking of going with the 9211-8i, three of them with the unraid proper firmware to support.

     

     

    Also can anyone tell me if it is worth my wild to go with AMD  multi core processor say 8-10 cores for plex and how is the compatibility with unraid?

    Or should i just throw in a 7700k ? and call it a day 

     

    Trying to figure out if plex supports multi core processing over 4 cores 

     

    I am streaming 4k remux about 50-80gb mkv movies , DTS Atmos 

    Thanks!

     

    Do you have the motherboard, RAM, PSU, etc., yet?  If not, you might consider going with used server grade stuff.  Great performance at lower cost.

  5. 14 hours ago, CSIG1001 said:

     

    Thanks for the info I will do some research on those HBAs with the proper firmware to use in unraid

    I would like to use a few SSDs for cache..  

     

    Hopefully the norco is worth it ..  i hate for the backplane to kill my drives . 

     

    As for flashing the LSI 9211-8i, here's a link to some detailed and straight forward instructions, including the link to the files you will need if you go with this LSI 9211-8i HBA.

     

    https://nguvu.org/freenas/Convert-LSI-HBA-card-to-IT-mode/

     

    Here's a video showing the steps to flash the HBA.  I don't remember what card he is flashing, other than it's an LSI.  The steps are the same.  Just use the link above for the files.  The link below (Youtube) is just to show how easy it is.  Also, in the same video he flashes a motherboard BIOS.

     

     

    • Like 1
  6. On 6/21/2018 at 12:29 AM, DoItMyselfToo said:

    Do the logs still need to be manually deleted via script each day or so?  Or has this been automated within the container?

     

    From diginc on github, "Automatic Ad List Updates - since the 3.0+ release, cron is baked into the container and will grab the newest versions of your lists and flush your logs. Set your TZ environment variable to make sure the midnight log rotation syncs up with your timezone's midnight."

     

    Looks like this container points to the latest release, so we should be covered, provided TZ is set correctly.  Find your TZ here.

  7. On 6/20/2018 at 2:10 PM, wgstarks said:

    Yes, 3 minutes. Runtime reported by the UPS is an estimate. Just because it says it will provide 3 minutes of runtime doesn’t mean that it will if your batteries aren’t in good condition. Since your other variables are set to zero you’ll get a hard shutdown if your batteries run down before the 3 minute runtime is reached. That’s why I suggested testing it, since I don’t know the power consumption of your server or the capacity of your UPS.

    Gottcha!  Yeah, I probably should have provided UPS info in the post.  My error.  Sorry.

     

    So, I was reading your post and thinking that 3 minutes on battery is nothing.  Especially, seeing that my system shows 83 minutes runtime left at 100% battery charge, which you did not see.  I realize that the 83 minutes is probably inaccurate but since my target is shutdown in under 10 minutes, this should provide enough of a cushion.

     

    Your comment ended up being very helpful.  Thanks.  As a result, I looked at the settings page again.  Apparently, the shutdown is invoked by the first trigger of the three.  So the 180 second trigger should be invoked first based on current battery health.  But I should probably have settings for the other two in a case where the battery health is lower than anticipated to prevent a hard shutdown, as you pointed out.

     

    As a result, I've set the "Battery level to initiate shutdown" to 50%; the "Runtime left to initiate shutdown" is set at 10 minutes.  And my "Time on battery before shutdown" is set to 180 seconds.

     

    This should get my system beginning a shutdown at 3 minutes on battery, unless my battery immediately reads some low health setting.  Then my system will hopefully be caught by the 50% rule and shutdown gracefully anyway.

     

    Thanks again.

     

  8. On 6/20/2018 at 1:52 PM, wgstarks said:

    Should work, assuming your UPS will provide that much runtime. Will shutdown at the first trigger reached. A test might not be a bad idea though. Runtime can be very inaccurate depending on the condition of your batteries.

    I'm confused.  The settings should allow the server to run on battery power for 3 minutes before shutting down.  I'm trying to set this to shut off very timely.  Am I missing something?

     

  9. I've read a number of posts in various threads in the forum that recommend setting unRAID to shutdown after a power disruption puts the server on battery power somewhere between 1-3 minutes, essentially insuring a shutdown within a 10 minute window.

     

    I want to use only "Time on battery before shutdown" to get my server shutdown within a definite 10 minute window.  If I use the following values for UPS Settings, do the zeros shut off the functions "Battery level to initiate shutdown" and "Runtime left to initiate shutdown"?

     

     

     

    UPS Settings.jpeg

  10. 42 minutes ago, DZMM said:

    Ok, I'm still getting freezes since upgrading from RC1 and I've just had my first VM crash ?  Am I the only person having problems (GUI mode stopped working, SMB settings wiped out and constant freezes and frequent VM crashes? with 6.5.3?

     

    highlander-diagnostics-20180615-0905.zip

     

    I'm new to unRAID, though it looks like if a problem arises when upgrading to a stable version from an RC version, then...

     

    On 6/13/2018 at 7:14 PM, nickp85 said:

     

    So shut down the server, take out the flash drive, plug it into my laptop, copy config folder off, wipe drive, prepare as a new unraid flash drive with 6.5.3 and then copy config folder back...

     

     

  11. 5 hours ago, mrbilky said:

    Although I don't have more than 1 mac pointed to this drive I don't see why you couldn't just point to it individually from each machine but not sure as I did a disk share or just create 3 different shares on a drive i.e. mac 1, mac 2, mac 3 and just select the right share from each pc, when you setup shares under AFP you will have the option to export to time machine as a test I just changed export on one of my shares and it does show up on my mac as a drive option in time machine

    Helpful.  I appreciate you.  Hopefully I can take some time to get this set-up within the next couple days.  Thanks.

  12. 1 hour ago, mrbilky said:

    I have time machine working without issue I did isolate 1 drive just for that and mapped it in time machine on my macbook to use both my airport extreme and my NAS drive as backups seems to work fine I think if I remember correctly you have to make the share/drive private time machine didn't like it without it but it has been awhile so not quite sure on that and if anything has changed

     

    I was just thinking about Time Machine.  Thanks for this post.  My last couple drives are finishing Preclear now.  Then I'll be getting the drives assigned and so forth.

     

    In my house we have three MacBook Pro's to backup via Time Machine.  Do you know whether I can use one HDD to backup the three devices or are you suggesting that I might be better having three separate HDD's?  I haven't looked much into this part of the set-up yet, so any thoughts you have regarding this would be appreciated.

  13. So here goes.  It's fixed.

     

    What did I do?  Haha.  Hmm?  Let's think.

     

    1.  Executed sensors-detect command, then rebooted server after preclear finished on one drive.

     

    2.  Navigated to and executed command: /boot/config/plugins/dynamix.system.temp# cat drivers.conf

     

    Output:

     

    coretemp
    jc42
    w83627ehf

     

    3.  Navigated to and executed command to display available sensor info:  /boot/config/plugins/dynamix.system.temp# sensors

     

    Output:

     

     

    jc42-i2c-0-1b
    Adapter: SMBus I801 adapter at 0400
    temp1:        +40.5°C  (low  =  +0.0°C)                  ALARM (HIGH)
                           (high =  +0.0°C, hyst =  -1.5°C)
                           (crit = +69.2°C, hyst = +67.8°C)

    jc42-i2c-0-19
    Adapter: SMBus I801 adapter at 0400
    temp1:        +38.5°C  (low  =  +0.0°C)                  ALARM (HIGH)
                           (high =  +0.0°C, hyst =  -1.5°C)
                           (crit = +69.2°C, hyst = +67.8°C)

    coretemp-isa-0000
    Adapter: ISA adapter
    CPU Temp:     +32.0°C  (high = +83.0°C, crit = +99.0°C)
    Core 1:       +28.0°C  (high = +83.0°C, crit = +99.0°C)
    Core 2:       +34.0°C  (high = +83.0°C, crit = +99.0°C)
    Core 3:       +30.0°C  (high = +83.0°C, crit = +99.0°C)

    w83627dhg-isa-0a10
    Adapter: ISA adapter
    Vcore:        +0.90 V  (min =  +0.60 V, max =  +1.49 V)
    in1:          +1.84 V  (min =  +1.62 V, max =  +0.03 V)  ALARM
    AVCC:         +3.23 V  (min =  +2.96 V, max =  +3.63 V)
    +3.3V:        +3.23 V  (min =  +2.96 V, max =  +3.63 V)
    in4:          +1.53 V  (min =  +1.35 V, max =  +1.65 V)
    in5:          +1.25 V  (min =  +1.13 V, max =  +1.38 V)
    in6:          +1.44 V  (min =  +1.42 V, max =  +1.52 V)
    3VSB:         +3.23 V  (min =  +2.96 V, max =  +3.63 V)
    Vbat:         +3.15 V  (min =  +2.96 V, max =  +3.63 V)
    Array Fan:   1240 RPM  (min =  712 RPM, div = 8)
    fan2:        1985 RPM  (min =  712 RPM, div = 8)
    fan3:        1328 RPM  (min =  712 RPM, div = 8)
    fan5:        1231 RPM  (min =  712 RPM, div = 8)
    MB Temp:      +35.0°C  (high = +60.0°C, hyst = +55.0°C)  sensor = thermistor
    temp2:        +33.0°C  (high = +95.0°C, hyst = +92.0°C)  sensor = CPU diode
    temp3:        +31.5°C  (high = +75.0°C, hyst = +70.0°C)  sensor = thermistor
    cpu0_vid:    +1.513 V
    intrusion0:  ALARM

    jc42-i2c-0-1a
    Adapter: SMBus I801 adapter at 0400
    temp1:        +37.2°C  (low  =  +0.0°C)                  ALARM (HIGH)
                           (high =  +0.0°C, hyst =  -1.5°C)
                           (crit = +68.8°C, hyst = +67.2°C)

    jc42-i2c-0-18
    Adapter: SMBus I801 adapter at 0400
    temp1:        +41.0°C  (low  =  +0.0°C)                  ALARM (HIGH)
                           (high =  +0.0°C, hyst =  -1.5°C)
                           (crit = +68.8°C, hyst = +67.2°C)

     

     

    The sensors drop-down menu in Dynamix System Temperature plugin is now populated and working.

  14. 15 hours ago, DoItMyselfToo said:

    Thanks, Squid! I’ll give it a go and report if I have a problem.


    Sent from my iPhone using Tapatalk

     

    root@unCube:/etc# cat sensors.d/sensors.conf
    # sensors
    chip "w83627dhg-isa-0a10"
    ignore "fan4"
    chip "jc42-i2c-0-18"
    label "temp1" "CPU Temp"
    chip "w83627dhg-isa-0a10"
    label "temp1" "MB Temp"
    chip "w83627dhg-isa-0a10"
    label "fan1" "Array Fan"

     

    I'm seeing the contents of the sensors.conf file.  The results make sense.  Ignoring fan4 makes sense, since no fans are connected to that header.  And the other results are the options that I selected in the drop down menu in the Dynamix System Temperature plugin.

     

    I did navigate to the plugin directory to look at the plugin drivers.conf file.

     

     /boot/config/plugins/dynamix.system.temp# cat drivers.conf

     

    coretemp
    jc42
    w83627ehf

     

    This is what shows up.

     

    So how do I get this to connect up with the plugin?

     

    Is it a matter of copying the sensors.conf from the /etc/sensors.d directory to the /boot/config/plugins/dynamix.system.temp directory?

     

    I'm just taking a stab at this; not really knowing.

  15. unRAID v6.5.2

     

    Problem:

     

    I have Dynamix System Temperature plug-in installed with Perl, as required.  The drivers loaded and the sensor readings were passed through.  After a proper reboot, the sensor readings were gone, replaced by "Not used."

     

    After some searching found the Lime-Tech Wiki page that shows "sensors" command line.  So I ran it in terminal.

     

    Output:

     

    root@unCube:~# sensors
    Error: File /etc/sensors.d/sensors.conf, line 4: Undeclared bus id referenced
    sensors_init: Can't parse bus name

     

    After attempting to show the content of the sensors.conf file, here's the output:

     

    root@unCube:/etc/sensors.d# sensors.conf content
    ./sensors.conf: line 2: chip: command not found
    ./sensors.conf: line 3: ignore: command not found
    ./sensors.conf: line 4: chip: command not found
    ./sensors.conf: line 5: label: command not found
    ./sensors.conf: line 6: chip: command not found
    ./sensors.conf: line 7: label: command not found
    ./sensors.conf: line 8: chip: command not found
    ./sensors.conf: line 9: label: command not found

     

    The Wiki shows the command sensors-detect, which is supposed to help configure the sensors.conf file.  After running sensors-detect in terminal, here's the output.

     

    Copy prog/init/lm_sensors.init to /etc/init.d/lm_sensors
    for initialization at boot time.
    You should now start the lm_sensors service to load the required
    kernel modules.

     

    I'm stuck here.  It looks like performing the copy operation shown above and starting lm_sensors should solve this problem.

     

    Any help would be appreciated.  Thanks in advance.

×
×
  • Create New...