Fixes for the DNS-320L

[João Cardoso]

This post is now obsoleted, as RC4.1 is now available and incorporates all fixes.

Read the README and execute the script before flashing RC4.1

This post will be updated as needed, stay tuned

Nov 13: Added section on user boot script:

  # make the poweroff command (and the webUI) shutdown the box

 # use <TAB> characters, not spaces, in the EOF section bellow, or just remove all indenting

Nov 25: added section to power-up the box automatically after a power fail/recovery cycle

Dec 8: fix power off code

Hi,

The Alt-F released firmware for the DNS-320L has same flaws, mainly because I didn't have one to try with.

Now that I have one, donated by Andreas Marsch, better support will be available, but it will take some time, as I'm not a fast runner.

With the help of several persistent users, namely Ronaldo Antoni, Henrik Bruening, Steven Samson and others, some issues have been corrected and fixes made available.

As the most productive topic (REPORTING STUFF: D-Link DNS 320L rev A3) has over 63 posts, I summarize here how to apply the fixes.

1-You have to download the dns320l.tar.gz file and extract it to disk using the following commands:

cd /mnt/<fs> # where <fs> can be sda2, sda4, md0,... it depends on your disk setup. To be used also in the next steps
echo -n "636c7cbec3cc770cf6fda3722dc17af6  dns320l.tar.gz" > dns320l.tar.gz.md5 # generate md5sum to verify download

wget -O dns320l.tar.gz https://groups.google.com/group/alt-f/attach/68d2937564df0add/dns320l.tar.gz?part=0.1

md5sum -c dns320l.tar.gz.md5 # must display "dns320l.tar.gz: OK"
mkdir dns320l-fixes
tar -C dns320l-fixes -xzf dns320l.tar.gz

2-You have then to create a script to execute at boot time and save it on the base of a filesystem root, such as /mnt/sda2/dns320l.sh.

Don't use MS-Win editors to edit it, or use only unix-compatible editors:

#!/bin/sh

# User script to be executed at boot time when the disk partition is detected and mounted

# UNTESTED, be sure you know what you are doing!

FIXDIR=/mnt/<fs>/dns320l-fixes # change <fs> for the same filesystem name you used in the previous step

case "$1" in

start)

board=$(cat /tmp/board)

if test "$board" != "DNS-320L-A1"; then exit 0; fi # this is only for the DNS-320L

# create power_led sys folder. Expect that files there will be created as needed.

mkdir -p /tmp/sys/power_led

# copy new sysctrl to /usr/sbin

rcsysctrl stop

cp $FIXDIR/sysctrl /usr/sbin

rcsysctrl start

# disable init from launching dns320-daemon, and terminate it

sed -i 's/\(.*dns320l-daemon.*\)/#\1/' /etc/inittab

kill -1 1

killall dns320l-daemon

cp $FIXDIR/dns320l-daemon /usr/sbin

# allow init to launch the dns320-daemon

sed -i 's/^[#]*[[:space:]]*\(.*dns320l-daemon.*\)/\1/' /etc/inittab

kill -1 1

# incorrect time at startup, update settings saved time

adjtime -restart

touch /tmp/settings_saved

# turn off USB led

if ! grep -q 'usb.*=' /etc/bay; then

echo 0 > /tmp/sys/usb2_led/brightness

fi

# make the poweroff command (and the webUI) shutdown the box

# use <TAB> characters, not spaces, in the EOF section bellow, or just remove all indenting

rm -f /sbin/poweroff

cat<<-EOF > /sbin/poweroff

#!/bin/sh

nohup rcall stop &

dns320l-daemon -x DeviceShutdown

busybox poweroff

EOF

chmod +x /sbin/poweroff

# power up the box after a power fail/recovery cycle

dns320l-daemon -x EnablePowerRecovery

;;

stop) : ;;

*) echo "$0 start|stop" ;;

esac

3-You then have to make the script executable by using the command

chmod +x /mnt/<fs>/dns320l.sh # replace <fs> with the filesystem used

4-You can test the script by executing the command

