ZoneMinder Forums

I've attached my NAS to Ubuntu 14.04 via fstab.

I've put the below in my fstab file.
I can browse to the NAS in Ubuntu fine, my next step is to re-direct Zoneminder events.

I followed this guide http://www.zoneminder.com/wiki/index.ph ... Hard_Drive

It stated I needed to update my fstab file with the below
However this doesn't work, no events are been placed here, no files are generated, when using the ZM GUI I can see the events but nothing will play back (I suspect this is because no files have been generated)

What am I doing wrong?

OK I managed to get this working.

I figured that connecting via CIFS wasn't the solution and was better using NFS since its more native to Linux. So I connected to my NAS and enabled NFS.

I next had to install NFS support on my Ubuntu 14.04 install.
Next I had to create a directory on the file system to mount my NAS too.
Great! I now need to set my Ubuntu install to map the NAS to the directory every time it boots up, to do this I needed to edit the FSTAB file.
Add the command in to map my NAS to the directory.
Now we have to redirect the ZM events and images folder, so still in the fstab file I added the following.
Saved everything and rebooted. It still didn't work, however this was down to permissions. I had to do the following, this will allow ZM to write to the directorys on my NAS.
Please note: I had to enable root access on my NAS to enable the following commands to work.
Rebooted everything and it all worked spot on.

The document you referenced is intended for a dedicated hard drive, not a network share, as the name of document implies.
Yes, you got it working, but there are some additional items worth noting that the document does not mention:

- Mounting network shares via fstab works as long as the network share is available. If you try to boot the zoneminder machine while the network share is not on the network, for any reason, you'll find that your machine will hang at boot....or take a really, really long time to boot. Instead, you may want to look into the tool called autofs. It is designed to work around this as it will mount your shares on-demand and won't hang up the box if the resource is unavailable.

- For those that only want to install the NFS client on their machine instead of the full blown NFS server, the package you need is called "nfs-common" rather than "nfs-kernel-server".

- With NFS, sometimes you have to create an account on the nfs server with the same name and uid as the account on the client. If not, you may see your files as owned by "nobody" even though you just did a chown www-data on the files. This affects newer versions of NFS such as the version that ships with Ubuntu.

knnniggett wrote:- Mounting network shares via fstab works as long as the network share is available.

On that thought, what happens when zmaudit discovers a database full of event entries, but the network share didn't mount/fell off?

Won't it start going through the database saying "this event no longer exists on disk, cleaning the database up" ??

mikb wrote:

knnniggett wrote:- Mounting network shares via fstab works as long as the network share is available.

On that thought, what happens when zmaudit discovers a database full of event entries, but the network share didn't mount/fell off?

Won't it start going through the database saying "this event no longer exists on disk, cleaning the database up" ??

Yes, that is the risk of using remote storage. By backing up the database on a regular basis, you have a chance to recover most of the events should this occur.