Torizon Core 7.1 OTA fails with composefs

Technical Support
, , , , ,
2

Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!

Did you like my answer?

:+1: :-1:

Hello,

I’m sorry to hear about the difficulties you’re experiencing with the update from Torizon Core 6.8.0 to 7.1.0. The error involving ‘systemd-udevd’ and the missing ‘/dev’ directory can indeed be challenging. Let’s go through some steps to help you troubleshoot and resolve this issue:

  1. Verify Configuration Files: Double-check your local.conf and other relevant configuration files to ensure they are correctly set up for Torizon Core 7.1.0. The torizon-signed declaration should be compatible with this version, so ensure there are no syntax errors or misconfigurations.

  2. Check ‘composefs’ Setup: Since the error log mentions ‘composefs’, ensure that it is properly configured. Verify that all necessary components and dependencies for ‘composefs’ are included in your build. You might want to check if there are any specific instructions or requirements for using ‘composefs’ with Torizon Core 7.1.0.

  3. Review the Update Process: Carefully review the steps you followed to update from Torizon Core 6.8.0 to 7.1.0. Ensure that each step was completed successfully and that there were no interruptions or errors during the update process.

  4. Investigate the ‘/dev’ Directory Issue: The error indicates that ‘/dev’ is missing on the root filesystem. This could be due to a misconfiguration or an incomplete update. Check if the root filesystem is correctly mounted and that all necessary directories, including ‘/dev’, are present. You might need to manually verify the filesystem structure.

  5. Compatibility of ‘torizon-signed’: Since torizon-signed caused build errors in 6.8.0, ensure that it is now compatible with 7.1.0. Look for any updates or patches that might address compatibility issues. It might also be helpful to consult the release notes for Torizon Core 7.1.0 for any changes related to signing.

If these steps do not resolve the issue, you might consider reverting to a previous stable version and reattempting the update, ensuring careful attention to the configuration and update process. This approach can help isolate the problem and ensure a successful update.

I hope this helps, and please feel free to reach out if you have further questions.

Best regards,
Toradex AI Assistant.

Please, also check if these links can help you solve your problem:

Systemd service management on Torizon.