Recommended Posts

Kos13, you can add the Seagate Goflex Nas to the list of supported devices. As a linux-noob, I spend quite some time in figuring out how to make it work. A step by step guide:

 

1. Download Putty and connect to the nas by using the NAS' ip.

 

2. Login with the following username (leave out the brackets):

[ADMIN_ACCOUNT_NAME]_hipserv2_seagateplug_XXXX-YYYY-ZZZZ-AAAA@[NAS_IP]

[ADMIN_ACCOUNT_NAME] = the admin account of the NAS. Whilst setting up the Seagate Goflex you had to make an admin account. Use the name of this account.

XXXX-YYYY-ZZZZ-AAAA = the product key of you NAS. You can find it at the bottom of your NAS device. Use CAPITALS!

[NAS_IP] = the ip address of your NAS. You can find it at the Seagate Dashboard or your router.

Example username: president_hipserv2_seagateplug_QWER-ASDF-ZXCV-ERTY@192.168.1.25

For the password, use the password that belongs to the admin account.

 

3. Gain root access. You need this to install software and create files on you Seagate Goflex NAS.

sudo -E -s

The prompt will show that the connection is refused, but it is lying :D.

 

4. Create a directory for the bittorrent sync software and go to this directory:

mkdir ~/.btsync && cd ~/.btsync

5. Download and unpack the software:

wget http://btsync.s3-website-us-east-1.amazonaws.com/btsync_arm.tar.gztar xvfz btsync_arm.tar.gz

6. Go to the directory and run the bittorent sync software:

cd ~/.btsyncsudo ./btsync

The prompt will show you something like this (your pid will be different):

BitTorrent Sync forked to background. pid = 3003

7. Navigate with your webbrowser to: [NAS]_IP:8888

Congratulations! You can configure Bittorent Sync.

 

 

When the power of your NAS fails, the Seagate Goflex will have to reboot. Unfortunately, Bittorrent Sync does not auto-start. You can make Bittorrent Sync automatically start up by following the next steps in the Putty terminal:

 

8.Create a script that you can call whilst booting:

vi /etc/init.d/btsync

9. In this script, write the following lines:

#! /bin/sh# /etc/init.d/btsync## Carry out specific functions when asked to by the systemcase "$1" instart)    /USERACCOUNT/.btsync/btsync --config /USERACCOUNT/.btsync/btsync.conf    ;;stop)    killall btsync    ;;*)    echo "Usage: /etc/init.d/btsync {start|stop}"    exit 1    ;;esacexit 0

Press the escape button. Type : and then x to save the file.

 

10. To allow the script to be called during startup, proper rights have to be assigned to it:

chmod 755 /etc/init.d/btsync

11. Add the script to the startup list:

/sbin/chkconfig --add btsync/sbin/chkconfig --levels 2345 btsync on

12. Reboot the NAS to see if it works after a restart. You can restart under preferences at the Seagate Share utility. Ofcourse, you can also just turn off the device and turn it on again.

 

Share this post


Link to post
Share on other sites

Works a treat on WD My Cloud.  I have the 3 TB version.

 

I followed the instructions on this post by a very knowledgeable user (RoyW);

http://forum.bittorrent.com/topic/17214-help-installing-bt-sync-on-wd-mybook-live/

 

The only differences are that you need the ARM version of bittorrent sync.  Also, the extraction wouldn't work using that command, so I just manually extracted the .tar.gz file and followed the next command.  Should work fine.

 

I must admit, I have no idea how to make the automatic restart script.  Has anyone found a step by step instruction set for someone who has absolutely no idea what he is doing?

Share this post


Link to post
Share on other sites

Sorry to post again, but I also got the restart script working on my WD My Cloud.

 

I essentially copied this; 

http://blog.bittorrent.com/2013/08/20/sync-hacks-how-to-sync-without-data-loss-using-btsync-raspberry-pi/

 

except the section that you copy and paste is this 

 

#! /bin/sh
# /etc/init.d/btsync
#
 
# Carry out specific functions when asked to by the system
case "$1" in
start)
    /shares/Public/btsync
    ;;
stop)
    killall btsync
    ;;
*)
    echo "Usage: /etc/init.d/btsync {start|stop}"
    exit 1
    ;;
esac
 
exit 0
 
IF you followed my previous post use that ^^
also for any other noobs, once that has been pasted in, press CTRL and x and then press 'Y' to save it.  After that just follow the rest of the post I linked.
 
Hopefully my goolging will save some other peoples time :)

Share this post


Link to post
Share on other sites

Is there any overview over which NAS will give you which speed?

 

I'm running a Gbit Lan here and can do 100 MB/sec between my computers. I'd like to get a NAS that can also do 100 MB/sec over Bittorrent sync.

 

Gbit == 125MB/sec. 1000 bit == 125 Bytes.

Share this post


Link to post
Share on other sites

I use two Drobo 5N. Is it possible to sync one Drobo with another? I want to use it as an offsite backup (one-on-one). An App for Drobo would be great! Does anyone have a guide for this stuff?

 

Sincerly,

a bittorrent-Noob

Share this post


Link to post
Share on other sites

I use two Drobo 5N. Is it possible to sync one Drobo with another? I want to use it as an offsite backup (one-on-one). An App for Drobo would be great! Does anyone have a guide for this stuff?

 

Sincerly,

a bittorrent-Noob

 

Do you have SSH access to it?

Share this post


Link to post
Share on other sites

If you are on linux or is capable of installing a ssh-client on your computer, then setting up BTSync would be trivial and I would help you. If you can't set up ssh on your computer, then I suggest getting someone to do it for you.

