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.