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

zero13th wrote:

hi Jcard, thanks for B7.

i want to report that some of config always revert back to default after restarting device

/etc/hosts
/etc/httpd.conf
/etc/samba/smb.conf
/etc/resolv.conf

is it normal? i must manually re-config httpd.conf and smb.conf if i want to access device from another ip segment
btw i'm using mikrotik rb750 router

That is not normal.

-flashed or reloaded Alt-F?
-Are you using dhcp? Those files are changed whenever a dhcp lease changes.
-Are these the only files that revert to defaults?  Can you change, say, /etc/sysctrl.conf (see below) and see if it survive reboots?
-Have you hand edited those files, and/or remove "strange" comments on them, like '#!#'?
-Of course, you remember saving settings when changing values, do you?

and  if harddisks on standby mode, is it possible to make fan stay off?
syslog attach.

thanks

The fan speed is dictated by the box temperature.

According to the log, the fan is stopping when the box temperature drops bellow 42ºC; but as soon as the fan stops, the temperature raises above 42ºC and the fan turns on again.

What you have to do is to rise the temperature at what the fan stops, say 42.5ºC or 43ºC. You have to try and error; your box temp is higher than mine,. you live in a hot country or have the room heating too high (I turn my fan off at 40ºC)

Go to Services->System->sysctrl->configure (changes will be saved in /etc/sysctrl.conf, that should be flash-saved)

zero13th wrote:

> -Are you using dhcp? Those files are changed whenever a dhcp lease changes.
yes, mikrotik as dhcp-server with 1 day leased time
thanks

A DHCP server sends a lot of information to its clients, not only the IP. You can see that info in the System Log, filtering with the string 'udhcpc'.

Given the supplied information, Alt-F has to update a certain number of files. Although care has been taken to only change the affected items, it is possible for others to be affected.
In order to diagnose the problem, I need to examine the file contents before and after they are updated.

Regarding the "Save Settings" reminder: it only states that certain predefined configuration files has been changed, not by content, but by date, i.e. the files were modified, even if its contents is the same.
E.g., when the IP lease sent by the DHCP server expires, a new one is requested, and most of the time the DHCP server sends the same IP, thus the files are updated, although its contents are the same.

So, be sure that file contents are changed.

Being a server, the DNS should have a static ip. This is considered good-practice.

If you want me to diagnose if the the changes made by Alt-F to the files are or not legitimate, please attach them after you modify them and after a DHCP lease change.

zero13th wrote:

in smb.conf, if adding extra shares, configuration survive when the device restarted, but when adding extra clients, the configuration is not survived
how the correct way to add extra clients?

ex:
10.1.1.0/24
10.1.2.0/24
10.1.3.0/24

You are referring to the 'hosts allow' directive? Yes, currently it is overwritten by the dhcp client script.
I can try to change that so only the first two fields are changed, keeping the others, such as in

   hosts allow = 127. 192.168.1.0/255.255.255.0 1.2.3.4/5 6.7.8.9/10

the 1.2.3.4/5 6.7.8.9/10 would be kept. Is that what you need/want? Really?

How do you go from B6 to B7 (not flashed)?

Still kind of new to this firmware. Will this break my chroot Debian Squeeze on USB?

krackpot wrote:

How do you go from B6 to B7 (not flashed)?

The same way you did to install B6?

Still kind of new to this firmware. Will this break my chroot Debian Squeeze on USB?

No, Alt-F does nothing to your disks unless you tel it to do so. By its own Alt-F only assembles existing RAID and check and mount existing filesystems.

And B7 has a Debian installer, that you can chroot or even execute natively (command line only).

jcard wrote:

What you have to do is to rise the temperature at what the fan stops, say 42.5ºC or 43ºC. You have to try and error; your box temp is higher than mine,. you live in a hot country or have the room heating too high (I turn my fan off at 40ºC)

Go to Services->System->sysctrl->configure (changes will be saved in /etc/sysctrl.conf, that should be flash-saved)

change low fan temp to 43ºC from yesterday until morning

--output omitted--
Apr  9 05:58:15 DNS-323 daemon.info sysctrl: temp=42.8     fan=0
Apr  9 06:01:15 DNS-323 daemon.info sysctrl: temp=43.2     fan=400
Apr  9 06:04:45 DNS-323 daemon.info sysctrl: temp=42.8     fan=0
Apr  9 06:07:15 DNS-323 daemon.info sysctrl: temp=43.2     fan=400
Apr  9 06:10:45 DNS-323 daemon.info sysctrl: temp=42.8     fan=0
Apr  9 06:13:15 DNS-323 daemon.info sysctrl: temp=43.2     fan=400
Apr  9 06:15:46 DNS-323 daemon.info sysctrl: temp=42.8     fan=0
Apr  9 06:19:16 DNS-323 daemon.info sysctrl: temp=43.2     fan=400
Apr  9 06:22:16 DNS-323 daemon.info sysctrl: temp=42.8     fan=0
Apr  9 06:25:16 DNS-323 daemon.info sysctrl: temp=43.2     fan=400
Apr  9 06:28:46 DNS-323 daemon.info sysctrl: temp=42.8     fan=0
Apr  9 06:31:46 DNS-323 daemon.info sysctrl: temp=43.2     fan=400
Apr  9 06:35:46 DNS-323 daemon.info sysctrl: temp=42.8     fan=0
Apr  9 06:38:17 DNS-323 daemon.info sysctrl: temp=43.2     fan=400
Apr  9 06:41:17 DNS-323 daemon.info sysctrl: temp=42.8     fan=0
Apr  9 06:44:47 DNS-323 daemon.info sysctrl: temp=43.2     fan=400

