Using a dedicated Hard Drive - Revision history

Burger: /* Tips/Troubleshooting */

2025-01-22T22:12:36Z

Tips/Troubleshooting

← Older revision		Revision as of 18:12, 22 January 2025
Line 134:		Line 134:
	===Permission Denied===		===Permission Denied===
	If you have multiple folder levels make sure permissions from the first all the way to the end storage folder allow www-data.		If you have multiple folder levels make sure permissions from the first all the way to the end storage folder allow www-data.

			===Eliminating Reserved Space for the HDD===
			If you aren't entirely worried about losing the filesystem, you can eliminate the reserved space. Though it is debatable whether this is a wise decision or not.
			tune2fs -m 0 /dev/<hddhere>
			* https://forums.zoneminder.com/viewtopic.php?p=136620
			* https://unix.stackexchange.com/questions/7950/reserved-space-for-root-on-a-filesystem-why

Burger: /* Deleting the Default Storage Area */

2024-12-11T06:37:11Z

Deleting the Default Storage Area

← Older revision		Revision as of 02:37, 11 December 2024
Line 50:		Line 50:

	===Deleting the Default Storage Area===		===Deleting the Default Storage Area===
	Let's say you have added a new HDD (or multiple) and you don't intend to use the default storage area of /var/cache/zoneminder/events. Unfortunately, if you get a HDD failure, it will default to the 'default' storage, which means it may fill up your root hdd, which eventually leads to MySQL being unable to run, and breaks Zoneminder. To avoid this, you may want to delete the default /var/cache/zoneminder/events directory from the storage page. Note that if you already have events there, it won't allow you to check the checkbox (it will be greyed out, and hovering over it will tell you that any storage with events can't be deleted). To resolve this, you can manually go to /var/cache/zoneminder/events, delete all files there, then run zmaudit.pl --storage_id 1 which will search through the database, and erase any events that are not on the filesystem. After this you will be able to remove the default storage area through the web gui.		Let's say you have added a new HDD (or multiple) and you don't intend to use the default storage area of /var/cache/zoneminder/events. Unfortunately, if you get a HDD failure, it will default to the 'default' storage, which means it may fill up your root hdd, which eventually leads to MySQL being unable to run, and breaks Zoneminder. To avoid this, you may want to delete the default /var/cache/zoneminder/events directory from the storage page.

			Note that if you already have events there, it won't allow you to check the checkbox (it will be greyed out, and hovering over it will tell you that any storage with events can't be deleted). To resolve this, you can manually go to /var/cache/zoneminder/events, delete all files there, then run zmaudit.pl --storage_id 1 which will search through the database, and erase any events that are not on the filesystem. After this you will be able to remove the default storage area through the web gui.

	==ZoneMinder 1.30.4 or Older==		==ZoneMinder 1.30.4 or Older==

Burger: /* Deleting the Default Storage Area */

2024-09-05T06:15:25Z

Deleting the Default Storage Area

← Older revision		Revision as of 02:15, 5 September 2024
Line 50:		Line 50:

	===Deleting the Default Storage Area===		===Deleting the Default Storage Area===
	Let's say you have added a new HDD (or multiple) and you don't intend to use the default storage area of /var/cache/zoneminder/events. Unfortunately, if you get a HDD failure, it will default to the 'default' storage, which means it may fill up your root hdd, which eventually leads to MySQL being unable to run, and breaks Zoneminder. To avoid this, you may want to delete the default /var/cache/zoneminder/events directory from the storage page. Note that if you already have events there, it won't allow you to check the checkbox (it will be greyed out, and hovering over it will tell you that any storage with events can't be deleted). To resolve this, you can manually go to /var/cache/zoneminder/events, delete all files there, then run zmaudit.pl --storage_id 1 which will search through the database, and erase any events that are not on the filesystem. After this you will be able to remove the default storage area.		Let's say you have added a new HDD (or multiple) and you don't intend to use the default storage area of /var/cache/zoneminder/events. Unfortunately, if you get a HDD failure, it will default to the 'default' storage, which means it may fill up your root hdd, which eventually leads to MySQL being unable to run, and breaks Zoneminder. To avoid this, you may want to delete the default /var/cache/zoneminder/events directory from the storage page. Note that if you already have events there, it won't allow you to check the checkbox (it will be greyed out, and hovering over it will tell you that any storage with events can't be deleted). To resolve this, you can manually go to /var/cache/zoneminder/events, delete all files there, then run zmaudit.pl --storage_id 1 which will search through the database, and erase any events that are not on the filesystem. After this you will be able to remove the default storage area through the web gui.

	==ZoneMinder 1.30.4 or Older==		==ZoneMinder 1.30.4 or Older==

