Dahua NVR Reboots during the day

[Shockwave199]

I kinda feel like these are the drawbacks of ip cameras and the nvr's that support them. This stuff seemed a lot less rare back in the analog days, when the cameras were dumb and the dvr ruled what was going on. Of course, it was analog, lol. Not much in terms of quality to miss there. I'm still analog and since testing my dahua megapixel setup its hard to look at D1 again, lol. But it is nice and problem free, that's for sure. Maybe cvi is less glitchy, I don't know. It seems to me they make ip cameras able to do it all and then when you want to use an nvr which insists IT'S in charge, everything gets into a pissing match for control. They need to make dumb ip cameras that just send a feed and let the nvr do all the work, much like analog. Then maybe things will get easier.

 

[hmjgriffon]

I kinda feel like these are the drawbacks of ip cameras and the nvr's that support them. This stuff seemed a lot less rare back in the analog days, when the cameras were dumb and the dvr ruled what was going on. Of course, it was analog, lol. Not much in terms of quality to miss there. I'm still analog and since testing my dahua megapixel setup its hard to look at D1 again, lol. But it is nice and problem free, that's for sure. Maybe cvi is less glitchy, I don't know. It seems to me they make ip cameras able to do it all and then when you want to use an nvr which insists IT'S in charge, everything gets into a pissing match for control. They need to make dumb ip cameras that just send a feed and let the nvr do all the work, much like analog. Then maybe things will get easier.

BI is pretty much like that.

 

[aristobrat]

@EMPIRETECANDY, any update from Dahua on the NVR rebooting issue?

Look at the black gaps on my NVR timeline below. I'm missing quite a few minutes of recordings because the NVR kept rebooting this day.

Thank you!

 

[HMS]

So, is this a particular model of Dahua DVR's or all of them? I'm getting ready to order cameras and a DVR but not if its going to not work? I am also going to do a BI setup as well to learn and experiment with but want the DVR for the NOW and dependable plug n play.

I'm seeing things are being narrowed down to possible causes linked to Intrusion det. motion detection recording. is there anyone using a Dahua DVR with "JUST" 24/7 constant recording with nothing Extra as far as trips or pushes and if so is it dependable?

At this point If it is dependable in a plain jane 24/7 constant record state, I'm thinking just going with a BIG DVR with a butt LOAD of drives to give me all the space i need and not worry about risking reboots at this point if it can be stable. Once i learn and feel more comfortable with BI ill transition over to that and start implementing all the extras, or hopefully they have a firmware fix but i cant wait for dependable, need that now even if it means throwing money at hard drives.

 

[mmdb]

i have nvr5216 16p only connected to monitor ,not even connected to router and only 24/7 constant recording ..so nothing extra and also lot of reboots ..but have blue wd 1t only

 

[Shockwave199]

Can you use motion detection only and not use smart detection and circumvent the problem? At least this would provide detection events on the playback time line so it's not a sea of recording with no clue of where an event might be. Not a fix but a hold over until a firmware fix maybe.

 

[mmdb]

i will look into it over weekend for now have 4 -5231 turret ..still need to install ptz49 and 1 turret ..would definitely try motion detection ..

 

[DavidDavid]

At this point If it is dependable in a plain jane 24/7 constant record state, I'm thinking just going with a BIG DVR with a butt LOAD of drives to give me all the space i need and not worry about risking reboots at this point if it can be stable. Once i learn and feel more comfortable with BI ill transition over to that and start implementing all the extras, or hopefully they have a firmware fix but i cant wait for dependable, need that now even if it means throwing money at hard drives.

I'd be willing to bet that 99.9% of the folks on this forum record 24/7 AND IVS events. So you recording only 24/7 is actually less than most are recording. By all means get a couple 10tb drives and record months at a time... But don't think you HAVE to.

There's calculators online that will help you estimate how many days you'll get per camera recording 24/7 that can help you estimate how much storage to buy so that you can feel comfortable with how many days you'll get of records.

 