try to change low fan temp to 45ºC in the morning

Apr  9 07:46:52 DNS-323 daemon.info sysctrl: temp=44.1     fan=0
Apr  9 07:47:52 DNS-323 daemon.info sysctrl: temp=44.6     fan=0
Apr  9 07:48:22 DNS-323 daemon.info sysctrl: temp=44.8     fan=0
Apr  9 07:49:22 DNS-323 daemon.info sysctrl: temp=45.1     fan=400
Apr  9 07:51:27 DNS-323 daemon.info sysctrl: Putting right_dev disk (sda) into sleep
Apr  9 07:51:32 DNS-323 daemon.info sysctrl: right_dev disk (sda) standby
Apr  9 07:51:32 DNS-323 daemon.info sysctrl: Putting left_dev disk (sdb) into sleep
Apr  9 07:51:37 DNS-323 daemon.info sysctrl: left_dev disk (sdb) standby
--output omitted--
Apr  9 08:18:23 DNS-323 daemon.info sysctrl: temp=44.8     fan=0
Apr  9 08:20:23 DNS-323 daemon.info sysctrl: temp=45.2     fan=400
Apr  9 08:26:24 DNS-323 daemon.info sysctrl: temp=44.8     fan=0
Apr  9 08:28:54 DNS-323 daemon.info sysctrl: temp=45.2     fan=400
Apr  9 08:34:54 DNS-323 daemon.info sysctrl: temp=44.8     fan=0
Apr  9 08:37:24 DNS-323 daemon.info sysctrl: temp=45.2     fan=400
Apr  9 08:41:54 DNS-323 daemon.info sysctrl: temp=44.8     fan=0
Apr  9 08:44:24 DNS-323 daemon.info sysctrl: temp=45.2     fan=400
Apr  9 08:49:25 DNS-323 daemon.info sysctrl: temp=44.8     fan=0
Apr  9 08:51:55 DNS-323 daemon.info sysctrl: temp=45.2     fan=400

The location of device is in my room with air conditioned environment, but the rising of the temperature seems endlessly.
I do not dare to change the temperature exceeds that, I'm afraid my hard drive will be damaged by high temperatures.
Is it possible to make if there are conditions when all hard drives in a standby position in a period of more than 30 or 60 minutes, the fan will stop spinning, and will start spinning if one hard drive out of standby?
I think eventually the device temperature will go down by itself because the air-conditioned environment

Last edited by zero13th (2011-04-09 06:47:24)

jcard wrote:

krackpot wrote:

How do you go from B6 to B7 (not flashed)?

The same way you did to install B6?

Still kind of new to this firmware. Will this break my chroot Debian Squeeze on USB?

No, Alt-F does nothing to your disks unless you tel it to do so. By its own Alt-F only assembles existing RAID and check and mount existing filesystems.

And B7 has a Debian installer, that you can chroot or even execute natively (command line only).

Thanks for the reply jcard!

I will try out the B7 firmware soon. I should have read the documentation on your changelog/announcement the other day which tells me how to do this. Was too tired from work

I am really excited to try out the Debian installer!

Hi Jcard,

the conditions are:
setting sysctrl fan off temp to 38ºC,
all disks standby,
air-conditioned room,
open the front case of the box,
services that running only inetd:
-swat
-printer
-telnet
+samba
no alt-f, ffp, debian.

i touched the disks, it felt cool
but fan still like this:

Apr 10 16:53:08 DNS-323 daemon.info sysctrl: temp=37.8     fan=0
Apr 10 16:53:38 DNS-323 daemon.info sysctrl: temp=38.2     fan=400
Apr 10 16:57:38 DNS-323 daemon.info sysctrl: temp=37.8     fan=0
Apr 10 16:58:08 DNS-323 daemon.info sysctrl: temp=38.2     fan=400
---output omitted---
Apr 10 18:22:39 DNS-323 daemon.info sysctrl: temp=38.2     fan=400
Apr 10 18:23:39 DNS-323 daemon.info sysctrl: temp=37.8     fan=0
Apr 10 18:24:09 DNS-323 daemon.info sysctrl: temp=38.2     fan=400
Apr 10 18:25:09 DNS-323 daemon.info sysctrl: temp=37.8     fan=0

