xineru

New Members
  • Content Count

    2
  • Joined

  • Last visited

About xineru

  • Rank
    New User
  1. 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) http://ffp.inreto.de/ffp/0.7/arm/fun_plug.tgz 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'
  2. 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