[Solar Deity]

Here are my results with pertinent setup information. Currently have 4x -- NVR5216-16P-4KS2's that I am taking care of, with two to follow in the very near future.

1st has a WD 4TB Purple with one 5231 and one SD59225U-HNI. Up since 2/28/17. Not using any POE ports. Power bricks powering all cams. Currently recording 24/7 on both channels. Checked all the logs. No random reboots

2nd has (2x) WD 4 TB Purple's and 2 -- SD59225U-HNI's. Up since 4/1/17. Not using any POE ports. Layer 3 switch to Hi POE midspan. Currently recording 24/7 on both channels. Checked all the logs. No random reboots

3rd has a WD 4TB Purple with a single 4431. Up since 4/22/17. Not using any POE ports. Power brick powering the cam. Currently recording 24/7 on both channels. Checked all the logs. No random reboots

4th is a test rig because of this thread. It has no hard drive, no cams, just running connected to a monitor since Friday, 4/30/17. Checked all the logs. No random reboots.

Have a 5th and 6th to set up still. One with a 2TB WD Purple and 2 - 5231's, the 2nd with a 4TB WD purple and 2 - 5231's.

Am I correct in recalling that the above NVR's are the non POE versions, save for @mmdb ?

All above NVR's with cams are running H.265 HVEC compression. I'll aslo add that there are no IVS events set up in the above examples, just 24/7 recording.

I'll add cams to the test rig as soon as Andy delivers, and set up the other two by the weekend.. I've been waiting a while for some test cams. I'll keep everyone updated.

SD

 

[mmdb]

thx solars city .. mine is poe version nvr .recording h264 ...will install second nvr the same 16 p next week and will let you know ..big thx

 

[HMS]

Here are my results with pertinent setup information. Currently have 4x -- NVR5216-16P-4KS2's that I am taking care of, with two to follow in the very near future.

1st has a WD 4TB Purple with one 5231 and one SD59225U-HNI. Up since 2/28/17. Not using any POE ports. Power bricks powering all cams. Currently recording 24/7 on both channels. Checked all the logs. No random reboots

2nd has (2x) WD 4 TB Purple's and 2 -- SD59225U-HNI's. Up since 4/1/17. Not using any POE ports. Layer 3 switch to Hi POE midspan. Currently recording 24/7 on both channels. Checked all the logs. No random reboots

3rd has a WD 4TB Purple with a single 4431. Up since 4/22/17. Not using any POE ports. Power brick powering the cam. Currently recording 24/7 on both channels. Checked all the logs. No random reboots

4th is a test rig because of this thread. It has no hard drive, no cams, just running connected to a monitor since Friday, 4/30/17. Checked all the logs. No random reboots.

Have a 5th and 6th to set up still. One with a 2TB WD Purple and 2 - 5231's, the 2nd with a 4TB WD purple and 2 - 5231's.

Am I correct in recalling that the above NVR's are the non POE versions, save for @mmdb ?

All above NVR's with cams are running H.265 HVEC compression. I'll aslo add that there are no IVS events set up in the above examples, just 24/7 recording.

I'll add cams to the test rig as soon as Andy delivers, and set up the other two by the weekend.. I've been waiting a while for some test cams. I'll keep everyone updated.

SD

Just so i am sure, Your running DVR's with 16ports of POI avaible but are NOT using the POI from the dvr. Instead your using power bricks or a switch that is POI enabled and supplying the power for that camera from the switch?

I know sounds like a stupid question but im just trying to be certain i understand.

Thanks for all the info!

 

[Tygunn]

I'm still getting reboots. Usually a couple a day. Andy reassured me that Dahua "is looking into it". Despite tweaking the keyframe settings I'm also having the problem that around motion events I'm missing a couple seconds of video. So far the biggest "intrusions" I've seen are a possum that likes to slowly plog by the camera at night, or rats. In most of these cases the drop out in recording at the motion event is causing me to miss some footage.

