Niklas

Members
  • Posts

    323
  • Joined

Posts posted by Niklas

  1. 22 minutes ago, binhex said:

    You can run it via default bridge, or custom bridge, macvlan is not supported.

    Sent from my EML-L29 using Tapatalk
     

    Oh ok, that's not what i wished for. I have the rtorrentvpn container running bridged but i have other containers running on br0 (macvlan) that can't use the privoxy part of the rtorrentvpn container because the limitation that does not allow host <-> macvlan. That's why this container made me get my hopes up. I really want some of the other containers to proxy http(s) traffic over vpn (pia) but it would be problematic for me to move all containers to bridge or host. So many different ports... ;)

    The thing is, I have it on br0 now and it seem to proxy my traffic when using the ip I have assigned to the container? It "could" work but not supported? Like one Firefox setup, with the macvlan ip and port 8118 for proxy server, surfing to the pia homepage tells me that my connection is using pia ("Your IP Address: xx Your ISP: PIA You are protected by PIA").

  2. Catch up to what? 

     

    So the enterprise systems out there with os on sticks (or internal flash devices) mounted in internal usb-ports should also catch up? To what? Unraid runs from ram so why change a working concept? Sticks can go bad but that's the case with ALL storage solutions. The stick is only used to store settings, boot and load Unraid system in to ram. The reading and unpacking the system to ram happens very early in the boot process and after that, unraid continues to boot from ram only. Reading settings from the stick and that's it. 

     

    Doing backups and in the worst case scenario, you will need to restore it to another stick. That's like 10 bucks for a good one? And you are up again. Easy and cheap to replace and most systems have good speed to ram. To work with all variety of systems, I see this solution as very good. A failed storage device could be costly. Also, moving the stick to another system will just work. 

  3. Good to hear that you are up and running again. 

     

    BTW, make external (not on same server) backups of the stick regularly, especially after changing settings. I do it automatically every night using the Duplicati docker. Backing up /boot to OneDrive (and the appdata share). I also use the CA Backup plug in to backup flash to array every night. 

  4. My fit runs hot when writing/reading much data at once. Like booting. But not that hot when the system is running. I think that's normal with small sticks. Less surface area to distribute the heat but not a problem. Designed that way. 😉 I changed my stick from a big Kingston stick to the smaller fit because it was protruding too much at the back of the server. My server is located on the floor in the hallway so I don't want my kids to accidentally hitting the stick and break it (and/or the port or motherboard). 😉

  5. Don't format it! Try to check the drive for errors. I don't know how that works on Mac. If and when the stick is repaired, I would back it up and replace the files on the stick using the unraid zip file to fix corrupt system files. Personally, I would not continue using the stick in my server. Just make sure to backup the files on the stick if you can before doing anything. 

  6. If you change something regarding your shares, this will be added to the syslog:

    Quote

    Mar  4 15:46:41 Server emhttpd: req (38): shareNameOrig=domains&shareName=domains&shareComment=Saved+VM+instances&shareAllocator=highwater&shareFloor=0&shareSplitLevel=1&shareInclude=&shareExclude=&shareUseCache=only&cmdEditShare=Apply&csrf_token=****************
    Mar  4 15:46:41 Server emhttpd: Starting services...
    Mar  4 15:46:41 Server emhttpd: shcmd (563): /etc/rc.d/rc.samba restart

    Both share name and share comment visible in the exported syslog. I used domains here but the same applies to all user shares. That does not get anonymized. I don't know if this happens with other changes that shows in the syslog. Using debug logging for some stuff could show some personal information too. Mover logging will show private filenames and so on. 

  7. On 2/27/2019 at 3:46 PM, Squid said:

    The dashboard isn't real time when in doubt about the status of the drivers enable the logging in the plugin and you'll see what the drive reports

    Sent via telekinesis
     


    Ok, thanks. Will look in to it.
    Never seen 0 spun down. Always at least 1.

    Edit:

    Quote

    Feb 27 18:37:36 Server root: #012/dev/sdg:#012 drive state is: unknown
    Feb 27 18:37:36 Server root: #012/dev/sdf:#012 drive state is: standby
    Feb 27 18:37:36 Server root: #012/dev/sde:#012 drive state is: standby
    Feb 27 18:37:36 Server root: Total Spundown: 3

    hm, sdg is spun up.


    smartctl -i -n standby /dev/sdg seems to work better. Nothing "unknown" with smartctl.

    Quote

    root@Server:~# smartctl -i -n standby /dev/sdg (up)
    smartctl 7.0 2018-12-30 r4883 [x86_64-linux-4.19.24-Unraid] (local build)
    Copyright (C) 2002-18, Bruce Allen, Christian Franke, www.smartmontools.org

    === START OF INFORMATION SECTION ===
    Model Family:     Seagate IronWolf
    Device Model:     ST4000VN008-2DR166
    Serial Number:    
    LU WWN Device Id: 5 000c50 0b29c58c1
    Firmware Version: SC60
    User Capacity:    4,000,787,030,016 bytes [4.00 TB]
    Sector Sizes:     512 bytes logical, 4096 bytes physical
    Rotation Rate:    5980 rpm
    Form Factor:      3.5 inches
    Device is:        In smartctl database [for details use: -P show]
    ATA Version is:   ACS-3 T13/2161-D revision 5
    SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
    Local Time is:    Wed Feb 27 18:49:33 2019 CET
    SMART support is: Available - device has SMART capability.
    SMART support is: Enabled
    Power mode was:   IDLE_B
     

    root@Server:~# smartctl -i -n standby /dev/sdf (down)
    smartctl 7.0 2018-12-30 r4883 [x86_64-linux-4.19.24-Unraid] (local build)
    Copyright (C) 2002-18, Bruce Allen, Christian Franke, www.smartmontools.org

    Device is in STANDBY mode, exit(2)

    root@Server:~# smartctl -i -n standby /dev/sde (down)
    smartctl 7.0 2018-12-30 r4883 [x86_64-linux-4.19.24-Unraid] (local build)
    Copyright (C) 2002-18, Bruce Allen, Christian Franke, www.smartmontools.org

    Device is in STANDBY mode, exit(2)

    Same with hdparm:
     

    hdparm -C /dev/sdg (up)

    /dev/sdg:
     drive state is:  unknown

    (counted as spun down in the code, when actually spun up)

     

    hdparm -C /dev/sdf (down)
    /dev/sdf:
     drive state is:  standby
     

    hdparm -C /dev/sde (down)

    /dev/sde:
     drive state is:  standby
     


    Edit again
    https://www.smartmontools.org/wiki/Powermode

    Replace in /usr/local/emhttp/plugins/ca.turbo/scripts/auto_turbo.php, set "Enable Automatic Turbo Mode" to no and then yes. Try. :)

    Line 80:

    $result = shell_exec("smartctl -i -n standby /dev/{$disk['device']} | awk 'NR==4'");

    Line 84:

    if ( strpos($result,"STANDBY") || strpos($result,"SLEEP") ) { 

    gives me good result. 

     

    Also changed the logging to be more clear for people like me (a bit stupid, lol)

    logger("Total Data Drives Spun Down: $totalSpunDown/" . count($validDisks));

    = "Feb 27 19:55:36 Server root: Total Data Drives Spun Down: 2/3"
     

    with hdparm and "if ( ! strpos($result,"active") ) {" the code counts unknown as spun down because it can't find "active".

    I guess it won't work good with devices or hba's without smart support? Could fall back to hdparm if so.

    • Thanks 2
  8. I used the plugin "Nerd Tools". Installed "kbd-1.15.3-x86_64-2.txz" (Settings - Nerd Pack) and added this to the go file on flash for Swedish keyboard (qwerty) in terminal etc:

    # load keyboard layout
    loadkeys se-latin1

    For german (qwertz), you have these:
    de-latin1-nodeadkeys
    de-latin1
    de-mobii
    de
    de_CH-latin1

    de_alt_UTF-8

    Add and reboot (you can also try it out by running "loadkeys de-latin1-nodeadkeys" in the server terminal without rebooting ofc).
     

    You could also download kbd-1.15.3-x86_64-2.txz manually and put it in to flash/extra folder and it will install at boot instead of using Nerd Tools.


    I hope this helps. :)

    • Like 1
  9. Something went wrong with the last update. Using latest.

     

    Log fills with this:

     

    Quote

    2019-02-19 14:59:16.565 Status: Domoticz V4.9701 (c)2012-2018 GizMoCuz
    2019-02-19 14:59:16.565 Status: Build Hash: 98723b7d, Date: 2018-06-28 08:00:58
    2019-02-19 14:59:16.565 Status: Startup Path: /var/lib/domoticz/
    2019-02-19 14:59:16.567 [1;31mError: Database incompatible with this Domoticz version. (You cannot downgrade to an old Domoticz version!)[0;0m

    V4.9701, the latest stable was 4.9700. Looks like it pulled from stable instead of latest?