Burger: /* Web Console Instructions */

2024-09-05T06:14:18Z

Web Console Instructions

← Older revision		Revision as of 02:14, 5 September 2024
Line 48:		Line 48:

	zmfilter has a log file in /var/log/zm/zmfilter.log if you've enabled these log files, and it can be tailed to view the filter in action.		zmfilter has a log file in /var/log/zm/zmfilter.log if you've enabled these log files, and it can be tailed to view the filter in action.

			===Deleting the Default Storage Area===
			Let's say you have added a new HDD (or multiple) and you don't intend to use the default storage area of /var/cache/zoneminder/events. Unfortunately, if you get a HDD failure, it will default to the 'default' storage, which means it may fill up your root hdd, which eventually leads to MySQL being unable to run, and breaks Zoneminder. To avoid this, you may want to delete the default /var/cache/zoneminder/events directory from the storage page. Note that if you already have events there, it won't allow you to check the checkbox (it will be greyed out, and hovering over it will tell you that any storage with events can't be deleted). To resolve this, you can manually go to /var/cache/zoneminder/events, delete all files there, then run zmaudit.pl --storage_id 1 which will search through the database, and erase any events that are not on the filesystem. After this you will be able to remove the default storage area.

	==ZoneMinder 1.30.4 or Older==		==ZoneMinder 1.30.4 or Older==

Burger: /* Web Console Instructions */

2024-07-29T12:03:08Z

Web Console Instructions

← Older revision		Revision as of 08:03, 29 July 2024
Line 45:		Line 45:
	[[File:Filter.png \| 600px]]		[[File:Filter.png \| 600px]]

	9. Choose the PurgeWhenFull filter. Add '''storage area''' and the default will be equal to, which will work. Choose your new storage area from the drop down. You can test the filter now, by clicking on '''List Matches'''. Click save, to make the changes permanent. <small>Note that this filter is not necessary for default storage ~~areas~~ of /var/cache/zoneminder, and will ~~infact~~ break the default storage area. So only ~~use~~ with external storage. Always test via 'list matches' to confirm your filter works as expected.</small>		9. Choose the PurgeWhenFull filter. Add '''storage area''' and the default will be equal to, which will work. Choose your new storage area from the drop down. You can test the filter now, by clicking on '''List Matches'''. Click save, to make the changes permanent. <small>Note that this filter is not necessary for the default storage area of /var/cache/zoneminder, and will in fact break the default storage area. So use only with external storage. Always test via 'list matches' to confirm your filter works as expected.</small>

	zmfilter has a log file in /var/log/zm/zmfilter.log if you've enabled these log files, and it can be tailed to view the filter in action.		zmfilter has a log file in /var/log/zm/zmfilter.log if you've enabled these log files, and it can be tailed to view the filter in action.

Burger: /* ZoneMinder 1.31 or Newer */

2023-01-13T17:06:09Z

ZoneMinder 1.31 or Newer

← Older revision		Revision as of 13:06, 13 January 2023
Line 4:		Line 4:
	Please follow the steps shown on our readthedocs site:		Please follow the steps shown on our readthedocs site:
	http://zoneminder.readthedocs.io/en/latest/installationguide/dedicateddrive.html		http://zoneminder.readthedocs.io/en/latest/installationguide/dedicateddrive.html

			There are also video instructions here:
			https://youtu.be/ElXdmx9FsKQ

	===Web Console Instructions===		===Web Console Instructions===

Snake: /* Tips/Troubleshooting */

2021-03-22T03:59:36Z

Tips/Troubleshooting

← Older revision		Revision as of 23:59, 21 March 2021
Line 123:		Line 123:
	===Creating Disk Images for Storage Areas===		===Creating Disk Images for Storage Areas===
	See: https://forums.zoneminder.com/viewtopic.php?f=42&t=29297		See: https://forums.zoneminder.com/viewtopic.php?f=42&t=29297

			===Permission Denied===
			If you have multiple folder levels make sure permissions from the first all the way to the end storage folder allow www-data.

Snake: /* Web Console Instructions */

2021-03-18T00:01:25Z

Web Console Instructions

