• February 24, 2025, 05:32:41 PM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

This Forum Beta is ONLY for registered owners of D-Link products in the USA for which we have created boards at this time.

Author Topic: Hangs Up (part 2)  (Read 5927 times)

topikito

  • Level 2 Member
  • **
  • Posts: 34
Hangs Up (part 2)
« on: February 15, 2009, 06:35:21 PM »
My DNS 323 hanged up while refreshing iTunes server... It's OK, disabled... i can live without it... Sometimes the "Downloads" Interface stops working... thats also wrong, but I can still handle it: restarting the device. But when it starts, it checks the BitTorrent incomplete downloaded files... I'm currently downloading a 6,4 GB file, and it HANGS UP!!!!!!!! Last time I saw it, it was nearly 85% downloaded, but now, it hanged up at 70% while checking, (restarted by disconnecting the power, just like i did when it hanged up while refreshing iTunes server - Not good for the HD's (and all my important information on them) ), and now hanged at 34%... I know it's not the most powerfull processor it's got, but... shouldn't it could handle a "simple" operation like checking a file?? (The NAS has just powered off the HD) I'm trying to access to the Web GUI... doesn't work... trying to access trough the file browser... doesn't connect to the device (using Mac OS X)... tried to ping it... it responded... So, the network is fine, but the "Linux" inside it has hanged up.. but it can handle the HDs because it stopped them... :S :-\  ??? :-[ Confused!!!!!!  :o And angry...  >:( this shouldn't happen.  :'(
Logged

ECF

  • Administrator
  • Level 11 Member
  • *
  • Posts: 2692
Re: Hangs Up (part 2)
« Reply #1 on: February 19, 2009, 08:45:23 AM »
Does it work OK after it has finished refreshing all servers?
Logged
Never forget that only dead fish swim with the stream

topikito

  • Level 2 Member
  • **
  • Posts: 34
Re: Hangs Up (part 2)
« Reply #2 on: February 19, 2009, 04:36:59 PM »
If you mean with servers the iTunes or UPnP the answer is that I've never refreshed them correctly because when I try to, it stops at 4%, and don't carry on... I can for example, press the refresh button for the UPnP and the progress bar appears, then it comes to the 4%... and it just don't move from there...  Furthermore, the HDs stop spinning after the 15 minutes of the config... Wich I think means it's not refreshing nothing. For using again the 323, I removed the large file... nearly 5 GB to the trash (well, it hasn't got trash)... And with my 1 Mb/s internet connection, you can imagine how much time that means for me. I don't know if the DNS-323 is working fine, because I can't use the iTunes Server and either the UPnP streaming server (my XBox 360 doesn't find any media on it). I still have it on guarantee, shall I return it?
Logged

ECF

  • Administrator
  • Level 11 Member
  • *
  • Posts: 2692
Re: Hangs Up (part 2)
« Reply #3 on: February 20, 2009, 08:30:04 AM »
It seems to me that you may have a corrupt file being shared in the iTunes and UPnP AV media server that is causing this halt. If you are sharing the root on both or either of these I would recommend trying just the folder containing your media. If you still have this issue you will need to locate the questionable file and remove it. It may be tough but you can try only sharing specific smaller folders and running the refresh until you find the folder it hangs on then try and locate which file and remove it.
Logged
Never forget that only dead fish swim with the stream

topikito

  • Level 2 Member
  • **
  • Posts: 34
Re: Hangs Up (part 2)
« Reply #4 on: February 20, 2009, 11:09:16 AM »
Ok, i'll try. Thanks for the response
Logged

topikito

  • Level 2 Member
  • **
  • Posts: 34
Re: Hangs Up (part 2)
« Reply #5 on: March 01, 2009, 01:49:30 PM »
Ok, i've tried what you said, and you are right. The unique problem is that i have more than 80GB of music. Imagine how hard it could be to find the wrong directory where the corrupt file is. Whatever, I'll do it. But I will wish that you could make a feature for the next firmwares that maybe shows where it halts and shows the filename of the corrupt one. Well, thanks for helping.
Logged