Search the Community
Showing results for tags 'iomega'.
Found 2 results
Years ago I had early (unreleased) versions of btsync installed on my iomega ix2-200 StorCenter NAS. It worked, though I never figured out how to make it launch at startup time. Now I might want to try again with Resilio sync. It's a 10 year-old NAS, ARM (probably 32-bit), running (I believe) a version of debian called LifeLine 2.1. Apparently it lacks the apt-get program but does have dpkg. I can ssh with root access. From what I've been able to figure out, I probably want the armel version of Resilio sync. Any tips on making this work (especially in how to make it start at boot time: I think the OS refreshes the application directory from a backup at boot, eliminating any added stuff)?
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