General NAS-Central Forums

Welcome to the NAS community
It is currently Mon Mar 27, 2017 4:33 pm

All times are UTC




Post new topic Reply to topic  [ 13 posts ] 
Author Message
PostPosted: Tue Feb 04, 2014 2:25 pm 
Offline

Joined: Mon Feb 03, 2014 11:52 pm
Posts: 9
I am attempting to load the FFP to a 1GB usb stick for my NSA210. Currently I am running firmware V4.40(AFD.2).

When I try to follow the steps to format the drive by adding files and then rebooting, I get nothing. So instead I went to volume web page and tried to create a ext3 drive. I get an error.
So instead I tried to create an ext2 drive, success. The two files I downloaded are FFPStick-2013-11-24.zip and ffp_for_NSA-220.3.zip. I have tried putting every combination of the files possible in the directions and rebooting. I still get the same files.

Update: formatted the usb drive in Lubuntu

First question, when the directions say make the file executable how am I suppose to accomplish this?

Next, I have downloaded the web_prefix file and moved it into the zyfx directory but I am lost as to what to do next to get the server to look to a secondary repository for the packages. So I downloaded the ffp_0.7_arm_003.zpkg file and moved it into the zy-pkgs directory. Reboot. Still nothing.

Moved the web_prefix file into the admin\zyfw directory but the ffp package never shows up.

Hopefully, I can get some help. Usually, I am pretty good with this stuff but I am just lost following the directions given. I really appreciate a pointer to get me going.

Thinking of selling this NSA210 and upgrading to the NSA310 if that is what it takes


Top
 Profile  
 
PostPosted: Thu Feb 06, 2014 9:04 pm 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 5973
Yesterday you wrote that your stick was repartitioned by the ffp-stick scripts. Did it contain any logfile on the FAT partition?

About the web_prefix file, you should only put it in \\<nas>\admin\zypkgs, and then press the 'update package list' button in the administration menu in the webinterface. Make sure the file doesn't have an extension.


Top
 Profile  
 
PostPosted: Fri Feb 07, 2014 12:28 am 
Offline

Joined: Mon Feb 03, 2014 11:52 pm
Posts: 9
Thanks for answering. Your the resident expert and super glad you saw my sos. I had a logfile but I have tried the install many times using two 1GB sticks. Will retry and post a logfile.

I put the web_prefix file in the folder and get nothing different. Done it again and again too.

Thanks again.


Top
 Profile  
 
PostPosted: Fri Feb 07, 2014 1:04 am 
Offline

Joined: Mon Feb 03, 2014 11:52 pm
Posts: 9
Here is what I get when I try to let the NSA210 format the usb stick to create both partitions. Note when I try to format as ext3 manually it also will not let me. Which is why I just said screw it and used my lubuntu gparted before.

Rotating logfiles...
Script fun_plug.sh version 20120901 running from /mnt/parnerkey
ffpstick started at Fri Feb 7 00:54:39 GMT 2014
Try to determine NAS type...
according to /zyxel/mnt/info/modelid: D401->NSA210
type NSA210, fw 4.40(AFD.2)
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...
cp: write error: No space left on device
Copied usb_key_func.sh nsa210_check_file md5sum nsa220_check_file salted_md5sum salted_md5sum_3x0 STG100_check_file STG211_check_file STG212_check_file mkdosfs after_booting.sh rootfs.tgz fun_plug.sh
*Not* copied fun_plug.tgz
Script fun_plug.sh version 20120901 running from /tmp/.ffpstick
Repartition /dev/sdb
unmount /mnt/parnerkey...done
Repartitioning...

Command (m for help): Building a new DOS disklabel. Changes will remain in memory only,
until you decide to write them. After that the previous content
won't be recoverable.


