External Drive Mount Fail & Hence Plex Container Fails to Start After Update to ZimaOS+ v1.5.4-beta1

Insight & Feedback
1

OS Version:
ZimaOS+ v1.5.4-beta1

Service Affected:
Plex (Docker container)

Issue Summary:
After updating to v1.5.4-beta1, Plex no longer starts. Restarting the container fails consistently with an OCI runtime mount error.

Error Message:

Error response from daemon: Cannot restart container 57044a6410460621f48a288045d5e0533e1cba5b3fa8a7facc35dd118ce3cdbf:
failed to create task for container: failed to create shim task:
OCI runtime create failed: runc create failed:
unable to start container process:
error during container init:
failed to fulfil mount request:
open /media/NVFLIX/PLEX: input/output error

What Changed:
Plex was working normally before upgrading to v1.5.4-beta1.
Issue appeared immediately after the update.

Mount Details:

  • Plex media directory mounted from:
    /media/NVFLIX/PLEX

  • Mount path unchanged from previous working version.

Steps Taken:

  • Restarted Plex container

  • Restarted Docker service

  • Rebooted system
    → Issue persists

Observations:

  • Error suggests a mount or filesystem access issue

  • Path exists, but Docker reports an I/O error during container init

  • Other containers may still access storage normally (if applicable)

Expected Behaviour:
Plex container should start normally with existing media mounts after OS update.

Actual Behaviour:
Container fails to start due to mount failure.

Request:
Guidance on whether:

Screenshot 2026-01-31 at 8.07.15 am
Screenshot 2026-01-31 at 8.07.15 am1399×735 108 KB

2

Infact Zima OS is not automounting the external Drive - Oops! Something went wrong…

readdirent /media/NVFLIX: input/output error

/NVFLIX/303 GB Available/1.02 TB

3

This isn’t a Plex or Docker issue.

After the 1.5.4-beta1 update, the external drive is not auto-mounting.
/media/NVFLIX is returning input/output errors, so Docker correctly refuses to start the container when the bind mount is unreadable.

Key points:

  • Host mount is broken > container cannot start
  • Path did not change, permissions are not the issue
  • Likely a beta automount regression or the filesystem not mounting cleanly after the update

To confirm the root cause on the ZimaOS host, please run the following commands and share the output:

lsblk -f
mount | grep NVFLIX
dmesg -T | tail -100

Once the disk is mounted cleanly and readable at the OS level, Plex should start immediately with no container or path changes needed.