Supported NAS


Recommended Posts

You need to setup folders on one of your devices. Create a folder on your pc than add this also on the NAS, sync will start.

i can't sync my nas.  i setup  (NAS->PC->android) then  (PC->NAS-Android) ....   android && pc works greate together.

but NAS don't see them  and when i have only NAS+Android  (no online devices).. :(

what do i need to do ? i changed Router port forwarding, but i'm in local.. so normaly i don't need it.

Link to comment
Share on other sites

I tried BT Sync on my Synology DS112j with no success. I used the http://www.synocommunity.com/ repository and installed the package. As soon as I execute the application, my whole NAS grinds to a halt. The network shares, the DSM web interface and all other applications stop working or become very slow. I can see the BT Sync webinterface, but it doesn't work. I can't click the buttons etc.

 

Edit: I own a DS112j. Not a DS211j...

Link to comment
Share on other sites

Greate news.

 

After updating btsync to 1.1.82, on my Zyxel NSA320,  everithing works greate.

i think i had sync issues because an old version 1.0.134.

 

-- Update procedure: just downloaded new verion from official website, after unTar an replace current btsync file (in /usr/local/zy-pkgs/bin ) by new one, chmod 775.

 

hope the creator of offial package will update it too

Link to comment
Share on other sites

I wonder if the Iomega ix2 works, will the cloud-enabled ix4 work, too?

 

I ask because the four-bay ix4 is on sale diskless for $169:

 

http://www.tigerdirect.com/applications/SearchTools/item-details.asp?EdpNo=8511568&srkey=LCU-101759656

 

I can confirm that It works with the ix4-300d.  It's running on mine.  See the next post.

 

