For the environnement, I’m using a verdin imx8mp with torizon OS 5.7.0 and offline synchronous update.
My goal is to perform an update from 5.7.0 to 6.7.0 and to include into this update a custom script that run atuomatically some system command in order to prepare the board to future 6.7.0 update.
I ran into this topic and tried what was recommend, unsuccessfully : [aktualizr, offline updates] Found in archive a file with bad file type: 40960 - #10 by RoccoBr
So trying to understand more about what is really happening I decided to get back to my original tcbuild.yaml file without the customisation (filesystem : -changes) but the update I was generating even with this original file was getting the same error.
I precise that before testing to generate an update with a custom “changes” file in the tcbuild.yaml file I was able to perform offline synchronous update from 5.7.0 to 6.7.0 and my updates directory weren’t getting any symlink.
Here are the file u may need for a better understanding : tcbuild.yaml (738 Bytes)
The “changes” file I have generated is private so I cannot put it here …
Hi, I’m the Toradex AI Assistant. I’m in early beta, and I would appreciate your feedback.
The Toradex Support team will follow up with you shortly!
Did you like my answer?
The error you’re encountering, “bad file type: 40960,” typically indicates an issue with the file types included in your update package. This can happen if there are unsupported or unexpected file types in the changes directory that you are trying to include in your custom image.
Here are a few steps you can take to troubleshoot and resolve this issue:
Verify File Types in Changes Directory:
Ensure that all files in your changes directory are of supported types. Unsupported file types can cause the update process to fail.
Check for Symlinks:
Even though you mentioned that your updates directory wasn’t getting any symlinks, double-check to ensure there are no symlinks in the changes directory. Symlinks can sometimes cause issues during the update process.
Revert to Original tcbuild.yaml:
Since you mentioned that reverting to the original tcbuild.yaml without the customizations still resulted in the same error, ensure that the changes directory is completely clean and does not contain any residual files from previous attempts.
Recreate the Changes Directory:
Try recreating the changes directory from scratch. Capture the configuration changes again using the isolate command to ensure that there are no corrupted or unsupported files.
Validate the Update Package:
Use the TorizonCore Builder tool to validate the update package before attempting the offline update. This can help identify any issues with the package contents.
Ensure that you are using the latest version of TorizonCore Builder. Sometimes, issues are resolved in newer versions of the tool.
If the issue persists after following these steps, you may need to provide more specific details about the contents of your changes directory (excluding any private or sensitive information) or seek further assistance from the Toradex community or support team.
This issue was present on older versions of Torizon OS, but fixed in later versions of 6.X as documented here: Torizon OS Issue Tracker
So the issue here is with the container images that you’re trying to update and the old update client not being able to process them properly. Now obviously the OS needs to be updated first, so that it can get the new update client with the fix, then you can update the container images.
This means you can’t do a synchronous update here. You need to do a separate OS update first to get the fix. Could you try this order and see if it resolves things.