The event flagging is particularly important to me since I want to be able to keep an eye on things that are happening during the day. The fact that there is no pre-recording and that events get marked just after the start of the event makes these almost useless as well.

I think at this point regardless of what resolution Dahua finds I'm going to look into using Blue Iris to do my primary recording. Perhaps I'll keep the NVR around to do 24/7 recording; dunno. Between reboots and the fact that it there are stutters in recording right around events, it makes the unit almost completely useless in a surveillance scenario.

Now to go investigate the requirements for a Blue Iris setup!

 

[Tygunn]

Here are my results with pertinent setup information. Currently have 4x -- NVR5216-16P-4KS2's that I am taking care of, with two to follow in the very near future.

1st has a WD 4TB Purple with one 5231 and one SD59225U-HNI. Up since 2/28/17. Not using any POE ports. Power bricks powering all cams. Currently recording 24/7 on both channels. Checked all the logs. No random reboots

2nd has (2x) WD 4 TB Purple's and 2 -- SD59225U-HNI's. Up since 4/1/17. Not using any POE ports. Layer 3 switch to Hi POE midspan. Currently recording 24/7 on both channels. Checked all the logs. No random reboots

3rd has a WD 4TB Purple with a single 4431. Up since 4/22/17. Not using any POE ports. Power brick powering the cam. Currently recording 24/7 on both channels. Checked all the logs. No random reboots

4th is a test rig because of this thread. It has no hard drive, no cams, just running connected to a monitor since Friday, 4/30/17. Checked all the logs. No random reboots.

Have a 5th and 6th to set up still. One with a 2TB WD Purple and 2 - 5231's, the 2nd with a 4TB WD purple and 2 - 5231's.

Am I correct in recalling that the above NVR's are the non POE versions, save for @mmdb ?

All above NVR's with cams are running H.265 HVEC compression. I'll aslo add that there are no IVS events set up in the above examples, just 24/7 recording.

I'll add cams to the test rig as soon as Andy delivers, and set up the other two by the weekend.. I've been waiting a while for some test cams. I'll keep everyone updated.

SD

So these are all POE NVRs. Mine is definitely a non-POE version. I suppose as a last resort I'll look at buying an oversized power supply and see if that helps.

 

[HMS]

I'd be willing to bet that 99.9% of the folks on this forum record 24/7 AND IVS events. So you recording only 24/7 is actually less than most are recording. By all means get a couple 10tb drives and record months at a time... But don't think you HAVE to.

There's calculators online that will help you estimate how many days you'll get per camera recording 24/7 that can help you estimate how much storage to buy so that you can feel comfortable with how many days you'll get of records.

yea, punched in the numbers and for 16 cameras running 24/7 with a 7day retention the magic number is 12Terabytes. And id be happy to use the IVS events but that is what appears to be a possible cause of these reboots.

But i have no idea how many of these DVRs are being utilized by people on this board. looks like there is possible 4-6 people having this issue, if there is another 50 people using them with no problems then the chance of it being firmware seems pritty pritty low to me just mathmaticaly, otherwise i feel the problem would be more widespread. But Im new to this so what the hell do i know . just trying to find the most dependable, no reboot, setup and then be happy to start adding the extras with no failures..

 

[Tygunn]

I measured the jack on my Dahua power supply; 5.5mm barrel with 2.1mm inside in. Its rated at 12v, 4 amps, tip positive, shield negative.

I might try one of these; same deal but 10 amps; if its a flaky power supply this will definitely rule it out.
SJP Adapter Power Supply 100-240V to DC 12V 10A Converter Adapter 120W High Power Switching Power Supply US Plug for LED Strip Light - - Amazon.com

 

[Tygunn]

