Print

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

[RYAT3]

nothing has changed for years.  issue is the new firmware

No, it was the previous F/W.

I reported 3 years ago now.

http://forums.dlink.com/index.php?topic=72739.msg292068#msg292068

[RYAT3]

My system with 2 cameras, 1 24x8, the other 10 hours per day did this a couple times years ago. I can not find it in the log and it hasn't done it on the new F/W.
(usb powered ultra passport WD)

system 2 with previous f/w and only 2 caeras 24x7 has not done it that i can see iogs.
system 1 which resides next to system 2 and has 4 24x7 cameras and still on the old f/w has done as recently as 2/17.

maybe caermas at full quality and 24x7 are the problem.  I cannot tell from here which system 2or 3 has the WD ultra pssport or the full size external HD WD with power supply. 

The power at home with 2&3 - I never get 5 volts when measuring what my devices are chargning at.

[Professor]

Can you check your Logs to see if you see any of these in the logs?
system watch-dog reboot.(code 64)

Has your DNR been factory reset and setup from scratch since the FW update?

I have had an occasional (once every few days) long loud beep from the using the new beta firmware.  Can't pin it down to any specific events though.  Other than that everything works OK - no recording or playback problems
[/quote

I did perform a factory reset from scratch since the beta Firmware update.  Nothing in my system logs to show why the beep occurs.  I have not had a long loud beep for the past 7 days though.  Seems to be a random occurrence so far.  My recording hdd is not full.  I use a WD MyPassport 2TB.  Have 2 DC-932LB cameras on 24 hour recording mode.

[FurryNutz]

What model cameras do you have connected?
What resolution are they using?

[Professor]

I am just reporting a problem that I have noticed with the new beta firmware for the DNR-202L and confirms what geetee2 has previously reported

I have also noticed that my system is being rebooted using the new Firmware.  It has also resulted in an occasional (once every few days) long loud beep from the using the new beta firmware.

I did perform a factory reset from scratch for the latest beta Firmware update and reformatted my recording HDD.  The problem seems to be a random occurrence so far.  I use a WD MyPassport Ultra 2TB for the recording HDD.  I have 2 DC-932LB cameras - one of them in 24 hour recording mode and the other recording about 12 hours/day.

My cameras do go offline occasionally - mainly due to my WiFi system, but my DNR-202L is never taken down.

My computer system and peripherals are on a battery backup system and there have been no power outages for several months
 
The system logs (below) for the past 2 weeks are showing a system watch-dog reboot.(code 64) which corresponds to the time the loud beep occurs from the DNR-202L.  I am not usually in the room with my computer and recording device when it occurs, but today at 2/21/2020 at 9:26:13 am local time the beep occured while I was on my computer.  It was a system reboot for the DNR-202L.  Also the system set to a new time a few seconds later.  I did not reset anything nor did I unmount and then remount the attached USB drive.  I did lose about 1 minute of recordings while the system went off line.  The system watch-dog reboot.(code 64) is a new error message that I have never seen before.  These anomalies just keep cropping up with the new beta firmware.  I did not have this problem using the old firmware.

2020/02/07, 10:32:37, system watch-dog reboot.(code 64)
2020/02/07, 10:33:05, system power on.
2020/02/07, 10:33:11, network set to DHCP
2020/02/07, 10:33:23, system set to new time 2020/02/07 10:33:17.
2020/02/07, 10:33:50, usb1 mounted successfully.

2020/02/08, 11:53:19, system watch-dog reboot.(code 64)
2020/02/08, 11:53:49, system power on.
2020/02/08, 11:53:55, network set to DHCP
2020/02/08, 11:54:41, usb1 mounted successfully.

2020/02/09, 01:12:25, system watch-dog reboot.(code 64)
2020/02/09, 01:12:57, system power on.
2020/02/09, 01:13:03, network set to DHCP
2020/02/09, 01:13:45, usb1 mounted successfully.
2020/02/09, 17:21:38, system watch-dog reboot.(code 64)
2020/02/09, 17:22:07, system power on.
2020/02/09, 17:22:13, network set to DHCP
2020/02/09, 17:22:59, usb1 mounted successfully.

2020/02/11, 11:13:03, admin login Ok from 192.168.1.16
2020/02/11, 15:37:43, system watch-dog reboot.(code 64)
2020/02/11, 15:38:09, system power on.
2020/02/11, 15:38:15, network set to DHCP
2020/02/11, 15:38:27, system set to new time 2020/02/11 15:38:20.
2020/02/11, 15:38:53, usb1 mounted successfully.
2020/02/11, 20:17:17, system watch-dog reboot.(code 64)
2020/02/11, 20:17:46, system power on.
2020/02/11, 20:17:52, network set to DHCP
2020/02/11, 20:18:34, usb1 mounted successfully.

2020/02/12, 04:06:02, system watch-dog reboot.(code 64)
2020/02/12, 04:06:32, system power on.
2020/02/12, 04:06:38, network set to DHCP
2020/02/12, 04:07:20, usb1 mounted successfully.

2020/02/16, 19:05:03, system watch-dog reboot.(code 64)
2020/02/16, 19:05:28, system power on.
2020/02/16, 19:05:34, network set to DHCP
2020/02/16, 19:05:46, system set to new time 2020/02/16 19:05:36.
2020/02/16, 19:06:07, usb1 mounted successfully.

2020/02/21, 09:26:13, system watch-dog reboot.(code 64)
2020/02/21, 09:26:40, system power on.
2020/02/21, 09:26:46, network set to DHCP
2020/02/21, 09:26:47, system set to new time 2020/02/21 09:26:47.
2020/02/21, 09:27:17, admin login Ok from 192.168.1.6
2020/02/21, 09:27:24, usb1 mounted successfully.
2020/02/21, 13:31:27, admin login Ok from 192.168.1.6

[RYAT3]

What was your previous F/W?

Your assumption is wrong, because I had it on the previous ?2016? F/W and still do.

Also you should see that your TEXT goes all funny depending on the reboot.

[Professor]

Let's just say I starting noticing it with the new F/W.  Don't remember what Firmware I used previously.  I also upgraded my desktop computer over the past month or so and needed to reset the DNR-202L for it work properly.   As long as I know where the beep is coming from and I get an occasional system reset I can live with the issue

[geetee2]

yup. STILL beeping  every roughly 1 hour is hour or so.   Is with the new firmware. 

BUGGY
BUGGY
BUGGY.

revert to previous fw and no beeps but of course the 2020 bug.

please advise.

[FurryNutz]

Even after a factory reset wit the new FW? Mines not beeping. Not sure why the difference. 

[geetee2]

multiple people are reporting the same reboot and hence beep issue. 

please confirm that dlink will fix this ASAP for the beping is keeping us awake.  Poor quality code from Dlink after waiting so long for a 2020 fix.   EMBARRASSING

[FurryNutz]

Users will need to contact D-Link support and let them know about what your seeing. As there's nothing else we can do here in the forums.

Would be nice to know if someone can do a factory reset to confirm the issue still happens. Would be "EMBARRASSING" if the problem was fixed by a reset.

[FurryNutz]

I presume that the main forum post has been resolved as users have been able to access and playback videos with the new FW. We can mark this post thread as solve and closed.

[GreenBay42]

Issue was sent to engineers. Hopefully they can fix it or figure out what it causing the reboots.

[GreenBay42]

Reply from the engineers regarding "watchdog" error and rebooting:

The code 64 is WebUI relative error report and could you confirm with the customer:

1. What browser do they use?

2. How many cameras have been managed by the DNR-202L? What Cameras are they using?

3. Do they set up DNR-202L to register Mydlink service?

4. Can they reproduce the issue every time?
 
PS: All our currently NVR is only support the IE 11 browser and the rest browsers are not working.

[geetee2]

nothing has changed from previous fw version to latest.   happens all the time