DSM-G600, DNS-3xx and NSA-220 Hack Forum

fonz wrote:

rcblackwell wrote:

I'm unable to locate the /.bootstrap directory or the setup.sh file within fun_plug.tgz or packages available from http://www.inreto.de/dns323/fun-plug/0.5/.

It's not included. The idea is that you can place ffp wherever you like, and create your custom .bootstrap/setup.sh to locate and mount it.

I'm pleading insanity

Try as I may I can't seem to get my setup.sh script to work properly. As indicated by the following error the problem appears to be with the grep command

Wed Sep 10 20:38:59 GMT 2008
* Running /mnt/HD_a2/.bootstrap/setup.sh ...
grep: illegal option -- w
BusyBox v1.00-pre1 (2007.12.10-08:03+0000) multi-call binary

Usage: grep [-ihHnqvs] PATTERN [FILEs...]


Here's my setup.sh script.

#!/bin/sh

usbdisk_mount_options="-t auto"
usbdisk_dev="sdc1"
usbdisk_name="USB"
usbdisk_mountp="/mnt/HD_a2/$usbdisk_name"

insmod /mnt/HD_a2/ffp/lib/modules/$(uname -r)/usb-storage.ko #2>/dev/null
sleep 2
lsmod | grep -w usb_storage #>/dev/null 2>/dev/null
if [ $? -ne 0 ]; then
    echo "Success - usb-storage.ko module loaded."

    # wait for disk...
    grep -w $usbdisk_dev /proc/partitions #>/dev/null 2>/dev/null
    if [ $? -ne 0 ]; then
        let timeout=90
        echo "Waiting for $usbdisk_dev (up to $timeout seconds) ..."
        while [ $timeout -gt 0 ]; do
            grep -w $usbdisk_dev /proc/partitions #>/dev/null 2>/dev/null
            [ $? -eq 0 ] && break
            sleep 2
            let timeout=${timeout}-2
            echo $timeout
        done
        grep -w $usbdisk_dev /proc/partitions #>/dev/null 2>/dev/null
        if [ $? -ne 0 ]; then
            echo "Failed. Did not find $usbdisk_dev in /proc/partitions."
    #        exit 1
        fi
    fi

    # mount it
    mkdir -p $usbdisk_mountp
    echo "Mounting /dev/$usbdisk_dev on $usbdisk_mountp"
    mount $usbdisk_mount_options /dev/$usbdisk_dev $usbdisk_mountp >$usbdisk_mountp/mount-error.txt 2>&1
    if [ $? -ne 0 ]; then
        echo "Failed"
        cat $usbdisk_mountp/mount-error.txt
    fi
else
    echo "Warning - usb-storage.ko module failed to load!"
fi

Any assistance that's offered would be greatly appreciated.

Last edited by rcblackwell (2008-09-11 03:46:59)

luusac wrote:

Can it be that you are using an old version of busybox that does not support the -w option, i.e. the fun_plug is not finding the later version on disk?

Of course, he is. setup.sh is run very early, and PATH doesn't include /ffp/sbin or /ffp/bin. Bob, your options: a) only use commands that work with the unmodified firmware, b) add 'PATH=/ffp/sbin:/ffp/bin:$PATH' to your script. From then on, you'll have the ffp versions of the commands available.

fonz wrote:

luusac wrote:

Can it be that you are using an old version of busybox that does not support the -w option, i.e. the fun_plug is not finding the later version on disk?

Of course, he is. setup.sh is run very early, and PATH doesn't include /ffp/sbin or /ffp/bin.

That explains why the script runs fine from the command line but fails when called from fun_plug during boot. I didn't realize the DNS had a different version of BusyBox. Armed with this information I did an Internet search for BusyBox. Low and behold I found the BusyBox website as well as many others dedicated to this tiny exec. All commands and switches are listed thus making it easier for me to see what's available.

I tried option a) but for some reason the script ended up in a loop complaining about not being able to find file paths for some of the other commands. Perhaps I messed something else up when I tried this so I'll give it another whirl!

I learned something new today. Appreciated.

Last edited by rcblackwell (2008-09-11 14:14:14)

fonz wrote:

- consider mounting the usb disk to /mnt/xyz instead of /mnt/HD_a2/xyz (which might prevent proper unmounting of /mnt/HD_a2 on shutdown)
- after successful mount, you should update FFP_PATH to point to the ffp on usb-disk, so fun_plug creates the correct /ffp link

