Print

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

[FurryNutz]

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.

[FurryNutz]

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.

[Professor]

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.

[FurryNutz]

What USB version are these drives? USB2.0 or 3.0?

[Professor]

All Drives are USB 3.0.    I edited my original response to include USB 3.0

[FurryNutz]

Ok, thank you much. 

[geetee2]

ditto.   usb 3

[FurryNutz]

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.

[geetee2]

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.

[FurryNutz]

Only a few users. Please be patient while D-Link works on this.

[GreenBay42]

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.

[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

[RYAT3]

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?

[PAFL]

sorry  for the delay

WD  My Passport 082  1 Tb

[GreenBay42]

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.