Share this post


Link to post
Share on other sites

i make this:

http://www.droboport...1-0-132/drobofs

  • Browse the DroboFS with explorer (typed \\{drobofs ip address} ) and mapped a network drive to theDroboApps shared. The DroboApps Share isn't visible through Drobo dashboard.
  • Downloaded btsync.tgz and copied it into the DroboApps drive
  • Used Drobo Dashboard to restart the DroboFS
  • Browsed to http://{drobofsipaddress}:8888/
  • I see the Web UI, can make a scret, but my PC (Windows) can´t sync. whats wrong
    ?

Thanks

Share this post


Link to post
Share on other sites

There was no Firewall. I think the App for Drobo  have a bug. So i buy a raspberry Pi Mountete the nas and instal bittorrent sync. Everything is in sync and fine. Thanks a lot

Share this post


Link to post
Share on other sites

Hi all,

I'm trying to get btsync running on a Buffalo TS Live.  I managed to d/l and install and got it to start with some help from this forum on setting the alignment for arm.

 

Now when running, I get the message that btsync is being forked to the background.  Then it disappears.  I can't access the the webui.  PS doesnt show the process as running and trying to kill the pid given at startup tells me that the process doesn't exist.

 

The system log shows nothing at all.  I turned on debugging and only get this:

 

sync.log

[20140216 13:22:07.217] total physical memory -1 max disk cache 2097152[20140216 13:22:07.221] Using IP address 192.168.1.102[20140216 13:22:07.287] test sha1: AE5B <cut for security>[20140216 13:22:07.287] test sha2: 630D <cut for security>[20140216 13:22:07.287] test aes: 0A94 <cut for security>

I think maybe I just don't have enough memory.  Here's the results of free.

~# free              total         used         free       shared      buffers  Mem:       126080        90372        35708            0          108 Swap:       546048            0       546048Total:       672128        90372       581756

Thank you for any help.

Share this post


Link to post
Share on other sites

Hi Igboo,

 

The message "BitTorrent Sync forked to background, pid=xxxx"  is okay. It just indicates that not BTSync is running and let you know the process ID.

 

The fact that you can't find it in the process list later means that either process crashed or exited by some reason. Could you please verify if there are core dump files in btsync folder and provide a full debug log for analysis?

 

Thanks!

Share this post


Link to post
Share on other sites

Hi Igboo,

 

The message "BitTorrent Sync forked to background, pid=xxxx"  is okay. It just indicates that not BTSync is running and let you know the process ID.

 

The fact that you can't find it in the process list later means that either process crashed or exited by some reason. Could you please verify if there are core dump files in btsync folder and provide a full debug log for analysis?

 

Thanks!

 

Hello RomanZ,

 

I have debug enabled with the contents of debug.txt as FFFF.  All I get in the log is the five lines I posted.  I just tried running again.  This is all I get.

[20140217 11:20:30.815] total physical memory -1 max disk cache 2097152[20140217 11:20:30.819] Using IP address 192.168.1.102[20140217 11:20:30.821] test sha1: AE5BD <cut for securtiy>[20140217 11:20:30.821] test sha2: 630DC  <cut for security>[20140217 11:20:30.821] test aes: 0A940  <cut for security>

I lose the process immediately... If I run the command to start btsync and then run ps, it's already gone.

 

For what it's worth, here is my system log since the last reboot.

