Print

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

[gama]

My DNR-322L started to beeping randomly like there was a problem.  Looking at the logs did not really offer any answers.  But it did show a large number of what looked to be some kind of power events.  But this DNR is on a UPS so power should not be an issue, plus there has been no power loss or outages at the location.  So I formatted the hard drives and then did "2019/06/07, 15:40:06, system firmware upgrade to ver v3.02.07(WW) from remote.".  Ever since the upgrade, it reboots with "system watch-dog reboot.(code 64)"  any were from every two (2) to twelve (12) hours.

I can use any and all the help I can get.

Firmware Information      
Agent Version :         2.2.0-b53   
Current NVR Firmware Version :   v3.02.07   
Firmware Date :         Sep 13 2018   
Current NVR Device Pack :   v2.17.01   
Device Pack Date :      Sep 13 2018

Log


2019/06/04, 04:54:13, raid level0 mounted successfully.
2019/06/04, 05:00:36, admin login Ok from 127.0.0.1
2019/06/04, 06:39:39, admin login Ok from 127.0.0.1
2019/06/04, 07:24:51, admin login Ok from 192.168.1.2
2019/06/04, 07:55:18, admin login Ok from 127.0.0.1
2019/06/05, 07:53:50, admin login Ok from 192.168.1.2
2019/06/05, 08:22:51, admin login Ok from 192.168.1.2
2019/06/05, 11:01:23, admin login Ok from 192.168.1.2
2019/06/05, 18:38:10, admin login Ok from 192.168.1.16
2019/06/06, 12:42:33, admin login Ok from 192.168.1.2
2019/06/06, 12:45:32, admin login Ok from 127.0.0.1
2019/06/06, 13:01:58, admin login Ok from 127.0.0.1
2019/06/06, 17:09:52, admin login Ok from 127.0.0.1
2019/06/07, 10:28:31, admin login Ok from 192.168.1.2
2019/06/07, 10:30:05, raid0 format
2019/06/07, 10:35:08, raid level0 mounted successfully.
2019/06/07, 10:39:31, hdd-R unmounted successfully.
2019/06/07, 10:39:34, hdd-L unmounted successfully.
2019/06/07, 10:39:37, raid level0 unmounted successfully.
2019/06/07, 10:39:--, system normal power off.
2019/06/07, 15:40:06, system firmware upgrade to ver v3.02.07(WW) from remote.
2019/06/07, 10:40:35, system power on.
2019/06/07, 10:40:38, network set to static IP 192.168.1.25
2019/06/07, 10:40:53, system set to new time 2019/06/07 10:40:44.
2019/06/07, 10:41:02, admin login Ok from 192.168.1.2
2019/06/07, 10:41:32, raid level0 mounted successfully.
2019/06/07, 11:55:--, system watch-dog reboot.(code 64)
2019/06/07, 11:55:48, system power on.
2019/06/07, 11:55:51, network set to static IP 192.168.1.25
2019/06/07, 11:56:56, admin login Ok from 192.168.1.2
2019/06/07, 11:56:56, raid level0 mounted successfully.
2019/06/07, 18:38:--, system watch-dog reboot.(code 64)
2019/06/07, 18:38:21, system power on.
2019/06/07, 18:38:24, network set to static IP 192.168.1.25
2019/06/07, 18:39:03, raid level0 mounted successfully.
2019/06/07, 22:20:--, system watch-dog reboot.(code 64)
2019/06/07, 22:20:39, system power on.
2019/06/07, 22:20:42, network set to static IP 192.168.1.25
2019/06/07, 22:21:36, raid level0 mounted successfully.
2019/06/07, 22:34:--, system watch-dog reboot.(code 64)
2019/06/07, 22:34:27, system power on.
2019/06/07, 22:34:30, network set to static IP 192.168.1.25
2019/06/07, 22:35:27, admin login Ok from 192.168.1.5
2019/06/07, 22:35:33, raid level0 mounted successfully.
2019/06/07, 22:45:--, system watch-dog reboot.(code 64)
2019/06/07, 22:46:14, system power on.
2019/06/07, 22:46:17, network set to static IP 192.168.1.25
2019/06/07, 22:46:37, admin login Ok from 192.168.1.2
2019/06/07, 22:46:49, raid level0 mounted successfully.
2019/06/07, 22:53:05, hdd rewrite mode change to on.
2019/06/08, 09:08:--, system watch-dog reboot.(code 64)
2019/06/08, 09:08:52, system power on.
2019/06/08, 09:08:55, network set to static IP 192.168.1.25
2019/06/08, 09:09:31, raid level0 mounted successfully.
2019/06/08, 13:12:04, admin login Ok from 192.168.1.6
2019/06/08, 18:24:--, system watch-dog reboot.(code 64)
2019/06/08, 18:25:14, system power on.
2019/06/08, 18:25:17, network set to static IP 192.168.1.25
2019/06/08, 18:25:57, raid level0 mounted successfully.
2019/06/08, 19:46:--, system watch-dog reboot.(code 64)
2019/06/08, 19:46:40, system power on.
2019/06/08, 19:46:43, network set to static IP 192.168.1.25
2019/06/08, 19:47:21, raid level0 mounted successfully.
2019/06/09, 06:26:--, system watch-dog reboot.(code 64)
2019/06/09, 06:27:32, system power on.
2019/06/09, 06:27:35, network set to static IP 192.168.1.25
2019/06/09, 06:27:49, system set to new time 2019/06/09 06:27:44.
2019/06/09, 06:28:34, raid level0 mounted successfully.
2019/06/09, 10:20:--, system watch-dog reboot.(code 64)
2019/06/09, 10:20:37, system power on.
2019/06/09, 10:20:40, network set to static IP 192.168.1.25
2019/06/09, 10:21:50, raid level0 mounted successfully.
2019/06/09, 12:41:--, system watch-dog reboot.(code 64)
2019/06/09, 12:42:07, system power on.
2019/06/09, 12:42:10, network set to static IP 192.168.1.25
2019/06/09, 12:42:44, raid level0 mounted successfully.
2019/06/09, 13:37:--, system watch-dog reboot.(code 64)
2019/06/09, 13:37:22, system power on.
2019/06/09, 13:37:25, network set to static IP 192.168.1.25
2019/06/09, 13:38:01, raid level0 mounted successfully.
2019/06/09, 13:38:--, system watch-dog reboot.(code 64)
2019/06/09, 13:39:15, system power on.
2019/06/09, 13:39:18, network set to static IP 192.168.1.25
2019/06/09, 13:39:51, raid level0 mounted successfully.
2019/06/09, 17:03:--, system watch-dog reboot.(code 64)
2019/06/09, 17:03:49, system power on.
2019/06/09, 17:03:52, network set to static IP 192.168.1.25
2019/06/09, 17:04:29, raid level0 mounted successfully.
2019/06/10, 01:48:--, system watch-dog reboot.(code 64)
2019/06/10, 01:48:22, system power on.
2019/06/10, 01:48:25, network set to static IP 192.168.1.25
2019/06/10, 01:49:19, raid level0 mounted successfully.
2019/06/10, 03:38:--, system watch-dog reboot.(code 64)
2019/06/10, 03:38:45, system power on.
2019/06/10, 03:38:48, network set to static IP 192.168.1.25
2019/06/10, 03:39:24, raid level0 mounted successfully.
2019/06/10, 06:51:--, system watch-dog reboot.(code 64)
2019/06/10, 06:52:11, system power on.
2019/06/10, 06:52:14, network set to static IP 192.168.1.25
2019/06/10, 06:52:48, raid level0 mounted successfully.
2019/06/10, 06:53:58, admin login Ok from 192.168.1.2
2019/06/10, 12:07:--, system watch-dog reboot.(code 64)
2019/06/10, 12:07:41, system power on.
2019/06/10, 12:07:44, network set to static IP 192.168.1.25
2019/06/10, 12:08:19, raid level0 mounted successfully.
2019/06/10, 14:14:--, system watch-dog reboot.(code 64)
2019/06/10, 14:14:54, system power on.
2019/06/10, 14:14:57, network set to static IP 192.168.1.25
2019/06/10, 14:15:58, raid level0 mounted successfully.
2019/06/11, 02:02:--, system watch-dog reboot.(code 64)
2019/06/11, 02:03:03, system power on.
2019/06/11, 02:03:06, network set to static IP 192.168.1.25
2019/06/11, 02:03:40, raid level0 mounted successfully.
2019/06/11, 08:08:--, system watch-dog reboot.(code 64)
2019/06/11, 08:08:52, system power on.
2019/06/11, 08:08:55, network set to static IP 192.168.1.25
2019/06/11, 08:09:10, system set to new time 2019/06/11 08:09:05.
2019/06/11, 08:09:57, raid level0 mounted successfully.
2019/06/11, 08:52:44, admin login Ok from 127.0.0.1
2019/06/11, 09:45:58, admin login Ok from 192.168.1.2

