ZoneMinder Forums

I have 1.37.65 running on Ubuntu 24.04. Looking at the Storage drop down, I noted that default is 97% full. I have two external hard drives servicing my set up and have all of my cameras reporting to one or the other. Why would some events suddenly be directed to default and how can I get them moved to the proper location?

Me too. Looks like it started yesterday at 17:57 until 19:22. I have exactly the same as you - two drives configured and all cameras recording to one or other. Both cameras on one drive seemed to end up on default. Is it coincidence or is there some wierd date bug given that it's happened to us on the same day?

I've had to add a Purge when Full filter on default to even be able to see events (anything to do with logs was causing an error).

Should have included that mine is v1.36.35 running on Rocky 9.5.

To update my situation it looks like the harddisk failed at 17:47 - just found it is mounted readonly and there are lots of IO errors.
Does ZM switch to the default disk if it can't write to the specified disk?

Yes it tries all disks.

viewtopic.php?p=135280

This is good as it doesn't lose any video footage, but the default storage area is also the MySQL and root drive, so it is best to delete the default storage area. What you want is to have an extra hdd available similar to RAID, which can be used as a hot spare. You don't want to fill up the root hdd as then ZM won't work at all.

You have to have logging on the system, so you know if a hdd fails. Simple bash scripts can be enough.
https://wiki.zoneminder.com/SMS_Notific ... Monitoring

iconnor wrote: ↑Mon Dec 09, 2024 7:32 pm Yes it tries all disks.

Does it first go to the first disk in the storage listing?

If that's the case, then in order to setup a hot spare, you could delete the default storage, then setup an unused HDD as the first added storage area, followed by the storage areas you intend to use. So if any one of the hdds fail, it will go to the first HDD, which is the spare.

I found the issue. The Hard Drive became dislodged from it's mounting and was hanging by it's cable. Found the I/O errors in the log and investigated. The whole system is mounted in an inaccessible area, so the errant drive was not visually detected. I may try to reassign the default as I saw suggested, if that should work. The default area just does not have enough storage on my system.

kc8akw wrote: ↑Mon Dec 16, 2024 10:33 pm The Hard Drive became dislodged from it's mounting and was hanging by it's cable. Found the I/O errors in the log

Wow. There really isn't a category of SMART error to cover that one, is there?

Very lucky to have caught this before it fell off the cable or caused collateral hardware damage by dropping into something else.