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

mfpockets wrote:

Hi,

I tried to follow install option 3a:

3-a) Just want to try Alt-F every now and then:
    Download Alt-F-<version>.tar and fun_plug, rename the downloaded
    fun_plug to, e.g, alt-f.sh, put them in your box root directory, and
    execute alt-f.sh from the shell command line.

    Your ffp directory, if found in the root directory of any filesystem
    of your disk, will be recognized and used by Alt-F. The ffp init script
    will be executed by Alt-F on boot, but you should disable all non needed
    ffp init scripts, disable loading of kernel modules, and only keep services that
    Alt-F don't have.
    Alt-F binaries have precedence over ffp ones.

But when I load the script it reboots the machine, I loose SSH and Telnet access, and browsing to http://mynasip shows me the orignal D-link webpage.  When I reboot, I get access to my ssh again because the script is set to only run 1x.  I read that FFP could be getting in the way of things and taking up too much memory on boot, so I tried to chmod 000 my fun_plug file so it wouldnt be executable on reboot and only the altf.sh file would boot, but this showed the same results. and then I needed to recopy a fun_plug file with 777 rights to get access to my ffp stuff again. 

It did untar the tarball and make a alt-f folder on the drive root, but it doenst seem to run alt-f on top of the vendor firmware like it is supposed to.

Am I doing something wrong?  can someone steer me in the right direction? I also cant seem to find any log files for altf

You are doing nothing wrong. Please read this post:
http://dns323.kood.org/forum/viewtopic. … 522#p40522

Renaming or removing the ffp fun_plug is not enough, you have also to rename the ffp directory:
  mv fun_plug fun_plug-safe
  mv ffp ffp-safe

This is because Alt-F tries to run the /ffp/etc/rc script if it finds it at the root of any filesystem. If by hazard some ffp service or kernel module conflicts with Alt-F you might have a problem.

But you should find at least a "alt-f-reloaded.log" file in /mnt/HD_a2

mfpockets wrote:

Thanks I will attempt this now and report back.

When you say this: But you should find at least a "alt-f-reloaded.log" file in /mnt/HD_a2

Do you mean I should already see one before I try what you suggested?

Because I have no log. In fact if I search my NAS (through windows file explorer) It doesnt find any files with the word reload in it.

So I tried this, and then ran my alt-f script, the system disconnected me from SSH, and now I can't access anything, the web page, ssh, telnet... and holding the power button doesnt shut down.... is it safe to unplug and turn back on?

So I can confirm that prior to tryng the mv ffp ... that no script file had ever been created after my description of several attempts in my first post. 

After turning the unit off and back on there was a script file.  No errors really clearly listed though.  I tried the script again and it is now doing the heartbeat with the LED so it will take a while as its a 1.5tb that is almost full.

Will report back on if it works.

Thanks!

mfpockets wrote:

Took a while, but it works.  I would say it took almost 1 hour to finish the drive check though.

Checking filesystems is a necessary curse.
The initial dlink firmware didn't did it, although recent versions allow you to do it (manually I suppose).
Not doing a filesystem check check every now and then allows errors to grow, compromising most of a disk data.
Errors can appear for a variety of reasons, such as a power failure when there are disk operations occurring, or pulling the power cord when the system hangs :-)

Alt-F warns you with several days (or mount operations)  of antecedence whenever a check must be done, in order for you to do it timely, instead of having to wait for the check to complete when you most need the box (Murphy Law, I know you know it).
You can also specify the periodicity of filesystem checks -- even disable them entirely -- the data is yours.

Next time you won't need to wait so long for Alt-F to boot.

Last edited by jcard (2011-01-15 03:23:02)