Japes

calling this one good. 7.5 hours in and still looking good. Thanks Jorge.

It's been three hours which is double the longest up time I had yesterday and it's still running. Looks like this may have been the issue. I'll check back in later to confirm after a bit more time.

Food that setting and it was set to “Auto”. Changed to “typical current idle”. Let’s see if this works. I don’t have anything overclocked so that’s ok. if this doesn’t work I’ll disable C-States globally since I saw that

Earlier today my server went unresponsive. I Rebooted it and it was fine for a couple hours and then the same thing. I've been using Unraid for a long time now but recently upgraded to 6.10.1 maybe a few months ago. I think I uploaded everything here I need to but I don't know what much of this means. Any help would be great. tower-syslog-20220826-0242.zip tower-diagnostics-20220825-2212.zip

oh, for sure. Photos are stored on an external hard drive that is backed up to the unraid server. It was more a comment of that seeming weird since I haven't added photos to the server in over a week and Mover is supposed to have been run nightly so the Cache drive must have been having issues for at least a week. So, the Docker weirdness I was experiencing last week kind of makes sense now.

Everything seems to be going ok so far. Only one of the dockers so far needed to be re set up like new.

I figured so that's what I was in the process of doing so I'' report back when that's done. Starting with all the family photos since it looks like the mover hasn't moved those in quite awhile

I'm guessing this is the issue but don't know how to proceed

tower-diagnostics-20220523-1109.zip

