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

thanks,

so
"if [ $1 = "shutdown" ]; then"
was the shutdown fix! nice. havent tested it yet but i believe it works


btw i'm running raid0 so when testing the spinup commands
"touch /mnt/HD_a2/.tmp_wakeup_disk;sleep 1;rm /mnt/HD_a2/.tmp_wakeup_disk"
would walke hd0 only in most occasions (HD_b2 does not exist)

i have changed it to:
touch /mnt/HD_a4/.tmp_wakeup_disk;sleep 1;rm /mnt/HD_a4/.tmp_wakeup_disk
touch /mnt/HD_b4/.tmp_wakeup_disk;sleep 1;rm /mnt/HD_b4/.tmp_wakeup_disk

which is more correct in every raid/non raid scenario (a4 and b4 always exist - if you formatted using d-link webs)

Is it possible to create a version for funplug 0.4? I would do it but don't know how.

Sorry, I forgot to unset the executing bit of cleanboot.sh in /ffp/start. Therefore I have compiled a new version 2.0.4, which fixes this.

That means, if you want to have the clean boot now enabled, you have to set the executing bit by:

chmod a+x /ffp/start/cleanboot.sh

marinalink

---

Attachments:
cleanboot-2.0.4-ffp05.tgz, Size: 4,330 bytes, Downloads: 1,621

Yes this should work smoothly with FW 1.05, but I was not able to test it.

I still have FW 1.04B84 running. You know: NEVER change a running system!

Thanks, will give it a go then.....

Tony

marinalink,

I downloaded your version of cleanboot because the original cleanboot 2.0 doesn't work on my CH3SNAS. It tries to write to the readonly /sys/crfs file system. Unfortunately I found out that your version is trying the same thing.
Maybe this is different on a DNS-323 but on the CH3SNAS /usr/sbin is linked to /sys/crfs/sbin, at least in firmware 1.04RC4.
I'm not willing to brick my box by writing to the flash. ;-)

Do I have to modify the script myself to use the folders of ffp like /ffp/sbin or /ffp/bin to copy the files to? These folders come first in the $PATH.

YES!!! It works! :-)

Thank you very much. After installing the modified script I can now reboot and shutdown with cleanly unmounted drives. I did a check on the hard disks and also the minix flash and now the error messages are gone.
The only errors I get are from the USB drive with the FFP on it. I believe that this can't be circumvented because most of the system runs from it.

There is only one thing which I didn't understand. You suggested to use "rm -r sbin" at one point.
Well, the "sbin" in "/usr/" is only a symbolic link. "rm sbin" should be enough to remove it and in fact it is enough on my box.
I don't know why it didn't work for the other fellow. Do you have an explanation for this strange behaviour?