This directory contains experimental firmware, it is advised to have a3.3V serial adapter on your box, in case anything does not runs OK.If you use them, please report back your experiences on the forum:
Attach the System Log and the System Configuration
(System->Utilities->View Logs) when reporting.
Only with your collaboration it is possible to fix any issue.
After successfully flashing Alt-F you can always revert back to thevendor's firmware by using Alt-F Firmware Upgrade page, that acceptsboth Alt-F and the vendor's firmware.-The Alt-F-0.1RC4-DNS-325.bin firmware file was tested and is running ona hardware rev-A1 box. See the box bottom label to know what hardwarerevision you have. If you test it on a rev-A2 board, please report back.-The Alt-F-0.1RC4-DNS-320.bin was *NOT TESTED*. It should work withminor issues on a rev-A1 board. See the box bottom label to know whathardware revision you have. The DNS-320 is similar to the DNS-325, andit is expected that the most important things, such as network and diskaccess, will work OK.-To use those files you have to use them as a normal vendor firmwareupgrade, i.e., use the box vendor's firmware upgrade page to apply(flash) them.-If you have any 'ffp' instalation, rename the 'ffp' folder to somethingelse before flashing, as it might conflicts with Alt-F. You can safelyinstall ffp later under Alt-F control.-You might want to read the How to Use Wiki, as those instructions also apply.
I installed it to my Rev A1 DNS-320 tonight and it seems to be flying along nicely.
I had some issues with chrome (Error was:- Unable to load the web page because the server sent no data. Error code: ERR_EMPTY_RESPONSE)
I will try and set up Plex next,
not sure whether to go fun_plug
or debian?
rcsysctrl stop
rm -f /tmp/sys/*_led
ln -sf "/sys/class/leds/dns320:blue:power" /tmp/sys/power_led
ln -sf "/sys/class/leds/dns320:orange:l_hdd" /tmp/sys/left_led
ln -sf "/sys/class/leds/dns320:orange:r_hdd" /tmp/sys/right_led
ln -sf "/sys/class/leds/dns320:orange:usb" /tmp/sys/usb_led
ln -sf "/sys/class/leds/dns320:blue:usb" /tmp/sys/usb2_led
echo 43000 > /tmp/sys/temp1_input
rcsysctrl start
echo 0 > /tmp/sys/pwm1 # turns fan off
echo 127 > /tmp/sys/pwm1 # fan at mid speed
echo 255 > /tmp/sys/pwm1 # fan at top speed
echo 43000 > /tmp/sys/temp1_input # sets sys temp to 43ºC, fan will turn according to Services->System->sysctrl, Configure
nanddump -ql 2048 /dev/mtd4 | grep -E '..(:..){5}'
Chris
[root@DNS-325]# rcsysctrl start
Starting sysctrl: OK.
[root@DNS-325]# rcsysctrl status
sysctrl stopped
Feb 14 09:31:47 DNS-325 daemon.info sysctrl: Starting Feb 14 09:31:47 DNS-325 daemon.info sysctrl: reading /etc/bay Feb 14 09:31:47 DNS-325 daemon.info sysctrl: reading /etc/misc.conf Feb 14 09:31:47 DNS-325 daemon.info sysctrl: reading /etc/sysctrl.conf Feb 14 09:31:47 DNS-325 daemon.info sysctrl: args.lo_fan=2000 Feb 14 09:31:47 DNS-325 daemon.info sysctrl: args.hi_fan=5000 Feb 14 09:31:47 DNS-325 daemon.info sysctrl: args.lo_temp=45 Feb 14 09:31:47 DNS-325 daemon.info sysctrl: args.hi_temp=50 Feb 14 09:31:47 DNS-325 daemon.info sysctrl: args.mail=1 Feb 14 09:31:47 DNS-325 daemon.info sysctrl: args.recovery=1 Feb 14 09:31:47 DNS-325 daemon.info sysctrl: args.fan_off_temp=38 Feb 14 09:31:47 DNS-325 daemon.info sysctrl: args.max_fan_speed=6000 Feb 14 09:31:47 DNS-325 daemon.info sysctrl: args.crit_temp=54 Feb 14 09:31:47 DNS-325 daemon.info sysctrl: args.warn_temp=52 Feb 14 09:31:47 DNS-325 daemon.info sysctrl: args.crit_temp_command="/sbin/poweroff" Feb 14 09:31:47 DNS-325 daemon.info sysctrl: args.warn_temp_command="(null)" Feb 14 09:31:47 DNS-325 daemon.info sysctrl: args.front_button_command1="/mnt/sda2/Public/RW/1st.sh" Feb 14 09:31:47 DNS-325 daemon.info sysctrl: args.front_button_command2="/mnt/sda2/Public/RW/2nd.sh" Feb 14 09:31:47 DNS-325 daemon.info sysctrl: args.back_button_command="/mnt/sda2/Public/RW/bk.sh" Feb 14 09:31:47 DNS-325 daemon.info sysctrl: sdb left rdwr=0 last=0 spindow=1200 power=1 Feb 14 09:31:47 DNS-325 daemon.info sysctrl: sda right rdwr=0 last=0 spindow=1200 power=1 Feb 14 09:31:47 DNS-325 daemon.info sysctrl: (null) (null) rdwr=0 last=0 spindow=1200 power=1 Feb 14 09:31:47 DNS-325 daemon.info sysctrl: open /tmp/sys/left_led/trigger: No such file or directory Feb 14 09:31:47 DNS-325 daemon.info sysctrl: open /tmp/sys/left_led/brightness: No such file or directory Feb 14 09:31:47 DNS-325 daemon.info sysctrl: open /tmp/sys/right_led/trigger: No such file or directory Feb 14 09:31:47 DNS-325 daemon.info sysctrl: open /tmp/sys/right_led/brightness: No such file or directory Feb 14 09:31:47 DNS-325 daemon.info sysctrl: open /tmp/sys/usb_led/trigger: No such file or directory Feb 14 09:31:47 DNS-325 daemon.info sysctrl: open /tmp/sys/usb_led/brightness: No such file or directory Feb 14 09:31:47 DNS-325 daemon.err sysctrl: open /tmp/sys/power_led/trigger: No such file or directory
[root@DNS-325]# ls /sys/class/leds/
dns320:blue:power dns320:blue:usb dns320:orange:l_hdd dns320:orange:r_hdd dns320:orange:usb
#!/bin/sh
rcsysctrl stop
rm -f /tmp/sys/*_led
ln -sf "/sys/class/leds/dns320:blue:power" /tmp/sys/power_led
ln -sf "/sys/class/leds/dns320:orange:l_hdd" /tmp/sys/left_led
ln -sf "/sys/class/leds/dns320:orange:r_hdd" /tmp/sys/right_led
ln -sf "/sys/class/leds/dns320:orange:usb" /tmp/sys/usb_led
ln -sf "/sys/class/leds/dns320:blue:usb" /tmp/sys/usb2_led
echo 43000 > /tmp/sys/temp1_input
rcsysctrl start
Starting sysctrl: OK.
[root@DNS-325]# rcsysctrl status
sysctrl running
Hello,
The first part resolved the "awk..." issue found on the status page. The MAC is returned, I did strip it from that log if you are wondering, I should have noted that. Added a startup script, as you mention. The fan is off (because of the next part I suspect). Using the commands, the fan control works manually. The buttons did not do anything, then I noticed the sysctrl service did not start:[root@DNS-325]# rcsysctrl start
Starting sysctrl: OK.
[root@DNS-325]# rcsysctrl status
sysctrl stopped
This is in the log:
Feb 14 09:31:47 DNS-325 daemon.info sysctrl: open /tmp/sys/left_led/trigger: No such file or directory Feb 14 09:31:47 DNS-325 daemon.info sysctrl: open /tmp/sys/left_led/brightness: No such file or directory Feb 14 09:31:47 DNS-325 daemon.info sysctrl: open /tmp/sys/right_led/trigger: No such file or directory Feb 14 09:31:47 DNS-325 daemon.info sysctrl: open /tmp/sys/right_led/brightness: No such file or directory Feb 14 09:31:47 DNS-325 daemon.info sysctrl: open /tmp/sys/usb_led/trigger: No such file or directory Feb 14 09:31:47 DNS-325 daemon.info sysctrl: open /tmp/sys/usb_led/brightness: No such file or directory Feb 14 09:31:47 DNS-325 daemon.err sysctrl: open /tmp/sys/power_led/trigger: No such file or directory
So looking the sym links were to nowhere. This looks like even I can fix it.[root@DNS-325]# ls /sys/class/leds/
dns320:blue:power dns320:blue:usb dns320:orange:l_hdd dns320:orange:r_hdd dns320:orange:usb
Now my startup script is:#!/bin/sh
rcsysctrl stop
rm -f /tmp/sys/*_led
ln -sf "/sys/class/leds/dns320:blue:power" /tmp/sys/power_led
ln -sf "/sys/class/leds/dns320:orange:l_hdd" /tmp/sys/left_led
ln -sf "/sys/class/leds/dns320:orange:r_hdd" /tmp/sys/right_led
ln -sf "/sys/class/leds/dns320:orange:usb" /tmp/sys/usb_led
ln -sf "/sys/class/leds/dns320:blue:usb" /tmp/sys/usb2_led
echo 43000 > /tmp/sys/temp1_input
rcsysctrl start
[root@DNS-320]# ./temp.sh -v
debug: f0 f0 d0 4 2 1e 0 0 0 0 0 0 0 d4 d4 d4
30
null::respawn:/usr/sbin/dns320-temp.sh
#!/bin/sh
#
# Jamie Lentil copyright and licence
# adapted by <your name>
one time init
while true; do
send request
read response
if error
logger -st dns320-temp "error/warning message"
exit # init will restart it. be sure script is foolproof, or init will turns crazy
fi
echo $((temp*1000)) > /tmp/sys/temp1_input
sleep 30 # sysctrl itself only reads temp every 30 seconds
done
Great!To use sub-second sleep, use 'usleep microseconds', e.g. 'usleep 100000'In order to have it running continuously, and be restarted automatically in case it terminates, add
null::respawn:/usr/sbin/dns320-temp.shto /etc/inittab (notice the name and directory change), then 'kill -1 1' to make 'init' launch that script.And the script must have a loop itself, something like
#!/bin/sh
#
# Jamie Lentil copyright and licence
# adapted by <your name>
one time init
while true; do
send request
read response
if error
logger -st dns320-temp "error/warning message"
exit # init will restart it. be sure script is foolproof, or init will turns crazy
fi
echo $((temp*1000)) > /tmp/sys/temp1_input
sleep 30 # sysctrl itself only reads temp every 30 seconds
done
Hi
If I wanted to replace a disk with a one of higher capacity, can data be transferred internally within the nas to the other disk?
HiThanks for making this work on dns 320, dlinks firmware was starting to get a bit stale, im not a Linux person so if this ever goes wrong im screwed. My thoughts are it seems great and the possibilities look endless but I do have a few issues.
It is very easy to start and stop services in the web interface by one click of the button and there are some critical services in there that would kill the functionality if accidently stopped so could there be a confirmation message on some of the critical services in system and networking?
packages are great but on the package screen it lists apps that can be updated and the offered update is the one in brackets and a version lower? if it is the other way around then for some reason the package does not update.
is the temperature algorithm right?
is there a way to get the alt f page visible using ddns from external? I almost have it but the web page says forbidden (password required) but does not prompt but the only port I forwarded was port 80 so perhaps port 443 as well?.
im not sure :-/ Anyway so far so good its a great bit of nas firmware and im well impressed.oh and this worked first time on 320 rev a with zero fannying on
If I wanted to replace a disk with a one of higher capacity, can data be transferred internally within the nas to the other disk?
is the temperature algorithm right?
It is very easy to start and stop services in the web interface by one click of the button and there are some critical services in there that would kill the functionality if accidently stopped so could there be a confirmation message on some of the critical services in system and networking?
If you are referring to inetd, I think that I have it fixed, i.e., even if boot-disabled it will be launched.And there are always a couple of fail-safe recovery methods, read the "sysctrl" online help (Services->System->sysctrl, Configure, hit the (?) icon.
oh and this worked first time on 320 rev a with zero fannying on
What do you mean with "zero fannying on"?
Hi,
Hi,I succesfully installed on a DNS-325 rev-A2 box. So far everything works great.
Hi,I succesfully installed on a DNS-325 rev-A2 box. So far everything works great.
Great! So the rev-A2 is also supported. Does everything works OK? Leds, buttons (front, USB back, recessed reset back), fan control, temperature reading...?Can you please attach the Kernel log? System->Utilities->View logs, Kernel log, hit the Download button at the bottom.It would be great if one could distinguish the rev-A1 from the rev-A2 -- do you know what the differences are? (I have a rev-A1)
You might be interested in reading the top-posted "Experimental Snapshot RC4 release for the DNS-320/321/323/325" topic.Thanks!Joao
I was able to pull the disks from my Alt-f DNS-323 and insert into the DNS-325 and it worked great.
Ah, nobody has yet reported success or failure for the DNS-321, and I will not release RC4 for it while I don't have feedback.
On Tuesday, March 18, 2014 6:36:25 PM UTC-4, João Cardoso wrote:Ah, nobody has yet reported success or failure for the DNS-321, and I will not release RC4 for it while I don't have feedback.Hi João,I had given some feedback on my 321 a few months back, but I'm available to do more testing
. I'd hate to have RC4 held up needlessly.
What can I do for you?
ApK
Revisiting the Plex topic, based on this link https://support.plex.tv/hc/en-us/articles/201373823 it looks like there is a version available for ARM processors - can this be revisited?
Note: Not all models from these manufacturers are supported. Please refer to the NAS Compatibility List for more detailed information.
-A link to the package homepage and to the source code download page.-If you only see downloads for specific systems, such as MS-windows, Mac, Debian, etc, but no source code to download, don't bother to make the request.