Help Using Dedicated Hard Drive

Forum for questions and support relating to the 1.25.x releases only.
Locked
volantis
Posts: 14
Joined: Tue Dec 11, 2012 2:19 pm

Help Using Dedicated Hard Drive

Post by volantis »

I have a fully operating Zoneminder system, at least until I followed the directions here to setup a dedicated hard drive for recording events and images.

Now I am not recording anything. The log file shows:
2013-05-17 zmfix 2327 ERR Can't stat /dev/video7: No such file or directory zmfix.cpp 86
2013-05-17 zmfix 2327 ERR Can't stat /dev/video5: No such file or directory zmfix.cpp 86
2013-05-17 zmfix 2327 ERR Can't stat /dev/video6: No such file or directory zmfix.cpp 86
2013-05-17 zmfix 2327 ERR Can't stat /dev/video4: No such file or directory zmfix.cpp 86
2013-05-17 zmfix 2327 ERR Can't stat /dev/video3: No such file or directory zmfix.cpp 86
2013-05-17 zmfix 2327 ERR Can't stat /dev/video2: No such file or directory zmfix.cpp 86
2013-05-17 zmfix 2327 ERR Can't stat /dev/video1: No such file or directory zmfix.cpp 86

I noticed there is no error entry for video0, however, video0 also does not record.

The /etc/fstab file has been modified to include:
/dev/sdc1 /recorded_video ext4 defaults 0 2
/recorded_video/images /usr/share/zoneminder/images none defaults,bind 0 2
/recorded_video/events /usr/share/zoneminder/events none defaults,bind 0 2

The name of the drive is recorded_video, the "images" and "events" directories are created, and the file system if ext4.

The /lib/udev/rules.d/50-udev-default.rules file was modified to include:
KERNEL==”video*″, SYMLINK+=”video”, MODE=”0666″

When running # ls -l /dev/video*
the output is:
crw-rw-rw-+ 1 root video 81, 0 May 17 22:30 /dev/video0
crw-rw-rw-+ 1 root video 81, 2 May 17 22:29 /dev/video1
crw-rw-rw-+ 1 root video 81, 4 May 17 22:30 /dev/video2
crw-rw-rw-+ 1 root video 81, 6 May 17 22:34 /dev/video3
crw-rw-rw-+ 1 root video 81, 8 May 17 22:31 /dev/video4
crw-rw-rw-+ 1 root video 81, 10 May 17 22:32 /dev/video5
crw-rw-rw-+ 1 root video 81, 12 May 17 22:33 /dev/video6
crw-rw-rw-+ 1 root video 81, 14 May 17 22:33 /dev/video7

With the above modifications to a working system, my "record" cameras are all red on the Zoneminder screen.

If someone can see what I am doing wrong, please correct me.
Flasheart
Posts: 342
Joined: Thu Jul 06, 2006 2:27 pm

Re: Help Using Dedicated Hard Drive

Post by Flasheart »

Not sure what's happened there - do /dev/video* files actually exist with the same permissions they did before? I can only assume the udevd rules are somehow breaking things.

If you've followed my guide here http://www.zoneminder.com/wiki/index.ph ... Hard_Drive - that describes mounting the events/ dir onto a dedicated drive. Zoneminder itself, and its sources, never move - and if writing would go wrong, then syslog or zm.log would show that.
volantis
Posts: 14
Joined: Tue Dec 11, 2012 2:19 pm

Re: Help Using Dedicated Hard Drive

Post by volantis »

Thanks for your attention to my issue.

I meant to link to your page as the inspiration for my actions. Yes, I followed your directions, or at least I think I did. Obviously, I have missed something.

It was after following those directions that I had the errors and tried to change the permissions of the new folders. I also tried changing line 132 in /usr/share/perl5/ZoneMinder/Memory.pm to "our $arch = 32".

This morning, I undid the changes to Memory.pm and undid the change to the default rules such that it would be as though I had followed the directions on your page only. Now the sources are in yellow instead of red. I can see the videos, but they are not recording to the new drive. It is as though they are in "monitor" state even though "recorded" is selected. I'm getting a huge log file, though. The error, "Shared data size conflict in shared_data for monitor Stairs, expected 328, got 316" for each of the cameras" appears for each camera and then interspersed are INF messages saying the cameras are recording. The drives show no activity.

BTW, Dolphin shows the events and images directories to have the full space of the drives. They appear to be linked in dolphin.
Locked