Command (m for help): Command action
e extended
p primary partition (1-4)
Partition number (1-4): First cylinder (1-972, default 1): Using default value 1
Last cylinder or +size or +sizeM or +sizeK (1-972, default 972):
Command (m for help): Command action
e extended
p primary partition (1-4)
Partition number (1-4): First cylinder (17-972, default 17): Using default value 17
Last cylinder or +size or +sizeM or +sizeK (17-972, default 972): Using default value 972

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
Done. Creating and mounting filesystems...
Create ext3 filesystem on /dev/sdb2 and mount...
Filesystem label=FFPROOT
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
62208 inodes, 248440 blocks
12422 blocks (5%) reserved for the super user
First data block=0
Maximum filesystem blocks=4194304
8 block groups
32768 blocks per group, 32768 fragments per group
7776 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376
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...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...salted_md5sum...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 20120901 running from /mnt/parnerkey
ffpstick started at Fri Feb 7 00:55:10 GMT 2014
Try to determine NAS type...
according to /zyxel/mnt/info/modelid: D401->NSA210
type NSA210, fw 4.40(AFD.2)
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 NSA210 -f "4.40(AFD.2)" -r no -l &
Script fun_plug.sh version 20120901 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/info...
probe /zyxel/mnt/sysdisk...
probe /usr/local/etc...
probe /usr/local/var...
probe /usr/local/dmsf...
probe /etc/zyxel...
probe /i-data/b577baa0...
probe /e-data/52F4-2EED...
found ffpstick on /e-data/52F4-2EED, moving logfile
probe /e-data/0ba3bc0b-076c-4726-8fc9-ebef9a459bd0...
probe /usr/local/zy-pkgs...
No /anymountpoint/ffproot/after_booting.sh found
Probe all mount points 10 seconds...
probe /proc/bus/usb...
probe /dev/pts...
probe /zyxel/mnt/info...
probe /zyxel/mnt/sysdisk...
probe /usr/local/etc...
probe /usr/local/var...
probe /usr/local/dmsf...
probe /etc/zyxel...
probe /i-data/b577baa0...
probe /e-data/52F4-2EED...
probe /e-data/0ba3bc0b-076c-4726-8fc9-ebef9a459bd0...
probe /usr/local/zy-pkgs...
probe /etc/zyxel/zy-pkgs...
probe /usr/local/apache/htdocs/zyxel/pkg...
probe /proc/fs/nfsd...
probe /usr/local/apache/web_framework/data/cache...
probe /usr/local/apache/web_framework/data/config...
No /anymountpoint/ffproot/after_booting.sh found
Probe all mount points 20 seconds...
probe /proc/bus/usb...
probe /dev/pts...
probe /zyxel/mnt/info...
probe /zyxel/mnt/sysdisk...
probe /usr/local/etc...
probe /usr/local/var...
probe /usr/local/dmsf...
probe /etc/zyxel...
probe /i-data/b577baa0...
probe /e-data/52F4-2EED...
probe /e-data/0ba3bc0b-076c-4726-8fc9-ebef9a459bd0...
probe /usr/local/zy-pkgs...
probe /etc/zyxel/zy-pkgs...
probe /usr/local/apache/htdocs/zyxel/pkg...
probe /proc/fs/nfsd...
probe /usr/local/apache/web_framework/data/cache...
probe /usr/local/apache/web_framework/data/config...
No /anymountpoint/ffproot/after_booting.sh found
Probe all mount points 30 seconds...
probe /proc/bus/usb...
probe /dev/pts...
probe /zyxel/mnt/info...
probe /zyxel/mnt/sysdisk...
probe /usr/local/etc...
probe /usr/local/var...
probe /usr/local/dmsf...
probe /etc/zyxel...
probe /i-data/b577baa0...
probe /e-data/52F4-2EED...
probe /e-data/0ba3bc0b-076c-4726-8fc9-ebef9a459bd0...
probe /usr/local/zy-pkgs...
probe /etc/zyxel/zy-pkgs...
probe /usr/local/apache/htdocs/zyxel/pkg...
probe /proc/fs/nfsd...
probe /usr/local/apache/web_framework/data/cache...
probe /usr/local/apache/web_framework/data/config...
No /anymountpoint/ffproot/after_booting.sh found
Probe all mount points 40 seconds...
probe /proc/bus/usb...
probe /dev/pts...
probe /zyxel/mnt/info...
probe /zyxel/mnt/sysdisk...
probe /usr/local/etc...
probe /usr/local/var...
probe /usr/local/dmsf...
probe /etc/zyxel...
probe /i-data/b577baa0...
probe /e-data/52F4-2EED...
probe /e-data/0ba3bc0b-076c-4726-8fc9-ebef9a459bd0...
probe /usr/local/zy-pkgs...
probe /etc/zyxel/zy-pkgs...
probe /usr/local/apache/htdocs/zyxel/pkg...
probe /proc/fs/nfsd...
probe /usr/local/apache/web_framework/data/cache...
probe /usr/local/apache/web_framework/data/config...
No /anymountpoint/ffproot/after_booting.sh found
Probe all mount points 50 seconds...
probe /proc/bus/usb...
probe /dev/pts...
probe /zyxel/mnt/info...
probe /zyxel/mnt/sysdisk...
probe /usr/local/etc...
probe /usr/local/var...
probe /usr/local/dmsf...
probe /etc/zyxel...
probe /i-data/b577baa0...
probe /e-data/52F4-2EED...
probe /e-data/0ba3bc0b-076c-4726-8fc9-ebef9a459bd0...
probe /usr/local/zy-pkgs...
probe /etc/zyxel/zy-pkgs...
probe /usr/local/apache/htdocs/zyxel/pkg...
probe /proc/fs/nfsd...
probe /usr/local/apache/web_framework/data/cache...
probe /usr/local/apache/web_framework/data/config...
No /anymountpoint/ffproot/after_booting.sh found
Probe all mount points 60 seconds...
probe /proc/bus/usb...
probe /dev/pts...
probe /zyxel/mnt/info...
probe /zyxel/mnt/sysdisk...
probe /usr/local/etc...
probe /usr/local/var...
probe /usr/local/dmsf...
probe /etc/zyxel...
probe /i-data/b577baa0...
probe /e-data/52F4-2EED...
probe /e-data/0ba3bc0b-076c-4726-8fc9-ebef9a459bd0...
probe /usr/local/zy-pkgs...
probe /etc/zyxel/zy-pkgs...
probe /usr/local/apache/htdocs/zyxel/pkg...
probe /proc/fs/nfsd...
probe /usr/local/apache/web_framework/data/cache...
probe /usr/local/apache/web_framework/data/config...
No /anymountpoint/ffproot/after_booting.sh found
60 seconds should be enough for anybody ;)
Will try to mount ffproot myself
Probe all mount points 70 seconds...
probe /proc/bus/usb...
probe /dev/pts...
probe /zyxel/mnt/info...
probe /zyxel/mnt/sysdisk...
probe /usr/local/etc...
probe /usr/local/var...
probe /usr/local/dmsf...
probe /etc/zyxel...
probe /i-data/b577baa0...
probe /e-data/52F4-2EED...
probe /e-data/0ba3bc0b-076c-4726-8fc9-ebef9a459bd0...
probe /usr/local/zy-pkgs...
probe /etc/zyxel/zy-pkgs...
probe /usr/local/apache/htdocs/zyxel/pkg...
probe /proc/fs/nfsd...
probe /usr/local/apache/web_framework/data/cache...
probe /usr/local/apache/web_framework/data/config...
probe /tmp/ffproot...
No /anymountpoint/ffproot/after_booting.sh found
Probe all mount points 80 seconds...
probe /proc/bus/usb...
probe /dev/pts...
probe /zyxel/mnt/info...
probe /zyxel/mnt/sysdisk...
probe /usr/local/etc...
probe /usr/local/var...
probe /usr/local/dmsf...
probe /etc/zyxel...
probe /i-data/b577baa0...
probe /e-data/52F4-2EED...
probe /e-data/0ba3bc0b-076c-4726-8fc9-ebef9a459bd0...
probe /usr/local/zy-pkgs...
probe /etc/zyxel/zy-pkgs...
probe /usr/local/apache/htdocs/zyxel/pkg...
probe /proc/fs/nfsd...
probe /usr/local/apache/web_framework/data/cache...
probe /usr/local/apache/web_framework/data/config...
probe /tmp/ffproot...
No /anymountpoint/ffproot/after_booting.sh found
Probe all mount points 90 seconds...
probe /proc/bus/usb...
probe /dev/pts...
probe /zyxel/mnt/info...
probe /zyxel/mnt/sysdisk...
probe /usr/local/etc...
probe /usr/local/var...
probe /usr/local/dmsf...
probe /etc/zyxel...
probe /i-data/b577baa0...
probe /e-data/52F4-2EED...
probe /e-data/0ba3bc0b-076c-4726-8fc9-ebef9a459bd0...
probe /usr/local/zy-pkgs...
probe /etc/zyxel/zy-pkgs...
probe /usr/local/apache/htdocs/zyxel/pkg...
probe /proc/fs/nfsd...
probe /usr/local/apache/web_framework/data/cache...
probe /usr/local/apache/web_framework/data/config...
probe /tmp/ffproot...
No /anymountpoint/ffproot/after_booting.sh found
Probe all mount points 100 seconds...
probe /proc/bus/usb...
probe /dev/pts...
probe /zyxel/mnt/info...
probe /zyxel/mnt/sysdisk...
probe /usr/local/etc...
probe /usr/local/var...
probe /usr/local/dmsf...
probe /etc/zyxel...
probe /i-data/b577baa0...
probe /e-data/52F4-2EED...
probe /e-data/0ba3bc0b-076c-4726-8fc9-ebef9a459bd0...
probe /usr/local/zy-pkgs...
probe /etc/zyxel/zy-pkgs...
probe /usr/local/apache/htdocs/zyxel/pkg...
probe /proc/fs/nfsd...
probe /usr/local/apache/web_framework/data/cache...
probe /usr/local/apache/web_framework/data/config...
probe /tmp/ffproot...
No /anymountpoint/ffproot/after_booting.sh found
Probe all mount points 110 seconds...
probe /proc/bus/usb...
probe /dev/pts...
probe /zyxel/mnt/info...
probe /zyxel/mnt/sysdisk...
probe /usr/local/etc...
probe /usr/local/var...
probe /usr/local/dmsf...
probe /etc/zyxel...
probe /i-data/b577baa0...
probe /e-data/52F4-2EED...
probe /e-data/0ba3bc0b-076c-4726-8fc9-ebef9a459bd0...
probe /usr/local/zy-pkgs...
probe /etc/zyxel/zy-pkgs...
probe /usr/local/apache/htdocs/zyxel/pkg...
probe /proc/fs/nfsd...
probe /usr/local/apache/web_framework/data/cache...
probe /usr/local/apache/web_framework/data/config...
probe /tmp/ffproot...
No /anymountpoint/ffproot/after_booting.sh found
Probe all mount points 120 seconds...
probe /proc/bus/usb...
probe /dev/pts...
probe /zyxel/mnt/info...
probe /zyxel/mnt/sysdisk...
probe /usr/local/etc...
probe /usr/local/var...
probe /usr/local/dmsf...
probe /etc/zyxel...
probe /i-data/b577baa0...
probe /e-data/52F4-2EED...
probe /e-data/0ba3bc0b-076c-4726-8fc9-ebef9a459bd0...
probe /usr/local/zy-pkgs...
probe /etc/zyxel/zy-pkgs...
probe /usr/local/apache/htdocs/zyxel/pkg...
probe /proc/fs/nfsd...
probe /usr/local/apache/web_framework/data/cache...
probe /usr/local/apache/web_framework/data/config...
probe /tmp/ffproot...
No /anymountpoint/ffproot/after_booting.sh found
Probe all mount points 130 seconds...
probe /proc/bus/usb...
probe /dev/pts...
probe /zyxel/mnt/info...
probe /zyxel/mnt/sysdisk...
probe /usr/local/etc...
probe /usr/local/var...
probe /usr/local/dmsf...
probe /etc/zyxel...
probe /i-data/b577baa0...
probe /e-data/52F4-2EED...
probe /e-data/0ba3bc0b-076c-4726-8fc9-ebef9a459bd0...
probe /usr/local/zy-pkgs...
probe /etc/zyxel/zy-pkgs...
probe /usr/local/apache/htdocs/zyxel/pkg...
probe /proc/fs/nfsd...
probe /usr/local/apache/web_framework/data/cache...
probe /usr/local/apache/web_framework/data/config...
probe /tmp/ffproot...
No /anymountpoint/ffproot/after_booting.sh found
Probe all mount points 140 seconds...
probe /proc/bus/usb...
probe /dev/pts...
probe /zyxel/mnt/info...
probe /zyxel/mnt/sysdisk...
probe /usr/local/etc...
probe /usr/local/var...
probe /usr/local/dmsf...
probe /etc/zyxel...
probe /i-data/b577baa0...
probe /e-data/52F4-2EED...
probe /e-data/0ba3bc0b-076c-4726-8fc9-ebef9a459bd0...
probe /usr/local/zy-pkgs...
probe /etc/zyxel/zy-pkgs...
probe /usr/local/apache/htdocs/zyxel/pkg...
probe /proc/fs/nfsd...
probe /usr/local/apache/web_framework/data/cache...
probe /usr/local/apache/web_framework/data/config...
probe /tmp/ffproot...
No /anymountpoint/ffproot/after_booting.sh found


