DSM-G600, DNS-3xx and NSA-220 Hack Forum

Such script would be excellent... My drives spin down normally, but the fan is annoying, when running all the time Good luck

Ok, toady I just couldn't stand the fan sound... Disassembled the unit, tried to change the fan, but only found that original fan in fact IS silent! Tried 2 other fans, but original one was the most silent. Unfortunately best fans I have and use are all 12V, so no luck. So I decided not to care about damn warranty Cut out "protective" piece of plastic from the back plate, enlarged the opening, added some padding. After that the unit is MUCH more quiet, in fact I can barely hear it now Well, the original "brute force" idea works after all, at least in my case, haha

While comparing fans and playing with the unit I "discovered" that there surely IS some fan rpm management working in DNS-323. In the boot process there is a phase in which fan runs at full speed and then settles down to a low rpm. It is a HUGE difference in sound. So thermal management seems to work - the only problem is, that even if both drives are powered down (in sleep state), fan still runs. It would make sense to spin down (turn off completely) the fan as soon as both disks are in sleep state, so the box would be totally silent when not in use. I wonder if it is possible just by modifying the code gotdiskey just mentioned (in next FW?). Well, I guess this won't happen anyway

I made some quick pictures from the process, you can see them with some notes here - http://members.chello.sk/ondro727/

@someguy:

Don't let your eyes fool you - the hole and all modification is FAR from perfect, but I don't have tools and time to make it as perfect as I'd like... Used sharp knife (sorry, I don't know the english word for it...) to cut out the central piece of plastic, then enlarged the hole using some rasp (I am not sure of this word either ) and as soon as it was wider than fan itself, I finished it with some soft abrasive coated paper. Nothing special

Well, Linux is not a big friend of mine (shame on me), so there's no way I can help with the script But if there is anyone...

As I said, the real downside of this process is that you void warranty by this modification. Anyway, if the unit dies, I still can use original back plate from other DNS-323 from a friend of mine

I guess next logical step would be to broadcast your fanspeed and temperature to an external node, e.g. your Mediacenter.

.
.
  fanspeed w $newRPM 
  #
  echo "TEMP: $T;FAN: $newRPM" | /mnt/HD_a2/lnx_bin/nc 192.168.0.255 60606
  #
  sleep $update_interval
.
.

...and on your XBMC you create a small Python script which listens to 60606 and show some information on the screen.
...or nc.exe -l -p1234 on your PC will give you the details....
...or why not a neat Firefox plugin ;-)
...or an SMS gateway,

Well done! Please add your information to the Wiki http://dns323.kood.org/hardware:fan

/Apan

Nice: Does anyone know where the (two?) temperature probe(s) are?  Could be fun to experiment : ).  We're relying on the black-box algorithm of g 0.   

It would also be great to have a simple script that simply detects whether or not the drives are sleeping or not.
I like the monitoring server idea. net-snmp is an option..

Also, now that I think of it, what if the script fails? -- we might have a fire on our hands - or do we get an smtp alert? : ).

- one more thing:  we could also use a simple script to detect whether a system uses Farenheit or Celcius to store Temperature -- this way scripts could be more transportable (e.g: if someone writes a Script with Max temperatures at 176 Farenheit, but they run it on a Celcius-based machine... trouble!!)

Last edited by someguy (2007-02-07 22:27:12)

someguy wrote:

Nice: Does anyone know where the (two?) temperature probes are?  Could be fun to experiment : ).  We're relying on the black-box algorithm of g 0.  Unknown if g 0 returns a problem if g 1 maxes, while g 2 stays cool, for instance.

I think there is only one temperature probe that is accessed by g 0. Unfortunately I have no idea where it's located...

# temperature
temperature - query and set the temperature sensor

Usage: temperature [function]

Functions:
 h - show this help
 w [1,2] degree - set temperature degree in register 1:Thyst 2:Tos
 g [0~2] - get temperature in register 0:temperature 1:Thyst 2:Tos