[FurryNutz]

Have you factory reset the DNR and setup from scratch after the FW update?

[gama]

I have done a factory reset of the DNR twice.  First time I used a configuration file to setup it up.  The second time I only setup, from scratch, its static IP, the time, and formatted the hard drives.  I didn't even add cameras.  And I am still getting the same error.

Since the second reset, done 2019/06/30 at approximately 15:30, I have gotten the following sequence of events
1) system watch-dog reboot.(code 64)
2) system power on.
3) network set to static IP 192.168.1.25
4) raid level0 mounted successfully.

at the following times.
2019/06/30  17:14:--
2019/07/01  02:36:--
2019/07/01  07:51:--
2019/07/01  09:01:--

I do not know what else to try.

[FurryNutz]

I recommend you contact D-Link support and have them submit a support ticked on this asap.
Support time is running out for the 322L so this needs to be addresses soon:
Link> Tech Support Contact Information
We find that phone contact has better immediate results over using email.
Let us know how it goes please.

[tk1707]

This is how I stopped that random beeping forever: I took out the buzzer.
Here is how you do it:
1) poke out the rubber feet
2) unscrew the 2 screws
3) pry open the case
4) locate the piezoelectric buzzer (the black disk with a small hole in the center) and pull it off with a pair of pliers
5) reassemble the case