I did not make a new Unraid install I just uploaded through GUI to 6.10 and then upgraded again today when the pop up came up. I was upgrading an old 2TB drive with a new 6TB drive and I coppied all the data from old drive to a current drive. I then removed the old drive in the config and rebuilt parity with one less drive. all checked out. I then precleared the new drive and added it to the array and formatted it as normal. All checked out. noticed none of my dockers were showing in the dashboard (don't know if that was before or after but they were all on when I went to bed last night as the new drive was finishing Post Read. Remembered last time this happened a few years ago about the rebuilding docker.img. So I did that. but when I went to previous apps location it only had two plugins listed and dockers was greyed out. Unfortunately my flash back up is way out of date. Brain fart and I didn't backup before upgrade. I hadn't upgraded in awhile. I think I was on 6.5 still. But anyway on the app page after deleting and re enabling docker image in settings page I get this at the top. EDIT: found this but here is my cache info

What do you do if you deleted the docker.img file and rebuilt and then went to previously installed apps and find that none of the docker are there. WIll I have to manually reinstall all of these dockers or is there a way to recreate these with all my old settings? I upgraded to 6.10 this past week and installed a new precleared drive and woke up to none of the dockers working. So I did the Docker rebuild first...

Geez...now I feel like an idiot. Thanks a ton. I didn't realize there were two grabbers listed for Schedules Direct and I activated the first one I saw. I changed that and the log is showing that it's running now. EDIT: Just posting to follow up and say I'm back up and running. Thanks again.

SchedulesDirect issues. I've had to rebuild my server after some water issues with flooding in my house and it's been a few years since I set up TvHeadend so I'm not sure what I've done wrong here but I can't get the epg to work. I've SSH in and ran the config script I checked my apdata folder and it created a file and this is the contents username and password have been edited for posting. I then went back into TvHeadend EPG Grabber Module and enabled "internal: XMLTV.....Schedules Direct JSON.... I then re-run internal epg grabbers and I get this every time. what did I miss here?

Parity build was successful. Should I be concerned about anything else with this drive. It was a replacement for another drive and if I need to send it back my window is closing.

Preclear was successfull, 50% through Parity rebuild, no errors.

OK. I've updated everything as suggested and rebooted. Started Preclear and this is what I got... Disk log Apr 3 13:12:03 Tower kernel: sd 7:0:0:0: [sdh] 5860533168 512-byte logical blocks: (3.00 TB/2.73 TiB) Apr 3 13:12:03 Tower kernel: sd 7:0:0:0: [sdh] 4096-byte physical blocks Apr 3 13:12:03 Tower kernel: sd 7:0:0:0: [sdh] Write Protect is off Apr 3 13:12:03 Tower kernel: sd 7:0:0:0: [sdh] Mode Sense: 00 3a 00 00 Apr 3 13:12:03 Tower kernel: sd 7:0:0:0: [sdh] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Apr 3 13:12:03 Tower kernel: sd 7:0:0:0: [sdh] Attached SCSI removable disk Apr 3 13:12:16 Tower emhttp: WDC_WD30EFRX-68EUZN0_WD-WCC4N3YDXYXU (sdh) 2930266532 Apr 3 16:27:03 Tower kernel: sd 7:0:0:0: [sdh] tag#11 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Apr 3 16:27:03 Tower kernel: sd 7:0:0:0: [sdh] tag#11 Sense Key : 0x5 [current] Apr 3 16:27:03 Tower kernel: sd 7:0:0:0: [sdh] tag#11 ASC=0x21 ASCQ=0x4 Apr 3 16:27:03 Tower kernel: sd 7:0:0:0: [sdh] tag#11 CDB: opcode=0x88 88 00 00 00 00 00 a5 01 28 00 00 00 08 00 00 00 Apr 3 16:27:03 Tower kernel: blk_update_request: I/O error, dev sdh, sector 2768316416 Apr 3 16:27:03 Tower kernel: sd 7:0:0:0: [sdh] Stopping disk Apr 3 16:27:03 Tower kernel: sd 7:0:0:0: [sdh] Start/Stop Unit failed: Result: hostbyte=0x04 driverbyte=0x00 TOWER-preclear.disk-20170403-2221.zip tower-diagnostics-20170403-2223.zip

For the record, the reason I've used unRAID for so long was that if you had a stable platform that worked you didn't need to constantly update every time something was updated. Most updates were adding new improvements as nothing needed to be "fixed" since it worked. I ran an older version for a long time and only upgraded when I decided to go beyond 2 TB drives. Asking for plugin support for something that was not buggy without checking for an updated version was never on my radar. I have now updated everything (v6 interface does make it extremely easy by the way) so I'll try again. Since apparently there was no other issues in my logs I'll report back in 24 hours or so.

I wasn't aware there was a new version so my guess would be that I am indeed not using the new version.

############################################################################################################################ # # # unRAID Server Preclear of disk WD-WCC4N3YDXYXU # # Cycle 1 of 1, partition start on sector 64. # # # # # # Step 1 of 5 - Pre-read verification: [7:44:37 @ 107 MB/s] SUCCESS # # Step 2 of 5 - Zeroing the disk: [3:33:28 @ 234 MB/s] SUCCESS # # Step 3 of 5 - Writing unRAID's Preclear signature: SUCCESS # # Step 4 of 5 - Verifying unRAID's Preclear signature: FAIL # # # # # # # # # # # # # # # # # ############################################################################################################################ # Cycle elapsed time: 11:18:09 | Total elapsed time: 11:18:09 # ############################################################################################################################ ############################################################################################################################ # # # S.M.A.R.T. Status default # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # ############################################################################################################################ # SMART overall-health self-assessment test result: PASSED # ############################################################################################################################ --> FAIL: unRAID's Preclear signature not valid. numfmt: invalid format '%1.f', directive must be %['][-][N]f root@Tower:/usr/local/emhttp# I preleared this drive successfully a week ago as a replacement for my parity drive that kept getting errors. Thankfully it was under warranty. Everything worked fine until this weekend. My wife says everything was fine while I was gone but when I returned home I found the new Parity Drive had a red X. I tried assigning it and rebooting and then reassigning it but it wouldn't enable it. So I unassigned it rebooted and started a Preclear. It seemed to go fine until the above error. I've attached the logs I think are needed and hopefully one of you can help me out. Thanks tower-diagnostics-20170403-0851.zip TOWER-preclear.disk-20170403-0854.zip

Oops, that one was all me. The guide data was still present from the Mythtv scan so I thought I had done that already in TVheadend. Thanks for pointing me to my mistake.

I think I have it mostly worked out. I added the following to my AdvanceSettings in my Kodi install... <network> <buffermode>2</buffermode> <cachemembuffersize>41943040</cachemembuffersize> <readbufferfactor>5</readbufferfactor> </network> <pvr> <minvideocachelevel>30</minvideocachelevel> <minaudiocachelevel>30</minaudiocachelevel> </pvr> I adjusted the Cache level until I got a satisfactory balance between buffering and channel change times. Seems to be mostly ok except the three channels on the PBS stream. However I did run into a different issue now...my EPG is now blank. I manually ran the grabber and it appears to run but I get nothing. Loglevel debug: enabled 2016-09-11 20:00:25.378 xmltv: /usr/bin/tv_grab_na_dd: grab /usr/bin/tv_grab_na_dd 2016-09-11 20:00:25.380 spawn: Executing "/usr/bin/tv_grab_na_dd" 2016-09-11 20:00:26.094 spawn: using config filename /config/.xmltv/tv_grab_na_dd.conf 2016-09-11 20:00:29.812 spawn: Fetching from Schedules Direct Fetched 5059 k/bytes in 3 seconds 2016-09-11 20:00:54.216 spawn: loading data: ################################################## 2016-09-11 20:00:54.216 spawn: NOTE: Your subscription will expire: 2017-09-02T15:12:47Z 2016-09-11 20:01:14.844 spawn: Writing schedule: ################################################# 2016-09-11 20:01:14.844 spawn: Downloaded 7798 programs in 48 seconds 2016-09-11 20:01:15.190 xmltv: /usr/bin/tv_grab_na_dd: grab took 50 seconds 2016-09-11 20:01:15.287 xmltv: /usr/bin/tv_grab_na_dd: parse took 0 seconds 2016-09-11 20:01:15.287 xmltv: /usr/bin/tv_grab_na_dd: channels tot= 38 new= 0 mod= 0 2016-09-11 20:01:15.287 xmltv: /usr/bin/tv_grab_na_dd: brands tot= 0 new= 0 mod= 0 2016-09-11 20:01:15.287 xmltv: /usr/bin/tv_grab_na_dd: seasons tot= 0 new= 0 mod= 0 2016-09-11 20:01:15.287 xmltv: /usr/bin/tv_grab_na_dd: episodes tot= 0 new= 0 mod= 0 2016-09-11 20:01:15.287 xmltv: /usr/bin/tv_grab_na_dd: broadcasts tot= 0 new= 0 mod= 0 If there is a different location where more logs would be please let me know. I enabled debug log output prior to running it this last time but I can't find where a log would be output to.

I'm not encoding. It is worse when I'm watching one channel and something else is recording, but it also happens when I'm not recording. I'm concentrating on just the PC right now. I do have the Mpeg licenses on the Pi and that fixed all issues with livetv with Myth but decided one at a time would be best. I did notice that certain channels were consistently worse and thought it could be my antenna but noticed that the signal strength was still saying 98% as the lowest. I do have Kodi-headless and mariaDb dockers running as well. It didn't seem to make a difference before.

Figured I needed to give them both a fair shot. A week with Mythtv and now a week with TVH. TVH was easier to set up. Now I'm just tweaking it. I'm getting buffering for liveTV on not only my Pi but also my windows kodi machine. Once I figure that out I'll more than likely be sticking with TVH. everything else about it seems to be smoother for my Kodi setups and management.

Thanks for such a quick response. That worked.

Very Excited to see this. I've been experimenting with Mythtv but TVHeadend seems to be better supported with Kodi. So I installed through the Community Applications and then went to setup everything. Started the Wizard but there were no options when it got to TV Adapter and Networks. I have a HDHomerun Connect that was working with MythTV. I did see a note "Tuners already in use will not appear below" and I figured MythTV was "using" it even though I had stopped it. I tried removing the MythTV Docker but nothing changed. I then removed TVHeadend, rebooted again and started over with just TVHeadend. Still nothing. I've searched but can't find a solution. Now I'm stressed because I killed a semi working MythTV setup with schedulesdirect going (mostly) and now I'm stuck. I'm sure I'm missing something simple but can't for the life of me figure out what. I read about older versions of TVHeadend needing a HDHomerun driver installed but I thought this version (listed as 4.1 in the about tab) was suppose to be set up for HDHomerun out of the box.