my questions:
is it only my rev.C1 box like this? or all rev.C1 box like this?

but if you say it's not safe and would be pointless then.. what else can i say
thanks anyway

zero13th

zero13th wrote:

Hi Jcard,

the conditions are:
setting sysctrl fan off temp to 38ºC,
all disks standby,
air-conditioned room,
open the front case of the box,
services that running only inetd:
-swat
-printer
-telnet
+samba
no alt-f, ffp, debian.

i touched the disks, it felt cool
but fan still like this:

Apr 10 16:53:08 DNS-323 daemon.info sysctrl: temp=37.8     fan=0
Apr 10 16:53:38 DNS-323 daemon.info sysctrl: temp=38.2     fan=400
Apr 10 16:57:38 DNS-323 daemon.info sysctrl: temp=37.8     fan=0
Apr 10 16:58:08 DNS-323 daemon.info sysctrl: temp=38.2     fan=400
---output omitted---
Apr 10 18:22:39 DNS-323 daemon.info sysctrl: temp=38.2     fan=400
Apr 10 18:23:39 DNS-323 daemon.info sysctrl: temp=37.8     fan=0
Apr 10 18:24:09 DNS-323 daemon.info sysctrl: temp=38.2     fan=400
Apr 10 18:25:09 DNS-323 daemon.info sysctrl: temp=37.8     fan=0

my questions:
is it only my rev.C1 box like this? or all rev.C1 box like this?

but if you say it's not safe and would be pointless then.. what else can i say
thanks anyway

zero13th

Someone has measure the DNS electric power consummation, and found that even with the two disks in standby 7 Watts are being consumed.
Most of this electric power is converted to heat, and that makes the box temperature rise.
With the fan stopped,  some of the generated heat is dissipated through the box case, and eventually the temperature will stop rising and will stabilize in a value that depends on ambient temperature.
If the value at which the temperature stops rising is low enough for the disk health, the fan can be kept off, otherwise the fan must be turned on.

The fan role is to exhaust most of the heat from the box, preventing the temperature to rise. To exhaust heat, the fan must circulate fresh air through the heat-generating components; this means that the air intakes and outtakes must be wide enough and unobstructed, it is not enough to have the fan running.

From your logs, you can observe that: the temperature rises, the fan turns on and as a consequence the temperature drops, then the fan turns off. Perhaps a hysteresis could be added, e.g., the fan would turn on only when the temperature raises 1ºC above the setpoint, and would stop only when the temperature drops 1ºC bellow the setpoint. But that would not avoid the constant turn-on/off, it would only be more spaced in time.

During the winter, my box temperature drops to 37/38 ºC, with the fan turned off. Last night (Spring) the lower value was 39.7 ºC, and the fan didn't turn off during all night.

Its Sunday, sorry for the lecture

PS-Notice that the box hardware sensors report temperatures with a 1ºC resolution, the decimal values you see are the result of a running average.

tinybilbo wrote:

Hi,
Is there any way to autostart (on boot) the install of debian squeeze, either chroot or reloaded?

No, only start an user supplied script:
Services->User->user->Configure->"Script to execute on powerup"

tinybilbo wrote:

hi,
whats the command to (re)load the debian install from the command line?
(something like "kexec -l /mnt/sdc2/boot/vmlinuz-2.6.32-5-orion5x --initrd=/mnt/sdc2/boot/initr
d.img-2.6.32-5-orion5x \ --command-line="console=ttyS0,115200" && kexec -e")
Thanks

Inglisgh is not my mother language. From your's

> autostart (on boot) the install of debian squeeze

I understood that you want to *start installing* Debian on boot

What you propose is not a good idea, as a clean Alt-F shutdown will not be made and filesystems will be left dirty. That was one of the main motivations for Alt-F -- to not do unclean shutdowns.

Starting Debian is not like starting your preferred program, an OS has to be cleanly shutdown and a new one started.

BTY, there seems to exists some Debian install and kexec issues, take a look at
https://groups.google.com/forum/?fromgr … 92hvMTy6Ik

Question for faq

After flash and basic install i formatted both disks as md0 raid-1 ext4. After that the system resynced the md0 for more than 30 minutes, empty disks. Normal or crazy behaviour?

hi

im having trouble loacating and accessing my dlink after b7 install

i was running b6 (on top) and i just installed (on top) b7, now i may have used used the old fun_plug not sure now, wasnt paying enough attention i guess

with b6 i had set a static ip of 192.168.1.11  and now that ip reveals nothing, cant see dlink in network map either (win7)

i believe it worked, as the LED looks like it used to and holding the power button gives the orange blink on one then other drive

but for the life of me i cant reconnect to it. also i have HEAPS of data still on drive that i dont really wanna lose.

also reason i went to alt-f is original firmware was playing up so i dont really wanna have to rely on that cause dont know how it will work after all this time

any help would be much appreciated. side note: i am a beginner at this linux stuff

Thanks

RellikZephyr