• Content Count

  • Joined

  • Last visited

About richard-bt

  • Rank
    Sync Team

Profile Information

  • Gender
    Not Telling
  1. kreischweide, does the x86 package work correctly on that NAS? I think you're correct that "Most consumer grade QNAP systems work with the x86 packages only". I think it is only the higher end QNAP NAS supporting > 4 GB of RAM which will work with the x86_64 package.
  2. Thank you for reporting Alex. I've pulled the qoriq build form the KB article until we determine the possibility of a fix for qoriq.
  3. Updated packages for 2.0.85 for QNAP have been posted: If you already installed 2.0.85, please re-install with the latest package. This should resolve the issues having to do with 2.0 folders not being synced. If the x86_64 QNAP packages are still not starting - can someone please SSH in to the NAS as admin, and send me the results of running the commands "/etc/init.d/ stop" and "/etc/init.d/ start"?
  4. The Synology package uses the glibc23 binary, so no worries on Synology being overlooked. You should try the 2.0.85 below. @All - Download links for 2.0.85 for Synology have been updated: This should resolve the issue where 2.0 folders were not syncing. If you already installed 2.0.85, please re-install with this latest version. If anyone can confirm that the issue is resolved for avotron, bromolow, cedarview, or evansport - this would be greatly appreciated.
  5. Thanks for testing! With the release of Sync 2.0, the latest resource for installing Sync on your Drobo is available on the help site.
  6. Howdy MrTorrent, I'm guessing that you were upgrading an existing install from 1.4? Are there any messages within the NAS's notification area? If you're able to SSH in to the NAS as admin, what are the results of running the command "/etc/init.d/ stop" and "/etc/init.d/ start"? Thanks, Richard
  7. progers885, > why not just do it for those who have already... We can't justify the extra engineering and maintenance costs for a specially built binary just for these users; especially when our efforts are so focused on Sync 2.0. While "not terribly difficult" it's still no small amount of work. We do regularly review our options for NAS; and as soon as the support for applications on the single drive My Cloud improves I suspect it'll be a forerunning option. studdmufin, > So am i correct in saying that you guys are working on getting it into the WD app store for the ex2/ex4 models? and hopefully have that at launch of 2.0? Packages of Sync 2.0 for the EX2/EX4 should be available on our download page at launch. > is the ex4 kernel actually a 64k/4k kernel or are you referencing that you want an app store for the other my cloud units Both. I would like an app store available on all of the My Cloud devices because that would allow a user to install Sync with an easy point-and-click interface. With the firmware I used a few weeks ago, the EX2/EX4 kernels were indeed hybrid 64k/4k allowing for our regular ARM binary to work. The only catch was that the EX4 needed to have /proc/cpu/alignment set to 2 ("fixup"). On EX4 the alignment wasn't set to fixup while the same firmware version for the EX2 was set to fixup. You may want to consider scripting setting alignment 2 fixup when starting Sync because it will revert to the stock setting when your NAS restarts. If you wanted to install Sync yourself on your EX4 with SSH, I think it'd be possible. It has been some weeks, though, since I last tried so I can't be 100% sure that all this is still the case.
  8. Mogarick, unfortunately we're stuck between a rock and a hard place. I think there may have been some confusion in conveying what we will support because "My Cloud" is a term which applies to multiple products: some of which we hope to support and some which we are unable to support. That Sync worked sideloaded on the single drive My Cloud when it first shipped, and that a later firmware update broke compatibility for all sideloaded applications is certainly frustrating for all of us. For the single drive My Cloud, it falls into the category of unable to support largely for two reasons: Lack of a built-in app store for easy installation - the install process for Sync should not require SSH64k kernel memory alignment - requires custom building the Sync binaryWe're happy to provide an off-the-shelf ARM binary for users to install themselves because that one ARM binary can be run on many different platforms. While cross compiling Sync just for My Cloud 64k alignment shouldn't be terribly difficult, that effort doesn't make sense if the only WD owners that'll be able to use Sync are those skilled enough to use SSH. As more than the 64k problem, lack of an app store is the bigger blocker for us. QNAP, Netgear, and Seagate support are possible because they have an app store. Overland Storage including Sync in their firmware is possible because we have a business relationship with them. Unfortunately WD neither has an app store nor do we have a business relationship with them. I specifically used the words "at launch" because I did not want to exclude the possibility of supporting this device later. I do hope that WD implements an app store and switches to a hybrid 64k/4k kernel like they did with the My Cloud EX2/EX4. We want Sync on such a prevalent device too. You mentioned that you have not upgraded the firmware of your device. As long as you're able to keep that firmware version you should still be able to run our normal ARM binary for 2.0 when it's released.
  9. There are currently no plans to support the single drive WD My Cloud when 2.0 launches. We are only packaging Sync for NAS which have an app store. With the current firmware (v04.01.02-417) for the single drive WD My Cloud, there is no app store. WD does have an app store for the EX2 and EX4 My Cloud and we have worked on packages for these two models. We do hope to release packages of Sync 2.0 for the EX2/EX4 when 2.0 launches.
  10. Howdy! We're seeking some testers for the Drobo package we've been working on. This package is based on 1.4.103. It is likely that this package will not be updated until 2.0 launches. This package is only intended for the Drobo 5N. NOTE: The contents of this Sync folder are 1.4.103. For 2.0, please see: Sync Key for folder containing this package: BH5W76CXL2LNBPA6FRTC622WIVAWRXUAR If you're on Windows/Mac, you can add this Sync Key with the "Enter a key..." drop down.Screenshot: You'll need to place BitTorrent_Sync.tgz in to the DroboApps share (\\<IP-of-Drobo-5N>\DroboApps or smb://<IP-of-Drobo-5N>/DroboApps) With the introduction of Dashboard 2.5.x, the "DroboApps" share is no longer visible in Dashboard; however, you can manually access the share with these instructions: After placing the .tgz, you'll need to restart your device. Sync will then be running on port 8888 of your Drobo, e.g.: http://<IP-of-Drobo-5N>:8888 For reporting problems, I'm a big fan of using Jing ( for quickly recording and uploading video or annotated images. It is a lot easier for me to understand and reproduce issues by referencing video / annotated images.
  11. I've updated the Sync folder in the first post to contain packages for alpine, armada375, avoton, and x64. This should cover the newer model Synology NAS. Please let me know if there are any issues with these new packages. Again, you can enter this key from the "Enter a key..." drop down menu item: BYD2RWABB66V5EBYSNSCBYGDZR2JNHN5T A note on DS414j support - as forum users are reporting that the arm build isn't working out-of-the-box - I am not yet packaging for comcerto2k. As it may be a while before I can work on the comcerto2k issues, folks with this NAS can reference this forum post for instructions on how to get Sync running on your own. However, note that you'll have to recreate the symbolic link to the .so every time the DSM updates. I'm going to work on replies for the posts since my last post next. Thank you for your patience.
  12. Howdy, sorry for the delay. I was occupied with work to get done before the holidays and am now visiting with my family. I am on PTO until the 6th of January so my replies will be sporadic until at least then. > Any plan to release BTSync for DS415+ (Intel Atom C2538, avoton package)? I'm not sure that a package specific for that chip is necessary? Does the x86 package not work? (Unfortunately I don't have this hardware to test myself). > But is there any chance you can look into how to activate synoindex and maybe, possibly, adapt Bittorrent Sync to work accordingly? In referencing the post you linked to, it would seem that there would need to be some integration with the synoindex command. So far our methodology for official packages has been to not do extra custom work for each NAS platform, as then we must maintain the custom functionality for each platform. As our engineering and testing resources are limited we must be careful of how tightly coupled our integrations are. I will catalog this as a feature request for our backlog, but I suspect it is not an item we will be able to get to anytime soon. > This package doesn't seem to have restricted privilege like Synocommunity package. Should that be a problem where an user can see unauthorised folders? With this package we run as the root/admin user. It should not be a problem where a user can see unauthorized programs because only an administrative user should be configured with access to the Sync WebUI. The BitTorrent Sync WebUI/dameon does not support multi-user administration on any platform. We have chosen to run under a privileged user to have a simpler user experience. We found that requiring a user to configure user/group permissions for each folder to be too complex. If a more advanced user wants to configure Sync in such a way then we would direct them towards the SynoCommunity package which allows for this finer control. > Can you make one that supports Comcerto2000 architecture that is on the DS414j? I think this should be possible. We have support with our ARM build for QNAP with the Comcerto chip and so all that should be necessary is wrap the ARM build in a package flagged as supporting Comcerto. Unfortunately, I do not think that I will be able to do this until after the winter holidays. > Could you confirm how the application handles/replicates file permissions between two Synology NAS devices? I.e does it replicate the permissions on new files the same as the original file (unlike the currently BTSync software) As these packages wrap the existing BitTorrent Sync binaries, they do not have any extra functionality over the provided binaries on the download page.
  13. Howdy, I've created a post asking for feedback on some official Synology packages of Sync. As I don't have a DS414j, would you please try the packages I've posted to see if they even install on the 414j? If the builds I have don't install on the 414j, please let me know in that thread and I'll get to making a package specifically for the 414j.
  14. UPDATE: Thanks for testing. With the launch of Sync 2.0, please see for the latest on installing Synology on your NAS. Howdy! We're seeking testers for the Synology packages we've been working on. It's a stripped down version of the Synocommunity package that is hopefully easier for a user to configure. I only have a DS214 in the lab so I've only been able to test the ArmadaXP package myself. Before we make these packages more generally available we'd appreciate some feedback; especially for the non-ArmadaXP packages. Packages are available for these architectures: Armada 370 Armada XP Bromolow Cedarview Evansport PowerPC PPC853x Qoriq x86 88f6281 To know which package you should use, this is a helpful chart to cross reference your model of Synology device and its architecture: NOTE: The contents of this folder are 1.4.103. For 2.0, please see Sync Key for a folder containing these packages: BYD2RWABB66V5EBYSNSCBYGDZR2JNHN5T If you're on Windows/Mac, you can add this Sync Key with the "Enter a key..." drop down. Screenshot: These packages are based on Sync 1.4.103, with some modifications to the WebUI to minimize clutter in file picker. As these packages are not signed you'll need to modify the "Trust Level" of the Synology Package Center to allow "Any publisher" Screenshot: For reporting problems, I'm a big fan of using Jing ( for quickly recording and uploading video or annotated images. It is a lot easier for me to understand and reproduce issues by referencing video / annotated images. Thanks for the help, Richard
  15. The change log should be that of the differences between 1.3 and 1.4, as this is the first 1.4 release on Netgear. I'm sorry to say that I do not know of a good place to point you to for that general change log. Offhand, the main difference between 1.3 and 1.4 is that Sync Links are now the preferred method of sharing a Sync folder instead of the Secret Key. Along with this are fairly significant changes to the look and feel of the WebUI. The only NAS specific changes have to do with fixing a bug with the settings for "device name" and "listening port" not being saved between restarts.