Motioneye accessing network share failed cannot mount network share

blindeyeseesall

unread,

May 13, 2018, 11:20:50 AM5/13/18

to motioneye

I noticed that when I have motionEyeOS installed, under File Storage->Storage Device I can select a network location.  When I have motionEyes installed from Raspian and the pre-built deb package, I don't have that option.  Is there any way to add this feature manually?

Bruce Brannock

unread,

May 13, 2018, 3:26:04 PM5/13/18

to motioneye

Perhaps they're assuming that you would set up your network share Within raspbian itself and then do custom path however that is a bummer sorry to hear that. That is my motionEyeOS which is running on a pi 3 I got curious and wanted to see.

Motioneye accessing network share failed cannot mount network share

Bruce Brannock

unread,

May 14, 2018, 3:31:09 PM5/14/18

to motioneye

So you got me wondering I installed Raspbian Lite and then installed motionEye the same way you did with the pre-built Debian package for the pi  I'm going to see if I can do it. I have openmediavault on another Raspberry Pi that I have network sharing setup SMB/CIFS but that is interesting I was assuming which assuming is wrong that all the features would be the same in the motionEye interface. However I am cheating I also installed Webmin to make the process easier.

Motioneye accessing network share failed cannot mount network share

On Sunday, May 13, 2018 at 11:20:50 AM UTC-7, blindeyeseesall wrote:

Calin Crisan

unread,

May 15, 2018, 1:44:24 PM5/15/18

to motioneye

Make sure that you run as root and that you have smb_shares option set to true in your motioneye.conf.

Bruce Brannock

unread,

May 15, 2018, 5:40:10 PM5/15/18

to motioneye

Bruce Brannock

unread,

May 15, 2018, 5:43:37 PM5/15/18

to motioneye

I just realized who you are you're the founder of the feast lol

On Tuesday, May 15, 2018 at 1:44:24 PM UTC-7, Calin Crisan wrote:

Calin Crisan

unread,

May 16, 2018, 1:31:47 PM5/16/18

to motioneye

I am indeed. I follow discussions on this forum and try to come up with short and helpful answers, when I can.

Bruce Brannock

unread,

May 16, 2018, 5:30:47 PM5/16/18

to motioneye

It's pretty cool knowing that the Creator is here giving help. Which is much appreciated. 

Blog

Question Trouble Connecting MotionEye OS (Raspberry Pi 3) to Network Share on FreeNAS 11.2

  • Thread starter motorboatinking
  • Start date Mar 8, 2019

Dec 22, 2014 79 0 4,660 5

  • #1

I installed MotionEye OS 4.1.1 on my Raspberry Pi 3. I have FreeNAS 11.2 that I would like to save motion events to.

Initially I was thinking of just mounting an nfs share to /home/nfs and specifying the storage device as a custom path to /home/nfs.
I was getting a read-only error, so I used mount -o remount,rw / to create nfs/

When I run mount -t nfs <serverIP>:/mnt/MotionEye /home/nfs/ OR mount <serverIP>:/mnt/MotionEye /home/nfs/ the command just hangs.
I can mount perfectly fine from Linux Mint, and currently any device on the lan has access to that share.

If I delete the nfs share and try and mount, I get a "failed: Permission denied" error, and in FreeNAS I see a "mount request denied..." error. But with the share created, motion eye hangs and FreeNAS says nothing.

So I thought I would use an SMB share. I created the share in FreeNAS with the name MotionEye.
There was no password field when creating the share, so I'm assuming the username and password fields in the MotionEye gui are for the owner of the dataset? I also tried using root as username.

I get an error in motioneye.log ERROR: failed to mount smb share "//<ServerIP>/MotionEye" at "/data/media/motioneye_<ServerIP> _motioneye_motioneye"
I can't see the SMB share from my Windows 10 VM. I've only used NFS from FreeNAS, but everything looks like SMB should work when I look at both the share settings and the smb service settings.

I've looked at about all the settings I'm familiar with. Is there anything obvious that I'm missing?

Edit* It's working now. Not sure why, everything looks the same as when I was having trouble.

Jan 13, 2011 14,023 434 76,290 3,207

  • #2

  1. Leave Motion Eye or whatever other application you're using aside.
  2. Create a SMB share on your NAS. Make sure you can access that share (read, write etc) from your Windows PC.
  3. Use same user name / password on your RPi to access the share. Make that share mounted during startup. Make sure you can access your NAS from command .
  4. Configure your app to use the mount point as an ordinary path. MotionEye does not have to know where exactly your data is stored, all it needs to know is a file/folder path.

Dec 22, 2014 79 0 4,660 5

  • #3

  1. Leave Motion Eye or whatever other application you're using aside.
  2. Create a SMB share on your NAS. Make sure you can access that share (read, write etc) from your Windows PC.
  3. Use same user name / password on your RPi to access the share. Make that share mounted during startup. Make sure you can access your NAS from command .
  4. Configure your app to use the mount point as an ordinary path. MotionEye does not have to know where exactly your data is stored, all it needs to know is a file/folder path.

I got it working, and what you said is basically what I did.

I figured it would be easiest to get SMB working with Windows, like you said. Once I saw the server from File Explorer, I went back to MotionEye and it worked right away.

  • Advertising
  • Cookies Policies
  • Privacy
  • Term & Conditions
  • Topics