/mnt/<fs>/dns320l.sh start # replace <fs> with the filesystem used

5-If it works OK (watch the Status page and the System Log), you must activate the script using the webUI, going to Services->User, user, Configure, and fill in the "Script to execute on powerup:" entry with /mnt/<fs>/dns320l.sh, where again <fs> must be replaced

6-You now have to "save settings", System->Settings, Save Settings

7-To fully test it you have to reboot.

As you know, the box can't (yet) be powered-off using commands, you have to pull the power cord.

The following command enables doing that, but to be sure that the 15 seconds time window are enough to perform a clean shutdown, stop all services using the webUI (System->Utilities), before issuing the commands:

dns320l-daemon -x DeviceShutdown # powers-off the box within 15 seconds.  Be sure that filesystems are unmounted!
poweroff # depending on your system setup, this will hopefully perform a clean shutdown within the 15 seconds scheduled poweroff

Hope there is no inaccuracies.

Please report any issue,

João

[John Hamilton]

Just want to say thanks for this post.  I followed the other as well, but I get easily lost.  This is the same content, just a little cleaner.  Once again, thank you.

On Monday, 22 September 2014 10:41:49 UTC-3, João Cardoso wrote:

Hi,

The Alt-F released firmware for the DNS-320L has same flaws, mainly because I didn't have one to try with.

Now that I have one, donated by Andreas Marsch, better support will be available, but it will take some time, as I'm not a fast runner.

With the help of several persistent users, namely Ronaldo Antoni, Henrik Bruening, Steven Samson and others, some issues have been corrected and fixes made available.

As the most productive topic (REPORTING STUFF: D-Link DNS 320L rev A3) has over 63 posts, I summarize here how to apply the fixes.

1-You have to download the dns320l.tar.gz file and extract it to disk using the following commands:

cd /mnt/<fs> # where <fs> can be sda2, sda4, md0,... it depends on your disk setup. To be used also in the next steps

wget -O dns320l.tar.gz https://groups.google.com/group/alt-f/attach/68d2937564df0add/dns320l.tar.gz?part=0.1

mkdir dns320l-fixes
tar -C dns320l-fixes -xzf dns320l.tar.gz

2-You have then to download a script to execute at boot time and save it on the base of a filesystem root, such as /mnt/sda2/dns320l.sh.

An alternative slightly modified script that's easier to edit (don't use MS-Win editors to edit it, or use only unix-compatible editors):

#!/bin/sh

# User script to be executed at boot time when the disk partition is detected and mounted
# UNTESTED, be sure you know what you are doing!

FIXDIR=/mnt/<fs>/dns320l-fixes # change <fs> for the same filesystem name you used in the previous step

case "$1" in
    start)
        board=$(cat /tmp/board)
        if test "$board" != "DNS-320L-A1"; then exit 0; fi # this is only for the DNS-320L

        # create power_led sys folder. Expect that files there will be created as needed.
        mkdir -p /tmp/sys/power_led

        # copy new sysctrl to /usr/sbin
        rcsysctrl stop
        cp $FIXDIR/sysctrl /usr/sbin
        rcsysctrl start

        # disable init from launching dns320-daemon, and terminate it
        sed -i 's/\(.*dns320l-daemon.*\)/#\1/' /etc/inittab
        kill -1 1
        killall dns320l-daemon
        cp $FIXDIR/dns320l-daemon /usr/sbin

        # allow init to launch the dns320-daemon
        sed -i 's/^[#]*[[:space:]]*\(.*dns320l-daemon.*\)/\1/' /etc/inittab
        kill -1 1

        ;;
    stop) : ;;

    *) usage $0 "start|stop" ;;
esac

3-You then have to make the script executable by using the command

chmod +x  /mnt/<fs>/dns320l.sh # replace <fs> with the filesystem used

4-You can test the script by executing the command

/mnt/<fs>/dns320l.sh start # replace <fs> with the filesystem used

5-If it works OK (watch the Status page and the System Log), you must activate the script using the webUI, going to Services->User, user, Configure, and fill in the "Script to execute on powerup:" entry with /mnt/<fs>/dns320l.sh, where again <fs> must be replaced