Feb 16 13:14:03 HS-DHTGLD3C syslogd 1.4.1: restart.Feb 16 13:14:03 HS-DHTGLD3C kernel: klogd 1.4.1, log source = /proc/kmsg started.Feb 16 13:14:03 HS-DHTGLD3C kernel: Cannot find map file.Feb 16 13:14:03 HS-DHTGLD3C kernel: No module symbols loaded - kernel modules not enabled. Feb 16 13:14:03 HS-DHTGLD3C kernel: cannot find any symbols, turning off symbol lookups Feb 16 13:14:03 HS-DHTGLD3C kernel: Linux version 2.6.16.16-arm1 (root@dh2-bs) (gcc version 3.4.4 (release) (CodeSourcery ARM 2005q3-2)) #3 Wed Mar 7 13:21:58 JST 2007Feb 16 13:14:03 HS-DHTGLD3C kernel: CPU: ARM926EJ-Sid(wb) [41069260] revision 0 (ARMv5TEJ)Feb 16 13:14:03 HS-DHTGLD3C kernel: Machine: MV-88fxx81Feb 16 13:14:03 HS-DHTGLD3C kernel: Using UBoot passing parameters structureFeb 16 13:14:03 HS-DHTGLD3C kernel: Sys Clk = 250000000, Tclk = 166664740Feb 16 13:14:03 HS-DHTGLD3C kernel: Feb 16 13:14:03 HS-DHTGLD3C kernel: Feb 16 13:14:03 HS-DHTGLD3C kernel: - Warning - This LSP release was tested only with U-Boot release 1.7.3 Feb 16 13:14:03 HS-DHTGLD3C kernel: Feb 16 13:14:03 HS-DHTGLD3C kernel: Memory policy: ECC disabled, Data cache writebackFeb 16 13:14:04 HS-DHTGLD3C logchkd[793]: logchkd ver.1.11(Feb 14 2007) startedFeb 16 13:14:04 HS-DHTGLD3C TeraStation: Started logchkdFeb 16 13:14:04 HS-DHTGLD3C kernel: CPU0: D VIVT write-back cacheFeb 16 13:14:04 HS-DHTGLD3C kernel: CPU0: I cache: 32768 bytes, associativity 1, 32 byte lines, 1024 setsFeb 16 13:14:04 HS-DHTGLD3C kernel: CPU0: D cache: 32768 bytes, associativity 4, 32 byte lines, 256 setsFeb 16 13:14:04 HS-DHTGLD3C kernel: Built 1 zonelistsFeb 16 13:14:04 HS-DHTGLD3C kernel: Kernel command line: console=ttyS0,115200 root=/dev/sda2 rw initrd=0x00800040,15M panic=5 BOOTVER=1.10Feb 16 13:14:04 HS-DHTGLD3C kernel: PID hash table entries: 1024 (order: 10, 16384 bytes)Feb 16 13:14:04 HS-DHTGLD3C kernel: Console: colour dummy device 80x30Feb 16 13:14:04 HS-DHTGLD3C kernel: Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)Feb 16 13:14:04 HS-DHTGLD3C kernel: Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)Feb 16 13:14:04 HS-DHTGLD3C kernel: Memory: 128MB 0MB 0MB 0MB = 128MB totalFeb 16 13:14:04 HS-DHTGLD3C kernel: Memory: 110464KB available (3128K code, 573K data, 112K init)Feb 16 13:14:04 HS-DHTGLD3C kernel: Mount-cache hash table entries: 512Feb 16 13:14:04 HS-DHTGLD3C TeraStation: Started inetdFeb 16 13:14:04 HS-DHTGLD3C kernel: CPU: Testing write buffer coherency: okFeb 16 13:14:04 HS-DHTGLD3C kernel: checking if image is initramfs...it isn't (no cpio magic); looks like an initrdFeb 16 13:14:04 HS-DHTGLD3C TeraStation: Started kernelmonFeb 16 13:14:04 HS-DHTGLD3C kernel: Freeing initrd memory: 15360KFeb 16 13:14:04 HS-DHTGLD3C kernel: NET: Registered protocol family 16Feb 16 13:14:04 HS-DHTGLD3C kernel: FLASH boardId = 14Feb 16 13:14:04 HS-DHTGLD3C kernel: Flash bankwidth 1, base ff800000, size 400000Feb 16 13:14:04 HS-DHTGLD3C kernel: BUFFALO TS_HTGL FLASH size 4096[KB]Feb 16 13:14:04 HS-DHTGLD3C kernel: Feb 16 13:14:04 HS-DHTGLD3C miconmon[808]: miconmon-1.03 started Feb 16 13:14:04 HS-DHTGLD3C kernel:   Marvell Development Board (LSP Version 1.7.8_NAS)-- BUFFALO_BOARD_TS_HTGL_R5 Feb 16 13:14:04 HS-DHTGLD3C kernel: Feb 16 13:14:04 HS-DHTGLD3C kernel:  Detected Tclk 166664740 and SysClk 250000000 Feb 16 13:14:04 HS-DHTGLD3C kernel: Marvell USB EHCI Host controller #0: c16f5e00Feb 16 13:14:04 HS-DHTGLD3C kernel: pexBarOverlapDetect: winNum 2 overlap current 0Feb 16 13:14:04 HS-DHTGLD3C kernel: mvPexInit:Warning :Bar 2 size is illigalFeb 16 13:14:04 HS-DHTGLD3C kernel: it will be disabledFeb 16 13:14:04 HS-DHTGLD3C kernel: please check Pex and CPU windows configurationFeb 16 13:14:04 HS-DHTGLD3C kernel: PCI: bus0: Fast back to back transfers enabledFeb 16 13:14:04 HS-DHTGLD3C kernel: PCI: bus1: Fast back to back transfers enabledFeb 16 13:14:04 HS-DHTGLD3C kernel: SCSI subsystem initializedFeb 16 13:14:04 HS-DHTGLD3C kernel: usbcore: registered new driver usbfsFeb 16 13:14:04 HS-DHTGLD3C kernel: usbcore: registered new driver hubFeb 16 13:14:04 HS-DHTGLD3C kernel: use IDMA acceleration in copy to/from user buffers. used channels 2 and 3 Feb 16 13:14:04 HS-DHTGLD3C kernel: Done. Feb 16 13:14:04 HS-DHTGLD3C kernel: Fast Floating Point Emulator V0.9 (c) Peter Teichmann.Feb 16 13:14:04 HS-DHTGLD3C kernel: SGI XFS with large block numbers, no debug enabledFeb 16 13:14:04 HS-DHTGLD3C kernel: Initializing Cryptographic APIFeb 16 13:14:04 HS-DHTGLD3C kernel: io scheduler noop registeredFeb 16 13:14:04 HS-DHTGLD3C kernel: io scheduler anticipatory registered (default)Feb 16 13:14:04 HS-DHTGLD3C kernel: io scheduler deadline registeredFeb 16 13:14:04 HS-DHTGLD3C kernel: io scheduler cfq registeredFeb 16 13:14:04 HS-DHTGLD3C kernel: Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabledFeb 16 13:14:04 HS-DHTGLD3C kernel: serial8250: ttyS0 at MMIO 0x0 (irq = 3) is a 16550AFeb 16 13:14:04 HS-DHTGLD3C kernel: serial8250: ttyS1 at MMIO 0x0 (irq = 4) is a 16550AFeb 16 13:14:04 HS-DHTGLD3C kernel: RAMDISK driver initialized: 3 RAM disks of 16384K size 1024 blocksizeFeb 16 13:14:04 HS-DHTGLD3C kernel: loop: loaded (max 8 devices)Feb 16 13:14:04 HS-DHTGLD3C kernel: Marvell Gigabit Ethernet Driver 'egiga':Feb 16 13:14:04 HS-DHTGLD3C kernel:   o Ethernet descriptors in DRAMFeb 16 13:14:04 HS-DHTGLD3C kernel:   o DRAM SW cache-coherencyFeb 16 13:14:04 HS-DHTGLD3C kernel:   o Checksum offload enabledFeb 16 13:14:04 HS-DHTGLD3C kernel:   o Loading network interface ** egiga_init_module (0)Feb 16 13:14:04 HS-DHTGLD3C kernel: 'eth0' Feb 16 13:14:04 HS-DHTGLD3C kernel: Core Driver (ERROR)  0 : Warning: Future revision ID 02 for Device 6042. Implementing latest workaroundsFeb 16 13:14:04 HS-DHTGLD3C kernelmon: cmd=lanact 0 halfFeb 16 13:14:04 HS-DHTGLD3C kernel: Core Driver (ERROR)  0 : disable pci conventional features when working in PCI-X. pciCommand original value:0x0107e371. new value: 0x0107e011.Feb 16 13:14:04 HS-DHTGLD3C kernel: scsi0 : Marvell SCSI to SATA adapterFeb 16 13:14:04 HS-DHTGLD3C kernel: scsi1 : Marvell SCSI to SATA adapterFeb 16 13:14:04 HS-DHTGLD3C kernel: scsi2 : Marvell SCSI to SATA adapterFeb 16 13:14:04 HS-DHTGLD3C kernel: scsi3 : Marvell SCSI to SATA adapterFeb 16 13:14:05 HS-DHTGLD3C kernel: ** BUFFALO Disable Command Queuing Function [0 0] **Feb 16 13:14:05 HS-DHTGLD3C kernel: ** BUFFALO Disable Command Queuing Function [0 1] **Feb 16 13:14:05 HS-DHTGLD3C kernel: ** BUFFALO Disable Command Queuing Function [0 2] **Feb 16 13:14:05 HS-DHTGLD3C kernel: ** BUFFALO Disable Command Queuing Function [0 3] **Feb 16 13:14:05 HS-DHTGLD3C kernel:   Vendor: SAMSUNG   Model: HD501LJ           Rev: CR10Feb 16 13:14:05 HS-DHTGLD3C kernelmon: cmd=lanact 1000 fullFeb 16 13:14:05 HS-DHTGLD3C kernel:   Type:   Direct-Access                      ANSI SCSI revision: 03Feb 16 13:14:05 HS-DHTGLD3C kernel:   Vendor: SAMSUNG   Model: HD501LJ           Rev: CR10Feb 16 13:14:05 HS-DHTGLD3C kernel:   Type:   Direct-Access                      ANSI SCSI revision: 03Feb 16 13:14:05 HS-DHTGLD3C kernel:   Vendor: SAMSUNG   Model: HD501LJ           Rev: CR10Feb 16 13:14:05 HS-DHTGLD3C kernel:   Type:   Direct-Access                      ANSI SCSI revision: 03Feb 16 13:14:05 HS-DHTGLD3C kernel:   Vendor: SAMSUNG   Model: HD501LJ           Rev: CR10Feb 16 13:14:05 HS-DHTGLD3C kernel:   Type:   Direct-Access                      ANSI SCSI revision: 03Feb 16 13:14:05 HS-DHTGLD3C kernel: Linux IAL (ERROR) : retry command host=0, bus=0 SCpnt = c14a3920Feb 16 13:14:05 HS-DHTGLD3C kernel: SCSI device sda: 976773168 512-byte hdwr sectors (500108 MB)Feb 16 13:14:05 HS-DHTGLD3C kernel: sda: Write Protect is offFeb 16 13:14:05 HS-DHTGLD3C kernel: SCSI device sda: drive cache: write backFeb 16 13:14:05 HS-DHTGLD3C kernel: SCSI device sda: 976773168 512-byte hdwr sectors (500108 MB)Feb 16 13:14:05 HS-DHTGLD3C kernel: sda: Write Protect is offFeb 16 13:14:05 HS-DHTGLD3C kernel: SCSI device sda: drive cache: write backFeb 16 13:14:05 HS-DHTGLD3C kernel:  sda: sda1 sda2 sda4 < sda5 sda6 >Feb 16 13:14:05 HS-DHTGLD3C kernel: sd 0:0:0:0: Attached scsi disk sdaFeb 16 13:14:05 HS-DHTGLD3C kernel: Linux IAL (ERROR) : retry command host=1, bus=1 SCpnt = c14a3920Feb 16 13:14:06 HS-DHTGLD3C kernel: SCSI device sdb: 976773168 512-byte hdwr sectors (500108 MB)Feb 16 13:14:06 HS-DHTGLD3C kernel: sdb: Write Protect is offFeb 16 13:14:06 HS-DHTGLD3C kernel: SCSI device sdb: drive cache: write backFeb 16 13:14:06 HS-DHTGLD3C kernel: SCSI device sdb: 976773168 512-byte hdwr sectors (500108 MB)Feb 16 13:14:06 HS-DHTGLD3C kernel: sdb: Write Protect is offFeb 16 13:14:06 HS-DHTGLD3C kernel: SCSI device sdb: drive cache: write backFeb 16 13:14:06 HS-DHTGLD3C kernel:  sdb: sdb1 sdb2 sdb4 < sdb5 sdb6 >Feb 16 13:14:06 HS-DHTGLD3C kernel: sd 1:0:0:0: Attached scsi disk sdbFeb 16 13:14:06 HS-DHTGLD3C kernel: Linux IAL (ERROR) : retry command host=2, bus=2 SCpnt = c14a3920Feb 16 13:14:06 HS-DHTGLD3C kernel: SCSI device sdc: 976773168 512-byte hdwr sectors (500108 MB)Feb 16 13:14:06 HS-DHTGLD3C kernel: sdc: Write Protect is offFeb 16 13:14:06 HS-DHTGLD3C kernel: SCSI device sdc: drive cache: write backFeb 16 13:14:06 HS-DHTGLD3C kernel: SCSI device sdc: 976773168 512-byte hdwr sectors (500108 MB)Feb 16 13:14:06 HS-DHTGLD3C kernel: sdc: Write Protect is offFeb 16 13:14:06 HS-DHTGLD3C kernel: SCSI device sdc: drive cache: write backFeb 16 13:14:06 HS-DHTGLD3C kernel:  sdc: sdc1 sdc2 sdc4 < sdc5 sdc6 >Feb 16 13:14:06 HS-DHTGLD3C kernel: sd 2:0:0:0: Attached scsi disk sdcFeb 16 13:14:06 HS-DHTGLD3C kernel: Linux IAL (ERROR) : retry command host=3, bus=3 SCpnt = c14a3920Feb 16 13:14:06 HS-DHTGLD3C kernel: SCSI device sdd: 976773168 512-byte hdwr sectors (500108 MB)Feb 16 13:14:06 HS-DHTGLD3C kernel: sdd: Write Protect is offFeb 16 13:14:06 HS-DHTGLD3C kernel: SCSI device sdd: drive cache: write backFeb 16 13:14:06 HS-DHTGLD3C kernel: SCSI device sdd: 976773168 512-byte hdwr sectors (500108 MB)Feb 16 13:14:06 HS-DHTGLD3C kernel: sdd: Write Protect is offFeb 16 13:14:06 HS-DHTGLD3C kernel: SCSI device sdd: drive cache: write backFeb 16 13:14:06 HS-DHTGLD3C kernel:  sdd: sdd1 sdd2 sdd4 < sdd5 sdd6 >Feb 16 13:14:06 HS-DHTGLD3C kernel: sd 3:0:0:0: Attached scsi disk sddFeb 16 13:14:06 HS-DHTGLD3C kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0Feb 16 13:14:06 HS-DHTGLD3C kernel: sd 1:0:0:0: Attached scsi generic sg1 type 0Feb 16 13:14:06 HS-DHTGLD3C kernel: sd 2:0:0:0: Attached scsi generic sg2 type 0Feb 16 13:14:06 HS-DHTGLD3C kernel: sd 3:0:0:0: Attached scsi generic sg3 type 0Feb 16 13:14:06 HS-DHTGLD3C kernel: physmap flash device: 400000 at ff800000Feb 16 13:14:06 HS-DHTGLD3C kernel: >jedec_probeFeb 16 13:14:06 HS-DHTGLD3C kernel: Found: SST 39LF020Feb 16 13:14:06 HS-DHTGLD3C kernel: phys_mapped_flash: Found 1 x8 devices at 0x0 in 8-bit bankFeb 16 13:14:06 HS-DHTGLD3C kernel: number of JEDEC chips: 1Feb 16 13:14:06 HS-DHTGLD3C kernel: cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.Feb 16 13:14:06 HS-DHTGLD3C kernel: cmdlinepart partition parsing not availableFeb 16 13:14:06 HS-DHTGLD3C kernel: RedBoot partition parsing not availableFeb 16 13:14:06 HS-DHTGLD3C kernel: ehci_platform ehci_platform.4523: EHCI Platform Host ControllerFeb 16 13:14:06 HS-DHTGLD3C kernel: ehci_platform ehci_platform.4523: new USB bus registered, assigned bus number 1Feb 16 13:14:06 HS-DHTGLD3C kernel: ehci_platform ehci_platform.4523: irq 17, io mem 0x00000000Feb 16 13:14:06 HS-DHTGLD3C kernel: ehci_platform ehci_platform.4523: USB 0.0 started, EHCI 1.00, driver 10 Dec 2004Feb 16 13:14:06 HS-DHTGLD3C kernel: usb usb1: configuration #1 chosen from 1 choiceFeb 16 13:14:06 HS-DHTGLD3C kernel: hub 1-0:1.0: USB hub foundFeb 16 13:14:06 HS-DHTGLD3C kernel: hub 1-0:1.0: 1 port detectedFeb 16 13:14:06 HS-DHTGLD3C kernel: USB Universal Host Controller Interface driver v2.3Feb 16 13:14:06 HS-DHTGLD3C kernel: Initializing USB Mass Storage driver...Feb 16 13:14:06 HS-DHTGLD3C kernel: usb 1-1: new high speed USB device using ehci_platform and address 2Feb 16 13:14:06 HS-DHTGLD3C kernel: usb 1-1: configuration #1 chosen from 1 choiceFeb 16 13:14:06 HS-DHTGLD3C kernel: hub 1-1:1.0: USB hub foundFeb 16 13:14:06 HS-DHTGLD3C kernel: hub 1-1:1.0: 4 ports detectedFeb 16 13:14:06 HS-DHTGLD3C kernel: usbcore: registered new driver usb-storageFeb 16 13:14:06 HS-DHTGLD3C kernel: USB Mass Storage support registered.Feb 16 13:14:06 HS-DHTGLD3C kernel: mice: PS/2 mouse device common for all miceFeb 16 13:14:06 HS-DHTGLD3C kernel: md: linear personality registered for level -1Feb 16 13:14:06 HS-DHTGLD3C kernel: md: raid0 personality registered for level 0Feb 16 13:14:06 HS-DHTGLD3C kernel: md: raid1 personality registered for level 1Feb 16 13:14:06 HS-DHTGLD3C kernel: md: raid5 personality registered for level 5Feb 16 13:14:06 HS-DHTGLD3C kernel: md: raid4 personality registered for level 4Feb 16 13:14:06 HS-DHTGLD3C kernel: raid5: measuring checksumming speedFeb 16 13:14:06 HS-DHTGLD3C kernel:    arm4regs  :   429.200 MB/secFeb 16 13:14:06 HS-DHTGLD3C kernel:    8regs     :   329.600 MB/secFeb 16 13:14:06 HS-DHTGLD3C kernel:    32regs    :   513.200 MB/secFeb 16 13:14:06 HS-DHTGLD3C kernel: raid5: using function: 32regs (513.200 MB/sec)Feb 16 13:14:06 HS-DHTGLD3C kernel: md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27Feb 16 13:14:06 HS-DHTGLD3C kernel: md: bitmap version 4.39Feb 16 13:14:06 HS-DHTGLD3C kernel: Kernel event proc (C) BUFFALO INC. V.1.00 installed.Feb 16 13:14:06 HS-DHTGLD3C kernel: MICON ctrl (C) BUFFALO INC. V.1.00 installed.Feb 16 13:14:06 HS-DHTGLD3C kernel: MICON V2 (C) BUFFALO INC. V.1.00 installed.Feb 16 13:14:06 HS-DHTGLD3C kernel: UPSDRV (C) BUFFALO INC. V.1.00 installed.Feb 16 13:14:06 HS-DHTGLD3C kernel: BUFFALO UPS Recover Function Initialized.Feb 16 13:14:06 HS-DHTGLD3C kernel: NET: Registered protocol family 2Feb 16 13:14:06 HS-DHTGLD3C kernel: IP route cache hash table entries: 2048 (order: 1, 8192 bytes)Feb 16 13:14:06 HS-DHTGLD3C kernel: TCP established hash table entries: 8192 (order: 3, 32768 bytes)Feb 16 13:14:06 HS-DHTGLD3C kernel: TCP bind hash table entries: 8192 (order: 3, 32768 bytes)Feb 16 13:14:06 HS-DHTGLD3C kernel: TCP: Hash tables configured (established 8192 bind 8192)Feb 16 13:14:06 HS-DHTGLD3C kernel: TCP reno registeredFeb 16 13:14:06 HS-DHTGLD3C kernel: TCP bic registeredFeb 16 13:14:06 HS-DHTGLD3C kernel: NET: Registered protocol family 1Feb 16 13:14:06 HS-DHTGLD3C kernel: NET: Registered protocol family 17Feb 16 13:14:06 HS-DHTGLD3C kernel: md: Autodetecting RAID arrays.Feb 16 13:14:06 HS-DHTGLD3C kernel: md: autorun ...Feb 16 13:14:06 HS-DHTGLD3C kernel: md: ... autorun DONE.Feb 16 13:14:06 HS-DHTGLD3C kernel: RAMDISK: Compressed image found at block 0Feb 16 13:14:06 HS-DHTGLD3C kernel: VFS: Mounted root (ext2 filesystem).Feb 16 13:14:06 HS-DHTGLD3C kernel: md: md1 stopped.Feb 16 13:14:06 HS-DHTGLD3C kernel: md: bind<sdb2>Feb 16 13:14:06 HS-DHTGLD3C kernel: md: bind<sdc2>Feb 16 13:14:06 HS-DHTGLD3C kernel: md: bind<sdd2>Feb 16 13:14:06 HS-DHTGLD3C kernel: md: bind<sda2>Feb 16 13:14:06 HS-DHTGLD3C kernel: raid1: raid set md1 active with 4 out of 4 mirrorsFeb 16 13:14:06 HS-DHTGLD3C kernel: md: md0 stopped.Feb 16 13:14:06 HS-DHTGLD3C kernel: md: bind<sdb1>Feb 16 13:14:06 HS-DHTGLD3C kernel: md: bind<sdc1>Feb 16 13:14:06 HS-DHTGLD3C kernel: md: bind<sdd1>Feb 16 13:14:06 HS-DHTGLD3C kernel: md: bind<sda1>Feb 16 13:14:06 HS-DHTGLD3C kernel: raid1: raid set md0 active with 4 out of 4 mirrorsFeb 16 13:14:06 HS-DHTGLD3C kernel: XFS mounting filesystem md1Feb 16 13:14:06 HS-DHTGLD3C kernel: kjournald starting.  Commit interval 5 secondsFeb 16 13:14:06 HS-DHTGLD3C kernel: EXT3 FS on md0, internal journalFeb 16 13:14:06 HS-DHTGLD3C kernel: EXT3-fs: mounted filesystem with ordered data mode.Feb 16 13:14:07 HS-DHTGLD3C kernel: XFS mounting filesystem md1Feb 16 13:14:07 HS-DHTGLD3C kernel: XFS mounting filesystem md1Feb 16 13:14:07 HS-DHTGLD3C kernel: VFS: Mounted root (xfs filesystem).Feb 16 13:14:07 HS-DHTGLD3C kernel: Trying to move old root to /initrd ... /initrd does not exist. Ignored.Feb 16 13:14:07 HS-DHTGLD3C kernel: Unmounting old rootFeb 16 13:14:07 HS-DHTGLD3C kernel: Trying to free ramdisk memory ... okayFeb 16 13:14:07 HS-DHTGLD3C kernel: Freeing init memory: 112KFeb 16 13:14:07 HS-DHTGLD3C kernel: Adding 136512k swap on /dev/disk1_5.  Priority:-1 extents:1 across:136512kFeb 16 13:14:07 HS-DHTGLD3C kernel: Adding 136512k swap on /dev/disk2_5.  Priority:-2 extents:1 across:136512kFeb 16 13:14:07 HS-DHTGLD3C kernel: Adding 136512k swap on /dev/disk3_5.  Priority:-3 extents:1 across:136512kFeb 16 13:14:07 HS-DHTGLD3C kernel: Adding 136512k swap on /dev/disk4_5.  Priority:-4 extents:1 across:136512kFeb 16 13:14:07 HS-DHTGLD3C kernel: kjournald starting.  Commit interval 5 secondsFeb 16 13:14:07 HS-DHTGLD3C kernel: EXT3 FS on md0, internal journalFeb 16 13:14:07 HS-DHTGLD3C kernel: EXT3-fs: mounted filesystem with ordered data mode.Feb 16 13:14:07 HS-DHTGLD3C kernel: eth0: link downFeb 16 13:14:07 HS-DHTGLD3C kernel: eth0: link up<5>, full duplex<5>, speed 1 Gbps<5>Feb 16 13:14:07 HS-DHTGLD3C kernel: md: md2 stopped.Feb 16 13:14:07 HS-DHTGLD3C kernel: md: bind<sdb6>Feb 16 13:14:07 HS-DHTGLD3C kernel: md: bind<sdc6>Feb 16 13:14:07 HS-DHTGLD3C kernel: md: bind<sdd6>Feb 16 13:14:07 HS-DHTGLD3C kernel: md: bind<sda6>Feb 16 13:14:07 HS-DHTGLD3C kernel: raid5: device sda6 operational as raid disk 0Feb 16 13:14:07 HS-DHTGLD3C kernel: raid5: device sdd6 operational as raid disk 3Feb 16 13:14:07 HS-DHTGLD3C kernel: raid5: device sdc6 operational as raid disk 2Feb 16 13:14:07 HS-DHTGLD3C kernel: raid5: device sdb6 operational as raid disk 1Feb 16 13:14:07 HS-DHTGLD3C kernel: raid5: allocated 4210kB for md2Feb 16 13:14:07 HS-DHTGLD3C kernel: raid5: raid level 5 set md2 active with 4 out of 4 devices, algorithm 2Feb 16 13:14:07 HS-DHTGLD3C kernel: RAID5 conf printout:Feb 16 13:14:07 HS-DHTGLD3C kernel:  --- rd:4 wd:4 fd:0Feb 16 13:14:07 HS-DHTGLD3C kernel:  disk 0, o:1, dev:sda6Feb 16 13:14:07 HS-DHTGLD3C kernel:  disk 1, o:1, dev:sdb6Feb 16 13:14:07 HS-DHTGLD3C kernel:  disk 2, o:1, dev:sdc6Feb 16 13:14:07 HS-DHTGLD3C kernel:  disk 3, o:1, dev:sdd6Feb 16 13:14:08 HS-DHTGLD3C kernel: XFS mounting filesystem md2Feb 16 13:14:10 HS-DHTGLD3C sshd[964]: Server listening on 0.0.0.0 port 22.Feb 16 13:14:15 HS-DHTGLD3C clientUtil_server[1089]: startup daemon Feb 16 13:14:15 HS-DHTGLD3C clientUtil_server[1089]: assigned intreface eth0 Feb 16 13:14:15 HS-DHTGLD3C clientUtil_server[1089]: clientUtil_server Ver.1.02Feb 16 13:14:15 HS-DHTGLD3C daemonwatch[1095]: daemonwatch ver.1.01Feb 16 13:14:15 HS-DHTGLD3C lsprcvd[1093]: lsprcvd started.Feb 16 13:14:16 HS-DHTGLD3C kernel: usbcore: registered new driver usblpFeb 16 13:14:16 HS-DHTGLD3C kernel: drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driverFeb 16 13:14:16 HS-DHTGLD3C root: TeraStation VERSION=1.10 SUBVERSION=HDD 2.07Feb 16 13:14:18 HS-DHTGLD3C errormon[1214]: errormon-ver.1.01 started Feb 16 13:14:18 HS-DHTGLD3C TeraStation: Started errormonFeb 16 13:14:18 HS-DHTGLD3C TeraStation: #[miconapl.mcon_get_version] mcon_version=TS-HTGL/R5Ver1.0Feb 16 13:17:34 HS-DHTGLD3C nmbd[1045]: [2014/02/16 13:17:34, 0] nmbd/nmbd_become_lmb.c:become_local_master_stage2(396) Feb 16 13:17:34 HS-DHTGLD3C nmbd[1045]:   ***** Feb 16 13:17:34 HS-DHTGLD3C nmbd[1045]:    Feb 16 13:17:34 HS-DHTGLD3C nmbd[1045]:   Samba name server HS-DHTGLD3C is now a local master browser for workgroup STEIN on subnet 192.168.1.102 Feb 16 13:17:34 HS-DHTGLD3C nmbd[1045]:    Feb 16 13:17:34 HS-DHTGLD3C nmbd[1045]:   ***** Feb 16 13:19:45 HS-DHTGLD3C sshd[7446]: Accepted password for root from 192.168.1.7 port 61083 ssh2Feb 16 13:19:45 HS-DHTGLD3C sshd[7446]: lastlog_perform_login: Couldn't stat /var/log/lastlog: No such file or directoryFeb 16 13:19:45 HS-DHTGLD3C sshd[7446]: lastlog_openseek: /var/log/lastlog is not a file or directory!Feb 16 13:19:45 HS-DHTGLD3C sshd[7555]: lastlog_perform_login: Couldn't stat /var/log/lastlog: No such file or directoryFeb 16 13:19:45 HS-DHTGLD3C sshd[7555]: lastlog_openseek: /var/log/lastlog is not a file or directory!Feb 16 17:03:41 HS-DHTGLD3C sshd[27258]: Accepted password for root from 192.168.1.7 port 49673 ssh2Feb 16 17:03:41 HS-DHTGLD3C sshd[27258]: lastlog_perform_login: Couldn't stat /var/log/lastlog: No such file or directoryFeb 16 17:03:41 HS-DHTGLD3C sshd[27258]: lastlog_openseek: /var/log/lastlog is not a file or directory!Feb 16 17:03:41 HS-DHTGLD3C sshd[27369]: lastlog_perform_login: Couldn't stat /var/log/lastlog: No such file or directoryFeb 16 17:03:41 HS-DHTGLD3C sshd[27369]: lastlog_openseek: /var/log/lastlog is not a file or directory!Feb 17 00:07:06 HS-DHTGLD3C ntpdate[6983]: step time server 162.243.55.105 offset 0.010799 secFeb 17 00:07:06 HS-DHTGLD3C linkstation: [Success] Sync to ntp serverFeb 17 11:17:41 HS-DHTGLD3C sshd[31556]: Accepted password for root from 192.168.1.7 port 50541 ssh2Feb 17 11:17:41 HS-DHTGLD3C sshd[31556]: lastlog_perform_login: Couldn't stat /var/log/lastlog: No such file or directoryFeb 17 11:17:41 HS-DHTGLD3C sshd[31556]: lastlog_openseek: /var/log/lastlog is not a file or directory!Feb 17 11:17:41 HS-DHTGLD3C sshd[31672]: lastlog_perform_login: Couldn't stat /var/log/lastlog: No such file or directoryFeb 17 11:17:41 HS-DHTGLD3C sshd[31672]: lastlog_openseek: /var/log/lastlog is not a file or directory!

