meep

Heres the log. Though I did follow @jonathanm's advice and that cleared the remaining files off. Maybe you'll spot something in the log. Am I correct to assume that selecting a directory should move any files and sub-directories therein? unbalance.log

Would be grateful if someone could advise what I'm doing wrong here as I cannot quite grasp how unbalance is dealing with folders.... My Cache drive is failing and I want to move off a number of files/folders resident there. My docker share is set to all disks with cache preferred. so the files are scattered across several disks, but mainly on cache. I want to consolidate them to a single disk, swap out the cache, and move the dockers folder back. I changed my dockers share to disk 4 only and set cache to no. The share has about 2GB of data in it. I selected the Dockers share folder in unBalance for a Gather operation. After a period of thinking, it offered top move only 14kB of data. On checking, I see that my docker share contains 2x items, an Appdata folder and an OSX .DS_store file. unBalance seems to want to move the file , and ignores the folder. I proceeded to try again, selecting only the Appdata folder this time. Again, it offered to move any files inside this top level folder, but was ignoring the sub folders. Is this how it works? I went ahead and selected each folder inside Appdata individually and executed the move. Now, what its done is moved some folders entirely, some folders are partially moved (contents now on either disk 4 or remaining on cache) or some folders were not moved at all. No permissions or other errors were displayed in unValance and there's TBs of space on disk 4. Do I have a fundamental misunderstanding of how unBalance is supposed to work? The OP says it can be used to move files or folders, but it seems to be very selective about what folders it's willing to move. Why would it not move everything inside a selected parent folder? Here's what I've ended up with after asking unBalance to gather all the appdata folders to Disk4;

I'm with this. My Settings and Plugin pages are now a mess of indistinguishable monochrome blandness. At least provide an either/or option.

Just updated now that the DVB Edition is available. Looks good. Couldn't resist. making up the attached...

Perfect. Changed to Read/Write and the error went away. I ended up setting timeshift to use RAM inside the Docker UI in this case as TVHeadEnd supports that but this is a handy trick to know.

I tried doing this on a tvheadend docker to write timeshift files to memory (/tmp/timeshift/) but the docker failed to start, showing this error; any ideas?

I don't doubt it's user related for one minute!! I've tried to use Bouquets but they don't seem to be working. My real problem is that my openVPN has stopped working for some unknown reason. This means I can't troubleshoot during work! I need to get that fixed first.

I'll do that when I have the time and inclination to replicate the issue. Right now, my unRAID/ TVHeadEnd setup is refusing to map DVB-S services to channels and failing to record from DVB-T channels so a big mess that I'm trying to work on.

Here's the bug report for future reference; https://tvheadend.org/issues/4273

Probably something I messed up, in all likelihood!

Can't get at that now as, of course, my openVPN is also acting up following recent events. I'll check this evening and report back. Many many thanks to you and @CHBMB for your patience in holding my hand through this.

That makes complete sense. Thanks for the clarity and helping me understand!

And that's key to my question here.... I installed the 4.0.9 Stable version of this Docker. On my Docker page, an available update was show. I upgraded. Now my TVH reports v4.1.2449 Is this expected behaviour? Furthermore, this 4.0.9->4.1.2449 install it works for me whereas installing what I would understand to be the same version directly does not? That's the confusing bit.

Mostly jesting there, but... It is all working now but if future docker or TVH updates are going possibly break break things, of something changes in unRaid etc. or I neede to keep on top of the TVH people to address new issues, it's justall getting a bit unstable. Of course, I should just pick a working susyem and stick with it but I'm my own worst enemy when it comes to upgraditis!

Thanks. That was really my question - I don't want to uninstall my Stable (working) docker, install the 'latest', find the version, uninstall it and reinstall stable. Of course, I'd likely have all that done by now if I'd just started it instead of asking the question here.

Think I'll just go back to $ky.....

That doesn't make sense? I had originally installed 'Latest' docker version which didn't work and for which I didn't take a version number. I then deleted the docker and support folder and installed 4.0.9/Stable which worked. Afterwards, there was an update which I applied and I confirmed all tuners were still working. I checked the TVH version at that point and it's as screengrabbed in my post above (same as the version you noted just now). I would have expected the 'latest' nonworking version to be newer?

Do we know the version of the development build in the docker currently? I don't want to go through the uninstall/reinstall tango but do want to report it correctly to the nice TvHeadEnd people. Thanks

So it turns out it may be TVHeadEnd after all. I reverted to the 4.09 Stable Docker (I had initially installed Default/Latest in which I had the described problem). Immediately, the tuners all showed up as I would expect: I ran the Docker update and now I'm on tvheadend 4.1.x. Don't quite understand how that happened but the tuners are still correctly displayed. This is on the latest unRAID DVB 6.3.2 (stock DD drivers); So I guess the question is, why would the Default/Latest TVH Docker have the problem and the older version dos not?

I have a TVHeadEnd hardware config question hopefully someone cn help me with.... Until recently, I was running TvHeadEnd in a plugin with my Digital Devices Octopus and DVB-T and DVB-S tuners all running on UnRaid DVB Edition. A recent power cut brought down my server and, on restart, I couldn't get my DVB-T tuners to work (they showed up OK but didn't receive a signal). Having planned for some time to migrate to this Docker, I figured this was the opportunity to bite the bullet. I updated unRAID DVB to 6.3.2 and installed the docker. DVB Edition reports all my tuners present but when I look at the TvAdapters tab of TVHeadEnd, there's an oddity. (images attached) Tuners 0 and 1 are DVB-T and they work OK. Tuners 2 and 5 are on one Octopus daughtercard and they show up and tune channels. However, tuners 3 and 4 show up strangely. On the working DVB-S, the tuner device is shown under 2 directory levels, whereas on the non-working DVB-S tuner, it shows under 1 and has a 'folder' name (if that makes sense). The upshot is that I cannot assign a network to these tuners so I'm down to 2x rather than 4x DVB-S tuners. Any thoughts on this appreciated!

What would be the chances of a (version of) MQTT with mosquitto-auth-plug for MySql? https://github.com/jpmens/mosquitto-auth-plug I'm building an Alexa skill for squeezeboxes (http://hab-tunes.com) and would need to authenticate user access per topic. Thanks for considering!

How would that work with GPUs?

Thank you

Quick update. I saw a Docker update waiting so decided to try. Here's what I see; -Installed some new nodes using npm install node-red-contrib-alexa -Restarted Node-Red Docker -Saw the new functions on the left in admin -Stopped Node-Red Docker -Applied Update -Restarted Node-Red Docker -The new node functions were gone. I suspect that these are being installed to the docker itself and the update process refreshes this? Should I be installing these nodes to my config directory? (navigate to config and then run the install command?) Thanks Peter

Is there something up with the node-red docker not retaining installed nodes on update/restart? I had installed a few new non-standard nodes but following a few updates and restarts, they are now gone from the sidebar. I may have changed mapped ports a couple of times as well which I find causes things to disappear in some dockers. I also changed the admin URL from / to / admin. Just wondering if there's a known issue before I embark on some testing....