DNS-320

419 views
Skip to first unread message

m1ch4l

unread,
Mar 2, 2017, 12:46:01 PM3/2/17
to Alt-F
Hi.
I'll would like to install Alt-F on my DNS-320 rev. A for the first time. I have 2 questions: first, i have two 1 TB disks in RAID mirror, when i will upgrade stock firmware to Alt-F what will happend with data RAID ? Second question, do Alt-F supports Time Machine backup? If yes, where can i configure?

João Cardoso

unread,
Mar 3, 2017, 2:02:10 PM3/3/17
to Alt-F


On Thursday, 2 March 2017 17:46:01 UTC, m1ch4l wrote:
Hi.
I'll would like to install Alt-F on my DNS-320 rev. A for the first time. I have 2 questions: first, i have two 1 TB disks in RAID mirror, when i will upgrade stock firmware to Alt-F what will happend with data RAID ?

It will be used as found.
Eventually, depending on the fw version and filesystem type you are using, a lengly filesystem check will be done at first boot.
 
Second question, do Alt-F supports Time Machine backup? If yes, where can i configure?

If what you means is Time Machine as found on Macs, Alt-F has a 'natatalk' package for AFS (Apple File Sustem) that supports TM shares.
There are several other ways/packages for doing backups on the box.


m1ch4l

unread,
Mar 7, 2017, 1:55:12 PM3/7/17
to Alt-F
Thx for your answer João. Like i said earlier, i have two 1 TB disks in RAID 1. Could you tell me why in status page, on RAID area the first disc have capacity 0.5GB ? You can observe this on screen in attachment.
1.png

João Cardoso

unread,
Mar 7, 2017, 2:40:38 PM3/7/17
to Alt-F


On Tuesday, 7 March 2017 18:55:12 UTC, m1ch4l wrote:
Thx for your answer João. Like i said earlier, i have two 1 TB disks in RAID 1. Could you tell me why in status page, on RAID area the first disc have capacity 0.5GB ? You can observe this on screen in attachment.

That is a RAID device, not a disk, disks are in an upper section.
RAID devices (md0/1/2/...) are built from disk partitions (sda2/sdb3...), and on a RAID device a filesystem (ext2/3/4/NTFS/vfat) must be created. That's a filesystem that handles your data. Read the RAID, Filesystem, Partitioner online help (the (?) blue icon)

In your case, md0 is a RAID1 created by the D-Link firmware for swap/paging usage, when main memory is short. Alt-F just used what it found.
Alt-F uses disk partitions, normally sda1/sdb1, for swap, but it can handle swap created over RAID, that's OK.

If you are using Alt-F-0.1RC5 don't forget to apply the "network corruption fix"  posted in the forum top.

m1ch4l

unread,
Mar 11, 2017, 5:02:52 AM3/11/17
to al...@googlegroups.com
Ok, i understund. If i delete md0 and md1 and then i will create new RAID1, Alt-F also create swap in RAID 1 and i will have the same situation like now ? 0,5 GB for swap size is default ?

You mean this: 

There are evidences of network data corruption on RC5.
One such evidence is the empty Status page, but data corruption might occur while reading any file from the NAS.
All models (the DNS-321/323/320/320L/325) but the DNS-327L are affected.

Bill Rosenberg has found the culprit and you should take the necessary measures to avoid data loss/corruption on your box.
You can find and follow Bill's solution here

To apply it automatically, you have to:

1-install the Alt-F 'ethtool' package (Packages->Alt-F, if not yet installed select first the filesystem were to install)
2-create a "user boot script" that runs at boot time and executes the necessary command.
2-a) Go to Services->User, user Configure,
2-b) on the "Script to execute on powerup" specify a file name on the same filesystem where Alt-F packages were installed
  (such as /mnt/sda2/user.sh if Alt-F were installed in sda2, or /mnt/md0/user.sh if Alt-F were installed in md0, or /mnt/sda4... )
2-c) hit the "Edit" button and after the line

echo "Starting $0"

add the line

/Alt-F/usr/sbin/ethtool -K eth0 tso off