6-You now have to "save settings", System->Settings, Save Settings

7-To fully test it you have to reboot.

As you know, the box can't (yet) be powered-off using commands, you have to pull the power cord. The following command enables doing that:

dns320l-daemon -x DeviceShutdown # powers-off the box within 15 seconds.  Be sure that filesystems are unmounted!
poweroff # depending on your system setup, this will hopefully perform a clean shutdown within the 15 seconds scheduled poweroff

[Rafael Ourique]

This is truly amazing João. I really thank you and all people that supported it.

May i ask, when you fully identify the 320l's peculiarities and implement the necessary changes/fixes, will it be uploaded as a "RC5"?

[João Cardoso]

On Sunday, September 28, 2014 7:10:46 AM UTC+1, Rafael Ourique wrote:

This is truly amazing João. I really thank you and all people that supported it.

May i ask, when you fully identify the 320l's peculiarities and implement the necessary changes/fixes, will it be uploaded as a "RC5"?

Probably as RC4.0.1 

[João Cardoso]

On Monday, September 22, 2014 2:41:49 PM UTC+1, João Cardoso wrote:

(...) 

As you know, the box can't (yet) be powered-off using commands, you have to pull the power cord.

The following command enables doing that, but to be sure that the 15 seconds time window are enough to perform a clean shutdown, stop all services using the webUI (System->Utilities), before issuing the commands:

dns320l-daemon -x DeviceShutdown # powers-off the box within 15 seconds.  Be sure that filesystems are unmounted!
poweroff # depending on your system setup, this will hopefully perform a clean shutdown within the 15 seconds scheduled poweroff

The following script will automate the procedure:

#!/bin/sh
nohup rcall stop &
dns320l-daemon -x DeviceShutdown
busybox poweroff

Just create a file, say /mnt/<fs>/dns320l-fixes/poweroff, make it executable using the command

chmod +x /mnt/<fs>/dns320l-fixes/poweroff

and invoke it as

/mnt/<fs>/dns320l-fixes/poweroff

where <fs> must again be replaced with the appropriate filesystem

Please test it and report back, so I will add it to the first "user" script post.

If it works, just copy it to /sbin/poweroff, and the standard 'poweroff' command and the webUI poweroff will also work.

It works on my DNS320L, but as it is full of modifications, I can't be sure that it is not working because of some other changes.

[Kjeld Vang Larsen]

Hi, 

thanks for the good work. 

I tried to install the Rc4 on the 320l but had to revert to the dlink firmware due to the shutdown. But just found your post on it. Will give it a new try. 

But another very annoying issue was the fan. It keeps switchings between 3000 (silent) and 6000 (noisy) rpms. I tried to change the tempure ture settings on the page, as well on systrl but without no changes. (As well did the settings for temperature seem quite buggy - changes were not saved. Have you noticed same behavior with the fan?

Many thanks, Regards, Kjeld

[João Cardoso]

Yes, the first post addresses most of these issues.

You also need to apply a fix for the sysctrl webUI (System->Utilities, Fixes)

 

Many thanks, Regards, Kjeld

[Kjeld Vang Larsen]

Great. I was not aware of the tread. Am a noob with the Google Groups, but it seems the issues have been solved. 

You mentioned you will compile a RC4.01 for the 320L in September with all the collected fixes. Is that just around to be released - should I wait a few more days, or should i go for the RC4 and patch that one instaed?

 

[João Cardoso]

On Wednesday, October 1, 2014 7:44:42 AM UTC+1, Kjeld Vang Larsen wrote:

Great. I was not aware of the tread. Am a noob with the Google Groups, but it seems the issues have been solved. 

You mentioned you will compile a RC4.01 for the 320L in September with all the collected fixes. Is that just around to be released - should I wait a few more days, or should i go for the RC4 and patch that one instaed?

I will made RC4.0.1, I just don't know when. I'm as free as Alt-F :-)

 

 

[Chris]

Hi,

I wanted report back since I'm running Alt-F 0.1RC4 on my DNS-320L Rev. A1.

