Applicable Products
- Any QNAP NAS running QTS or QuTS hero that supports custom
autorun.sh scripts
Scenario
- You refer to Running Your Own Application at Startup and created an
autorun.sh script under /tmp/config with executable permissions (-rwxr-xr-x). - The autorun feature is enabled in Control Panel > Hardware.
- After rebooting, the expected actions do not occur. It is unclear whether:
autorun.sh was never triggered, orautorun.sh ran, but some commands failed due to timing or environment differences.
- Running the same script manually via SSH works as expected, which makes the root cause harder to identify.
Solution
The most direct way to confirm that autorun.sh runs at boot is to add a buzzer command and a log entry at the beginning of the script.
- If you hear a beep after boot,
autorun.sh was triggered. - If you hear a beep but the main functionality does not work, commands later in the script may be failing because a required network interface, filesystem, or service is not ready.
Prerequisitesautorun.sh is stored at /tmp/config/autorun.sh.- The file is executable:
-rwxr-xr-x. - The autorun feature is enabled in Control Panel > Hardware.
To implement this, first reduce autorun.sh to a minimal observable version:
#!/bin/bash
# Minimal execution proof
echo "autorun.sh started at $(date)" >> /tmp/autorun.log
hal_app --se_buzzer enc_id=0,mode=0
Buzzer commands
- Short beep:
hal_app --se_buzzer enc_id=0,mode=0 - Long beep:
hal_app --se_buzzer enc_id=0,mode=1
Recommended usage:
- Place two short beeps at the very start: indicates that
autorun.sh has started and two short beeps at the end of autorun.sh .
#!/bin/bash
echo "autorun.sh started at $(date)" >> /tmp/autorun.log
hal_app --se_buzzer enc_id=0,mode=0
hal_app --se_buzzer enc_id=0,mode=0
# Your actual configuration below
sleep 5
# ... your commands here ...
echo "autorun.sh completed at $(date)" >> /tmp/autorun.log
hal_app --se_buzzer enc_id=0,mode=0
hal_app --se_buzzer enc_id=0,mode=0
Interpreting the results
Note: QNAP NAS systems emit beep sounds at specific points during normal boot:
- Power-on beep: Single short beep when power is applied (very early in boot, before autorun.sh runs)
- System-starting beep Single short beep when the operating system starts loading (before autorun.sh runs)
- System-ready beep: Usually a long beep after the OS has initialized and services are starting (after autorun.sh runs )
In order to distinguish autorun.sh beeps from the system boot beeps, you may add a differenet beep combinations in your autorun.sh during debug stage.
Besides, you can also view /tmp/autorun.log to check whether autorun.sh is executed.
Warnings
autorun.sh runs with elevated privileges during boot. Ensure that the syntax is correct to avoid system instability.- The buzzer confirms that the script was triggered, but does not guarantee that every command inside it succeeded.
Further Reading
適用產品
- Any QNAP NAS running QTS or QuTS hero that supports custom
autorun.sh scripts
情境
- 您參考了在啟動時運行您自己的應用程式並在
/tmp/config下建立了一個具有可執行權限的autorun.sh腳本 (-rwxr-xr-x)。 - 在控制台 > 硬體中啟用了自動運行功能。
- 重新啟動後，預期的動作未發生。尚不清楚是否：
autorun.sh從未被觸發，或autorun.sh已運行，但由於時間或環境差異，某些命令失敗。
- 透過 SSH 手動執行相同的指令碼可正常運作，這使得根本原因更難識別。
解決方案
確認autorun.sh在啟動時運行的最直接方法是在腳本的開頭添加蜂鳴器命令和日誌條目。
- 如果在啟動後聽到蜂鳴聲，則
autorun.sh已被觸發。 - 如果聽到蜂鳴聲但主要功能未正常運作，則可能是指令碼中的後續命令因所需的網路介面、檔案系統或服務尚未準備好而失敗。
先決條件autorun.sh儲存在/tmp/config/autorun.sh。- 檔案是可執行的：
-rwxr-xr-x。 - 在控制台 > 硬體中啟用了自動運行功能。
要實現此功能，首先將autorun.sh縮減為最小可觀察版本：
#!/bin/bash
# 最小執行證明
echo "autorun.sh started at $(date)" >> /tmp/autorun.log
hal_app --se_buzzer enc_id=0,mode=0
蜂鳴器命令
- 短嗶聲：
hal_app --se_buzzer enc_id=0,mode=0 - 長嗶聲：
hal_app --se_buzzer enc_id=0,mode=1
建議使用：
- 在開始時放置兩個短嗶聲：表示
autorun.sh已開始，並在autorun.sh結束時放置兩個短嗶聲。
#!/bin/bash
echo "autorun.sh started at $(date)" >> /tmp/autorun.log
hal_app --se_buzzer enc_id=0,mode=0
hal_app --se_buzzer enc_id=0,mode=0
# 您的實際配置如下
sleep 5
# ... 您的命令在此 ...
echo "autorun.sh completed at $(date)" >> /tmp/autorun.log
hal_app --se_buzzer enc_id=0,mode=0
hal_app --se_buzzer enc_id=0,mode=0
解讀結果
注意：QNAP NAS 系統在正常啟動過程中的特定點會發出嗶聲：
- 開機嗶聲：通電時發出單短嗶聲（啟動初期，在 autorun.sh 執行之前）
- 系統啟動嗶聲 單短嗶聲當作業系統開始載入時（在 autorun.sh 執行之前）
- 系統準備嗶聲：通常在作業系統初始化後，服務開始時發出長嗶聲（在 autorun.sh 執行之後）
為了區分 autorun.sh 嗶聲與系統啟動嗶聲，您可以在除錯階段於 autorun.sh 中新增不同的嗶聲組合。
此外，您還可以查看/tmp/autorun.log 以檢查autorun.sh是否執行。
警告
autorun.sh在啟動過程中以提升的權限運行。確保語法正確以避免系統不穩定。- 蜂鳴器確認指令碼已觸發，但不保證其中的每個命令都成功執行。
進一步閱讀