Thank you for the tip on mount location. My old installation of ffp mounted the USB key to /mnt/USB. Since I was modelling this installation on the script provided in /ffp/etc/examples I assumed /mnt/HD_a2/USB would be okay.

In respect to item 2; Thank you; once the script problem was resolved I intended to update FFP_PATH accordingly. In reviewing the fun_plug script I see the ffp symlink is created after calling setup.sh. In my mind it would be better to create this link before calling the setup script then have setup.sh update the link as deemed appropriate.

Sample fun_plug code follows;

....

# create /ffp link
echo "ln -snf $FFP_PATH /ffp"
ln -snf $FFP_PATH /ffp

# check for setup script. an example use for this is to load USB
# kernel modules and mount a USB storage device. The script is
# sourced, that means you can change variables, e.g. FFP_PATH to point
# to the USB device.
if [ -x $FFP_SETUP_SCRIPT ]; then
    echo "* Running $FFP_SETUP_SCRIPT ..."
    . $FFP_SETUP_SCRIPT
fi

....

Sample setup.sh script code follows;

...

# Test for existence of ffp on USB drive
if [ -d /USB/path/to/ffp/exists ]; then
   FFP_PATH="USB/path"
   echo "ln -snf $FFP_PATH /ffp"
   ln -snf $FFP_PATH /ffp
fi

...

# return to fun_plug script

rcblackwell wrote:

I intended to update FFP_PATH accordingly. In reviewing the fun_plug script I see the ffp symlink is created after calling setup.sh. In my mind it would be better to create this link before calling the setup script then have setup.sh update the link as deemed appropriate.

What if there's no ffp at $FFP_PATH? The whole purpose of setup.sh is to locate your ffp installation, so that the correct /ffp link can be created. Note that setup.sh is also run before a fun_plug.tgz tarball is installed. So using setup.sh you can even redirect the initial installation to a usb drive. Ideally, setup.sh doesn't use anything beside firmware tools. In that sense, my suggestion to add /ffp/sbin and /ffp/bin to $PATH in setup.sh was, of course, wrong.

rcblackwell wrote:

fonz wrote:

What if there's no ffp at $FFP_PATH? The whole purpose of setup.sh is to locate your ffp installation, so that the correct /ffp link can be created.

Agreed. The reason for reversing the order in which the symlink and the setup.sh script executed should address this.

Having completed a working script I know see that I originally misunderstood the approach. Using the following code (setup.sh) I'm able to mount a USB drive, set the FFP_PATH then start ffp from the USB drive.

#!/bin/sh

usbdisk_mount_options="-t auto"
usbdisk_dev="sdc1"
usbdisk_name="USB"
usbdisk_mountp="/mnt/$usbdisk_name"

# Load usb-storage module
insmod /mnt/HD_a2/ffp/lib/modules/$(uname -r)/usb-storage.ko

# Test to see if usb-storage module loaded.
/bin/grep -q usb_storage /proc/modules
if [ $? -eq 0 ]; then
    # Announce Successful load of usb-storage.ko
    echo "Success - usb-storage.ko module loaded."

    #  Wait for disk to initialize.
    let timeout=60
    while [ $timeout -gt 0 ]; do
    echo "Waiting $timeout seconds for $usbdisk_dev to initialize."
        /bin/grep -q $usbdisk_dev /proc/partitions
        [ $? -eq 0 ] && break
        sleep 2
        let timeout=${timeout}-2
    done
    /bin/grep -q $usbdisk_dev /proc/partitions
    if [ $? -eq 0 ]; then
        # Disk found. Attempt to create mount point.
        mkdir -p $usbdisk_mountp
        echo "Mounting /dev/$usbdisk_dev on $usbdisk_mountp"
        mount $usbdisk_mount_options /dev/$usbdisk_dev $usbdisk_mountp >$usbdisk_mountp/mount-error.txt 2>&1
        if [ $? -eq 0 ]; then
            echo "Success - /dev/$usbdisk_dev mounted as $usbdisk_mountp."
            # Test for existence of ffp on USB drive
            if [ -d $usbdisk_mountp/ffp ]; then
                # Establish path to symlink
                FFP_PATH="$usbdisk_mountp/ffp"
            fi            
        else
            echo "Warning - failed to mount /dev/$usbdisk_dev!"
            cat $usbdisk_mountp/mount-error.txt
        fi
    else
        echo "Warning - failed to mount /dev/$usbdisk_dev. Did not find $usbdisk_dev in /proc/partitions!"        
    fi
