motioneye-project/motioneye

custom Path not working - save to the path

Open

#2,173 opened on Aug 14, 2021

View on GitHub
 (5 comments) (0 reactions) (0 assignees)Python (3,533 stars) (636 forks)batch import
dockerhelp wantedtroubleshooting

Description

Hi to all, i have one small problem and i want your help, My problem is that my setup cant save the media files are created (movies or pictures) to my external ssd usb HDD

My setup : Raspberry pi 4 2GigaRam Raspberry pi Os lite - Kernel version: 5.10 Docker : 20.10.8 Portainer : 1.24.2 MotionEye Version : 0.42.1 Motion Version : 4.2.2 OS Version : Debian 9.12 log2ram : installed (to extend Sd card life , swap disabled ) External usb SSD HDD : Intenso 256 Giga Fat32

i installed the usbmount to auto mount my external usb drive/Hdd My mounting point is : /mnt/usb1

My setup to the camera is : File Storage, Custom Path : /mnt/usb1/motioneye/Camera1 (default path was : /var/lib/motioneye/Camera1)

in : /etc/motioneye/motioneye.conf i changed also the path (it was the last thing i did when i saw that everything else didnt work)

# default output path for media files (must be writable by motionEye)
#media_path /var/lib/motioneye
media_path /mnt/usb1/motioneye

with : lsblk -fp the result is :

NAME FSTYPE LABEL UUID                                 FSAVAIL FSUSE% MOUNTPOINT
/dev/sda
|                                                                     
`-/dev/sda2
     vfat   SSD   0B44-D05F                             238.4G     0% /mnt/usb1
/dev/mmcblk0
|

with : sudo blkid the result is : /dev/sda2: LABEL_FATBOOT="SSD" LABEL="SSD" UUID="0B44-D05F" TYPE="vfat" PTTYPE="atari" PARTUUID="17d64133-02"

From terminal i can see my mounting point and can explore / create folders with all my users (root,pi,myuser) cd /mnt/usb1

But i cant find a folder named "motioneye" . is like the motioneye cant write to the SSD or cant see it ?

Contributor guide

Tech stack
pythondockershell
Domain
backendinfrastructure
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Linux file permissionsDocker volume mountsMotionEye configuration
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
First, verify that the Docker container running MotionEye has the correct volume mount for /mnt/usb1. Check if the container's motion user has write permissions to that directory. Inspect motionEye logs for permission denied errors. Also confirm that usbmount mounts the drive with the correct options for the container to access. If the issue persists, consider using a named volume or bind mount with proper permissions instead of relying on usbmount.