My journey was going from stock dlink to fun_plug on usb drive to debian squeeze on usb drive finally to Alt-F. I have been following the development for quite some time and was pleased to read that the DNS-320L is now supported.

After adding a second drive a few days ago, i noticed that the system was acting up in terms of not being reachable via ssh and so on. Thats when i decided to try Alt-F.

I flashed the firmware file and followed all the instructions (package update, fixes, dns320l fixes). I then configured the samba, afp shares, time machine, transmission, nzbget the way i wanted it and was very pleased to have a working system. I also had a degraded raid 1 swap space which i corrected according to the instructions in another thread.

fyi: I have changed the stock fan with a 12v noctua fan, because noise of the stock fan drove me nuts. Alt-F seems to handle it quite well, since the fan can now go from off to low to high, which didn't work in the stock firmware from what i recall. i had to leave it on the setting low or high because the fan would not spin up from off state.

One thing i noticed is that it takes a quite i while until i can see the shares when connecting via afp. When i click on the nas icon in finder it takes about 10 seconds until i can see the folders (this was faster with stock firmware). This is just a tiny little thing and absolutely no problem, because then it is faster than stock. But i will check if i can find something in the OSX console and report back.

I am impressed how easy it was to set everything up. I usually like to edit config files manually, but it was very comfortable working with the webui and i think that is very handy for someone who doesn't really enjoy working in a terminal window.

From a users perspective i have all i currently want from my nas. Thank you very much for your work. I will try to report back and give feedback on stuff i come across.

[João Cardoso]

On Sunday, October 5, 2014 10:50:30 AM UTC+1, Chris wrote:

Hi,

I wanted report back since I'm running Alt-F 0.1RC4 on my DNS-320L Rev. A1.

My journey was going from stock dlink to fun_plug on usb drive to debian squeeze on usb drive finally to Alt-F. I have been following the development for quite some time and was pleased to read that the DNS-320L is now supported.

After adding a second drive a few days ago, i noticed that the system was acting up in terms of not being reachable via ssh and so on. Thats when i decided to try Alt-F.

I flashed the firmware file and followed all the instructions (package update, fixes, dns320l fixes). I then configured the samba, afp shares, time machine, transmission, nzbget the way i wanted it and was very pleased to have a working system. I also had a degraded raid 1 swap space which i corrected according to the instructions in another thread.

I'm doing some tests on the donated DNS320L that I now have (thanks Andreas), and found another D-Link idiosyncrasy: JBOD (linear "RAID") is setup on the disk MBR!!! (yes, !!!).

Using D-Link 1.04b fw I setup  a RAID1 using only part of the disk space and the remaining space as JBOD, and this is the result:

[root@dns325]# mdadm --examine --scan --verbose

ARRAY /dev/md0 level=raid1 num-devices=2 UUID=82ab3294:52362cfa:99e4564d:3c32c8b1

   devices=/dev/sdb1,/dev/sda1

ARRAY /dev/md1 level=raid1 num-devices=2 UUID=3e9d6bcf:d62e060a:46f5bc7e:d7015fde

   devices=/dev/sdb2,/dev/sda2

ARRAY /dev/md2 level=linear num-devices=2 UUID=9b9bb7a7:a23714f3:e53a7f69:4368ce15

   devices=/dev/sdb3,/dev/sdb,/dev/sda3,/dev/sda

So, there are two issues with 1.04b08:

1-swap devices over a RAID1 (if at least it was RAID0...) -- what a waste of resources!

2-metadata for JBOD on the device disk (not on a device partition)

Although it is OK to have RAID on whole disks, mixing device disks and device partitions on a RAID is not

WARNING: So, if you have a similar RAID configuration, Alt-F will not be able to auto-assemble *any* RAID devices.

 

fyi: I have changed the stock fan with a 12v noctua fan, because noise of the stock fan drove me nuts. Alt-F seems to handle it quite well, since the fan can now go from off to low to high, which didn't work in the stock firmware from what i recall. i had to leave it on the setting low or high because the fan would not spin up from off state.