Right now, I'm torture-testing it with a 74,000 files, 176GB sync (ver 1.1.82 running on Win7-64, and 1.1.70 on the ix4).   It stalled the first time I tried it; likely because I did something wrong.  I deleted both sync-folder entries (on the NAS and on my PC) then created a new sync folder entry on my PC's BTSync (so it's the Master), then on the NAS (pasting in the Secret key).  It's now indexing as expected.

 

Jovik's clear instructions worked perfectly.  It needs to be noted, however, that simply enabling SSH access to the ix4-300d will void your warranty - this is per Lenovo (even if the problem is that the power supply blew up because of a bad capacitor, I suppose).  So make sure your ix4 is all working fine before you go poking in there.

 

Bonus: the BTSync folders are stored in non-public-facing folders and are thus invisible to the (created via the EMC 'Shares' utility) 'normal' browseable shared folders.

 

It's also good to know that you can disable the EMC/Easyshare's annoying/rude "I'll map that Share to a drive letter of MY choice" feature by right-clicking on the EMC icon in the System Tray and unchecking 'Map Drive Letters'.

Link to comment
Share on other sites

Hmm, it's not working: it got through the indexing, then it created a whack of folders in the ix4's BTSync folder, it transfered about 24MB of files, then it stopped.   Could it be because I don't have a port open for the ix4 on my router?  I'm only syncing folders on the LAN for now (I've unchecked Use Relay Server and Use Tracker Server).   I'll have to investigate and report back. 
 
I can report something odd: if I log onto BTSync on the ix4 (via my-ip:8888/gui/en/index.html), then click on Folder Preferences, the tabs are reversed (see below): the General tab shows 'Advanced' settings and the General tab shows the 'Secret' fields. 

The reverse of how it behaves/appears on the PC.  BTSync on the ix4 is version 1.1.70.

 

post-34986-0-14738900-1381801836_thumb.p

 

 

Edited to add: I'm giving up on the ix4-300d - it's a very disappointing NAS. 

 

I've ordered a Thecus N5550 - the company is a lot more hacker-friendly, and per their forum, BTSync works on it - see their third Party Modules discussion topic.  Once I can confirm it works, I'll report back. (It works!  See my post later on.)

Link to comment
Share on other sites

Hi,

I could install on Zyxel NSA310 (search the topic, it is documented) but on reboot I loose all my folders, what file should be writeable to save settings?

Thanks

Gabor

Similar problem on iomega ix2-200: I copy the executable to root and run it, but after a NAS reboot, the file (and its settings file) are gone. Apparently iomega's startup code rejects foreign bodies! Anybody know how to hack around this? 

Link to comment
Share on other sites

  • 3 weeks later...
  • 2 weeks later...

Based on the work of eseelke, erkr and others I was able to get btsync installed on a Zyxel NSA320.

 

Make sure you already have FFP installed. http://zyxel.nas-central.org/wiki/FFP-stick

 

Download the latest version of btsync for ARM (version 1.1.70 at the moment), untar/unzip the tar.gz file, and then place btsync at /ffp/bin/btsync. If you downloaded the file to your local computer you can SCP it to the NAS:

scp btsync root@NSA320:/ffp/bin/

Create the /ffp/start/btsync.sh file:

#!/ffp/bin/sh# PROVIDE: btsync# REQUIRE: LOGIN. /ffp/etc/ffp.subrname="btsync"command="/ffp/bin/btsync"btsync_flags="--config /ffp/etc/btsync.conf"required_files="/ffp/etc/btsync.conf"run_rc_command "$1"

Then set the start script to be executable:

chmod u+x /ffp/start/btsync.sh 

The default config file can be installed by:

/ffp/bin/btsync --dump-sample-config > /ffp/etc/btsync.conf

I recommend that you modify the config to move the btsync storage path out of the FFP root and onto one of your drives. The storage path will contain things like the sync.log which can get large and is accessed a lot, so a USB stick might not be the best place for it.

"storage_path" : "/i-data/md0/.btsync"

I ran into the unreachable web UI and 100% CPU issue that some people are reporting. What I found is that if you change the web UI port to something other than 8888, such as 8080, then this issue goes away. I'm not sure why port 8888 is unavailable on my NAS, but it appears that if btsync can't listen on the port, it gets into a loop that eats the CPU.

 

Thanks for the great tutorial but I am still a little struggeling following it. The stick with the ffb runs fine on my NSA320. creatting the SSH and accessing the NSA320 via SSH (using Putty) works fine. But with the next step I got stuck. I downloaded the latest ARM package from btsync, unzip and untar it with 7zip and wanted create the folder btsync in the /ffp/bin directory. I used WINSCP and always receice the error message:

 

Permission denied.

Error code: 3

Error message from server: Permission denied

Request code: 14

 

even copying the file directly to the /ffp/bin directory  results in an error message:

 

Permission denied.

Error code: 3

Error message from server: Permission denied

Request code: 14

 

can anybody help me how to proceed? Sorry I am not experienced at all with the prompt line tool (windows user :-)  )

 

Thanks for your help!

Link to comment
Share on other sites

Thanks, With this info I easily got version 1.1.48 running on my NSA325 (Zyxel)

I only changed /ffp/start/btsync.sh to support start, status and stop:

#!/ffp/bin/sh. /ffp/etc/ffp.subrcommand="/ffp/bin/btsync"run_rc_command "$1"
Thanks

 

Hello I'm trying to put it (bitorrent sync) in a nsa310, but I can not open that ffpstick me telnet access, anyone could explain the steps in great detail. For more I read I do not get it wrong.
 
Greetings and sorry for automatic translation to English

 

Hola estoy intentando poner bitorrent sync en un nsa310, pero no logro que ffpstick me abra el acceso telnet, Alguien podría explicarme los pasos de forma muy detallada. Por mas que leo no entiendo que hago mal.

 

Saludos y perdón por la traducción automática al ingles

Link to comment
Share on other sites

here ffpboot.log, in the other things the last thing : "ping: bad address 'ffp.inreto.de'" the nas have internet conection and not firewalk actived in the router.  can help me?

 

 

thanks.

 

 

Rotating logfiles...

Script fun_plug.sh version 20131124 running from /mnt/parnerkey

ffpstick started at Tue Nov 26 13:00:46 UTC 2013

Try to determine NAS type...

according to /zyxel/mnt/info/modelid: A203->NSA310_ZyXEL

type NSA310_ZyXEL, fw V4.62(AFK.0)

Find the current usb device...usb device is /dev/sdb1 on device /dev/sdb

Check for filesystem...Filesystem is vfat

Check /dev/sdb for number of partitions.../dev/sdb has 1 partitions

Will have to repartition

Copy files to ramdisk...

Copied usb_key_func.sh nsa210_check_file md5sum nsa220_check_file NSA221_check_file salted_md5sum nsa310_check_file_C0 salted_md5sum_3x0 STG100_check_file STG211_check_file STG212_check_file mkdosfs after_booting.sh rootfs.tgz fun_plug.sh

Script fun_plug.sh version 20131124 running from /tmp/.ffpstick

Repartition /dev/sdb

unmount /mnt/parnerkey...done

Repartitioning...

 

The number of cylinders for this disk is set to 10112.

There is nothing wrong with that, but this is larger than 1024,

and could in certain setups cause problems with:

1) software that runs at boot time (e.g., old versions of LILO)

2) booting and partitioning software from other OSs

   (e.g., DOS FDISK, OS/2 FDISK)

 

Command (m for help): Building a new DOS disklabel with disk identifier 0x22662f23.

Changes will remain in memory only, until you decide to write them.

