I am in the same squeeze - installed all fine - worked well.
Then used DietPi-Drive_Manager to link to my Synology-NAS.
Speed test went ok.
Placed simple txt-file into mount and it showed on the NAS.
Changed the storage folder to /mnt/nfs_client.
Nothing is showing up on the NAS.
"usermod -aG dietpi motioneye" failed, because user motioneye is unknown.
no_root_squash on Synology is set. Checked the owner of /mnt/nfs_client being root:root. Tried to change it to motion:root - like it is set for the default storage at /mnt/dietpi_userdata/motioneye. This did not work and returned "invalid argument.
Reason: I did setup the mount with DiePi-Drive_Manager, which fixed it to the user root:root. And does not allow any changes.
There might be an issue with the Drive_Manager.
Have made a new clean install on an SD, just root, no other user. Same result: motioneye or motion can’t write to the mnt-folder. And it is also not possible to change the owner to motion. BTW there is no user motioneye.
Going into Synology, there are within the shared folder “KameraSued” no sub-folders. Only my two test-files, which both have the owner “root”.
When you setup the mount-point, did you use the dietpi-drive_manager or did you go manually?
I had the same issue with motion trying to access a synology share (samba in my case).
For me the solution described here did the trick, except that the umount-mount sequence did not work. I had to reboot instead.
And of course I used “uid=motion,gid=root,file_mode=0770,dir_mode=0770” in the fstab entry. Changed it with notepad++, not sed, but that shouldn’t matter.
OK, I had naively supposed that it would work the same way under nfs.
I now tried the nfs-way and it worked after chown’ing the synology target directory to myusername:users and setting squash to ‘Alle Benutzer zu Admin zuordnen’
The owner:group of the mnt directory was 1027:users, probably because I had not used drive_manager but manually edited fstab by adding this line: 192.168.188.42:/volume1/web/web_images /mnt/nfs_client nfs nofail,noauto,x-systemd.automount
Hi, for what it is good? Feel that I owe you some feedback.
The reason, why motioneye did not store any files, stems from the default settings under MOVIES in motioneye. The default is “H264/OMX (.mp4) " and these codecs are missing in the system. Just changing this setting to H264(.mp4)” does the trick because the related codecs are installed.
Maybe you want to forward this detail so that the dev-guys either change the default or load the codecs.
Yes this is a known issue with motionEye, not only as it is supported on Raspberry Pi only, but also since it requries either the RPi’s legacy graphics stack or fake KMS enabled. With the new default (on RPi OS) full KMS stack, OMX does not work either.
However, this is a topic for the motionEye repo, and I agree the default should be just changed to “H264(.mp4)”.