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

Hope this isn't taken as being a "spammy" kind of post, but I thought I'd share exact output of 'ps' with both the not-working-boot-launch and the working-manual-launch of chkbutton2.

The two PIDs begin to change with 'crond', though all the same number of processes are present in both. Do you think the order makes any difference?

The beginning is common to both:

PID   USER     COMMAND
    1 root     init                                
    2 root     [ksoftirqd/0]
    3 root     [events/0]
    4 root     [khelper]
    5 root     [kthread]
   11 root     [kblockd/0]
   14 root     [khubd]
   49 root     [pdflush]
   50 root     [pdflush]
   52 root     [aio/0]
   51 root     [kswapd0]
  190 root     [scsi_eh_0]
  191 root     [scsi_eh_1]
  192 root     [scsi_eh_2]
  193 root     [scsi_eh_3]
  204 root     [mtdblockd]
  218 root     [kcryptd/0]
  219 root     [kmirrord/0]
  241 root     [loop0]
 1293 root     atd 
 1298 root     smbd -D 
 1300 root     nmbd -D 
 1308 root     smbd -D 
 1330 root     xmldb -n config 
 1373 root     [md0_raid1]
 1411 root     [kjournald]
 1447 root     [kjournald]
 1515 root     [kjournald]
 1564 root     [kjournald]
 1609 root     /web/webs 
 1625 root     fancontrol 0 
 1645 root     op_server 3 3 3 
 1654 root     -sh 
 1716 root     check_hotplug 
 1720 root     check_daemon

If started at boot via enabling execute permissions /ffp/start:

PID   USER     COMMAND
 1746 root     crond 
 1783 root     pure-ftpd (SERVER)                                                                                                               
 1836 root     lpd Waiting
 1876 root     mserver 
 1877 root     apkg 
 1933 root     [scsi_eh_4]
 1934 root     [usb-storage]
 1942 root     [scsi_eh_5]
 1943 root     [usb-storage]
 1951 root     [scsi_eh_6]
 1952 root     [usb-storage]
 2115 root     /ffp/sbin/syslogd -C100 
 2125 root     /ffp/sbin/klogd -c 3 
 2141 root     /sbin/chkbutton2 /ffp/share/chkbutton2/cleanup.sh /ffp/share/chkbutton2/backup.sh 
 2156 root     /ffp/sbin/sshd 
 2191 root     /ffp/bin/openvpn --daemon --config /ffp/etc/openvpn/server.conf --tls-server 
 2242 root     sshd: root@pts/0  
 2244 root     -sh 
 2261 root     ps

If started manually as root via SSH:

PID   USER     COMMAND
 1783 root     pure-ftpd (SERVER)                                                                                                               
 1836 root     lpd Waiting
 1876 root     mserver 
 1877 root     apkg 
 1933 root     [scsi_eh_4]
 1934 root     [usb-storage]
 1942 root     [scsi_eh_5]
 1943 root     [usb-storage]
 1951 root     [scsi_eh_6]
 1952 root     [usb-storage]
 2115 root     /ffp/sbin/syslogd -C100 
 2125 root     /ffp/sbin/klogd -c 3 
 2156 root     /ffp/sbin/sshd 
 2191 root     /ffp/bin/openvpn --daemon --config /ffp/etc/openvpn/server.conf --tls-server 
 2242 root     sshd: root@pts/0  
 2244 root     -sh 
 2468 root     crond 
 2494 root     /sbin/chkbutton2 /ffp/share/chkbutton2/cleanup.sh /ffp/share/chkbutton2/backup.sh 
 2495 root     ps

You've done everything you could to help, and I'm very appreciative of that.

So right now I've changed my code per your suggestion to:

chkbutton2_start() 
{
        echo "Setting up $name..."
    pid=$(pidof chkbutton)
    if [ "$pid" != "" ]; then
        kill $pid
    fi

    cp $required_files /sbin/
    ln -sf /sbin/chkbutton2 /sbin/reboot2
    ln -sf /sbin/chkbutton2 /sbin/poweroff2
    # proc_start $command
    at now + 10 min<<EOF
    /sbin/chkbutton2
EOF
}