One thing i noticed is that it takes a quite i while until i can see the shares when connecting via afp. When i click on the nas icon in finder it takes about 10 seconds until i can see the folders (this was faster with stock firmware).

I think that this should be related with the strong encryption required by afp.

For flash memory space reasons (for the DNS-323, which is the base reference) hardware cryptographic support is not built in the kernel, while for the DLink firmware it is. You might be able to fix this by installing the kernel-modules package and loading the mv_cesa (and possibly also the crypto_hash and/or cryptodev) kernel module.

If you try please let us know the outcome.

 

This is just a tiny little thing and absolutely no problem, because then it is faster than stock. But i will check if i can find something in the OSX console and report back.

I am impressed how easy it was to set everything up. I usually like to edit config files manually, but it was very comfortable working with the webui and i think that is very handy for someone who doesn't really enjoy working in a terminal window.

From a users perspective i have all i currently want from my nas. Thank you very much for your work. I will try to report back and give feedback on stuff i come across.

Thanks

 

[João Cardoso]

On Monday, November 10, 2014 7:19:13 PM UTC, João Cardoso wrote:

...

I'm doing some tests on the donated DNS320L that I now have (thanks Andreas), and found another D-Link idiosyncrasy: JBOD (linear "RAID") is setup on the disk MBR!!! (yes, !!!).

Using D-Link 1.04b fw I setup  a RAID1 using only part of the disk space and the remaining space as JBOD, and this is the result:

[root@dns325]# mdadm --examine --scan --verbose

ARRAY /dev/md0 level=raid1 num-devices=2 UUID=82ab3294:52362cfa:99e4564d:3c32c8b1

   devices=/dev/sdb1,/dev/sda1

ARRAY /dev/md1 level=raid1 num-devices=2 UUID=3e9d6bcf:d62e060a:46f5bc7e:d7015fde

   devices=/dev/sdb2,/dev/sda2

ARRAY /dev/md2 level=linear num-devices=2 UUID=9b9bb7a7:a23714f3:e53a7f69:4368ce15

   devices=/dev/sdb3,/dev/sdb,/dev/sda3,/dev/sda

So, there are two issues with 1.04b08:

1-swap devices over a RAID1 (if at least it was RAID0...) -- what a waste of resources!

To be fair, this setup is used on advanced setups. I don't think it to be valuable on a SOHO low end NAS.

 

2-metadata for JBOD on the device disk (not on a device partition)

Although it is OK to have RAID on whole disks, mixing device disks and device partitions on a RAID is not

WARNING: So, if you have a similar RAID configuration, Alt-F will not be able to auto-assemble *any* RAID devices.

After all it is not D-Link fault, it's a RAID 0.9 metadata issue, and only applies for a D-Link mixing of RAID0/1 plus JBOD. It does not applies to a RAID0 or RAID1 or JBOD only setup.

For Alt-F to be able to handle the RAID0/1 *plus* JBOD D-Link setup, the JBOD metadata has to be converted to the 1.0 metadata. I have used it and data was preserved in the process.

You have to use the following sequence of commands, taking note on the highlighted values:

/ # mdadm --examine --scan --verbose
ARRAY /dev/md0 level=raid1 num-devices=2 UUID=44f83028:4635ef5b:d51c328f:b7e8025d
   devices=/dev/sdb1,/dev/sda1
ARRAY /dev/md1 level=raid1 num-devices=2 UUID=c447c423:bb30a538:6ff37312:db663576
   devices=/dev/sdb2,/dev/sda2
ARRAY /dev/md2 level=linear num-devices=2 UUID=05451b74:a2ac4472:61af8284:9c1cdfd7
   devices=/dev/sdb3,/dev/sdb,/dev/sda3,/dev/sda

now the JBOD must be unmounted and stopped:

/# umount /dev/md2 # this will fail under Alt-F, as it is not mounted, but nonetheless...

/# mdadm --stop /dev/md2 # # this will fail under Alt-F, as md2 is not assembled, but nonetheless...

In the next command the sdb3, sda3 order and the uuid value has be the same as the one reported in the previous command.