yea, punched in the numbers and for 16 cameras running 24/7 with a 7day retention the magic number is 12Terabytes. And id be happy to use the IVS events but that is what appears to be a possible cause of these reboots.

But i have no idea how many of these DVRs are being utilized by people on this board. looks like there is possible 4-6 people having this issue, if there is another 50 people using them with no problems then the chance of it being firmware seems pritty pritty low to me just mathmaticaly, otherwise i feel the problem would be more widespread. But Im new to this so what the hell do i know . just trying to find the most dependable, no reboot, setup and then be happy to start adding the extras with no failures..

Yeah, it doesn't seem to be widespread at all. I pushed Andy to try and get an explanation of what code 0x06 means. I write software for a living; we tend to ensure all these obscure codes have a meaning. If we knew the meaning, then it would help narrow things down. However, I didn't get a straight answer.

I mean its entirely possible that there is a software bug that only manifests on some hardware too.

In any case I'll try a new power supply, but I'm also going to start looking at a Blue Iris setup. Given how flaky this thing is I have a feeling it won't be working the one time I do need it.

 

[HMS]

So these are all POE NVRs. Mine is definitely a non-POE version. I suppose as a last resort I'll look at buying an oversized power supply and see if that helps.

Are you thinking that your unit without POE with a smaller power supply maybe is lacking in wattage, therefor when the DVR gets a CPU intensive event such as recognizing, and starting a event with all the associated events/pushes/ect that are associated with it the machine is essentially browning out and giving you errors?

 

[aristobrat]

Mine seems to shutdown/reboot gracefully during these events, which wouldn't be my expectation of how a low-power situation plays out... but who knows.

Many back-to-back events is what seems to cause mine to reboot. My visiting mom loading up her car to leave Saturday AM caused a ton of back-to-back IVS events on my driveway cam. The NVR rebooted 3x during that hour.

The "record delay" for IVS on that camera is set to 10 seconds. I wonder if I bump that up to 60, if that'd reduce how quickly back-to-back events can occur, which may help reduce the reboots.

I don't want to go down the Blue Iris route. I hope Dahua can iron these issues out.

 

[Tygunn]

Are you thinking that your unit without POE with a smaller power supply maybe is lacking in wattage, therefor when the DVR gets a CPU intensive event such as recognizing, and starting a event with all the associated events/pushes/ect that are associated with it the machine is essentially browning out and giving you errors?

Yes, I'm thinking something like that. Or maybe its just not a stable power supply and its producing inconsistent power under load? Who knows.

Though 12v x 4amps = 48w, which should be MORE than enough. My NVR, 10 cameras, POE switch, WIFI router, smart hubs and cable modem are all hooked up to the same UPS, and it says idle draw is 60w. So I find it hard to imagine the power supply is the problem.

 

[DavidDavid]

Mine seems to shutdown/reboot gracefully during these events, which wouldn't be my expectation of how a low-power situation plays out... but who knows.

Many back-to-back events is what seems to cause mine to reboot. My visiting mom loading up her car to leave Saturday AM caused a ton of back-to-back IVS events on my driveway cam. The NVR rebooted 3x during that hour.

The "record delay" for IVS on that camera is set to 10 seconds. I wonder if I bump that up to 60, if that'd reduce how quickly back-to-back events can occur, which may help reduce the reboots.

I don't want to go down the Blue Iris route. I hope Dahua can iron these issues out.

I assumed mine was working fine because every time I walked thru where I know we I had IVS lines, my phone would ding. I got pretty good at ignoring them, but was always aware of them. It was so consistent that for a week or two that I assumed everything was fine. Then I came home one day to a package on the doorstep, and I wasn't notified. Then I checked my logs and realized I was in the group of rebooting NVR's. Now I'm noticing that frequently something will happen that I didn't get alerted on my phone.

I agree about not wanting to go down BI route. I chose this nvr for a few reasons that were important to me. Really sad for these issues. Gonna be a lot of money if we have to send these all back to Andy