Hope that's correct. I'll post back the results soon.

EDIT: No dice. Weird!

Last edited by krimb1 (2009-06-26 13:46:07)

I noticed the author of the script also created the yafsck.sh script. Is it possible to combine the 2 scripts?
Something like if you keep the button pressed for 12 seconds, it will perform the yafsck script, followed by a reboot, so services like lpd are started again as well?

knireis wrote:

I noticed the author of the script also created the yafsck.sh script. Is it possible to combine the 2 scripts?
Something like if you keep the button pressed for 12 seconds, it will perform the yafsck script, followed by a reboot, so services like lpd are started again as well?

I think it is possible, you have to try it.

Is better to use the scripts associated with the button actions: the reboot/shutdown script and the backup script. You have to use the second, as the first has only 5 secs to do its work.

You can write your own script and customize /ffp/start/chkbutton2.sh, or modify the default and dummy one, /ffp/share/chkbutton2/backup.sh, adding the needed commands. You start it by momentary pressing the box back reset button.

You might have to change yafsck.sh, setting the "doreboot" variable to "yes" -- don't do it if you are using yafsck.sh in the boot mode!!! This was discussed in another thread.

Tradicionaly fsck is done at boot time, not at shutdown time, for obvious reasons. At boot time, If the disk is clean, fsck just takes a couple of seconds to complete, and boot time is not compromised. If the box was not properly shutdown, than you might have to wait a lot of time.
But, even if the disk is clean, every N mounts or M days fsck does a complete check. No free lunch :-)

krimb1 wrote:

Jun 27 18:28:34 dlink-EE65AE user.info kernel:  used obsolete MD ioctl, upgrade your software to use new ictls.
Obsolete ioctl? Isn't mdadm related to RAID configuration? Looking for help.

EDIT: I wanted to test my RAID theory and tried reformatting both my drives to standard partitions, no RAID. Unfortunately I keep getting "Hard Drive(s) Formatting Failure. (Error Code:107)." Do you think this might be related as well?

krimb1,

Being a noob, I'm reluctant to jump in, but since I don't see any other replys...

I've read somewhere here on the forum that the "used obsolete MD ioctl" is a non-issue.  Part of D-Link's firmware, and not a problem.  I think we all have that message (I know I do).  Perhaps you could do a search, and find that post.  Something I noticed, but did not test to find all the "in's and out's" was if funplug was running, I could not "scan drives" or "format" using the 1.08 beta.  Sadly, I also forgot to mention that I am running RAID 1 on my first box, and a single drive on my second (my testing Toaster ).  checkbutton2 runs fine on both boxes.  I don't think this is your problem.

You had asked about how to change the start order of things in the /ffp/start directory.  In each of those ".sh" files, they usually begin with some lines stating PROVIDE, REQUIRE, and BEFORE.  By manipulating these entries, you can move things around.  Be careful!  Always recheck what you've done with rcorder *.sh .  It's possible to muck things up with "circular entries" (things will loop, and never finish).  I have no idea if there are other ramifications to doing this, but I've had no problems myself.

In your spot, I think I'd try narrowing things down.  What isn't causing the problem...  I'd try turning everything off in the /ffp/start first.  Command chmod a-x filename.sh   Of course, you need to leave telnetd (or sshd) running, and the checkbutton2.  If your problem goes away, start re-enabling things, one at a time (chmod a+x filename.sh), perhaps finding the conflict.  If the problem doesn't go away trying this, at least you know it's nothing you are starting here (or the order of starting) that is causing the problem, and you can look elsewhere. 

Being very new to Linux, I am reluctant to post this, but perhaps it may be helpful.

Good Luck!

Jerry

Last edited by Sharp Rock (2009-06-28 19:58:30)

Jcard, just wondering if I overlooked the obvious: do I need to compile chkbutton2 to run on my DNS323? I don't think I did, just ran 'funpkg -i cleanboot2-0.2.tar.gz'.