Thanks!

Share this post


Link to post
Share on other sites

igboo,

 

Thanks. What about core dump file? Did you have a chance to notice it?

 

If they are, they should be located either in folder where btsync binary stays, or in a hidden subfolder ".sync" which is created near binary.

 

THanks.

Share this post


Link to post
Share on other sites

Version 1.2.82 installed and running fine on a Netgear ReadyNas RN102 running OS6.1.6.

 

Note: I was unable to get the free BtSync "App" available in the ReadyNas's App store running correctly.

It would lanuch, run and sync files as expected but would not save its configuration and folder list over reboots.

Seems to be some problem with file ownership and/or write permissions.

 

I installed btsync via ssh and put an entry in /etc/init.d to start it at boot, works fine.

Share this post


Link to post
Share on other sites

igboo,

 

Thanks. What about core dump file? Did you have a chance to notice it?

 

If they are, they should be located either in folder where btsync binary stays, or in a hidden subfolder ".sync" which is created near binary.

 

THanks.

 

There is no core dump created.  Do I need to do anything to cause the core dump to happen?

 

Cheers

Share this post


Link to post
Share on other sites

igboo,

 

Please do the following:

-open console, run command "ulimit -c unlimited"

-run btsync with "--nodaemon" switch.

When btsync exits - please see the core dump file in btsync directory.

 

