danielb7390

Hey! Thanks for the quick fix!

Hi, First of all, thanks for maintaining this plugin! Unfortunately i had 2 power cuts in the last week that lasted more than the normal few seconds, and some weird stuff happened, and i cant figure out exactly whats wrong. In attachment, debug zip, and print screens. Sequence of events: The settings are set to power off when battery.runtime < 300. UPS battery is quite new, and seems to be reporting accurate runtime. 21:30 The power failed 21:26 NUT script decided it was time to shutdown the server. But runtime at that time was >900s left (check last image) (Somehow the server started back up, unrelated to NUT, i have to check my BIOS settings... i guess wake by USB or something is causing this) At 21:29, it was back up, and battery runtime was 822. At 21:39 NUT script decided it was time to shutdown, this time with the correct runtime left. Not sure how to debug this at all. I took a look at the scripts and all looks great, the only way i see to this fail is if the upsc command fails, making grep/awk fail causing the -gt comparison to fail somehow (nut-notify@L72), I'm probably way off on this, my bash script skills are 0 to none 🤣 nut-debug-20240315085147.zip

Finally updated to 6.9.1, I'm either having great results or something else is causing this great results. My TBW log used to show ~500gb/day ... 2 days in with 6.9.1... ~15gb/day this is like 33x less 🤔 I swapped the SSD with a same model one (crucial mx500 1tb) the old one was already at 125TB TBW, this one is at 12.6TB TBW. Installed the same exact dockers. Formatted the new SSD cache as XFS, changed docker to use a folder instead of a image file.

I'm wondering if it's not possible to copy the contents from inside the image to the new folder and avoid reinstall the dockers?

I'm trying to find a way to avoid hitting 100% HDD usage when copying files from the downloads folder to their destination, and found this in the docker documentation, searched this forum and only found this thread with no real solution. Tried —-device-write-bps /dev/sdd:1mb But didn't work. Anyone knows how to do this?

Thanks for the plugin. I even started a thread requesting this as a feature.. and another user pointed me here. Does everything i wanted! Thanks!

I didn't get notified of your reply... That does exactly what i need! THANKS!

Hi, This would be a useful feature to me and probably others. I have a gitlab instance running, and for each CI job it creates a docker with a name starting with `runner-`, if it would be possible to add a setting to filter out dockers by a regex or something it would be awesome. Right now my dockers page is double the length it should be because of all this dockers 😄 tl;dr: a setting to default filter docker list by name using regex

Today i remembered to compare the LBAs since my last post on may 10th may 10th = 48905653011 LBAs June 1st = 68670054075 LBAs Difference = 19764401064 LBAs = 9424GB = 9.424TB in 21 days 448GB/day 18.7GB/hour 0.31GB/minute I guess it could be way better since i'm not writting that much to the cache drive at all...

That script(well, smartctl) gave me wrong numbers, my ssd reports that the power on hours are only 349 (14days), that's not correct, i bought it new when i installed unraid on 14 march, and has been running 24/7 since then (uptime ~57days). Recalculating manually and assuming the total LBAs written is not wrong... 48905653011 LBA=22.77 TB perDay = 22.77 TB/57days = 0.40 TB/day = 400 GB/day perHour = 0.40 TB/24h = 0.017 TB/h = 17 GB/hour It seems i'm not getting hit that hard as i thought i was.. still think it's a bit on the high side tho.

Yeah, i don't get it why this is only minor.. if my brand new ssd dies by the end of the year because of this i will be pissed!

Hi, Why the default has replication activated to a file? Is there a reason? How can i disabled it? Tried to override log_bin to OFF/0 in custom.cnf but didn't work..

It seems i got hit with this one also. Cache is a 1TB crucial sata ssd, btfs, not encrypted afaik I seems to have 5MB/s+ writes constant on the ssd, after finding one of the culpirts (unifi controller) that was also writing a lot to appdata, now my 2nd process with most writes is the [loop2]... In a few minutes there's 500MB of writes from [loop2]... At this rate my ssd will probably die soon 😨 My docker list maybe it can help find common dockers? linuxserver/sonarr linuxserver/qbittorrent nextcloud:latest gitlab/gitlab-runner gitlab/gitlab-ce linuxserver/tvheadend linuxserver/minisatip linuxserver/plex binhex/arch-krusader linuxserver/mariadb linuxserver/ombi linuxserver/bazarr linuxserver/radarr phpmyadmin/phpmyadmin didstopia/tvhproxy debian8/apcupsd-cgi

Adding to this, yesterday i no longer had the need for the share.. i was unable to delete share #1, had to remove it by hand from xml.

same here also

Bumping this up, this is annoying me since i started to use unraid a few weeks ago, specially trying to write file paths, our "/" is "shift + 7" for example

Thanks for the suggestion. Installed minisatip docker, had a hard time scanning for all the channels again. Random tuning errors. Remembered to check the TVH version that was installed on my VM and it was 4.2.9, the docker image was a more recent version. So, i recreated the docker and selected the 4.2 image. Just to test tried to pass the tuners directly to TVH, still scanning/tuning problems. So i then tried with minisatip and it seems to be working fine! Got all channels at once, and seems to be tuning to channels fine now. I guess the most recent TVH image has some new bug or is incompatible in some way with my hardware.

Hi, Im new to unraid, currently running the trial version and have a Hauppague WinTV Quad PCIe tunner (europe version). Installed this plugin, selected the OpenELEC build that matched my current unraid version, all 4 tunners are detected. Installed tvheadend docker, Passed the /dev/dvb into it. The problems started at the scan stage, it took multiple scans to find all the channels. Then to tune a channel it would almost never work. Rebooted the docker, same. Rebooted unraid started working fine. After a few minutes back to the same issue. tvHeadend reports no signal, poll timeout. To check if the problem was my tunner or tv signal, i created a ubuntu VM, installed the drivers from the official PPA of Hauppage and passed thought the tunner. It works perfect, scanned all channels on the first try, tunning work consistently. Am i missing something or Are the Unraid DVB drivers broken? I would like to avoid having a VM just for this... Thanks in advance.