# Detecting Intros stuck forever

**URL:** <https://forums.plex.tv/t/detecting-intros-stuck-forever/935800>\
**Category:** Plex Media Server\
**Tags:** server-linux\
**Created:** [January 27, 2026, 2:14pm UTC](https://forums.plex.tv/t/detecting-intros-stuck-forever/935800 "2026-01-27T14:14:41Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![Tvfan567](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/tvfan567/32/345449_2.png) [@Tvfan567](https://forums.plex.tv/u/Tvfan567)\
**Post date:** [January 28, 2026, 10:42am UTC](https://forums.plex.tv/t/detecting-intros-stuck-forever/935800/7 "2026-01-28T10:42:34Z")

</div>

Thank you, I have my transcode directory mapped to /transcode which maps to /dev/shm/ on the host - which I believe means it uses RAM. This is to reduce wear on disk drives. I have monitored RAM usage and it never gets anywhere close to full when the issue happens. I’ve had a google around and some people recommend creating a temp folder like this on ram…  
mkdir -p /tmp/PlexRamScratch && mount -t tmpfs -o size=8g tmpfs /tmp/PlexRamScratch  
So I’ve now mapped my transcode folder to /tmp/PlexRamScratch and set the above command to run on server startup.  
I’m not familiar with inotify, is this something I should research and consider?  
Do you think this is a good idea. I’ll try it see how it goes.

---

_[View the full topic](https://forums.plex.tv/t/detecting-intros-stuck-forever/935800)._