Thanks!

Share this post


Link to post
Share on other sites

igboo,

 

Please do the following:

-open console, run command "ulimit -c unlimited"

-run btsync with "--nodaemon" switch.

When btsync exits - please see the core dump file in btsync directory.

 

Thanks!

 

Still no core dump.  I got this on the console:

# ./btsync --nodaemontotal physical memory -1 max disk cache 2097152Using IP address 192.168.1.102test sha1: AE5B  <cut>test sha2: 630D <cut>test aes: 0A94 <cut>./btsync: relocation error: ./btsync: symbol __res_iclose, version GLIBC_PRIVATE     not defined in file libc.so.6 with link time reference

Share this post


Link to post
Share on other sites

@German Users:

 

On most "FritzBox" Routers by AVM runs a modified Linux. Did anybody manage to get BTSync run on a FritzBox?

You can gain access per Telnet/SSH to the Box, so that should propably work? New FritzBoxes have a USB-Port and support external Drives natively, so a lot of German Users could easyly get an always-on Client without any additional Hardware?

Share this post


Link to post
Share on other sites

Netgear ReadyNAS 104 running Firmware 6.1.6

 

Installed BitTorrent Sync from App list on the ReadyNAS, access GUI setup via ip address on the LAN.  Very, very straight forward, so far this has been much easier that the Netgear software ReadyDrop or ReadyNAS Remote.

 

Bob Williamson

Share this post


Link to post
Share on other sites

igboo,

 

It looks like your glibc version is too old. Try checking glibc version, we have a special build for linux with glibc 2.3 the oldest on our download site.

 

To find the glibc version you can run "ldd --version" command or find your libc.so.* file and running it.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now