LSL1337

Members
  • Posts

    147
  • Joined

  • Last visited

Everything posted by LSL1337

  1. huge thanks, great script, I started using it with a few modifications.
  2. Hello. I've been away for a few weeks, but here are the debug logs attached. (I was getting battery replacement warnings on my new APC BX series UPS) I know I can disable this feature, but i find it very useful, to get notification, when the battery needs replacement eventually, and the UPS has this automatic self test every 2 weeks. Last time I got the replacement warning was yesterday 9:24PM (march 16th). Thanks for looking into it! nut-debug-20240317235549.zip
  3. Hi guys! I can't seem to get remote tunneled access to work. I can connect from outside the network, so my router portforwarding works, but I can only reach LAN IPs. I have 2 users configured. One is remote access to LAN, the other is remote tunneled access. Both work the same way. I can reach only LAN IP-s, nothing works for normal sites in the browser. I have few dockers running, no VMs. I think I have 2 dockers, which have different IP addresses then the unraid machine, not sure if this is non standard setup, and breaks the default routing or something with wireguard. thanks!
  4. Hello. What is the value, which triggers the battery replacement warning message? I have an APC BX 750 ups, and it regularly throws this message with a new original battery. The standard unraid ups service had the same issue, and i have found similiar issues with other people reporting the same thing with the BX series. I don't see anything in the reported status. ups.test.result Done and passed. On the first week, i got the notification daily or once in 2-3 days. Now it's been a few days... very weird Thanks.
  5. I just got BX 750, and I have the same issue...
  6. the docker works with "config type: device" and '/dev/bus/usb/001/006', this was not the issue. my question was do i need to somehow pass this USB id to the unraid sensor app?
  7. yes, i tried it with nzxt-smart2 and nzxt_smart2, and after that 'sensors', but it didn't add any new sensors at least it didn't throw error for the modprobe, so there is a driver with this name. when I launch the docker, I need to tell it which USB it's connected to. can I somehow give this info to the sensors or sensors_detect app?
  8. thanks for the reply! sensors doesn't show any values from the nzxt device, just from my normal sensors. sensors detect doesn't find the device either. the modprobe command didn't bring up anything, lsmod just showed the same thing as you wrote. any ideas?
  9. bump? anyone? seems like an easy thing to do, if you know your way around linux/unraid
  10. Hello, I added az NZXT Smart v2 fan controller to my unraid setup. In 6.11.0 changelog there is a line about it: How can I load these drivers, so they are shown in the UI, and they can be used to control the fanspeed with custom scripts via 'standard hwmon'. I installed the docker, which shows these fans inside the docker, and I can control them manually, but the docker can't read hdd temps. I'd prefer to use the fans without docker (liquidctl) anyway. The docker's readme also mentiones, that this device can be used through hwmon, and the drivers are part of the 5.13 kernel, which is i guess it is mentioned in the 6.11.0 changelog. (https://www.kernel.org/doc/html/latest/hwmon/nzxt-smart2.html) soooo, how do i load these drivers, and 'expose' these fans to unraid? Thanks!
  11. wow, it's working great now, thanks! what can I do to control the fans through unraid/hwmon? with 'nzxt-smart2' drivers? In that way, the old scripts could control it based on hdd temp maybe.
  12. yes, I'm trying to install the docker (avpnusr/liquidctl-docker) from CA, which needs "/sys/bus/usb/devices/xxx" i guess. is there any other way I can control my nzxt smart v2 under unraid? on the liquidctl github, there is a small note, that: "Smart Device V2 controllers are supported by the mainline Linux kernel with its nzxt-smart2 driver" but i had no luck with that either. i'm on the latest unraid build
  13. root@LSL-NAS:~# lsusb Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Ultra Fit Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 2040:0265 Hauppauge dualHD Bus 001 Device 002: ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS Bus 001 Device 006: ID 1e71:200f NZXT NZXT USB Device Bus 001 Device 005: ID 1462:7d20 Micro Star International MYSTIC LIGHT Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub root@LSL-NAS:~# lsusb -t /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 10000M |__ Port 1: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 2: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 3: Dev 3, If 0, Class=Vendor Specific Class, Driver=em28xx, 480M |__ Port 11: Dev 4, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 4: Dev 6, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 2: Dev 5, If 0, Class=Human Interface Device, Driver=usbhid, 12M
  14. hello, how do I figure out, which USB device is my nzxt fan controller? Hotplug USB plugin doesn't show anything in unraid. I'd like to use them to control 3 fans, but based on HDD temp alone. Is that doable, or cpu temp is the only one, which can be read by the device? Thanks!
  15. hello guys. i love this plug-in, but from now on I moved on to two cache pools. How does this plug-in handle that scenario? As I read the rpevious post, the settings are the same for both cache pools, but what about the trigger conditions? Is it checked for the different pools at a different time? I have a 2TB and a 500G pools with different habits. If I set a 75% trigger, what happens? is the 2TB and 500GB condition evaluated different? and mover only starts for the triggered cache? or it checks the sum of the 2 caches reaches 75%, which might mean, that my 500GB is full, and the 2TB is only 50%, it would mean this script is never triggered? Thanks for your help!
  16. yes, it's working if i only use the 2nd line, but i wouldn't like to lose HW transcoding, so i'd prefer both to work. so, how can i combine both lines into 1 working line?
  17. Hello, I run this docker with Intel quicksync for a long time. now I added an USB DVB card to my setup. my extra paramter before was: --device=/dev/dri now i'd like to add: --device=/dev/dvb/ what should by my 'combined' extra parameter string? If i just copied both, it didn't recognize my DVB card! Thanks!
  18. I have 2 linuxserver plex dockers running. one in host, the otehr is in br0. 192.168.1.100 (unraid ip) and 192.168.1.128 (br0). I have 2 tautulli linuxserver dockers running in bridge. First is 8181:8181, second is 8181:8182. my first tau docker can join to the 192.168.1.100:32400 plex docker my second tau docker can't join to the 192.168.1.128:32400 br0 plex docker. Only via internet. But since the IP changes in every few days, it looses connection. any idea what should i configure in each docker to be able to join them locally? thanks
  19. I just installed the new 1.21.x version, and HDR to SDR encode works like a charm with hw transcode. I have a 7700T (Kaby Lake), which supports hevc 10bit encode, decode. very nice, now remote users can watch HDR content easily. I even found the server side tonemap better, than the one done by PMP on directplay playback on sdr devices (w10). just my experience, maybe useful for others. I'm still on 6.8.x
  20. hi guys, maybe stupid question, but if I don't want to map these to RAM (don't have a huge amount), but to cache instead, would it work?
  21. what is the workaround? how do i know if i removed it? (I don't think I did btw, cos its more work, than just simply change 1 value) thanks for the quick reply! i think i changed it to 8182:8182, but the original 'parameter'
  22. I have 2 PMS (linuxserver) and 2 Tautulli (linuxserver) instances running. plex1 is host plex2 is br0 (different IP) both tautulli is bridge 8181 and 8182 ip mapped to host. occasionally my 2nd tautulli instance docker template is modified (during sunday morning scheduled jobs. auto update, or auto backup) and the 8181 default IP is also added to the template, after which it can't start, as it is already taken. Now both my plex dockers are linuxserver, and they obv. have different appdata folders, and they now got mixed up. can this 'feature' be disabled? any idea where to look for it? thanks
  23. Ok, i was going through my syslog, and found it by accident. So if anyone else wants to write this to share for any reason, you can use this very basic script: (via custom scripts daily or whatever) ##copy to user share cp /var/log/file.activity.log /mnt/user/backup/logs/FA/$(date +"%Y-%m-%d__%H-%M")__File_Activity.log ##clear the log /usr/local/emhttp/plugins/file.activity/scripts/rc.file.activity 'clear' ## remove logs older than 180 days find /mnt/user/backup/logs/FA/ -name '*.log' -type f -mtime +180 -exec rm -f {} \;
  24. Hello Is it possible to change the paths of the backup/cache/log directory? it says "Controlled by Docker Container" which doesn't say much to me. I'd like to put some of these to outside of /config