Does this mean anything? See log at 21:49:13That wont capture the USB logs because those are normal syslog transactions. AdGuardHome logs would not be helpful determining if you are experiencing USB troubles. If anything, Adguardhome logs would just fill your current system log with unnecessary chatter. You would be looking for system log entries either before Entware has mounted (e.g. system log entrees that indicate your USB storage has mounted successfully or errors indicated it failed to mount). Or, you would be looking for system logs that indicate a failure to unmount right before reboot. A lack of system log entries showing your USB mounting after reboot may indicate a bigger issue unrelated to AdGuardHome.
If you have verified your Entware is mounted and working on each AdGuardHome failure, then the other cause for AdGuardHome failing to start could be a result of insufficient memory available during the time AdGuardHome was started. (OOM killer got to it before it could start.) AdGuardHome debug logs would only be useful to you if you are making it to this point.
Code:
Aug 4 21:49:00 68U custom_script: Running /jffs/scripts/service-event-end (args: start dnsmasq)
Aug 4 21:49:00 68U AdGuardHome[4113]: 2023/08/04 21:49:00.404795 [info] AdGuard Home, version v0.108.0-b.42
Aug 4 21:49:00 68U AdGuardHome[4113]: 2023/08/04 21:49:00.405117 [info] AdGuard Home is running as a service
Aug 4 21:49:00 68U custom_script: Running /jffs/scripts/service-event (args: start logger)
Aug 4 21:49:01 68U AdGuardHome[4113]: 2023/08/04 21:49:01.999766 [info] tls: using default ciphers
Aug 4 21:49:02 68U dnsmasq[4232]: exiting on receipt of SIGTERM
Aug 4 21:49:02 68U AdGuardHome[4113]: 2023/08/04 21:49:02.278532 [info] safesearch default: disabled
Aug 4 21:49:02 68U AdGuardHome[4113]: 2023/08/04 21:49:02.346264 [info] Initializing auth module: /tmp/mnt/Asus/entware/etc/AdGuardHome/data/sessions.db
Aug 4 21:49:02 68U AdGuardHome[4113]: 2023/08/04 21:49:02.354402 [info] auth: initialized. users:1 sessions:5
Aug 4 21:49:02 68U AdGuardHome[4113]: 2023/08/04 21:49:02.355586 [info] AdGuard Home updates are disabled
Aug 4 21:49:02 68U AdGuardHome[4113]: 2023/08/04 21:49:02.356644 [info] web: initializing
Aug 4 21:49:00 syslogd started: BusyBox v1.25.1
Aug 4 21:49:00 kernel: klogd started: BusyBox v1.25.1 (2023-05-14 12:46:55 EDT)
Aug 4 21:49:00 custom_script: Running /jffs/scripts/service-event-end (args: start logger)
Aug 4 21:49:01 custom_script: Running /jffs/scripts/service-event (args: restart dnsmasq)
Aug 4 21:49:01 S99AdGuardHome[3542]: Started AdGuardHome from S99AdGuardHome[3542].
Aug 4 21:49:02 kernel: klogd: exiting
Aug 4 21:49:02 syslogd exiting
Aug 4 21:49:06 68U AdGuardHome[4113]: 2023/08/04 21:49:06.364040 [info] dnsproxy: cache: enabled, size 4096 b
Aug 4 21:49:06 68U AdGuardHome[4113]: 2023/08/04 21:49:06.364241 [info] dnsproxy: max goroutines is set to 300
Aug 4 21:49:06 68U AdGuardHome[4113]: 2023/08/04 21:49:06.403931 [info] AdGuard Home is available at the following addresses:
Aug 4 21:49:06 68U AdGuardHome[4113]: 2023/08/04 21:49:06.415179 [info] clients: processing addresses
Aug 4 21:49:06 68U AdGuardHome[4113]: 2023/08/04 21:49:06.567425 [info] go to http://127.0.0.1:14711
Aug 4 21:49:06 68U AdGuardHome[4113]: 2023/08/04 21:49:06.568244 [info] go to http://127.0.1.1:14711
Aug 4 21:49:06 68U AdGuardHome[4113]: 2023/08/04 21:49:06.570905 [info] go to http://47.72.207.189:14711
Aug 4 21:49:06 68U AdGuardHome[4113]: 2023/08/04 21:49:06.573129 [info] go to http://192.168.1.1:14711
Aug 4 21:49:06 68U AdGuardHome[4113]: 2023/08/04 21:49:06.574234 [info] go to http://10.8.0.1:14711
Aug 4 21:49:13 68U AdGuardHome[4113]: 2023/08/04 21:49:13.583828 [info] Received signal "interrupt"
Aug 4 21:49:13 68U AdGuardHome[4113]: 2023/08/04 21:49:13.584090 [info] stopping AdGuard Home
Aug 4 21:49:13 68U AdGuardHome[4113]: 2023/08/04 21:49:13.584180 [info] stopping http server...
Aug 4 21:49:13 68U AdGuardHome[4113]: 2023/08/04 21:49:13.635323 [info] service: action run has been done successful