Rick Gillyon

A bit of help if possible. I use xteve to combine iptv and ota tv via hdhomerun. The hdhomerun m3u has e.g. #EXTINF:-1 tvg-ID="BBC2" tvg-chno="2" tvg-name="BBC Two" tvg-logo="https://s3.amazonaws.com/schedulesdirect/assets/stationLogos/s17154_h3_aa.png",BBC Two http://192.168.1.17:5004/auto/v102 With 192.168.1.17 being the address of the hdhomerun. I'm now trying to add a second hdhomerun on 192.168.1.18. I had assumed that if I added another m3u, identical to my existing one except with the .18 ip, xteve would see that if there are no connections left to .17 for a specific channel, it will use .18 (limited to 4 connections per m3u). Unfortunately, it looks to be ignoring the second source for the channel. Any idea how I can combine both hdhomeruns as one source/playlist?

Reinstalling them won't do anything. You need to shut them down and delete the appdata. Or restore a known good backup.

It's the one by jalle19: Having said that, my advice is to do what I did, dump telly and the proxy and move to xTeVe. Far smoother and more reliable, using the built-in buffer in xTeVe there's no need for a proxy.

Did you set CA to look in DockerHub?

What's the "unraid.dvb" option in the build list, i.e. Edit: it has the same description as rc4.

Yes, to you. There have been one or two reporting corruption on cache, but very rare. It's possible those were caused by moving corrupt databases to cache. Cache certainly seems safest.

Regress to 6.6.7 or make sure all appdata is on a cache drive.

Thanks, I was obviously confused. Set to Yes and now moved.

I have two shares set to Cache Prefer, tv and plex: These are TV recording drives. Mover runs overnight and used to move the recordings to the array. I just noticed this has stopped working. Mover runs but finishes straight away: There are files in these shares but they just don't get picked up. Any idea where I'm going wrong? Diagnostics attached. Thanks. unraidpvr-diagnostics-20190924-0749.zip

or 3. Try 6.7.3-rc3 where limetech thinks it's fixed.

What version of unRAID?

It's an intermittent problem, chances are if plexpass failed, plex will eventually fail too.

Limetech posted this yesterday, which implies that they're not sure whether it is fixed by cache drive, and that it's not fixed in 6.8: Here:

Do you have appdata on cache? That seems to avoid the problem.

All my appdata is on cache pool, no corruption on 6.7.2 since release.

Check Q5 in the following Github link:  https://github.com/binhex/documentation/blob/master/docker/faq/unraid.md

You need to map them in Plex settings in manage channels. So you need an epg source too. You can specify the epg XML file in the telly config, and tell Plex to use the telly epg at http://<telly IP>/epg.xml

Map /etc/telly to appdata/telly/ and put your m3u there. Reference the m3u in telly.congig.toml as M3U = "/etc/telly/xxxxx.m3u" If I was starting now I'd use the xTeve docker though.

I have a new(ish) Seagate 8TB IronWolf HDD in my server, precleared fine, but I'm seeing some SMART numbers that I don't get on my other drives, i.e. Raw read error rate 31460368 Seek error rate 49357490 G-sense error rate 2744 Hardware ECC recovered 31460368 The SMART extended test passes, and the hits I get searching for these counters are mixed: some sources (i.e. Wikipedia) say don't worry, the counter isn't a counter but some weird raw value; other sources (especially for read error rate) say that the drive is failing. I'm still in RMA period for this drive, so I'm really just looking for someone to pat me on the head and tell me it'll all be okay. Full SMART report attached. Thanks! ST8000VN0022-2EL112_ZA1FEFD2-20190807-1701.txt

Mylar stopped working properly for me sometime in April. Prior to that it worked like a champ, since then I've had maybe 5 downloads total. Logs attached, any ideas? Sab seems fine, Mylar has just stopped finding stuff, but can be found manually from my indexers no problem. Sonarr etc. still working fine with Sab. Thanks. UPDATE: For others getting this same issue, I've found a solution. Edit Mylar's config.ini and remove the provider_order line completely. Sometimes this gets screwed up. So far I'm back to working again. Funny that @CHBMB replied to this just as I was typing out the update...

I think this is an unrelated Plex issue. I sorted this by rolling Plex back to 1.14.1.5488-1-01

Thanks for that. I always assumed Prefer and Only would move.

It does not happen with a cache drive, mover will just do the initial move then it's there for good.

Just set your appdata share to use cache, then mover will move it.

Hit the Container Size button on the Docker page to see which Docker is the problem.