No, you don't need to recompile it.
The warning is there just in case someone wants to modify it.

Bob, are you by any chance running chkbutton2 on a DNS-323 Rev B? I should mention I'm running on Rev A; is this a problem as well?

Yes, that must be the problem.

SharpRock: I think you were right on with suggesting ffp be disabled for reformatting. My box is now fully reformatted in RAID1 (and JBOD) in EXT3 using the 1.08 beta FW.

jcard: Don't think I can mail my DNS-323 Rev A1 to you so that you can troubleshoot, can I?

Blackwell: Haha, no problem! If you wouldn't mind running syslogd for me that would be a real saver. I'll try the 1.06 firmware and see if I can't get this baby to sleep in the meantime.

EDIT: Just for the record—in 1.08 beta FW on the DNS-323 A1, I cannot get chkbutton2 to sleep the HDs if chkbutton2.sh is executable at start. However if I manually telnet inside and start the script, everything works fine. I don't suppose there's anyway I could "simulate a ssh/telnet login" to login for me; run the script; and exit can I?

Last edited by krimb1 (2009-06-29 02:08:42)

krimb1 wrote:

EDIT: Just for the record—in 1.08 beta FW on the DNS-323 A1, I cannot get chkbutton2 to sleep the HDs if chkbutton2.sh is executable at start. However if I manually telnet inside and start the script, everything works fine. I don't suppose there's anyway I could "simulate a ssh/telnet login" to login for me; run the script; and exit can I?

krimb1, and the group,

Hmmm, I wonder...  If Bob is running checkbutton2 with no issues on hardware A1 +  FW 1.06, why wouldn't it work with a later FW?  The kernals are the same with 1.08beta.  And someone correct me if I'm wrong, the applications in the /ffp/start are the last things to be run.  When they finish, the booting is complete.  So if krimb1 can telnet into the box right after boot and start it manually with no issues, what could be hooking the application, keeping the drives active?  I just took a quick look at checkbutton2.sh.  So a file gets copied to the ramdisk (/sbin), and a couple of symlinks are done.  Then execute.

Thinking out loud.  I'm new, so kick me in the head if I get out of line. 

Is there a boot proccess running in the background on his machine that hasn't finished up when checkbutton2 runs?  I suggest a quick test.  Open up checkbutton2.sh with your favorite linux text editor and add a "sleep 30" to the begining of the script, right under the PROVIDES and BEFORE entries.  Maybe even a sleep 60.  This is an extreme test to see if something in the box has not settled before running checkbutton2.  Reboot with checkbutton2 executable.

Something else to check...  I just looked at my own box.  I can see the checkbutton2 file on the ramdisk in /sbin.  And I can see the symlinks.  krimb1, you might want to see if your script is really executing these commands correctly (when booting with checkbutton2), or is something preventing them from doing so.

Good Luck!

Jerry

EDIT: I just reread the original thread, and found where jcard gave instructions to modify the script to delay start by 10 minutes.  Please disreguard my rambling.

Last edited by Sharp Rock (2009-06-29 04:10:26)

WHOAH! Breakthrough!

Alright, so it's a bit of a hack. But isn't that what fun_plug is?

