• June 19, 2018, 12:58:01 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: nas 323 fan always on  (Read 2275 times)

sterox

  • Level 1 Member
  • *
  • Posts: 3
nas 323 fan always on
« on: November 11, 2010, 05:59:12 AM »

Hello, I have a problem with this NAS, it works almost perfectly, but when he wa in hibernation (discs), I turn on the fan!! and stays on!, I explain, during operation, it happens that the fan turns on, logical to cool, then go off, then goes to the NAS mode (idle) hard drives are switched off and the fan turns on and stays on always day and night! (This does not make sense).
I set 15 minutes for bernazione hdd, the firmware is 1.8 (it also does with 1.7) hdd's are compatible (as site-specific d-link) what can be? or may depend on what? (Rev c1 is the dns323)
Thanks. ???
Logged

dosborne

  • Level 5 Member
  • *****
  • Posts: 598
Re: nas 323 fan always on
« Reply #1 on: November 11, 2010, 06:30:18 AM »

Posted as a known issue in this sticky thread Sticky Topic: DNS-323 1.08 Ongoing Issue List
http://forums.dlink.com/index.php?topic=11993.0

Some users have had success by performing a reset back to factory settings, then reconfiguring from scratch, NOT restoring a saved configuration file.
« Last Edit: November 11, 2010, 06:33:56 AM by dosborne »
Logged
3 x DNS-323 with 2 x 2TB WD Drives each for a total of 12 TB Storage and Backup. Running DLink Firmware v1.08 and Fonz Fun Plug (FFP) v0.5 for improved software support.

sterox

  • Level 1 Member
  • *
  • Posts: 3
Re: nas 323 fan always on
« Reply #2 on: November 12, 2010, 02:32:43 AM »

Hello
thanks, I read the post
Logged

jtma67

  • Level 1 Member
  • *
  • Posts: 11
Re: nas 323 fan always on
« Reply #3 on: December 08, 2010, 03:10:23 PM »

I had the same problem... and I've upgraded to v 1.09 so I called support.... they indicated this is still a known problem and that the engineers are working on it.  Maybe it'll be fixed in firmware v1.10 ??
Logged