CS01-HS

Members
  • Posts

    362
  • Joined

  • Last visited

Recent Profile Visitors

1375 profile views

CS01-HS's Achievements

Contributor

Contributor (5/14)

54

Reputation

  1. Huh, I didn't realize the built-in apcupsd was compatible with a NUT master. I have a similar setup and use the NUT plugin instead. (Detailed description of my setup here.)
  2. Thanks, I should have searched. Looks like it goes all the way back to 6.8.3 I triggered it over an SMB connection. This particular share doesn't have NFS enabled unless you meant system-wide. I can imagine SMB bugs triggering the underlying fuse "bug" (which is marked as won't fix) so I'll wait for a version with SMB fixes before digging deeper. I think in my particular case a stale directory listing resulted in the attempted move of non-existent file.
  3. The SMB bugs? Sure, but it shouldn't break shfs.
  4. I was moving a file from one folder to another within a share (on Mac) when an error occurred and the share disconnected. Checking the terminal I saw /mnt/user/ was inaccessible. Sorry I don't have a full syslog or diagnostics to share but this (coincident with the SMB disconnection) seemed relevant: Dec 4 09:05:21 NAS shfs: shfs: ../lib/fuse.c:1451: unlink_node: Assertion `node->nlookup > 1' failed.
  5. And you're sure they sleep with the container stopped? Maybe you have USE_HDDTEMP set to yes? If not I don't know what could be causing it.
  6. Apple began AFP deprecation in 2013 and still haven't removed it I assume because they realize their SMB implementation's lacking. I wish unRAID would re-add AFP support but admittedly I don't know how much work's required to maintain it.
  7. Did you restart the container after (and verify your commenting out the block persisted through restart) ? Can't imagine with no calls to the drives how it would keep them awake.
  8. It's probably the smartctl call in telegraf. Check your config: vi /mnt/user/appdata/Grafana-Unraid-Stack/telegraf/telegraf.conf Do you have nocheck = "standby" in inputs.smart? [[inputs.smart]] # ## Optionally specify the path to the smartctl executable path = "/usr/sbin/smartctl" # # ## On most platforms smartctl requires root access. # ## Setting 'use_sudo' to true will make use of sudo to run smartctl. # ## Sudo must be configured to to allow the telegraf user to run smartctl # ## without a password. # # use_sudo = false # # ## Skip checking disks in this power mode. Defaults to # ## "standby" to not wake up disks that have stoped rotating. # ## See --nocheck in the man pages for smartctl. # ## smartctl version 5.41 and 5.42 have faulty detection of # ## power mode and might require changing this value to # ## "never" depending on your disks. nocheck = "standby" # Otherwise I don't know SAS but I remember some forum discussions of SAS and spindown, maybe you have to customize the call. Worst case you can comment out the whole block which should resolve spindown but will disable SMART stats in grafana.
  9. Darn. Maybe this is the push I need to learn docker/container distribution.
  10. I love the Grafana Unraid Stack - clean and simple. Any plans to update it with a recent version of Grafana? They've added some handy features since v7.3.7: https://grafana.com/categories/release/
  11. First thanks for this container, very handy. One suggestion: I was running batch conversions in HandBrake and couldn't figure out why my iGPU wasn't fully utilized: It turns out it was but it was maxing out 3D render load (95%) and the reporting script (get_intel_gpu_status.sh) grabs video load (9%): So I tweaked the script to grab whatever's highest: #!/bin/bash #This is so messy... #Beat intel_gpu_top into submission JSON=$(/usr/bin/timeout -k 3 3 /usr/bin/intel_gpu_top -J) VIDEO_UTIL=$(echo "$JSON"|grep "busy"|sort|tail -1|cut -d ":" -f2|cut -d "," -f1|cut -d " " -f2) #Spit out something telegraf can work with echo "[{\"time\": `date +%s`, \"intel_gpu_util\": "$VIDEO_UTIL"}]" #Exit cleanly exit 0 I overwrite the container's version with the following Post Argument, where utils is a new mapped path to the folder containing my tweaked version: && docker exec intel-gpu-telegraf sh -c '/usr/bin/cp -f /utils/get_intel_gpu_status.sh /opt/intel-gpu-telegraf/; chmod a+x /opt/intel-gpu-telegraf/get_intel_gpu_status.sh' (Full path to cp is necessary because cp is aliased to cp -i) Now the display reflects full utilization:
  12. One advantage I noticed was it exposed unraid-autostart which I've added to my backup sets since reinstallation through Previous Apps didn't restore it (though it worked perfectly otherwise.)
  13. I have appdata on a single XFS-formatted SSD. Recently on occasion a container would disappear on restart necessitating reinstall – thought it might be docker image corruption so I should recreate it. In the process I saw 3 options for docker root: BTRFS image XFS image Directory Directory looked interesting so I thought I'd try it. Have I chosen poorly? Are there benefits I can take advantage of?
  14. I don't know if either of these applies but since RC2 VNC with Safari doesn't work for me.
  15. Sorry for the delay, just saw this. Actually I meant Duplicacy's full appdata directory. On unRAID that's typically: /mnt/cache/appdata/Duplicacy I run the Backup/Restore Appdata plugin weekly which backs up all my containers' appdata directories (and my flash drive) to the array, so for simple corruption I'd just restore from that. I'm talking about catastrophic failure, your server's struck by lightning or stolen, etc. I believe everything necessary to recreate a container is either on flash or in appdata. So I take those two backups, created by the backup plugin, and save them elsewhere – an offline flash drive, remote server, etc.