Print

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

[tiredcam]

I have Live View on while at work to monitor the cams at my workplace and everything was working fine until a few days ago when the cams would disconnect from Live View by themselves. I cut all the cams down to 1 and even that last cam would disconnect by itself. All the cams are linked to my DNR322L via wired connections and I confirm that even while Live View was 'down', recording was still going on.

Two days ago, the NVR suddenly 'hung' i.e. I could not change menus and after force shutting down my IE, I could no longer log back on. I tried to shutdown the NVR via the front power switch by holding it for over 10 secs but it refuse to shutdown so I pulled the plug, waited for about 15 secs before powering on again.

I can see that my router assigns the IP address to the NVR but trying to login is a hit and miss with my IE timing out most times. Even if I am able to login, the loading of the Java apps takes a very very long time now and usually ends up hanging the NVR. Since I cannot do anything about it, I repeat the above i.e. pull the plug and reboot but it always ends up hanging sooner or later.

I have not been able to check if any recording was taking place during the 'hung' period. The one time I got in, I reset to factory defaults but it still hangs. Pinging the IP of the NVR returns a result so I know the data connection is live. LEDs on the front are all blue and I can hear the fan whirring on and off.

Anyone encountered this before or should I try to RMA this?

*UPDATE:
Turns out the problem was with my 2x 3TB WD AV-GP HDDs and not the DNR-322L. On a whim, I took out both HDDs and all the problems described e.g. slow login, slow Java response, hanging etc. all went away. Putting back one HDD in either slot did not create any issues but putting both in would bring all the problems back. Since both HDDs could function independently and the NVR did not indicate HDD failure, it was likely a software issue as I formatted both in JBOD format; it is likely the recording messed up the NVR somehow. I managed to login to the NVR with both HDDs in and ran a reformat. So far everything appear to alright so wish me luck.

[tiredcam]

While my previous issue of the DNR-322L locking up has been diagnosed to be a HDD issue, it appears that reformatting the drives was merely a temporary fix.

Since then I had reformatted both the Western Digital AV-GP drives (model no. WD30EURS) twice, first time using the JBOD format and the second time using RAID 0.

Both times, the recording volume appears to have been corrupted. From what I can piece together, this usually happens when the drive is about 80% full; with 3 cameras recording 24/7 at 720p/25FPS, this roughly works out to about 7-10 days left of recording time.

I have actually got a new NVR, having exchanged the old one with my retailer. I am now suspecting the HDDs may be broken but in my (limited) experience, usually HDD failures are pretty absolute i.e. they just stop working.

This intermittent issue makes me wonder if there is a compatibility issue between the DNR-322L and the WD drives I am using. I have came across 2 (old) sticky threads in the DNS-320 and DNS-321 forums that indicate that D-Link NAS has issues with the Advanced Format drives but this is an old issue that should have already been resolved.

The latest HDD compatibility sheet appears to be dated 10 Sep 2013 and does not have the WD30EURS listed on it which is funny because the AV-GP drives are touted to be designed for use in a 24/7 CCTV recording environment. Since the sticker on my drives indicate they were manufactured in late 2012, either the WD30EURS were never tested for compatibility or the list I saw is not the most current.

Any comments or further info on my issue (volume crashing) is most welcome. I will be getting the HDDs changed to be sure and will update if this issue still doesn't go away.

[Ctopia]

Hi tiredcam,

is your issue resolved? Did you bought compatible hard disks for your DNR. This is because I have the same issue of hanging up. My hard disks are compatible as per the compatibility list. The hang up started when our UPS shutdown, which doesnt have a USB feature. It seems, same as your observation, the drives malfunctioned. I reformatted the drives (JBOD) and then every hang ups were gone.
After 3 weeks, just this morning, it hanged up again - not pingable. I need to manually restart from the back.
I am now thinking of your 80% full - error possibility. Let me know if you resolved yours.

Thanks!

[tiredcam]

Hi tiredcam,