else
    # Storage module failed to load. Write error to ffp.log.
    echo "Warning - failed to load usb-storage.ko module!"
fi

With this script if the USB drive fails to initialize operation of ffp falls back to /mnt/HD_a2/ffp.  To ensure file synchronization between /mnt/USB/ffp and /mnt/HD_a2/ffp a cronjob that runs rsync at 5:55 am each day has been added to crontab. The cron job is added to crontab through addition of the following to the fun_plug.local file;

##################################
#  Add required jobs to crontab  #
##################################
CRONTXT=/mnt/HD_a2/crontab.txt

# start with existing crontab
/bin/crontab -l > $CRONTXT

# add Rsync job; keep ffp on USB drive in sync with ffp on HD_a2
# /bin/echo "55 5 * * * /ffp/bin/rsync -av --delete /mnt/USB/ffp /mnt/HD_a2" >> $CRONTXT

# install the new crontab
/bin/crontab $CRONTXT

# clean up
/bin/rm $CRONTXT
##################################

Last edited by rcblackwell (2008-09-14 03:38:52)

krimb1 wrote:

Though my disk shows when I run 'mount', under 'df' I don't see the mounted drive listed. Is this normal?

I don't think so as "df" on my machine shows the USB drive

df
Filesystem           1k-blocks      Used Available Use% Mounted on
rootfs                    9911      7478      1921  80% /
/dev/root                 9911      7478      1921  80% /
/dev/loop0                5760      5760         0 100% /sys/crfs
/dev/sda2            306636052 235418216  71217836  77% /mnt/HD_a2
/dev/sdb2            960404324 404405596 555998728  42% /mnt/HD_b2
/dev/sda4               497861      1369    496492   0% /mnt/HD_a4
/dev/sdb4               497861         5    497856   0% /mnt/HD_b4
/dev/sdc1              1982064    388100   1493280  21% /mnt/USB

krimb1 wrote:

Would it be possible to mount via UUID instead? I've attached my (pathetic ) attempt, but it hangs on:

Don't be so hard on yourself. There's nothing pathetic about your script.

I think it would be possible to use UUID. I seem to recall trying UUID however it was so long ago I don't recall what the the results were.

krimb1 wrote:

Code:

#!/ffp/bin/sh

I see you've referenced ffp in your script. I do recall having an issue with used

!/bin/sh

At this point in the boot process the ffp links hasn't been established thus

#!/ffp/bin/sh

isn't available.

Last edited by rcblackwell (2009-05-30 22:50:01)

rcblackwell wrote:

To ensure file synchronization between /mnt/USB/ffp and /mnt/HD_a2/ffp a cronjob that runs rsync at 5:55 am each day has been added to crontab.
...

As I'm trying to troubleshoot my UUID script, I was looking at your very nice rsync script in the meantime. I tried reading the rsync manpage but I was left a little confused.

My question is: which directory is the primary (source) and which is the secondary (backup destination)? Is (a) /mnt/HD_a2/ffp backed up to /mnt/USB/ffp nightly, or (b) vice-versa, or (c) are they somehow backed up equally??

Thanks for all the sharing of scripts, bu tboth of them don't work for me. I keep getting errors on the grep and blkid commands, probably because they are not yet available from setup.sh.

rcblackwell script:

/bin/grep: illegal option -- o

This is proboable because of the PATH thing fonz talks about.

krimb1 script:

/mnt/HD_a2/.bootstrap/setup.sh: /mnt/HD_a2/ffp/sbin/blkid: No such file or directory


Maybe same reason.

Adding /ffp/sbin and /ffp/bin to path (or /mnt/HD_a2/ffp/bin and /mnt/HD_a2/sbin) didn't help. Using hardcoded paths in the script didn't help either.

How did manage to solve this?

Opperpanter wrote:

krimb1 script:

/mnt/HD_a2/.bootstrap/setup.sh: /mnt/HD_a2/ffp/sbin/blkid: No such file or directory
.....
How did manage to solve this?

Regarding http://dns323.kood.org/forum/viewtopic. … 573#p14573 (thanks SilentException) you need to add something like this:

ln -snf $FFP_PATH /ffp

before blkid call

PS. You need ffp installed on HDD.

Last edited by mike7 (2010-08-21 07:54:19)