We want our installed applications to start automatically whenever the NAS powers on or reboots, without the need to manually log in via SSH and launch each service. Automating this process ensures that your custom services are always running and available, providing a seamless experience without extra effort on your part.

This can be achieved by creating a dedicated “Startup” script and configuring your NAS to execute it on every boot or reboot. By using this method, you can easily manage multiple services, adding or removing them from the script as needed, so your NAS always launches exactly the applications you want without any manual intervention.

IMPORTANT WARNINGS:

• This procedure will void your warranty.

• Proceed at your own risk—incorrect steps may break your NAS.

• Make sure you fully understand the instructions before continuing.

Prerequisites

• You must have SSH access enabled on your NAS. If you haven’t done this yet, follow this SSH Access Guide first.

Create the Startup Script (init-opt.sh)

1. Log in to your NAS via SSH using your preferred terminal (PuTTY, Terminal, etc.).

2. Create and open the startup script file in the nano editor:

   nano /opt/init-opt.sh


3. Paste the following script into the editor:

   #!/bin/sh
rm /opt/init-opt.log
echo "Last bootup:" >> /opt/init-opt.log
date >> /opt/init-opt.log
echo "Wait one minute, so that the storage pool is mounted" >> /opt/init-opt.log
sleep 1m
# Services after this line# Services before this line
   sleep 360d
   reboot

   • This script clears the previous log, records the current boot time, waits one minute to ensure your storage pool is fully mounted, and then runs your services (which you will add below).

   • After running your services, it waits a long time (360 days) and then reboots the NAS. This prevents the NAS from restarting repeatedly unless you manually reboot it earlier.

4. Save and exit nano:

   • Press CTRL + O to write the changes, then ENTER to confirm.

   • Press CTRL + X to exit nano.

5. Make the script executable:

   chmod +x /opt/init-opt.sh


Create and Run the Configuration Editing Script (editconfig.sh)

This script allows you to edit the NAS’s internal configuration so the startup script runs automatically on boot.

1. Create and open the file:

   nano /opt/editconfig.sh


2. Paste the following code:

   #!/bin/sh
mknod -m0660 /dev/loop3 b 7 3
chown root.disk /dev/loop3
mkdir /tmp/apps
mount -o loop /boot/images/apps /tmp/apps
nano /tmp/apps/usr/local/cfg/sohoProcs.xml
sleep 1
umount /tmp/apps
rm /dev/loop3


   • This script mounts the internal apps configuration file so you can edit it.

3. Save and exit nano (CTRL + O, ENTER, CTRL + X).

4. Make the script executable:

   chmod +x /opt/editconfig.sh


5. Run the script to open the config file:

   /opt/editconfig.sh


Modify Startup Configuration Based on Your Firmware Version

After running /opt/editconfig.sh, a text editor opens the file sohoProcs.xml. Here you will add instructions for the NAS to run your startup script automatically.

For Firmware 3.3.4.29856 and Older

• Scroll down inside the editor until you find Group 1, under the tag <Group> and inside the <mozzyclient> section.

• Add the following lines inside Group 1, exactly like this:

  <Program Name="init-opt.sh" Path="/opt/init-opt.sh">
<SysOption Restart="-1"/>
</Program>


• Save and exit nano (CTRL + O, ENTER, CTRL + X).

• WARNING: Only restart your NAS if you are 100% sure the file is correct. Incorrect changes to this file can break your NAS.

For Firmware 4.0.2.9960 and Newer

• Scroll down inside the editor to Group 1.

• Add the following lines inside Group 1, just before the closing </Group> tag:

  <Program Name="init-opt.sh" Path="/opt/init-opt.sh">
<SysOption Restart="-1"/>
</Program>


• Save and exit nano (CTRL + O, ENTER, CTRL + X).

• WARNING: Only restart your NAS if you are 100% sure the file is correct. Incorrect editing can break your NAS.

Add Startup Services to Your Script

Now that your startup script will run at boot, you can add the commands to start your desired services.

1. Open your startup script:

   nano /opt/init-opt.sh


2. Add your service start commands after the comment line # Services after this line. For example:

   ###########################
# Services after this line
PATH=$PATH:/opt/bin# Start Transmission daemon
   /opt/bin/transmission-daemon –config-dir /mnt/pools/A/A0/Downloads/config/transmission/ –allowed *.*.*.* >> /opt/init-opt.log
   echo “Transmission Started “ >> /opt/init-opt.log# Start SABnzbd
   /opt/bin/python2.6 /mnt/pools/A/A0/Downloads/.apps/sabnzbd/SABnzbd.py –server 0.0.0.0 –daemon
   echo “SABnzbd Started” >> /opt/init-opt.log

   # Start CouchPotato
   /opt/bin/python2.6 /mnt/pools/A/A0/Media/.Apps/CouchPotatoServer/CouchPotato.py –data_dir /mnt/pools/A/A0/Media/.Apps/_config/couchpotato/ –daemon
   echo “Couchpotato Started” >> /opt/init-opt.log

   # Start SickBeard
   /opt/bin/python2.6 /mnt/pools/A/A0/Media/.Apps/Sick-Beard/SickBeard.py –daemon
   echo “Sickbeard Started” >> /opt/init-opt.log

    

   # Start Minecraft Server
   PATH=$PATH:/mnt/pools/A/A0/Downloads/minecraft/ejre1.7.0_21/bin
   export PATH
   cd /mnt/pools/A/A0/Downloads/minecraft/mc
   java -Xms256M -Xmx512M -jar minecraft.jar nogui
   echo “Minecraft Started” >> /opt/init-opt.log

   # Services before this line
   ###########################
   sleep 360d
   reboot

Save and exit nano (CTRL + O, ENTER, CTRL + X).

Check the Startup Log

Every time your NAS boots and runs your startup script, it writes status messages to a log file. To check what happened during startup, use:

This log will help you verify whether your services started correctly.

Final Notes

• Never remove or modify default system applications listed in your NAS, as that may cause system instability.

• Only reboot your NAS after verifying your configuration changes are correct.

• Keep the editconfig.sh script for future edits or guides.