Peanutman85

I experienced the issue again. Diagnostics are attached. unraid-diagnostics-20191111-2141.zip

Oops. I already did. If it happens again with rc3, I'll post a new thread. If it doesn't, I'll upgrade again this weekend and post the diagnostics if/when it happens again.

For the past two days now, my server has lost network connectivity at approximately 6pm. A reboot has brought it back online both times. What appears to be the relevant part of the log is below. Any idea what is causing this? I plan on rolling back to rc3 to see if that stops this from occurring

That worked. Thanks

I'm experiencing the same issue

I also had this issue with 6.7.0. I was unable to connect after upgrading, but it works fine after downgrading back to 6.6.6

I also have this issue with a Samsung cache disk. It was btrfs, so to try to resolve it, I reformatted it as xfs, but I'm still experiencing the problem.

Nevermind. I'm an idiot. For some reason, when the update assistant warned me that there were extra parameters in the emhttp command, i deleted the entire command instead of just the extra parameters. I've now updated to 6.5.1. Sorry and thanks.

My update from 6.5.0 to 6.5.1 failed. I was unable to access the webgui, even when I booted to GUI Safe Mode. I ran the update assistant prior to updating and no issues were found. To roll it back, I tried to copy the files from the previous folder, but still experienced the same issue. In order to get it back up and running, i had to completely restore a backup of my flash drive from the last time I updated.

I'm still having issues on rc15e

Any chance someone could create a docker container to be able to run a host on Sia? https://github.com/NebulousLabs/Sia-UI

I think i found the problem. I believe it's a permissions issue. Have you guys ran the new permissions tool on the appdata folder/cache drive? I believe that's what created the issue for me. I installed a fresh container from scratch. Everything worked fine until i ran new permissions. At that point, I started getting the transcoding error again.

https://github.com/jakewaldron/PlexEmail/issues/3?_pjax=%23js-repo-pjax-container#issuecomment-282183459

Supposedly, the corruption issue has now been fixed. Any chance of getting the PlexEmail container added back?

I'm having the same problem. I've tried 1.5.4 and 1.6.1. I've also tried using both this docker container and the official Plex container, but the issue hasn't gone away The only thing I've seen in the Plex forums as a possible solution is to wipe out the container and reinstall starting from scratch, which I'd rather not do if avoidable

I'm experiencing the same issue with my server. Were you ever able to figure out the cause?

http://lime-technology.com/forum/index.php?topic=40937.msg481138#msg481138

That fixed it. Thank you!

I just tried updating the docker today and now the docker is gone. If I try to recreate it, I get the following error: "Unable to find image 'Shows:/tv:rw' locally Error response from daemon: invalid registry endpoint https://Shows:/v0/:'>https://Shows:/v0/: unable to ping registry endpoint https://Shows:/v0/ v2 ping attempt failed with error: Get https://Shows:/v2/: dial tcp 92.242.140.21:0: i/o timeout v1 ping attempt failed with error: Get https://Shows:/v1/_ping: dial tcp 92.242.140.21:0: i/o timeout. If this private registry supports only HTTP or HTTPS with an unknown CA certificate, please add `--insecure-registry Shows:` to the daemon's arguments. In the case of HTTPS, if you have access to the registry's CA certificate, no need for the flag; simply place the CA certificate at /etc/docker/certs.d/Shows:/ca.crt" Any idea what the problem is? It was working fine yesterday before I updated unRAID and the docker.

+1

I just noticed a problem with PlexRequests. I updated it last night, so not sure if that's what caused the problem. I am getting the following when I try to access the WebUI: Any ideas?

I'm having the same problem

Thanks!

I had an issue where my disk went offline while doing a parity sync. After rebooting, the disk is now showing "data invalid." However, the parity sync never finished and the disk passes the smart test. Is there a way to trust the disk, so I don't lose all the data on it?

Sounds like it's acting the same way mine does when I enable email notifications. Do you have any other notifications enabled except for Pushover and the text file? If so, try to disable those and see how it acts.