Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[RYAT3]

Reverted back again!

Was changing some settings (turning audio recording off ), customer was on phone watching,  browser locked up, and the problem returned.

Perplexing! 

[FurryNutz]

Reverted to the problem or FW.

Try a factory reset on the DNR?

[RYAT3]

Reverted to the problem or FW.

Try a factory reset on the DNR?

Reverted to the problem.

Did Not get to try the factory reset. Had to return to base.   I'll monitor this one here and see if it reverts also.

[FurryNutz]

See if you can do a reset...odd issue for sure...

[RYAT3]

Was at home base - heard the DNR-202L beep, then beep again.
Checked the menus - this one also reverted to the problem menus and months being undefined.

This time a code 64 in the log.


2017/11/25 13:15:43 admin login Ok from 192.168.1.156
2017/11/25 13:14:59 usb1 mounted successfully.
2017/11/25 13:14:51 network set to DHCP
2017/11/25 13:14:45 system power on.
2017/11/25 13:14:22 system watch-dog reboot.(code 64)
2017/11/25 13:02:53 admin login Ok from 192.168.1.156
2017/11/25 06:07:23 admin login Ok from 192.168.1.156

[FurryNutz]

I would check the power supplies on both...under load...

How many cameras are these NVRs watching?

[RYAT3]

4.
Place 1- 2230,5010l,960l,960l.
Place 2- 2330l,2330l,2330l,960l

[FurryNutz]

Something to try maybe, have one only connect to 1 camera, power cycle or factory reset the NVR and set up from scratch with one camera and test. See if it happens again or not.

What USB drive do you have connected? Size? Could be another test. Just run the NVR with out a USB drive connected and test...

[GreenBay42]

I sent the code 64 log to the techs and still waiting on a response back about the previous log entries. Engineers/vendor will hopefully respond back soon.

[FurryNutz]

Any status on this? 

I sent the code 64 log to the techs and still waiting on a response back about the previous log entries. Engineers/vendor will hopefully respond back soon.

[RYAT3]

Any status on this? 

I sent the code 64 log to the techs and still waiting on a response back about the previous log entries. Engineers/vendor will hopefully respond back soon.

I haven't emailed the techs like GB42 asked me to about the setup.

I did do several things in the meantime and had some other observations.

One time - the thing reset with syswatchdog code 64.  But the menus and everything were back to normal!

It's "crashing" syswatchdog code 64/reboot at least 5 times a week, no more than once per day.

I know that the WD UltraPassport usb 3.0 drive without external adapter is some what frowned upon/questioned - it has been running for 1 year with the 4 cams.  I doubt this type of writing fragments the drive. 

Anyways - as a test, I bought a new 4 TB WD drive with external power adapter.  After ultra passport filled up - it started writing to the new drive.  Next day - crash syswatchdog code 64/reboot.

I removed the WD ultra passport and only have the WD drive with the external power adapter - since then 3 crash/reboots.

I haven't seen any other connections in the log other than local, and my external IP address.I think it was a hacking attack - they'd be a little more forceful than once every few days?

[FurryNutz]

I recommend keeping in touch with Tech support about this. Give them all the details.