All recordings fail immediately: "There was a transcoder error". Help!

Server Version#: 1.19.5.3112
Player Version#:
Tuner Make/Model: HD Homerun Connect Duo
Guide/Lineup name:
Using XMLTV?:
Channel number/Name:

Running Plex in Docker on OMV (OpenMediaVault) on Raspberry Pi 4 with HD HomeRun. Installed a couple of weeks ago, got it working and recorded a couple of programmes. Just come back to it to record… and it’s not working. Scheduled recordings and attempting to record programmes currently on all fail with “There was a transcoder error” message. Updated plex to latest version, NAS has plenty of free space (over 1TB).

Log attached below. Basically I tried a couple of times to click “Record” on a currently playing programme from Guide. Both failed with same transcoder error message.

Can anyone help?

Plex Media Server.log (301.4 KB)

I’m seeing the following errors in your logs at the start of the log file you provided:

Jul 27, 2020 19:18:24.377 [0xb6f88970] WARN - [FFMPEG] - Error loading external lib: /config/Library/Application Support/Plex Media Server/Codecs/5f603a2-3204-linux-armv7hf_neon/libaac_latm_decoder.so: failed to map segment from shared object
Jul 27, 2020 19:18:24.377 [0xb6f88970] WARN - [FFMPEG] - Error loading external lib: /config/Library/Application Support/Plex Media Server/Codecs/5f603a2-3204-linux-armv7hf_neon/libhevc_decoder.so: failed to map segment from shared object
Jul 27, 2020 19:18:24.377 [0xb6f88970] WARN - [FFMPEG] - Error loading external lib: /config/Library/Application Support/Plex Media Server/Codecs/5f603a2-3204-linux-armv7hf_neon/libaac_encoder.so: failed to map segment from shared object
Jul 27, 2020 19:18:24.377 [0xb6f88970] WARN - [FFMPEG] - Error loading external lib: /config/Library/Application Support/Plex Media Server/Codecs/5f603a2-3204-linux-armv7hf_neon/libh264_decoder.so: failed to map segment from shared object
Jul 27, 2020 19:18:24.377 [0xb6f88970] WARN - [FFMPEG] - Error loading external lib: /config/Library/Application Support/Plex Media Server/Codecs/5f603a2-3204-linux-armv7hf_neon/liblibx264_encoder.so: failed to map segment from shared object
Jul 27, 2020 19:18:24.377 [0xb6f88970] WARN - [FFMPEG] - Error loading external lib: /config/Library/Application Support/Plex Media Server/Codecs/5f603a2-3204-linux-armv7hf_neon/libdca_decoder.so: failed to map segment from shared object
Jul 27, 2020 19:18:24.377 [0xb6f88970] WARN - [FFMPEG] - Error loading external lib: /config/Library/Application Support/Plex Media Server/Codecs/5f603a2-3204-linux-armv7hf_neon/libmpeg2video_decoder.so: failed to map segment from shared object
Jul 27, 2020 19:18:24.377 [0xb6f88970] WARN - [FFMPEG] - Error loading external lib: /config/Library/Application Support/Plex Media Server/Codecs/5f603a2-3204-linux-armv7hf_neon/libac3_decoder.so: failed to map segment from shared object

I see you are running Plex in a Docker container… I don’t use Docker for Plex, but I did a bit of quick googling and found this thread where another user was using Docker and OMV getting similar errors. Does your mountpoint in OMV have noexec set?

Yep. noexec etc. all set. Still getting error…!

It isn’t clear, you mounted with exec or you have noexec?

1 Like

Seconding Tiberius - please verify, because according to the other thread having noexec set causes this problem.

To provide insight –

  1. Codecs are “shared object” library files (blocks of executable code)
  2. Linux differentiates between code and data.
  3. All files can be read but not all files can be ‘executed’.
  4. Shared-object (codecs) require additional privilege (exec priv) to be integrated into the running executable (transcoder). This is where ‘noexec’ stops the operation (security mechanism).
1 Like

To clarify, I thought I had OMV mountpoint set with noexec. After your comments I went back to check. And I hadn’t. Fixed it and now solved. All working. Thank you so much chaps.

For anyone reading this with same problem here’s how I implemented suggestions above:
Solution 1: remove noexec from current mountpoint

  • SSH into Raspberry Pi
  • Open fstab (sudo nano /etc/fstab)
  • Under mountpoint(s) delete noexec:
  • Save & exit

That sorted problem for me. However, not 100% but from reading forum posts it seems that, even if you do this, OMV likes to re-mount with noexec after updates etc. and the problem comes back. I think solution is config file stops it doing that:

Solution 2: remove noexec from OMV configuration parameters

  1. SSH into OMV Pi
  2. sudo nano /etc/openmediavault/config.xml
  3. Search (ctrl W) for “mntent”, a little below it delete noexec from opts:
  4. Save & exit

Hopefully that will stop problem recurring.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.