Top
 Profile  
 
PostPosted: Fri Feb 07, 2014 5:49 am 
Offline

Joined: Mon Feb 03, 2014 11:52 pm
Posts: 9
This is from the lubuntu fat16/ext3 usb drive when i move files to fat16 then reboot.

Rotating logfiles...
Script fun_plug.sh version 20131124 running from /mnt/parnerkey
ffpstick started at Fri Feb 7 05:43:09 GMT 2014
Try to determine NAS type...
according to /zyxel/mnt/info/modelid: D401->NSA210
type NSA210, fw 4.40(AFD.2)
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 2 partitions
Copy myself to /tmp...And execute...
/tmp/.ffpstick/fun_plug.sh BackgroundPolling -d /dev/sdb -n NSA210 -f "4.40(AFD.2)" -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/info...
probe /zyxel/mnt/sysdisk...
probe /usr/local/etc...
probe /usr/local/var...
probe /usr/local/dmsf...
probe /etc/zyxel...
probe /i-data/b577baa0...
probe /e-data/FEF4-219D...
found ffpstick on /e-data/FEF4-219D, moving logfile
probe /usr/local/zy-pkgs...
probe /etc/zyxel/zy-pkgs...
probe /usr/local/apache/htdocs/zyxel/pkg...
probe /e-data/f7b55a2e-1edc-43d0-9341-69380c92c508...
No /anymountpoint/ffproot/after_booting.sh found
Probe all mount points 10 seconds...
probe /proc/bus/usb...
probe /dev/pts...
probe /zyxel/mnt/info...
probe /zyxel/mnt/sysdisk...
probe /usr/local/etc...
probe /usr/local/var...
probe /usr/local/dmsf...
probe /etc/zyxel...
probe /i-data/b577baa0...
probe /e-data/FEF4-219D...
probe /usr/local/zy-pkgs...
probe /etc/zyxel/zy-pkgs...
probe /usr/local/apache/htdocs/zyxel/pkg...
probe /e-data/f7b55a2e-1edc-43d0-9341-69380c92c508...
probe /proc/fs/nfsd...
probe /usr/local/apache/web_framework/data/cache...
probe /usr/local/apache/web_framework/data/config...
No /anymountpoint/ffproot/after_booting.sh found
Probe all mount points 20 seconds...
probe /proc/bus/usb...
probe /dev/pts...
probe /zyxel/mnt/info...
probe /zyxel/mnt/sysdisk...
probe /usr/local/etc...
probe /usr/local/var...
probe /usr/local/dmsf...
probe /etc/zyxel...
probe /i-data/b577baa0...
probe /e-data/FEF4-219D...
probe /usr/local/zy-pkgs...
probe /etc/zyxel/zy-pkgs...
probe /usr/local/apache/htdocs/zyxel/pkg...
probe /e-data/f7b55a2e-1edc-43d0-9341-69380c92c508...
probe /proc/fs/nfsd...
probe /usr/local/apache/web_framework/data/cache...
probe /usr/local/apache/web_framework/data/config...
No /anymountpoint/ffproot/after_booting.sh found
Probe all mount points 30 seconds...
probe /proc/bus/usb...
probe /dev/pts...
probe /zyxel/mnt/info...
probe /zyxel/mnt/sysdisk...
probe /usr/local/etc...
probe /usr/local/var...
probe /usr/local/dmsf...
probe /etc/zyxel...
probe /i-data/b577baa0...
probe /e-data/FEF4-219D...
probe /usr/local/zy-pkgs...
probe /etc/zyxel/zy-pkgs...
probe /usr/local/apache/htdocs/zyxel/pkg...
probe /e-data/f7b55a2e-1edc-43d0-9341-69380c92c508...
probe /proc/fs/nfsd...
probe /usr/local/apache/web_framework/data/cache...
probe /usr/local/apache/web_framework/data/config...
No /anymountpoint/ffproot/after_booting.sh found