is your issue resolved? Did you bought compatible hard disks for your DNR. This is because I have the same issue of hanging up. My hard disks are compatible as per the compatibility list. The hang up started when our UPS shutdown, which doesnt have a USB feature. It seems, same as your observation, the drives malfunctioned. I reformatted the drives (JBOD) and then every hang ups were gone.
After 3 weeks, just this morning, it hanged up again - not pingable. I need to manually restart from the back.
I am now thinking of your 80% full - error possibility. Let me know if you resolved yours.

Thanks!

Hi Ctopia,

I did get both HDDs changed and actually got 2x brand new 3TB WD30EURX (the shop ran out of WD30EURS), the EURX being a more superior version with a higher data transfer rate. I initially formatted both new HDDs to Raid 0 but it again locked up like I described in my previous posts. The latest HDD compatibility list I found on the D-Link website was dated Sep 2013; it had the WD 2TB WD20EURS-63S48Y0 on it and that was the only WD AVGP drive listed.

I am not sure if your issue is actually related to the power shutdown as I did not have any power cuts to my NVR. Any forced powering down was done by me because nothing else worked i.e. cannot shutdown from the NVR power button, pressing the 'Reset' button does nothing. However, you did mention that you could "manually restart from the back" so I am assuming your 'Reset' button still worked. Also, you mentioned your NVR was not pingable once it locked up; mine was still pingable but I could not access the browser GUI.

I finally bit the bullet and went for Raid 1 format which effectively halved my recording time, which was NOT the reason why I went for a 6TB setup but it was that or swap HDDs every so often. To date, there has not been a repeat of the lockups.

I suspect the DNR-322L may not be handling 6TB capacity properly even though it does not explicitly prevent a user from having this setup. I am assuming you have more than 3TB of total capacity as you did not mention your HDD(s) capacity. I would also like to ask anyone with a setup of more than 3TB across 2 HDDs e.g. 2x 2TB HDDs (or more) and are using JBOD/Raid 0 format to also share their experiences.

Alternatively, it could be that the AVGP firmware of the HDDs is somehow interfering with the DNR-322L since I believe the NVR came out before there were AVGP HDDs. I also have a niggling feeling that D-Link has not actually done a full test on the AVGP range of drives even though the DNR-322L is touted as a NVR.

In summary, my "fix" is to sacrifice half of my rated capacity in exchange for Raid 1 functionality (for which I do not really want or need) in order for the NVR to continue working.

[Ctopia]

Hi tiredcam,

Thanks so much for the reply.

-"manual reboot at the back" was actually pulling out the power cable. I dont have intention to reset because it will take time to setup again. I was hoping manual restart will fix it.
-Mine is just 2x 2TB WD20EARS-00MVWB0. I used JBOD = 4TB.

Now we had a hang up again. I am betting on your observation of 80% and above full since mine was 87.5% when it hanged up. It is again not pingable. I am now thinking the drives failed already because of the power failure we had long ago and the manual reboots I did
Anyway, I will try the RAID1 (though i really dont want to reduce recording size) or change drives maybe.

Thanks 

[billzer]

Hi Tiredcam & Ctopia

I Would like to add my similar experiences with the DNR-322L.