/# mdadm --create /dev/md2 --uuid=05451b74:a2ac4472:61af8284:9c1cdfd7 -llinear -n2 -c64 --metadata=1.0 --assume-clean /dev/sdb3 dev/sda3

now the 'mdadm --examine --scan --verbose' command will not report the /dev/sda nor /dev/sdb devices and on the next Alt-F reboot (to simplify) Alt-F will auto-assemble all RAID devices and mount the filesystems on it, keeping all your previous data. Of course, doing a backup first is always recommended.

If you later want to go back to the D-Link firmware you have to unmount the filesystem, stop the RAID, and replace the last 'mdadm create' command with

/# mdadm --create /dev/md2 --uuid=05451b74:a2ac4472:61af8284:9c1cdfd7 -llinear -n2 -c64 --metadata=0.90 --assume-clean /dev/sdb3 dev/sda3

And the D-Link firmware will happily recognize and use it (if no other changes or folder removals have been made!). I have done it.

...

 

One thing i noticed is that it takes a quite i while until i can see the shares when connecting via afp. When i click on the nas icon in finder it takes about 10 seconds until i can see the folders (this was faster with stock firmware).

I think that this should be related with the strong encryption required by afp.

For flash memory space reasons (for the DNS-323, which is the base reference) hardware cryptographic support is not built in the kernel, while for the DLink firmware it is. You might be able to fix this by installing the kernel-modules package and loading the mv_cesa (and possibly also the crypto_hash and/or cryptodev) kernel module.

If you try please let us know the outcome.

correction: you don't need to install the kernel-modules package, for the 320/320L/325 it is already pre-installed.

[Yasen Atanasov]

Works for me.

[Rafael Ourique]

gathered my courage and tested the changes...

when i try to test the dns320l.sh it gives me a "not found" message, even if it's on the right place

Got a linux-oriented soul to mess with it and now i get /mnt/sda2/dns320l.sh: line 54: syntax error: unexpected end of file (expecting ";;")

this is starting to give me a headache

[João Cardoso]

On Tuesday, November 25, 2014 1:31:25 AM UTC, Rafael Ourique wrote:

gathered my courage and tested the changes...

when i try to test the dns320l.sh it gives me a "not found" message, even if it's on the right place

Got a linux-oriented soul to mess with it and now i get /mnt/sda2/dns320l.sh: line 54: syntax error: unexpected end of file (expecting ";;")

You are right. I have added a comment on the relevant code section. The issue is that "here documents" require tabs, not spaces, and I don't know how to paste <TAB> here (if at all possible):

   Here Documents

       This  type of redirection instructs the shell to read input from the current source until a

       line containing only delimiter (with no trailing blanks) is seen.  All of the lines read up

       to that point are then used as the standard input for a command.

       The format of here-documents is:

              <<[-]word

                      here-document

              delimiter

       (...)

       If the redirection operator is <<-, then all leading tab characters are stripped from input

       lines  and  the line containing delimiter.  This allows here-documents within shell scripts

       to be indented in a natural fashion.

[Andrew G]

The "cat<<-EOF > /sbin/poweroff" in /mnt/sda2/dns320l.sh wrecks the system because /sbin/poweroff is a symlink to the busybox binary, which is the actual file that gets overwritten. Need to delete the symlink first.

causes errors like:-
/mnt/sda2 # chmod +x /sbin/poweroff
/mnt/sda2/dns320l.sh: line 1: chmod: Exec format error
request_module: runaway loop modprobe binfmt-0000

On Monday, 22 September 2014 14:41:49 UTC+1, João Cardoso wrote:

        # make the poweroff command (and the webUI) shutdown the box

        # use <TAB> characters, not spaces, in the EOF section bellow, or just remove all indenting

        cat<<-EOF > /sbin/poweroff

            #!/bin/sh

            nohup rcall stop &

            dns320l-daemon -x DeviceShutdown

            busybox poweroff

        EOF

        chmod +x /sbin/poweroff

[João Cardoso]

On Sunday, December 7, 2014 7:01:48 AM UTC, Andrew G wrote:

The "cat<<-EOF > /sbin/poweroff" in /mnt/sda2/dns320l.sh wrecks the system because /sbin/poweroff is a symlink to the busybox binary, which is the actual file that gets overwritten. Need to delete the symlink first.

Thanks. fixed now

[Jose Manuel]

Hi Joao,

    I installed successfuly ALT-f firmware in my DNS320L-A3.

    Then follow the steps to install the dns320l.sh fixes.

    It runs correctly and finish OK, but in system log appears an error message:

Dec  9 20:24:22 DNS320L daemon.info sysctrl: signaled to quit, quiting
Dec  9 20:24:22 DNS320L daemon.info sysctrl: Starting
Dec  9 20:24:22 DNS320L daemon.info sysctrl: reading /etc/bay
Dec  9 20:24:22 DNS320L daemon.info sysctrl: reading /etc/misc.conf
Dec  9 20:24:22 DNS320L daemon.info sysctrl: reading /etc/sysctrl.conf
Dec  9 20:24:22 DNS320L daemon.info sysctrl: can't open /etc/sysctrl.conf: No such file or directory Using defaults
Dec  9 20:24:22 DNS320L daemon.info sysctrl: args.lo_fan=2000
Dec  9 20:24:22 DNS320L daemon.info sysctrl: args.hi_fan=5000
Dec  9 20:24:22 DNS320L daemon.info sysctrl: args.lo_temp=45
Dec  9 20:24:22 DNS320L daemon.info sysctrl: args.hi_temp=50

     I go to /etc directoryand the file that exists is sysctl.conf not sysctrl.conf

   

    Another thing is that de usb, right and left disk leds stays in orange permanently, ¿is that correct?.

    Sorry for my bad english.

    Thank you for the great job.

[João Cardoso]

On Tuesday, December 9, 2014 7:55:10 PM UTC, Jose Manuel wrote:

Hi Joao,

Olá José

 

    I installed successfuly ALT-f firmware in my DNS320L-A3.

DNS320L-A1/A2/A3 supported. Thanks for reporting.

    Then follow the steps to install the dns320l.sh fixes.

    It runs correctly and finish OK, but in system log appears an error message:

Dec  9 20:24:22 DNS320L daemon.info sysctrl: signaled to quit, quiting
Dec  9 20:24:22 DNS320L daemon.info sysctrl: Starting
Dec  9 20:24:22 DNS320L daemon.info sysctrl: reading /etc/bay
Dec  9 20:24:22 DNS320L daemon.info sysctrl: reading /etc/misc.conf
Dec  9 20:24:22 DNS320L daemon.info sysctrl: reading /etc/sysctrl.conf
Dec  9 20:24:22 DNS320L daemon.info sysctrl:can't open /etc/sysctrl.conf: No such file or directory Using defaults

That's normal, "using defaults". When you change it using Services->System->sysctrl, Configure it will be created and used.

Dec  9 20:24:22 DNS320L daemon.info sysctrl: args.lo_fan=2000
Dec  9 20:24:22 DNS320L daemon.info sysctrl: args.hi_fan=5000
Dec  9 20:24:22 DNS320L daemon.info sysctrl: args.lo_temp=45
Dec  9 20:24:22 DNS320L daemon.info sysctrl: args.hi_temp=50

     I go to /etc directoryand the file that exists is sysctl.conf not sysctrl.conf

   

    Another thing is that de usb, right and left disk leds stays in orange permanently, ¿is that correct?.

Not enough information. Add screenshots of the Status and RAID webUI.

If you had RAID setup with RAID1, that means a degraded RAID; if don't have RAID, then the issue is swap over RAID, recently covered in https://groups.google.com/d/msg/alt-f/_hBkZsOBOSU/OFRKqtZYpnEJ

[Jose Manuel]

Ok, i will configure sysctrl later.

About raid, i only have 1 disk 2tb formatted in vendors firmware.
I remember in status page appears 1 small RAID1 partition, but i think thats not to be important, now i can't put screenshots.
I will read the post that you menttioned and report results tomorrow.