Top
 Profile  
 
PostPosted: Fri Feb 07, 2014 10:31 am 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 5973
This is very strange. The file 'after_booting.sh' is on first creation of the stick moved to ext2partition\ffproot\, and the partition is umounted. Then the script starts polling for the operating system to mount it, and it knows it is mounted by the existence of that (executable) file.
The partition is mounted as /e-data/0ba3bc0b-076c-4726-8fc9-ebef9a459bd0, but apparently the check
Code:
if [ -x /e-data/0ba3bc0b-076c-4726-8fc9-ebef9a459bd0/ffproot/after_booting.sh ] ; then
fails.

Can you have a look if that file exists, and if it's executable? This is only the case for an automatically generated stick. If you create it manually, you'll have to put after_booting.sh and rootfs.tgz in a map ffproot. The script should be executable.


Top
 Profile  
 
PostPosted: Fri Feb 07, 2014 11:28 am 
Offline

Joined: Mon Feb 03, 2014 11:52 pm
Posts: 9
Yes the file is there in the fat directory. Two followup questions. One, change the permissions in lubuntu right? And two, when you say put it in a map. You mean a map dir from windows?


Last edited by rigel1326 on Fri Feb 07, 2014 12:24 pm, edited 1 time in total.

Top
 Profile  
 