← Older revision		Revision as of 20:01, 17 March 2021
Line 22:		Line 22:
	[[File:Add_new_storage.png \| 600px]]		[[File:Add_new_storage.png \| 600px]]

	4. Configure paths appropriately. Here I have an external ext4 ~~SSD~~ which is mounted at /video/. You may mount anywhere. It doesn't have to be /video/. Also, this was used for an outdoor ZM install which required an SSD. Typically you will want an HDD, not an SSD. For those curious, the scheme refers to how the files are named as they are saved in the directory. In old versions of ZM, there were a number of sub directories, (e.g. month 11 would be directory 11, day 30 would be directory 30 in folder 11, for 11/30, and so on, for year, day, hour, etc..). This option is kept for backwards compatibility, but also a newer simpler scheme is available called Medium. The default is medium and that will suffice for most.		4. Configure paths appropriately. Here I have an external ext4 drive which is mounted at /video/. You may mount anywhere. It doesn't have to be /video/. Also, this was used for an outdoor ZM install which required an SSD. Typically you will want an HDD, not an SSD. For those curious, the scheme refers to how the files are named as they are saved in the directory. In old versions of ZM, there were a number of sub directories, (e.g. month 11 would be directory 11, day 30 would be directory 30 in folder 11, for 11/30, and so on, for year, day, hour, etc..). This option is kept for backwards compatibility, but also a newer simpler scheme is available called Medium. The default is medium and that will suffice for most.

	[[File:Console2.png \| 600px]]		[[File:Console2.png \| 600px]]

Snake: /* Web Console Instructions */

2021-03-17T23:59:54Z

Web Console Instructions

← Older revision		Revision as of 19:59, 17 March 2021
Line 22:		Line 22:
	[[File:Add_new_storage.png \| 600px]]		[[File:Add_new_storage.png \| 600px]]

	4. Configure paths appropriately. Here I have an external ext4 ~~filesystem~~ SSD which is mounted at /video/. For those curious, the scheme refers to how the files are named as they are saved in the directory. In old versions of ZM, there were a number of sub directories, (e.g. month 11 would be directory 11, day 30 would be directory 30 in folder 11, for 11/30, and so on, for year, day, hour, etc..). This option is kept for backwards compatibility, but also a newer simpler scheme is available. The default is medium and that will suffice for most.		4. Configure paths appropriately. Here I have an external ext4 SSD which is mounted at /video/. You may mount anywhere. It doesn't have to be /video/. Also, this was used for an outdoor ZM install which required an SSD. Typically you will want an HDD, not an SSD. For those curious, the scheme refers to how the files are named as they are saved in the directory. In old versions of ZM, there were a number of sub directories, (e.g. month 11 would be directory 11, day 30 would be directory 30 in folder 11, for 11/30, and so on, for year, day, hour, etc..). This option is kept for backwards compatibility, but also a newer simpler scheme is available called Medium. The default is medium and that will suffice for most.

	[[File:Console2.png \| 600px]]		[[File:Console2.png \| 600px]]

	5. ~~After that is added~~ and ~~saved,~~ return to the console. Click source tab to configure ~~where the~~ camera ~~stores video~~. Here we have the option of configuring where each camera can store its videos. This means you can have multiple HDDs, with multiple cameras, and split the storage across as many or as few HDDs as you wish. Camera 1 can record to HDD1, and Camera 2 can record to HDD2. Or you can have both Camera 1 and 2 on HDD1.		5. Save and return to the console. Click the source tab to configure storage on each camera. Here we have the option of configuring where each camera can store its videos. This means you can have multiple HDDs, with multiple cameras, and split the storage across as many or as few HDDs as you wish. Camera 1 can record to HDD1, and Camera 2 can record to HDD2. Or you can have both Camera 1 and 2 on HDD1.

	[[File:Source.png \| 600px]]		[[File:Source.png \| 600px]]

Snake at 18:34, 23 February 2021

2021-02-23T18:34:14Z

← Older revision		Revision as of 14:34, 23 February 2021
Line 1:		Line 1:
	With ZM, you may want to use a 2nd HDD dedicated for videos only, with no OS or db files on it.		With ZM, you may want to use a 2nd HDD dedicated for videos only, with no OS or db files on it. Or (in 1.32 and newer) you may want to add multiple HDDs, and spread out the cameras so that certain streams record to certain HDDs.

	==ZoneMinder 1.31 or Newer==		==ZoneMinder 1.31 or Newer==