2-d) hit the Submit button.
2-e) After returning to the User Services page, hit the user StartNow button.
3-"Save Settings".

There is no need to reboot, although you want to do it to verify that the command is executed.
To verify that you have to ssh or telnet the box and login as the 'root' user, same password as the webUI, then issue the command

ethtool --show-offload eth0 | grep tcp-segmentation

which should be 'off'

This is the definitive fix and you MUST apply it.

João Cardoso

João Cardoso

unread,
Mar 11, 2017, 12:03:54 PM3/11/17
to Alt-F


On Saturday, 11 March 2017 10:02:52 UTC, m1ch4l wrote:
Ok, i understund. If i delete md0 and md1

You will loose all your data!
 
and then i will create new RAID1,
 
There are several ways of doing this, one of them if the Disk Wizard , which will reformat the disks.

Other is pinpointing the issue and change just that. I'm not sure what your issue really is, or if you just want a fresh start, not preserving your current data.

 
Alt-F also create swap in RAID 1 and i will have the same situation like now ?

There is *no* problem in having swap over raid1. If that is your only concern, leave it as is (*).
If swap that is your only concern, you can try Disk->utilities->Recreate Swap. That will stop the RAID device used for swap and will create a new swap on the same disk partition (sda1/sdb1). This will not change your data.
 
0,5 GB for swap size is default ?

About 0.5GB per 2TB disk capacity. 0.5GB is the minimum.

(*) swap over RAID1 is usually setup on RAID systems. With RAID, one disk can fail and your data is still available and online on the other disk. If swap is distributed over the two disks on a non-RAID setup, if one disk fails and swap is being used the system will crash and you will have to reboot the box.


You mean this: 

There are evidences of network data corruption on RC5.

Yes!

m1ch4l

unread,
Mar 26, 2017, 6:56:09 AM3/26/17
to Alt-F
João, thank you for comprehensive answer.
Today and log in to my NAS and there was for the first news area with listed news.log. Ho did this happen ?