Im running 2x 2TB WD2003FZEX-00Z4SA0 in JBOD (4TB) (The Compatibility list is old, and i couldn't find any compatible drives to purchase that were still available in Australian stores)

Once i start to near storage capacity (85% when it started) my DNR locks and and freezes also. It isn't Pingable via direct access (Local IP Address nor the MYDLINK website.)

When i Hard Reset it (pull the cable out) it reboots and is responsive up until the point when the cameras start recording (about 5 mins) then locks up again.

I though to myself maybe its the DNR so I have pulled out the drives and it hasn't locked up once yet.

I fixed this problem before by reformatting the drives and forgot about it until yesterday when it locked again.

So it looks like its a problem with the Drive configuration. the HDDs are tested and working correctly, so it must be something to do with the D-Link Software and how it handles large capacity hard drives.

Im going to try wipe the hard drives and configure it to Raid and see how i go.

Will comment with updates if i have further issues

[tiredcam]

Hi billzer,

Your experience is pretty much spot on with mine. When mine locks up and I do a manual power down (yank out the power cable), the NVR works for a few minutes after boot up then locks up again. Never measured the time but 5 mins sounds about there.

I don't use the cloud functions at all so I am not able to check in online but remote viewing from the Dlink app via my iPad is not possible. I am able to still ping the IP address of the NVR though strangely but that is really a minor detail since the NVR is not working.

It has been about 2 months since I formatted to Raid 1 and it has not locked up since. I am going to put my money that the NVR firmware has issues with storage greater than 3TBs.

[vvryan10]

I am having the same issue with My DVR-326.  I am going to try Raid 1.  Sad because it seems like a Hugh waste of space.

All the same details as what you guys describe above tho.  And it worked great until 80%

Very frustrating tho

[tmyc]

Whats going on with these 322's. I just spent $1000 on my systems. The cameras work on mydlink.com, but I havent been able get the 322 tto show live view at all. I can't get any help from Dlink... of course blaming something on my new computer for blocking the plugins for IE and the CamCliCtrl on Chrome. I think I would have better off buying a 10 camera sys from Costco with a DVR than this bs from Dlink. If anyone can help please see my only thread here.

[billzer]

Yep it seems to be a problem with the Firmware software. very frustrating that it hasnt been addressed.

from working in retail selling these things ive come to learn that these type of products get released and rehashed very quickly and do not receive the support they deserve to get functioning properly.

TMYC i have commented in your other thread on how i "fixed" a similar problem with my NVR...hope it helps

[billzer]

Yep NVR has locked up again at 85% capacity on JBOD.... switching to Raid 1 form now onwards

[chris_uk]

I had this exact problem on multiple DNR-322L units (thank you all for contributing to this thread and making it easy for me to find the cause!)

Identical set-ups of 2 x 4Tb Deskstar 7K4000 HDS724040ALE640 for sheer recording space (approx. 15 days with 4 cams).
JBOD
(One volume - NVR only).

At 81%, interface ran very slow, cameras began dropping off, then hung a day or so later. Front power button non-responsive. Hard power reset got it working for a few minutes.

I unplugged all the 'recording' cameras from the network (just removing POE via the various switches rather than actually pulling cables in different buildings) = interface working.

Puzzled and searched the internet, found this thread, logged call.

DLink support advised installing:
ftp://ftp.dlink.eu/Products/dnr/DNR-322L/driver_software/DNR-322L_fw_revA2_2-10B2_all_multi_20140707.zip

Just installed, looks ok at first glance (Jave errors also a little better), historic recordings ARE THERE (gap of a few weeks when I assume the 80% threshold was met).

I didn't need to reformat etc., literally just unplug the cameras to force recording stop, enter the 322 interface, and update the firmware. Settings and config were preserved (although usual disclaimer of backups and remember config file etc. just in case).

Will keep an eye on and report back if it turns out to be a short lived victory!

[billzer]

Hi Chris_uk

That firmware version is a much later version that the D-link Support page lists as current on the DNR-322 Support page.

Interesting that they have a newer firmware version that isn't listed... makes me think that someone has forgotten to update the website page for it.

Let us know how you go with it once you hit that iffy 80-90% capacity mark.

if its successful i will switch back to JBOD for sheer storage capacity again.

[chris_uk]

I think that there's an engineering team in the UK (based in Park Royal near Wembley) so may still be in testing for other regions - it's listed on the UK product page here:
http://www.dlink.com/uk/en/support/product/dnr-322l-cloud-network-video-recorder
(however the dates in all the settings are the US MM/DD/YY format instead of the UK DD/MM/YY so it could easily just be an overlooked update on the other site too!)

The 322 has continued on from the point it got to pre-hang (old recordings available up to the 80% mark, new recordings are extra) and has now climbed to 86% total...
I noticed that the new setting in Setup > Recording Schedule is: "Automatic Overwrite  Recycle when the storage space is less than  2 / 5 / 10 / 15 / 20 %" with a default of 10%. We might not know if the auto-recycle is working until 90%+ is reached now then!

[billzer]

i updated the firmware and noticed that setting too, pretty nifty.

I have also noticed that the overall response rate of clicking between menus in the interface is a lot better/faster, making for a much less frustrating experience waiting for the interface to load.

i have not switched back to JBOD yet though, will await your results when you hit that recycle threshold