[Professor]

Thanks for the instructions for removing the piezoelectric buzzer. I definitely use it if needed.
 My unit inexplicitly stopped the random system watch-dog reboot (code 64) six months ago.  I have had my unit continuously running without any problems.  No random reboots or Code 64 errors. 
I have a 4Tb Western Digital MyBook Drive (externally powered) hooked up to the unit and 3 cameras running continuously with no problems for 9 months (last 6 months no code 64 errors).

[RYAT3]

I too started getting system watchdog 64 on a DNR-202 starting in November.

System has been running several years now without having any system watchdogs.

The DNR202L next to it, has always had watchdog 64 for several years now.

One has a full size external drive with power supply, the other one has a WD ultra passport 3.5", both 4GB..

There's a several posts in the DNR 202L subforum - i think they tracked it down to the drive used on the device.  I figured that's why one of the 2 acted up.  But now that both are active - it might be something else.

[FurryNutz]

I would have NOT resorted to that extreme of removing any hardware parts from the DNR. In this case this would be an incorrect move as the part remove would not be a cause of these system watch dog reboot errors being seen.

If users are seeing problems with there DNR units, I highly recommend posting about it here in the D-Link forums or making contact with D-Link support BEFORE taking any drastic actions with there DNR HW. In most cases and problems, can be resolved with some troubleshooting and information sharing. Please post and ask questions and ask for help. We are here to help as much as possible.

Good to know that others are seeing normal operations with there DNR units.

Good Luck.