D-Link Forums
The Graveyard - Products No Longer Supported => D-Link Storage => DNR-202L => Topic started by: geetee2 on February 26, 2020, 07:46:11 AM
-
Many users reporting that 2.05.08 beta is defective with below symptom. I placed email support and has been 4 days and still no reply from dlink support on this issue.
see syslog. shows device restarting.
2020/02/17, 06:58:42, network set to static IP 150.233.25.54
2020/02/17, 06:58:44, usb1 mounted successfully.
2020/02/17, 06:58:57, system set to new time 2020/02/17 06:59:02.
2020/02/17, 07:04:54, system watch-dog reboot.(code 64)
2020/02/17, 07:05:25, system power on.
2020/02/17, 07:05:28, network set to static IP 150.233.25.54
2020/02/17, 07:05:30, usb1 mounted successfully.
2020/02/17, 07:44:06, system watch-dog reboot.(code 64)
2020/02/17, 07:44:36, system power on.
2020/02/17, 07:44:39, network set to static IP 150.233.25.54
2020/02/17, 07:44:42, usb1 mounted successfully.
2020/02/17, 08:32:42, system watch-dog reboot.(code 64)
2020/02/17, 08:33:12, system power on.
2020/02/17, 08:33:15, network set to static IP 150.233.25.54
2020/02/17, 08:33:15, usb1 mounted successfully.
2020/02/17, 11:12:53, system watch-dog reboot.(code 64)
2020/02/17, 11:13:26, system power on.
2020/02/17, 11:13:29, network set to static IP 150.233.25.54
2020/02/17, 11:13:31, usb1 mounted successfully.
2020/02/17, 13:37:32, system watch-dog reboot.(code 64)
2020/02/17, 13:38:00, system power on.
2020/02/17, 13:38:03, network set to static IP 150.233.25.54
2020/02/17, 13:38:06, usb1 mounted successfully.
2020/02/17, 13:38:17, system set to new time 2020/02/17 13:38:22.
2020/02/17, 16:26:05, system watch-dog reboot.(code 64)
2020/02/17, 16:26:33, system power on.
2020/02/17, 16:26:36, network set to static IP 150.233.25.54
2020/02/17, 16:26:38, usb1 mounted successfully.
2020/02/17, 18:33:14, system watch-dog reboot.(code 64)
2020/02/17, 18:33:46, system power on.
2020/02/17, 18:33:49, network set to static IP 150.233.25.54
2020/02/17, 18:33:51, usb1 mounted successfully.
2020/02/17, 18:38:34, admin login Ok from 150.233.25.37
Report to moderator 73.92.112.250
geetee2
Level 2 Member
**
Posts: 33
View Profile Personal Message (Online)
Re: Cannot playback 2020 videos
« Reply #84 on: February 17, 2020, 08:27:27 PM »
RemoveRemove
you can see the issue here with new firmware:
2020/02/17 20:18:37 admin login Ok from 150.233.25.37
2020/02/17 20:08:06 usb1 mounted successfully.
2020/02/17 20:08:03 network set to static IP 150.233.25.54
2020/02/17 20:08:00 system power on.
2020/02/17 20:07:32 system watch-dog reboot.(code 64)
new formware is causing a reboot via watchdog.....
-
Thanks for letting us know.
Keep in contact with D-Link support. Its in there hands. Nothing we can do here in the forums.
Good Luck.
-
The techs are answering your email now. It came in on Monday so it was not 4 days. They will issue a ticket for this issue with the engineers.
-
Reply from the engineers:
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.
-
Will fill out tonight.
-
The code 64 is WebUI relative error report and could you confirm with the customer:
1. What browser do they use?
IE
2. How many cameras have been managed by the DNR-202L? What Cameras are they using?
Four DCS-2330L, quality looks to be set to High (cant read, says undefined), 30fps, audio on for 2
3. Do they set up DNR-202L to register Mydlink service?
Not associated with account.
4. Can they reproduce the issue every time?[/i]
0-2 times a day, random @ anytime, even when not viewing, usually view 6am-6pm
2020/02/27 14:41:40 system watch-dog reboot.(code 64)
2020/02/25 03:21:52 system watch-dog reboot.(code 64)
2020/02/22 21:12:57 system watch-dog reboot.(code 64)
2020/02/22 17:37:13 system watch-dog reboot.(code 64)
2020/02/22 07:09:54 system watch-dog reboot.(code 64)
2020/02/20 22:07:03 system watch-dog reboot.(code 64)
2020/02/18 15:56:09 system watch-dog reboot.(code 64)
2020/02/17 20:21:22 system watch-dog reboot.(code 64)
2020/02/13 15:38:49 system watch-dog reboot.(code 64)
2020/02/11 04:31:34 system watch-dog reboot.(code 64)
2020/02/07 22:25:39 system watch-dog reboot.(code 64)
2020/02/07 17:19:22 system watch-dog reboot.(code 64)
2020/02/04 09:24:20 system watch-dog reboot.(code 64)
2020/02/01 08:33:45 system watch-dog reboot.(code 64)
2020/01/29 14:18:39 system watch-dog reboot.(code 64)
2020/01/26 03:17:20 system watch-dog reboot.(code 64)
2020/01/25 07:15:26 system watch-dog reboot.(code 64)
PS: All our currently NVR is only support the IE 11 browser and the rest browsers are not working.
agent 2.1.0-b61
f/w ver v2.05.01
f/w date sep 28 2017
f/w device pack v2.16.01
Harddrive: WD EasyStore 25FB 3.6TB
---------------------------------------------------
Installed BETA8 on this device 2/28/2020.
After 12 hours, no watch dog reboots, all 4 cameras recording. 172GB free though on drive. Will report back if this does any reboot via watchdog.
Finally:
2/29/2020 12:07, system watchdog reboot 64, 165GB left.
2/29/2020 17:57, system watchdog reboot 64, 116GB left.
3/02/2020 21:09, system watchdog reboot 64
3/03/2020 16:31, system watchdog reboot 64
3/05/2020 00:18, system watchdog reboot 64
3/06/2020 00:20, system watchdog reboot 64
3/06/2020 20:50, system watchdog reboot 64
3/07/2020 03:32, system watchdog reboot 64
-
The one without a problem and sits right next to the other one on the same network router
started 2018/11/24
24x7 1 DCS-960L, 1 DCS-2330L, both 1280x720 30fps, very high,
agent 2.03.02
f/w date Mar 7 2016
device pack: v2.11.03
HD WD My Pasport 259,3.6TB
Update 1: no reboots after 12 hours on this one with beta 8 installed
-
My DNR 202L on 11/10/2016 threw a system watchdog code = 08
No 64s
Using WD my passport 259, 3.8TB
2-3 caermas, 960L,2210L, 2330L
3/7/2020 Changed HD port from the one near the network adapter, to the side port.
-
a simple for for dlink is to give all loyal 202l users a FREE upgrade to their newest dnr hardware. Solves everything :)
-
a simple for for dlink is to give all loyal 202l users a FREE upgrade to their newest dnr hardware. Solves everything :)
What are your motion detection settings?
-
D-Link no longer Mfrs DNS or DNR products.
-
@Professor
"Professor, did you try using a thumb drive by any chance?"
-
Yes. I used a thumb drive over a 2 day period - Weds. Mar 4 and Thur. Mar 5 . No reboots - no problems at all. Used a 128Gb SanDisk Ultra - USB 3.0. Sorry I thought I had reported that last week! I am back on my regular HDD system (4Tb My Book WD with it's own power supply). Just one reboot in 3 days (this morning at 7:09 am. Since the reboots are not consistent, I doubt the engineers will find a solution. But, I'm hopeful!
-
Wonder if there is a problem with FW and size of USB drives. :-\
-
Wonder if there is a problem with FW and size of USB drives. :-\
Power issue?
The DTrack tech said he had issues with a HDD (no external power supply) with the beta firmware, swapped it for a thumb drive and it worked. Not sure how just fixing the date issue would cause reboots.
-
Plausible. Need to have everyone let us know what drive sizes they use and if they are powered or not.
I have a 500Gb drive connected to mine. I'll set it up again and let it run and see if I get anything. No power supply on drive. It's a SATA to USB 3.0 adapter cable connected to a laptop drive.
-
Ok, just enabled manual record on all 3 of my cameras. I'll let this run for a couple of days or a few and check the logs each day. Listen for any beeps as well.
-
As an update to my system, I am currently a set up as follows:
DNR-202L f/w 2.05.08 installed with factory reset of device when installed the new firmware:
2 Cameras:
DCS-932LB camera recording 24/7 with motion detection set
DCS-932LB camera recording 6 am to 7 pm with motion detection set
4Tb WD My Book HDD USB 3.0 (with separate power outlet) attached to the DNR-202L recorder
4Tb externally powered My Book HDD has given only 1 error 64 reboot after 4 days of running
Previous tests:
128 Gb SanDisk Ultra 3.0 USB Thumb Drive - no Log 64 reboot error during 2 days of running - this was a test only at the request of the Forum Moderator. I had recording problems though using a thumb drive. Response time using the thumb drive was poor, resulting in the cameras constantly dropping in and out.
2TB Western Digital My Passport Ultra HDD USB 3.0 (no external power source:) multiple Log 64 error reboots-up to 6-9 per day. -- This was my original setup that ran extremely well for more than 3 years before switching to the new f/w to resolve the 2020 calendar error.
Consequently I am now running with the 4Tb Western Digital My Book HDD USB 3.0 with an external power source. It is the best setup so far minimizing the Log 64 reboot and maintaining system performance.
Hope this information helps everyone.
-
What USB version are these drives? USB2.0 or 3.0?
-
All Drives are USB 3.0. I edited my original response to include USB 3.0
-
Ok, thank you much. ;)
-
ditto. usb 3
-
So far no beep or reboots since yesterday:
System Log:
2020/03/09, 16:24:57, network port disconnected.
2020/03/09, 16:25:03, network port connected.
2020/03/09, 16:25:04, network set to static IP 192.168.0.202
2020/03/09, 16:29:00, admin login Ok from 192.168.0.110
2020/03/10, 22:03:06, admin login Ok from 192.168.0.114
NVR Log:
2020/03/09, 16:36:48, camera device 192.168.0.93 is loss on ch 1.
2020/03/09, 16:36:51, camera device 192.168.0.93 stream stop on ch 1.
2020/03/09, 16:37:10, camera device 192.168.0.93 is activate on ch 1.
2020/03/09, 16:37:15, camera device 192.168.0.94 stream stop on ch 3.
2020/03/09, 16:38:03, camera device 192.168.0.95 is loss on ch 2.
2020/03/09, 16:38:06, camera device 192.168.0.95 stream stop on ch 2.
2020/03/09, 16:38:18, camera device 192.168.0.94 stream stop on ch 3.
2020/03/09, 16:40:03, camera device 192.168.0.95 is activate on ch 2.
2020/03/09, 16:41:11, camera device 192.168.0.94 stream stop on ch 3.
2020/03/09, 19:00:01, ch2 start schedule record.
2020/03/09, 19:00:01, ch3 start schedule record.
2020/03/09, 19:02:01, ch1 start schedule record.
2020/03/09, 23:59:01, ch2 stop schedule record.
2020/03/10, 00:00:01, ch1 stop schedule record.
2020/03/10, 00:00:01, ch3 stop schedule record.
2020/03/10, 00:04:01, ch1 start schedule record.
2020/03/10, 00:04:01, ch2 start schedule record.
2020/03/10, 00:08:01, ch3 start schedule record.
2020/03/10, 00:43:57, ch1 stop schedule record.
2020/03/10, 00:43:58, ch1 start schedule record.
2020/03/10, 06:57:01, ch2 stop schedule record.
2020/03/10, 08:03:01, ch1 stop schedule record.
2020/03/10, 08:03:01, ch3 stop schedule record.
2020/03/10, 16:10:49, camera device 192.168.0.93 stream stop on ch 1.
2020/03/10, 16:18:06, camera device 192.168.0.93 is loss on ch 1.
2020/03/10, 16:18:08, camera device 192.168.0.93 stream stop on ch 1.
2020/03/10, 16:18:14, camera device 192.168.0.93 is activate on ch 1.
2020/03/10, 16:18:31, camera device 192.168.0.94 stream stop on ch 3.
2020/03/10, 16:19:14, camera device 192.168.0.95 is loss on ch 2.
2020/03/10, 16:19:15, camera device 192.168.0.95 stream stop on ch 2.
2020/03/10, 16:19:41, camera device 192.168.0.95 is activate on ch 2.
2020/03/10, 16:26:01, camera device 192.168.0.94 stream stop on ch 3.
2020/03/10, 18:56:01, ch2 start schedule record.
2020/03/10, 18:58:01, ch1 start schedule record.
2020/03/10, 19:00:01, ch3 start schedule record.
Event Log:
Shows no events logged since bring the 202 online yesterday.
Ok, just enabled manual record on all 3 of my cameras. I'll let this run for a couple of days or a few and check the logs each day. Listen for any beeps as well.
-
The dlink developers that made the 2020 fix can easily look at their code and decide what they impacted. Otherwise, we - the users are spinning our wheels.
-
Only a few users. Please be patient while D-Link works on this.
-
They CANNOT replicate the issue. Not sure if simply comparing the code will do it. This reboot issue has been in every firmware (looking at old case logs). Very few people reporting it over the years and there doesn't seem to be any common thread with the users. Not everyone uses the same camera/setup combination so this makes it hard to figure out. I completely understand what you are saying geetee2 (i agree 100% with you) and I asked that question - what changed in the code other than adding 2020+ to date? Unfortunately all this goes through several hoops. They are aware, they are working on it but do not have much to work with.
-
I had the same issue the fix was to buy a USB spliter and use an external power supply (aka old cell phone charger) . Have had no issues since 3 weeks was rebooting every few hours.
The spliter can be bought on amazon for $6.99 HIGHROCK 30cm USB 2.0 a Power Enhancer Y 1 Female to 2 Male Data Charge Cable Extension Cord(1pc)
https://www.amazon.com/gp/product/B00NIGO4NM/ref=ppx_yo_dt_b_asin_title_o03_s00?ie=UTF8&psc=1
PAFL
-
I had the same issue the fix was to buy a USB spliter and use an external power supply (aka old cell phone charger) . Have had no issues since 3 weeks was rebooting every few hours.
The spliter can be bought on amazon for $6.99 HIGHROCK 30cm USB 2.0 a Power Enhancer Y 1 Female to 2 Male Data Charge Cable Extension Cord(1pc)
https://www.amazon.com/gp/product/B00NIGO4NM/ref=ppx_yo_dt_b_asin_title_o03_s00?ie=UTF8&psc=1
PAFL
Which drive are you using specifically?
-
sorry for the delay
WD My Passport 082 1 Tb
-
They did verify the reboot issue is from power draw from the hard drive. Using the power enhancer from PAFL has worked. Again, not sure why I cannot get an answer on why updating the date has caused some power issues from the previous firmware. ::)
-
Was there any determination over the cause of this issue? I just updated to that new firmware and have had several of the beeping reboots over the past 24 hours. Only updated hoping it would fix another issue with my 960L video settings being locked out and forcing resolution changes on the cameras. I am using two flash drives, one is a usb 3.0 120 gb Lexar and the other is a 2 gb Diskgo. Definitely shouldn’t be a power issue as they are both solid state sticks
-
After you fw upgrade did you factory reset the DNR?
-
factory reset? No, woudln't that erase the firmware upgrade?
I might factory reset if I can't figure this out and roll back.
-
No does not erase FW upgrade. Just user FW configurations.
-
No does not erase FW upgrade. Just user FW configurations.
Crud, so i'm stuck with the buggy version :'(
-
"After you fw upgrade did you factory reset the DNR?"
-
"After you fw upgrade did you factory reset the DNR?"
Are you saying that this issue is resolved if I factory reset or is that just part of troubleshooting the issue? I'll try it now.
-
http://forums.dlink.com/index.php?topic=75417.msg306103#msg306103
"After you fw upgrade did you factory reset the DNR?"
Are you saying that this issue is resolved if I factory reset or is that just part of troubleshooting the issue? I'll try it now.
-
Seems like the factory reset did the trick, no more resets as far as I can tell.
Thanks for the help !
-
Enjoy. ;)