PostPosted: Fri Feb 07, 2014 12:23 pm 
Offline

Joined: Mon Feb 03, 2014 11:52 pm
Posts: 9
So I brought both sticks into lubuntu and looked at the permission of the .sh. Non executable but when i goto change it, it wont stick on the usb drive. I can change on deskop of my lubuntu to exe and get it to stick.

update: so it would seem this is a known issue that exe permissions don't transfer to fat usb. how were you able to get around this?


Top
 Profile  
 
PostPosted: Fri Feb 07, 2014 3:08 pm 
Offline

Joined: Mon Feb 03, 2014 11:52 pm
Posts: 9
Can I run this script in lubuntu complete it and then move to the NSA210 server?


Top
 Profile  
 
PostPosted: Fri Feb 07, 2014 6:13 pm 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 5973
rigel1326 wrote:
Yes the file is there in the fat directory. Two followup questions. One, change the permissions in lubuntu right? And two, when you say put it in a map. You mean a map dir from windows?
It *should* be on the ext2 partition, after automatic repartitioning of the stick.
And no, I don't mean a windows map. You partitoned and formatted the stick yourself in Lubuntu, which means you also have to create the directory 'ffproot' on the ext2 partition, and put the files in it.

rigel1326 wrote:
so it would seem this is a known issue that exe permissions don't transfer to fat usb. how were you able to get around this?
Actually FAT doesn't support the executable flag at all. So you can mount a FAT partition two ways, having all files executable, or having all files not executable. Fortunately the NAS mounts it in the 'executable' way, else the initial script wouldn't run at all.

