jtownmassacre

I just got done with a reboot and a memtest that came back with no errors. I'm going to cross my fingers and hope that the heat was the culprit. My Unraid server is a R720XD so I'm not sure how viable adding additional cooling to the DIMMS would be, outside of adjusting the fan curve in IPMI. The increased temperature in the room was a pretty unusual event so I'm not terribly concerned about doing anything drastic. I will keep a close eye on things for the time being. Thanks again bmartino1 for your assistance with this problem. This is my first post on the forum. I've always heard that Unraid has a great community and after my experience with this issue, I would have to agree with the sentiment! Stay cool out there brother!!

Thank you both for the assistance! I didn't think of the IPMI logs to help diag., that was a great idea. It does indeed seem to be a DIMM issue. Interesting to note, all the errors appeared during a time when the server was unusually hot, as in the room the server lives in was left without AC for a few days. Have either of you heard of getting errors like this during a period of unusually high temps? I ask because since the temps have been brought back to reasonable levels, I have not received any further errors. As a matter of fact, the "Fix Common Problems" plug-in has actually cleared the error seemingly by itself.

bmartino1, I am greatful for you taking time out of your day and attempting to help, but this is just copy/paste Squids post on the subject that I found by simply clicking on the error in the "Fix Common Problems" plug-in. I posted MY error messages in the hopes that someone familiar with the issue could give me a more "informed" opinion on exactly what the errors are telling me. Shutting down my server and going through 16 DIMMS one at a time is something I would like to avoid if possible, although that is what I might end up doing. Again, thank you bmartino1.

I received this error today: I went to the "Fix Common Problems" plugin and saw this: I then went to "System Logs" in the "Tools" tab and found these: It seems like it could be a RAM issue, but I am not sure. Any advice on how to proceed would be greatly appreciated!! Thanks for taking time out of your day to help!

Any updates? People are leaving your container because of this.

Now that you mention the two versions of ffmpeg, It was indeed the "emby" version people were referring to. I'm sorry I didn't clarify that in my previous post. I can't thank you enough for all you do for me and the community as a whole. Also, I really appreciate your timely response to this particular issue I'm (and a few others) facing! I love you containers and if one is available, I will use it for a sort of "standardized" folder mapping scheme.

I stand corrected. That info came from the Emby forums with a few people pointing the finger at the ffmpeg version being the issue. Someone even stated they manually updated to the latest ffmpeg and it started working again, so I'm at a loss as to what exactly the issue is. A google search does reveal others having the same/similar issue as me but the info is limited and wanting. If anyone has any advice for me as to how to get H.W. transcoding back it would be greatly appreciated. If I can't figure it out in the next couple of weeks, it's going to force me to switch to a different container and I want to avoid that if I can.

I have a similar issue where ANY transcode causes a solid pink screen. From what I've been able to piece together, the issue is having to do with ffmpeg and the fact that Binhex's Emby container is written in Arch. The latest ffmpeg is v 5.1 and the Arch repos are still using 4.8 or something similar. This is causing the transoding errors and until the Arch repo is updated with the latest ffmpeg, the problem will persist. I THINK there is a way to manually update the ffmpeg version but that's above my pay grade. I have also heard that this isn't the first time this container has had this issue. Do to the container being built with Arch it seems to me this issue will happen again. All this info is what I've managed to gather from the few sources I've been able to find regarding this issue. If any of my information is wrong, please correct me.