These are brand new hard drives. Used for one month. I highly doubt it's the drive. The smart ctl stats come back fine for the drives too. No signs of failure.
I did extensive (4 days) of deep 1's and 0's writing to my WD 4 TB purple before installing it in the 5216. Zero problems with the drive. My reboots mostly happen on an IVS trigger, almost immediatedly after the event. I'm getting really PO'd at how unreliable this NVR can be. Usually don't get more than 1 or 2 reboots a day. Yesterday I had no reboots at all. This after I installed SD cards in all my cams. Hoping Dahua puts some time into figuring out what the problem is. Pretty lame they can't tell you what the 0x06f error is.
I had it with both h264 and h265. FWIW, there's a bunch of us in this thread having the exact same problem.
I switched to h265 a few days ago and that doesn't seem to have any effect. I did notice when disabling Intrusion and going to all trip wire IVS events, the reboots seemed to disappear. It looks like this is all Intrusion zone related. That sucks, because tripwire doesn't always seem to catch everything when it trips. Haven't had any reboots for 3 days now.
what if you do multiple trip wires or something lol.
On one cam I have 5 trip wires. Each one about 1.5 feet apart. Even then, it seems you don't get an image until about the last 1 or 2 trips. Go figure. Not at all impressed with this. We need a fix for the reboot issue.
does it work much better with intrusion? this is another thing I like about blue iris, especially since i have to leave a good amount of space around my intrusion zones, I have it pre buffer like 5 seconds of video so I get plenty of the action that happened before the zone was tripped and also I get more snapshots.
are you running the newest firmware? perhaps that bug has been fixed. or will be in the next version.
I am running the latest firmware. Dated 07212016. It seems Dahua is notorious for not keeping up with the bugs in NVR's. Thinking of switching to BI, or at least using it as a backup.
Intrusion works much better at catching the action. But the reboots being the problem on an intrusion detection, makes it useless. You don't have any idea when it will happen. Very unreliable POS.
That's good info on the disk space issue. But wouldn't it be nice if they had a menu option to allow you how many days back you want to retain? Then, another option to purge by day, any day when there was no intrusions or trips. Even a linux utility for disk management. I think it's time to start playing with BI.
Any thoughts on SD cards for the camera, and letting the NVR backfill missing video from reboots? Not that you should have to do that, or setup a BI system.
Those would be great features. The one I miss from Synology Surveillance Station was being able to mark a particular video so that it won't be deleted. So you can keep a history of interesting stuff on the NVR itself, vs having to download it to a computer.
It seems ANR (1800 Seconds:default) only works when network connectivity drops and comes back. I installed 32GB microSD cards in all cams and checked over a period of a week. I was under the impression a reboot would be considered a network drop, but it seems it is not. Looking at the daily time lines for each cam, on a reboot, the black area stayed black. I thought maybe the NVR would automatically pull the missing video from each cam but I can find no evidence that this works as intended. Very disappointed in how dysfunctional (and poorly documented) this NVR is.Any thoughts on SD cards for the camera, and letting the NVR backfill missing video from reboots? Not that you should have to do that, or setup a BI system.