I still don't know what the heck is causing chkbutton2 not to work properly at boot on 1.08 beta. I've tried all sorts of things: adding the call to chkbutton2 at the end of fun_plug (despite fonz's wishes ); adding a line to /ffp/etc/rc; the works. No matter what I do—no matter when I call the script—it will always fail if it is executed during fun_plug.

Remember that funny "simulate an ssh login" idea? Well I pretty much achieved it with a crontab entry.

Essentially at the boot, the crontab is edited so that chkbutton2 is started "every 1 minute". Within 60 seconds chkbutton2 is launched and visible in 'ps'.

However it would be disastrous if the cron job were left in there—chkbutton2 would just keep being called! So with a little sed magic, as soon as chkbutton2 is called, the job in crontab is deleted.

You might ask why I didn't use the '@reboot' call in crontab. In fact that's what I tried at first, but for some reason or another it wouldn't work. I kind of like the "distance" chkbutton2 gains from the boot sequence the other way anyhow.

Best part is it worked! I'll make a tgz package out of it in a day or two and post it up as a DNS-323 A1 1.08 firmware workaround.


YAAAYYYY!!!!!!!!!

Last edited by krimb1 (2009-06-29 09:17:19)

chkbutton2, Chapter 2...

A few days ago, I made a seemingly minor change using the Web GUI.  The same evening, just before bed, I checked my /ffp/var/log/messages.  RATS!!!  I now had the same issues as kimb1.  All I changed was to sleep the drives after 30 minutes, instead of the 10 minutes I had been using.  Thinking this had to be something in FLASH that had gotten mucked up, I started flashing older FW, trying to over write what ever had not updated properly.  I ended up going to far back, and have bricked this box.  Since I do have 2 DNS-323 boxes, I moved the Raid 1 drives over to the other box, changed the USB stick too.  Brought it up, and changed all the needed configurations to reflect it's different name and IP.  All good EXCEPT the crond messages persisted.  They issue came along with the drives.  Swaped things back, and confirmed.  Problem is on the drives and not in flash memory.  I bricked a box for nothing (and feel pretty stupid).  I have a post in the firmware group asking for assistance.

To simplify the above:

Toaster working with no issues, FW 1.08beta, hardware B1, Raid 1 drives.  Running apps; chkbutton2, kickwebs (disabled this to make the change), samba 3.3.2, sshd, fanctl, booting ffp off a USB stick.

Made a change to sleep times for the drives using Web GUI.  Saved.  Now have the same crond message every 10 minutes, but my drives would still power down.  Perplexing!!!  And it's not in flash memory.  Perhaps a system file in the hidden directory on HD_a4/.systemfile

If I can get my first box back up (hoping) I will research this throughly!

Jerry

sorna wrote:

Hi,

I've installed this and there was no errors or anything. I could reboot/shut down the unit using the method mentioned. However I still get the following message

EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended

I've already run fsck and verified that the disks are fixed. But the errors were generated with the consecutive shut downs. I am having FW 1.08 (beta) in DNS-323.

Any help is appreciated. Thanks.

I had this problem as well. The solution for me was to change the mount point of my USB stick from /mnt/HD_a2/ffp to /mnt/USB. This removes the dependency between the mountpoints of USB and HD.

The mountpoint is configured in one of the funplug files, either 'fun_plug' or '.bootstrap/setup.sh'.

sorna wrote:

Thanks Rintje.

I have the following lines in fun_plug
# setup script (used for ffp on USB disk)
FFP_SETUP_SCRIPT=/mnt/HD_a2/.bootstrap/setup.sh
but there is no .bootstrap directory. (Tried through telnet with ls -a as well). I am not sure what I am missing. BTW I dont use any USB drives.

Oops, in that case this solution does not apply here. (It only makes sense in an USB setup.)

But it seems that chkbutton2 is not able to kill some process keeping files open on your harddrive. This makes the umount command fail.
Try the 'lsof' funplug package to see what files are open on your harddrive(s) before you shutdown.

To shutdown my processes more gently than just 'kill' them, i moved part of the cleanboot script into the /ffp/share/chkbutton2/cleanup.sh script. 
See the attachment for my cleanup file. Maybe this does some more thorough process cleanup than the default config as well, solving your problem.
Make sure you review the script before using it, it might contain some system-specific things like addressing only one harddrive and/or the USB stick. Hope this helps.

Edit
-----
- Fixed cleanup script path in first post
- On thing i forgot: chkbutton2 grants the cleanup.sh no more than 5 seconds to run. As my cleanup.sh script requires a little more, i increased the timeout from 5 to 25 seconds and then recompiled chkbutton2.

Last edited by rintje (2010-04-07 10:49:40)

---

Attachments:
cleanup.sh, Size: 5,083 bytes, Downloads: 416