After that, of course, the previous content won't be recoverable.

 

 

The number of cylinders for this disk is set to 10112.

There is nothing wrong with that, but this is larger than 1024,

and could in certain setups cause problems with:

1) software that runs at boot time (e.g., old versions of LILO)

2) booting and partitioning software from other OSs

   (e.g., DOS FDISK, OS/2 FDISK)

Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite)

 

Command (m for help): Command action

   e   extended

   p   primary partition (1-4)

Partition number (1-4): First cylinder (1-10112, default 1): Using default value 1

Last cylinder, +cylinders or +size{K,M,G} (1-10112, default 10112): 

Command (m for help): Command action

   e   extended

   p   primary partition (1-4)

Partition number (1-4): First cylinder (336-10112, default 336): Using default value 336

Last cylinder, +cylinders or +size{K,M,G} (336-10112, default 10112): Using default value 10112

 

Command (m for help): Partition number (1-4): Hex code (type L to list codes): Changed system type of partition 1 to 4 (FAT16 <32M)

 

Command (m for help): The partition table has been altered!

 

Calling ioctl() to re-read partition table.

 

WARNING: If you have created or modified any DOS 6.x

partitions, please see the fdisk manual page for additional

information.

Syncing disks.

Done. Creating and mounting filesystems...

Create ext3 filesystem on /dev/sdb2 and mount...

Filesystem label=FFPROOT

OS type: Linux

Block size=1024 (log=0)

Fragment size=1024 (log=0)

119888 inodes, 479073 blocks

23953 blocks (5%) reserved for the super user

First data block=1

Maximum filesystem blocks=524288

59 block groups

8192 blocks per group, 8192 fragments per group

2032 inodes per group

Superblock backups stored on blocks:

8193, 24577, 40961, 57345, 73729, 204801, 221185, 401409

Mount /dev/sdb2 on /mnt/parnerkey type ext3...mount: wrong fs type, bad option, bad superblock on /dev/sdb2,

       missing codepage or helper program, or other error

       In some cases useful info is found in syslog - try

       dmesg | tail  or so

 

 

Couldn't mount /dev/sdb2 on /mnt/parnerkey. Will retry in 3 seconds...mount: wrong fs type, bad option, bad superblock on /dev/sdb2,

       missing codepage or helper program, or other error

       In some cases useful info is found in syslog - try

       dmesg | tail  or so

 

 

Couldn't mount /dev/sdb2 on /mnt/parnerkey. Will retry in 3 seconds...mount: wrong fs type, bad option, bad superblock on /dev/sdb2,

       missing codepage or helper program, or other error

       In some cases useful info is found in syslog - try

       dmesg | tail  or so

 

 

Couldn't mount /dev/sdb2 on /mnt/parnerkey. Will retry in 3 seconds...mount: wrong fs type, bad option, bad superblock on /dev/sdb2,

       missing codepage or helper program, or other error

       In some cases useful info is found in syslog - try

       dmesg | tail  or so

 

 

Couldn't mount /dev/sdb2 on /mnt/parnerkey. Will retry in 3 seconds...mount: wrong fs type, bad option, bad superblock on /dev/sdb2,

       missing codepage or helper program, or other error

       In some cases useful info is found in syslog - try

       dmesg | tail  or so

 

 

Couldn't mount /dev/sdb2 on /mnt/parnerkey. Will retry in 3 seconds...mount: wrong fs type, bad option, bad superblock on /dev/sdb2,

       missing codepage or helper program, or other error

       In some cases useful info is found in syslog - try

       dmesg | tail  or so

 

 

giving up

Mount /dev/sdb2 on /mnt/parnerkey type ext2...done

Move files to ext3 partition...after_booting.sh...rootfs.tgz...done

Create dummy symlinks...done

Unmount /dev/sdb2...done

Create FAT filesystem on /dev/sdb1 and mount...mkdosfs 2.11 (12 Mar 2005)

Mount /dev/sdb1 on /mnt/parnerkey type vfat...done

Move files to vfat partition...usb_key_func.sh...nsa210_check_file...md5sum...nsa220_check_file...NSA221_check_file...salted_md5sum...nsa310_check_file_C0...salted_md5sum_3x0...STG100_check_file...STG211_check_file...STG212_check_file...mkdosfs...fun_plug.sh...done

...And calling the script on stick again...

Script fun_plug.sh version 20131124 running from /mnt/parnerkey

ffpstick started at Tue Nov 26 13:01:24 UTC 2013

Try to determine NAS type...

according to /zyxel/mnt/info/modelid: A203->NSA310_ZyXEL

type NSA310_ZyXEL, fw V4.62(AFK.0)

