RobLewis

Members
  • Content Count

    11
  • Joined

  • Last visited

  • Days Won

    1

About RobLewis

  • Rank
    Member
  1. I found that the ARM version works on my ix2-200 (non-cloud), but it seems to get automatically removed every time the device reboots. I don't know how to stop that.
  2. 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?
  3. OK, I can't find any way to start a new topic on the BitTorrent Sync forum--what's the secret? My problem is with Ubuntu 12 (on an old P4 Dell PC). When I boot the OS, I get an error alert: /usr/lib/btsync-user/btsyncindicator.py reports a crash at line 96, with AttributeError in setup_session(): 'Response' object has no attribute 'text' Any tips on what to do about this?
  4. I've already reported that btsync doesn't survive rebooting the NAS: the executable disappears from the root directory, either because it's purged by the system (as "foreign" software?) or maybe the root directory is refreshed from a backup at boot time. Other than that, I thought it was working. But yesterday something happened that broke my Mac's "Connect to Server..." Finder menu command. I tried to connect (as usual) to smb://<NAS IP address>, and it rejected my password. First time that's ever happened. I went to try rebooting the NAS using its standard web interface (which I could log into using the same password that was just rejected). It said it was rebooting, but the progress bar stalled at the very beginning of the process. I waited a long time, then issued the "reboot" command via the Mac Terminal program. This succeeded in rebooting the NAS. This made "Connect to Server..." work again with my normal password. Back in Terminal, I recopied btsync to the root directory and executed it. I was sad to discover that the folder sync operations I had set up had disappeared and would have to be recreated. I can't say for sure that the login password failure was btsync's fault, but it's the only thing new on the NAS. I did notice, before rebooting the NAS, that btsync was taking typically 40-70% of the CPU, as reported by the "top" program—when there was no actual syncing that needed to be done. Issues that need to be addressed: 1. Make btsync and the sync definitions survive reboots. 2. Auto-start btsync at boot time. (Maybe as part of a startup script that recopies it from a backup?) 3. Don't break "Connect to Server..." password 4. Investigate excessive CPU use
  5. I would think it's the only option that will run on the ix2-200's ARM processor.
  6. Here's what I did (using a Mac): Download the ARM version of the code & untar (double-click to expand). Copy (via the Mac) the executable btsync file to /mnt/soho_storage/samba/shares/public (the normal ix2-200 Public folder). If you have the ix2-200 mounted on your desktop, you can just drag btsync to its Public folder. Log in as root to the ix2-200. From a Mac Terminal window, enter: ssh root@<ix2-200's IP address>. When asked for your password, it's "soho" prepended to your normal admin password. Copy the file to the root directory: cp /mnt/soho_storage/samba/shares/public/btsync . (you need the space and period at the end of this command) Run the btsync program with this command: ./btsync Load this address in your browser: <ix2-200's IP address>:8888 This will bring up the GUI where you can set options. I haven't tried it, but reportedly you can have the program auto-run at startup by appending "/root/btsync" to the /etc/rc.local file. It works fine for me, with one problem: when the ix2-200 is restarted, the btsync file disappears from the root directory. I suspect this is because the unit restores the root directory from a backup at boot time, but I don't really know. For now I'm just recopying the file over when I reboot, which is rarely (starting at step 3 above). Oh, and if you ever want to stop the program, note the Process ID number that's displayed when you start btsync. Then in Terminal (assuming you're logged in as root), enter: kill <Process ID number> HTH.
  7. iomega ix2-200: executable gone after a restart. I had btsync running on my iomega ix2-200 NAS. Then apparently an AC glitch caused the UPS to shut it down. Upon restarting it, the executable btsync file had disappeared from the root directory. I wonder if the ix2-200 restores the root directory from a backup at each power-on, or something. Anybody know? I added the file back and started it and it seems to be running again. But this could get old.
  8. Seems to be working between Mac (10.7.5) and ix2-200 (non-cloud edition; synced folder is on an external USB drive attached to the NAS). Note you have to use SMB to mount the NAS on a Mac because AFP is broken.
  9. I'm trying to understand all the various advanced options, etc., and the Get Started page is frankly raising more questions than it answers. Is it possible that somebody could take another pass at this with an eye to being clear and explicit? I'll just cite a couple of examples: If what you call "secret" is actually the master secret, why not call it "master secret"? It would eliminate some possible confusion. "All the folders added with this secret will be granted a full set of permissions for two-way synchronization" seems needlessly complex. How about "All folders added with the master secret will be kept in sync"? Also, it's not clear whether more than one folder on a machine can be synced with the same master secret.
  10. You say you have the Cloud version of the ix2-200. Could that be the problem? I have the non-cloud version and am interested in trying BT Sync on it. I don't know which version to use, though.
  11. I have an iomega ix2-200 but I don't know which version of BT Sync to install. Any tips on installation appreciated.