2017-Mar-08 19:44:43 /pkgs/unstable/owncloud_7.0.15-1_arm.ipk
2017-Mar-08 19:45:46 /pkgs/unstable/Packages
2017-Mar-08 19:52:44 /Snapshots/2017-03-04/README.txt
2017-Mar-04 19:18:58 /Snapshots/2017-03-04/Simulator/qemu-zImage
2017-Mar-04 19:19:04 /Snapshots/2017-03-04/Simulator/qemu-rootfs.arm.sqall.xz
2017-Mar-04 19:19:16 /Snapshots/2017-03-04/Alt-F-0.1RC6-DUO-35LR.bin
2017-Mar-04 19:19:10 /Snapshots/2017-03-04/Alt-F-0.1RC6-DUO-35LR.sha1
2017-Mar-04 17:48:08 /Snapshots/2017-03-04/Simulator/README.txt
2017-Mar-04 17:48:22 /Snapshots/2017-03-04/Simulator/qemu-Alt-F.sh
2017-Mar-04 19:19:16 /Snapshots/2017-03-04/Alt-F-0.1RC6-DNS-327L-rev-Ax.bin
2017-Mar-04 19:19:10 /Snapshots/2017-03-04/Alt-F-0.1RC6-DNS-327L-rev-Ax.sha1
2017-Mar-04 19:19:10 /Snapshots/2017-03-04/Alt-F-0.1RC6-DNS-325-rev-Ax.sha1
2017-Mar-04 19:19:17 /Snapshots/2017-03-04/Alt-F-0.1RC6-DNS-325-rev-Ax.bin
2017-Mar-04 19:19:16 /Snapshots/2017-03-04/Alt-F-0.1RC6-DNS-323-rev-AxBxCx.bin
2017-Mar-04 19:19:09 /Snapshots/2017-03-04/Alt-F-0.1RC6-DNS-323-rev-AxBxCx.sha1
2017-Mar-04 19:19:10 /Snapshots/2017-03-04/Alt-F-0.1RC6-DNS-321-rev-Ax.sha1
2017-Mar-04 19:19:16 /Snapshots/2017-03-04/Alt-F-0.1RC6-DNS-321-rev-Ax.bin
2017-Mar-04 19:19:17 /Snapshots/2017-03-04/Alt-F-0.1RC6-DNS-320L-rev-Ax.bin
2017-Mar-04 19:19:10 /Snapshots/2017-03-04/Alt-F-0.1RC6-DNS-320L-rev-Ax.sha1
2017-Mar-04 19:19:18 /Snapshots/2017-03-04/Alt-F-0.1RC6-DNS-320-rev-Bx.bin
2017-Mar-04 19:19:10 /Snapshots/2017-03-04/Alt-F-0.1RC6-DNS-320-rev-Bx.sha1
2017-Mar-04 19:19:17 /Snapshots/2017-03-04/Alt-F-0.1RC6-DNS-320-rev-Ax.bin
2017-Mar-04 19:19:10 /Snapshots/2017-03-04/Alt-F-0.1RC6-DNS-320-rev-Ax.sha1
2017-Mar-04 19:19:10 /Snapshots/2017-03-04/Alt-F-0.1RC6-CH3SNAS.sha1
2017-Mar-04 19:19:16 /Snapshots/2017-03-04/Alt-F-0.1RC6-CH3SNAS.bin
2017-Feb-20 19:40:10 /pkgs/unstable/hddtemp_0.3-beta15_arm.ipk
2017-Feb-11 17:08:00 /pkgs/unstable/inadyn-mt_02.28.10-1_arm.ipk
2017-Feb-10 19:40:30 /pkgs/unstable/slang_2.2.4_arm.ipk
2017-Feb-10 19:40:30 /pkgs/unstable/mc_4.8.1.6-2_arm.ipk
2016-Dec-30 18:00:08 /Releases/0.1RC5/README-0.1RC5.txt
2016-Nov-22 17:09:54 /pkgs/unstable/php_5.4.34-3_arm.ipk
2016-Nov-22 16:45:20 /pkgs/unstable/owncloud_7.0.15_arm.ipk
2016-Jul-04 15:58:00 /pkgs/unstable/python_2.7.2-5_arm.ipk
2016-Jul-04 15:30:24 /pkgs/unstable/pyopenssl_0.13_arm.ipk
2016-Jun-27 13:36:24 /pkgs/unstable/syncthing_0.13.9_arm.ipk
2016-Dec-30 18:02:32 WARNING: possible issue when upgrading firmware under RC3/RC4/RC4.1/RC5
2016-Jul-09 14:44:00 WARNING: Network data corruption on RC5
2016-Jun-25 18:17:51 Alt-F-0.1RC5 is released

João Cardoso

unread,
Mar 26, 2017, 10:49:23 AM3/26/17
to Alt-F


On Sunday, 26 March 2017 11:56:09 UTC+1, m1ch4l wrote:
João, thank you for comprehensive answer.
Today and log in to my NAS and there was for the first news area with listed news.log. Ho did this happen ?

sourceforge.net, the Alt-F download and repository site, keeps a RSS feed of the project news and file releases.
Alt-F reads and parses that RSS feed twice a week (Services->Network, News) and displays the news.

m1ch4l

unread,
May 4, 2018, 12:11:38 PM5/4/18
to al...@googlegroups.com
Hello, again João,

I have already upgraded my DNS-320 to the newest version of ALT-F. The whole process was fine but currently, I have a problem to configure netatalk. The directory I have typed in apf config is unavailable when I try to connect from my system.
Do you have some manual how to do it right?
I configured SMB and there everything is working fine.

Ok, I resolved the problem. It was the problem with permissions to apf.conf file. 
Can you tell me what is default permissions to this file after installation?

João Cardoso

unread,
May 6, 2018, 1:26:56 PM5/6/18
to Alt-F
After using the webUI Submit button it is

 -rw-r--r--    1 root     root           678 May  6 18:06 /etc/afp.conf

and it is working.
Notice that I don't any Apple computer, I only tested the netatalk server with 'afpcmd' on linux

m1ch4l

unread,
May 6, 2018, 2:44:28 PM5/6/18
to Alt-F
Ok, thx :) Now everything is working fine :)
Reply all
Reply to author
Forward
0 new messages