Analysis of Your Update Issue
Based on your additional logs, I can see several important details about your system’s state. The logs show that Aktualizr is initializing multiple secondaries including docker-compose, bootloader, fuses, and M7 firmware components (1). The “No valid Director metadata found in storage” and “No valid Image metadata found in storage” messages indicate that the device hasn’t successfully completed the initial metadata synchronization with the update server (1).
Key Observations
1. Metadata Issues
Your logs show multiple instances of “Could not load latest root” which suggests the device is having trouble establishing proper communication with the Torizon Cloud update infrastructure (1).
2. Automatic Reboot Service Status
The ostree-pending-reboot.path service is active and waiting, which is the correct state. This service monitors for pending OSTree updates and triggers automatic reboots when needed (1).
3. Multiple Secondary Components
Your system is configured with several secondary update components:
- docker-compose secondary
- bootloader secondary
- fuses secondary
- M7 firmware secondary
This indicates a complex update configuration that may require all components to be properly synchronized (1).
Troubleshooting Steps
1. Check OSTree Status Directly
Run the following command to see the actual OSTree deployment status:
sudo ostree admin status
This will show you the current and pending deployments, helping identify if an update is actually staged.
2. Verify Network Connectivity
Ensure your device can reach the Torizon Cloud servers:
curl -I https://dgw.torizon.io
3. Check for Blocked Updates
Torizon OS provides mechanisms to allow and block updates (2). Verify if updates are currently blocked:
sudo systemctl status aktualizr-torizon
4. Enable Debug Logging
To get more detailed information about what’s happening, you can temporarily increase the logging level. Create a custom configuration file (1):
sudo mkdir -p /etc/sota/conf.d/
cat <<EOF | sudo tee /etc/sota/conf.d/99-custom-loglevel.toml
[logger]
loglevel = 1
EOF
Then restart Aktualizr:
sudo systemctl restart aktualizr-torizon
5. Manual Update Check
You can force Aktualizr to check for updates immediately rather than waiting for the polling interval:
sudo systemctl kill -s SIGUSR1 aktualizr-torizon
Understanding the Update Process
Torizon updates are designed to be power-cut tolerant and atomic operations (2). The system uses OSTree for reliable updates with automatic rollback capabilities if issues occur (2). When an update is “stuck,” it’s often due to metadata synchronization issues rather than the actual update process failing.
Next Steps
- Check OSTree status to understand the current deployment state
- Enable debug logging to get more detailed information about the update process
- Verify network connectivity to ensure communication with Torizon Cloud
- Monitor the logs after enabling debug mode to identify specific error conditions
If these steps don’t resolve the issue, the problem may be related to the specific update package or server-side configuration that requires further investigation.
Best regards, Toradex AI Assistant.
Did you like my answer? 
If I answered your question, please tick the “Solution” checkbox.
For follow-up questions to me, please use @ToradexAI in your post.
