I just installed Jellyfin and went through the setup process and the initial scanning killed the server. Again nothing in the logs.
This suggests the issue _is_ at least partly a hardware issue. All I have left are the CPU and motherboard but both work fine unless intensely scanning files.

I have tried:
- New power supply
- New cables
- Memtest (clear)
- Safe mode (with and without starting the array)
- Multiple different Plex docker images
- None of the HDD or NVMe are reporting errors

I have a new motherboard and the CPU appears to work fine (hw transcoding fine).

Could this be a HDD issue? 

I can run for days with no crash until I start the Plex docker. Then scheduled maintenance kills the server.
Complete panic and reboot but nothing in the logs.
 

Aug 10 15:18:08 Sakaar kernel: eth0: renamed from veth8e9cec0
Aug 10 15:18:08 Sakaar kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth2823d2e: link becomes ready
[ crash occurerd at approx 15:58]
Aug 10 15:59:33 Sakaar kernel: microcode: microcode updated early to revision 0x56, date = 2022-08-02
Aug 10 15:59:33 Sakaar kernel: Linux version 6.1.38-Unraid (root@Develop-612) (gcc (GCC) 12.2.0, GNU ld version 2.40-slack151) #2 SMP PREEMPT_DYNAMIC Mon Jul 10 09:50:25 PDT 2023

Attached is my syslog (mirrored to the Flash drive) and diagnostics in case someone can see something I can't.

EDIT: Jellyfin shows some failures in the logs prior to the crash but there are a few of the same type and I'm not sure that it could cause a crash.

 

MediaBrowser.Common.FfmpegException: ffmpeg image extraction failed for file:"/media/tv/Taskmaster/Season 12/Taskmaster (2015) - S12E01 - An Imbalance in the Poppability [WEBDL-1080p][AAC 2.0][x264]-NTb.mkv" at MediaBrowser.MediaEncoding.Encoder.MediaEncoder.ExtractImageInternal(String inputPath, String container, MediaStream videoStream, Nullable`1 imageStreamIndex, Nullable`1 threedFormat, Nullable`1 offset, Boolean useIFrame, Nullable`1 targetFormat, CancellationToken cancellationToken) at MediaBrowser.MediaEncoding.Encoder.MediaEncoder.ExtractImage(String inputFile, String container, MediaStream videoStream, Nullable`1 imageStreamIndex, MediaSourceInfo mediaSource, Boolean isAudio, Nullable`1 threedFormat, Nullable`1 offset, Nullable`1 targetFormat, CancellationToken cancellationToken) at Emby.Server.Implementations.MediaEncoder.EncodingManager.RefreshChapterImages(Video video, IDirectoryService directoryService, IReadOnlyList`1 chapters, Boolean extractImages, Boolean saveChapters, CancellationToken cancellationToken)

sakaar-diagnostics-20230810-1602.zip syslog (15)

Edited August 10, 20232 yr by Craig Dennis

My issue has been resolved but what an issue. I had one bad RAM module as well as intermittent overheating. No wonder it was so difficult to isolate. 

@Craig Dennis how were you able to isolate the problem to a bad RAM? I can’t tell you how much I’ve related to everyone’s post within this thread and still continue to have the same recurring issue. I am going to swap the ram to see if this resolves it.

Hello.

For your info, I tried yesterday with the latest version and... it crashed.

@Craig Dennis for me this is not a ram issue I think. We identified the issues cam with a specific version and next ones...

I also recently updated and tested each new release. Still crashes. So I reverted back and stuck on 
plexinc/pms-docker:1.30.2.6563-3d4dc0cce

Hello everybody.

I have more information to provide, maybe helping for the diagnosys.

I had issues with the mover in another topic, so I tried to disactivate it for data share of plex datas. It seemed to be solved and I tried that during about 2 weeks successfully.

BUT, today, 2 new crashes !! In fact, I suspect is was because of the parity check of unraid.

So... My idea is plex is doing something "wrong" sometimes and, if unraid is doing some kind of "maintenance" (mover, parity check...) it crashes all the system.

What do you thing about that ?

Hello.

Finally, I'm not sure... I tried to disactivate parity check but it still crashed after that.

I don't know what to try more

Hi has anyone found a solution to this as im having this issue as well. I have found this happen mostly when im transcoding 4k to a mobile device and the server randomly drops off. ive got  reasonalble amount of fans in my compact unraid server. all noctua ones. generally my temps looks good unless the transcode is over heating the cpu and its just locking up,Ive got quite a chuncky noctua fan on the cpu too. im running a 13600k with 64gb ddr5 ram.

 

Just had another crash , it looks like if im trying to transcode a large 4k movie which is uncompressed ie not X265 it seems to have a wobbler but cant see why as my setup should be more than capable of handling this. I also recently upgraded to 10gb connectivity with a 2.5gb feed going to my wireless router so it should more than capable of streaming to a wireless device.

Edited April 12, 20242 yr by PhantomICEMAN

I’m having the extact same issues that you guys are talking about. It also seems to be during scheduled tasks. Anybody been able to figure it out? Even a new container still has the same issue. 

Hi. The support told be I have a hardware issue that could cause the problem.

I'm trying to fix it before trying again... This is still strange, even with this hw issue, it's working with the former version

On 5/4/2023 at 4:40 PM, thellamapaul said:

I also have this issue, I also use an nVidia GPU for transcoding (750 Ti). Identified Plex as the issue after changing the time scheduled tasks start and the reboot time followed. Since I've been tracking it, it happened on 4/9, 4/14, 4/28, and 5/1, so pretty sporadic. I have Plex log to my Syslog and attached the logs around the most recent 3 incidents. According to the logs it looks like thumbnails, but there are plenty of times thumbnails are generated without the crash. I'm guessing it's something else that doesn't log.

plex reboot logs.txt 2.22 kB · 6 downloads

Just to add data, my issue ended up being a bad overclock config that was causing the system to crash under high load. 

I am having the same problem with Plex crashing my entire system. System ran flawlessly for 6+ months then suddenly started crashing. Didn't realize that it was Plex at first and started process of elimination. Ended up on Plex being the cause, but I am not able to determine a root cause for the issue. System is brand new bought 6 months ago.

Motherboard: MAG Z690 TOMAHAWK WIFI DDR4 (MS-7D32

CPU: Intel® Core™ i7-14700K @ 3366 MHz

Memory: 64GB total, (2) 32GB slots

Any help is greatly appreciated.

This just started for me as well... entire server becomes nearly completely unresponsive, I can't do anything in the UI except login. I can usually SSH in but most things don't return. Every time it happens, and I eventually get in and run a ps, I can see several old random hung transcode sessions from my Plex container. It doesn't seem to be filling RAM (I do use /dev/shm for transcodes) and I'm using a Tesla P4 card with the latest nVidia driver. I am going to try downgrading to "Production" (from version 565 to version 550) and see if that helps... but right now the only fix has been to power cycle the server because poweroff and reboot at the console don't ever do anything (I can trigger these remotely as it's an Epyc system with IPMI). I've been rebooting about every 3 days for 3 weeks now.  Edited to add: when I do experience this, manually trying to kill the transcode PIDs does nothing; commands trying to stop the docker container or daemon just hang.

Edited December 9, 20241 yr by iamr00t

Im having the same issues.. I wondered about it being a power supply issue... 
Ive ordered a new one.

I have had the same crashes on two different cache drives. 
I also had some issues with IO errors on both drives but only replaced to plex. 

 

and randomly I had a drive pop up as failing unread. but when I changed power connectors that error went away. 
This lead me to believe that the issue was power or motherboard..