Find the current usb device...usb device is /dev/sdb1 on device /dev/sdb

Copy myself to /tmp...And execute...

/tmp/.ffpstick/fun_plug.sh BackgroundPolling -d /dev/sdb -n NSA310_ZyXEL -f "V4.62(AFK.0)" -r no -l &

Script fun_plug.sh version 20131124 running from /tmp/.ffpstick

Wait for the stick to be mounted again by the firmware...

Probe all mount points 0 seconds...

probe /proc/bus/usb...

probe /dev/pts...

probe /zyxel/mnt/nand...

probe /zyxel/mnt/sysdisk...

probe /lib/security...

probe /lib/modules...

probe /tmp/tmpfs...

probe /usr/local/etc...

probe /usr/local/var...

probe /etc/zyxel...

probe /i-data/8b907a2e...

No /anymountpoint/ffproot/after_booting.sh found

Probe all mount points 10 seconds...

probe /proc/bus/usb...

probe /dev/pts...

probe /zyxel/mnt/nand...

probe /zyxel/mnt/sysdisk...

probe /lib/security...

probe /lib/modules...

probe /tmp/tmpfs...

probe /usr/local/etc...

probe /usr/local/var...

probe /etc/zyxel...

probe /i-data/8b907a2e...

probe /e-data/5294-9BA4...

found ffpstick on /e-data/5294-9BA4, moving logfile

probe /usr/local/zy-pkgs...

probe /etc/zyxel/zy-pkgs...

probe /usr/local/apache/htdocs/adv,/pkg...

No /anymountpoint/ffproot/after_booting.sh found

Probe all mount points 20 seconds...

probe /proc/bus/usb...

probe /dev/pts...

probe /zyxel/mnt/nand...

probe /zyxel/mnt/sysdisk...

probe /lib/security...

probe /lib/modules...

probe /tmp/tmpfs...

probe /usr/local/etc...

probe /usr/local/var...

probe /etc/zyxel...

probe /i-data/8b907a2e...

probe /e-data/5294-9BA4...

probe /usr/local/zy-pkgs...

probe /etc/zyxel/zy-pkgs...

probe /usr/local/apache/htdocs/adv,/pkg...

probe /e-data/ea1a0c13-0076-4634-b624-735abc3922f6...

found ffproot on /e-data/ea1a0c13-0076-4634-b624-735abc3922f6/ffproot

probe /usr/local/apache/web_framework/data/cache...

probe /usr/local/apache/web_framework/data/config...

Starting /e-data/ea1a0c13-0076-4634-b624-735abc3922f6/ffproot/after_booting.sh version 20131124 at Tue Nov 26 14:02:18 GMT 2013...

Extract rootfs.tgz...Done

Which FFP version to use?

Is OABI supported?...yes. Is EABI supported?...yes, choosing FFP 0.7/arm

Will try to download fun_plug.tgz (version 0.7/arm)


If the script stops here, downloading the tarball from ffp.inreto.de failed.

You can try to get internet access for the NSA310_ZyXEL,

or copy fun_plug.tgz (case sensitive!) to the share containing ffproot.

It should be recognized and installed.

It is possible that you have to reboot the box before this share shows up.

ping ffp.inreto.de...

ping: bad address 'ffp.inreto.de'

ping: bad address 'ffp.inreto.de'

ping: bad address 'ffp.inreto.de'

ping: bad address 'ffp.inreto.de'
Link to comment
Share on other sites

  • 2 weeks later...

Hello everybody,

 

I can confirm that it works with Synology:

DS413 (PPC CPU, Glib Version 2.8)

DS211 (ARM CPU, Glib Version 2.5)

both DS installed via the packages.synocommunity.com.

 

It does not run on a Synology:

DS209+II  (PPC CPU, Glib 2.3.4)

I tried to install it to the DS209+II as well, but it didn't work.

The package won't start.

 

I tried the download package ppc, but it tell me that it needs Glib 2.4.

If somebody does know a way to install it on a DS209+II, i would be really happy, but i guess we need a ppc version from btsync with glib 2.3, like the x86 version.

 

Mats

I would Be very interested in a solution....

Link to comment
Share on other sites

We do have statically compiled libc, however it needs to be supported by OS. In this case OS does't support it. We will look to option to disable ionotify to support older versions. But it seems we will need support from you in testing all variations, since it we won't be able to test all combinations.

We do have statically compiled libc, however it needs to be supported by OS. In this case OS does't support it. We will look to option to disable ionotify to support older versions. But it seems we will need support from you in testing all variations, since it we won't be able to test all combinations.

It does not work on DS209+. Is there a chance to get a version which runs one day on ppc with glibc 2.3? That would bei so GREAT!

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.