rigel1326 wrote:
Can I run this script in lubuntu complete it and then move to the NSA210 server?
With some tricks this should be possible, yes, but it won't help you, as the script after_booting.sh is supposed to start FFP on each boot. The only special case on the first time is that it first has to download the FFP base package.
If the 'fun_plug.sh' script on the FAT partition can't find it the first time, I guess it cannot find it a 2nd time either.


Top
 Profile  
 
PostPosted: Fri Feb 07, 2014 7:55 pm 
Offline

Joined: Mon Feb 03, 2014 11:52 pm
Posts: 9
Can you have a look if that file exists, and if it's executable? This is only the case for an automatically generated stick. If you create it manually, you'll have to put after_booting.sh and rootfs.tgz in a map ffproot. The script should be executable.

Created a share on the drive called ffproot moved the files above and now i have telnet adding ssh and all that next thanks!!!


Top
 Profile  
 
PostPosted: Sat Feb 08, 2014 12:09 am 
Offline

Joined: Mon Feb 03, 2014 11:52 pm
Posts: 9
Follow up question: what do you need on the stick to stsrtup now that ffp is on the actual drive. I imagine this is the same as installing the package.


Top
 Profile  
 
PostPosted: Sat Feb 08, 2014 8:13 am 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 5973
The same ffproot/after_booting.sh. This script checks if ffp is installed, (by looking at the existence of some file in ffproot/bin/) and if yes, it starts ffp, and if not it downloads and installs ffp and then starts it.

Is your script disappeared again?


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 13 posts ] 

All times are UTC


Who is online

Users browsing this forum: No registered users and 2 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group