Print

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

[jiggysmb]

After upgarde to 1.06 my drives had a lot of activity throughout the night (RAID1) but by the next morning everything was functional.  After powering the unit off for about 48 hours I turned it on and was able to access the device for about 5 minutes then went to see the square led was white and drive LEDs were pinkish.  When I powered off the unit they flashed orange/pink for a few seconds then the unit turned off.  Now this occurs each time I turn on the device? 

Any suggestions would be greatly appreciated.

[samendolaro]

This happend to me as well. I solved it by mapping my Itunes and UPNP server to a directly with a maximum of 4 levels. If I picked the volume or root directory the drives went pink after inactivity.

Try as a test to change the directory mapping of these servers to an empty directory and see if it remains stable. If it does then you just need to reorganize your content.

[kqmaverick]

I had this issue and i dont know if i have fixed it here yet, my last troubleshooting step was to clean of the drives  and try to reformat/rebuild my JBOD (Spanning) but having 2 1GB HD's installed the process of backing up data has been taking some time. I noticed that after i got the used space down to less then 50% the problem stopped occuring, leading me to believe based on my use of JBOD that possibly 1 of my HD's is having issues. Once i finish backing up all data and reformat/rebuild JBOD and fill it back up hopefully the problem dosent return. Do you have any problems accessing the drive VIA windows explorer once the LED's turn pink? i found i was unable to access files on the DNS-323 until i rebooted after the LED's turned pink.

[jiggysmb]

I disabled iTunes and the problem was still occuring. 

Creating a single upnp folder with one folder for my video files seems to have solved the problem but when I enabled itunes with a single folder for mp3s it bombed out again....  Maybe 1.07 will fix this problem?

I have had this unit since before it was available to the public and have faithfully held onto it. It seems every other release adds valuable features but each has had some major downfall.  Then the following release has the fixes.  I was too excited to see the 360 streaming and jumped the gun on this one.  Not sure if it is poor beta testing, but I will only install odd numbered updates from now on :-)

[Mannen]

I have the same impression. After running stable, as i did for over a year, you just donīt want to jibble around whit different issues that d-link already should have fixed. Maybe they wantet a little to much this time? I would love to go 1.06 but i kinda like stability on backup devices, so i rest in peace whit 1.05. For now.

The thing is that we can back up and rebuild (My disklights turned pinkish and i got that tip from someone here, suggesting that my unit was faulty!) and change serverconf and directories and many other things, but in the end the only thing you end up whit is a lot of time wasted.

Just look at this forum, and all the crazy issues that turned up all of a sudden. I think D-LINK really should admit that this was a faulty issue, and that a new FW is in the pipe.