Googling for thyst and tos gives quite a lot of hits among others
lm75a_1.pdf where they say on page 2: " set-point registers (Tos & Thyst) to store programmable  overtemp shutdown and hysteresis limits"

On my box g 1 always return 75 and g 2 always returns 80. I really hope nothing inside it is that hot

Lipovitan.B3 wrote:

is it really safe to run the unit at 60° ?? I read somewhere in the specs of my samsung hdds that 60°C should be upper limit ...

It is not meant to run at 60 degrees, I simply wanted to cap the maximum RPM so that the fan does not break, I have not tested fanspeed w 30000 to see if it's safe You can always use more conservative parameters... With the preceding parameters my unit has a temperature of 47-48 C under light load, which gives a fanspeed of 2400-2600. I should test and see what happens under a  heavier load. What temperatures do you other people have?

Last edited by galf (2007-02-07 19:34:34)

someguy wrote:

- one more thing:  we could also use a simple script to detect whether a system uses Farenheit or Celcius to store Temperature -- this way scripts could be more transportable (e.g: if someone writes a Script with Max temperatures at 176 Farenheit, but they run it on a Celcius-based machine... trouble!!)

The current version of the script might very well fail if the units are in Farenheit... It would be quite easy to fix though, I just need to add a parameter that defines the unit of T1 and T2. Then its a question of making sure all units match and convert if necessary.

Could anybody with a system that uses Farenheit post exactly what temperature g 0 reports?

someguy wrote:

galf wrote:

On my box g 1 always return 75 and g 2 always returns 80.

Cool. That would be consistent with the findings of the great .pdf file that you found (there's a lot of great information in it) - are you sure that chip is the one that's used in the dns-323?:

Just to make it clear, I have no idea which chip is used in the dns-323. I simply assume that most of these chips are fairly similar and thus have certain standard features. I think it is safe to assume that the meaning of  temperature g 1 and 2 are those given in that pdf. Note that you can write values to these registers but not to g 0.

I have problem running ctrl_fanspeed script It is caused by "missing" <sed> command. It looks to me, that there is no way I can run <sed> (streameditor) on DNS-323... How is that? You use this script without a problem, so what is wrong in my case?

When I try to run sed from within telnet (sed or ./sed), all I got is:

/mnt/HD_a2/lnx_bin/sh: ./sed: not found

sed doesn't seem to be listed anywhere in the system. Am I completely wrong or is there any other problem?

At the moment all I run is telnet (set up exactly as written in wiki - working without a problem), no other modifications, firmware rev. 1.02b. Any suggestions?

UPDATE: Well, I supposed that sed was a part of the system... Now I copied it manually (from the same archive as telnet files) to the disk and it is running fine. Sorry for that At least if someone comes to this problem too... But some other question - would you update the script so it kills the original fancontroll at the start? Sorry I'm not any good in scripting, so parsing ps command for "fancontrol", obtaining pid and killing it by this pid is out of my reach

Last edited by ondro727 (2007-02-15 03:37:48)

mig wrote:

ondro727 wrote:

UPDATE: ... But some other question - would you update the script so it kills the original fancontroll at the start? Sorry I'm not any good in scripting, so parsing ps command for "fancontrol", obtaining pid and killing it by this pid is out of my reach

I just came across this command which is useful to kill a process in a script on the DNS-323

#/bin/pidof

You call it with the argument of the name of a process and it returns the pid
You can add the following to the beginning of your script

Code:

#!/bin/sh

PID=$(/bin/pidof fancontrol)

if [ -n "$PID" ]
then
   kill -9 $PID
fi

//Mig

You can do it all on one line (it won't check if the PID is even there, it'll just try to kill it)

kill -9 `pidof fancontrol`

those are backwards ticks, on my keyboard it's the one above the 'tab' key.

I've said it before, but why don't you all get an inexpensive USB Key Drive(flash drive, €16/Gb) and put all your stuff there? Instructions to get it running are already in the wiki. The only thing you need on the HDD is a minimal fun_plug and the usb-storage.ko module.

/Apan