Hi balena community,
it’s been a while since i build my last balena OS image (approx 1 year), therefore i might skipped through some major changes in the balena-jetson repo, that caused this issue.
What is the current behavior?
I checked out the v2.69.1+rev4 release and a new device (.svg, .coffee and .json).
These files are an exact copy of the jetson-nano files, only the name was replaced by custom-nano and the following flags have been added:
"state": "RELEASED",
"community": "true",
"private": "true",
Furthermore the meta-balena-jetson layer has been appended with the conf/machine accordingly:
#@TYPE: Machine
##@NAME: custom-nano
##@DESCRIPTION: Machine configuration for custom Jetson Nano
MACHINEOVERRIDES = "jetson-nano:${MACHINE}"
require conf/machine/jetson-nano.conf
After succesfully building the image on a powerfull server, i copied the resulting resin-image-custom-nano.resinos-img to my laptop. When configuring the image a couple of strange things are happening before the configuration fails
balena os configure ~/Downloads/resin-image-custom-nano.resinos-img--application testApp --debug
Could not find OS version:
Could not read OS version from the image. Please specify the balenaOS
version manually with the --version command-line option.
ExpectedError: Could not read OS version from the image. Please specify the balenaOS
version manually with the --version command-line option.
at getOsVersionFromImage (/usr/local/lib/balena-cli/build/commands/os/configure.js:224:15)
After adding the current version 2.69.1 to the image the 12th partition can not be found.
balena os configure ~/Downloads/resin-image-custom-nano.resinos-img --application testApp --version 2.69.1 --debug
Partition not found: 12.
PartitionNotFound: Partition not found: 12.
at /usr/local/lib/balena-cli/node_modules/resin-image-fs/node_modules/partitioninfo/build/partitioninfo.js:144:23
at Generator.next (<anonymous>)
at fulfilled (/usr/local/lib/balena-cli/node_modules/tslib/tslib.js:111:62)
From previous event:
at Object.exports.interact (/usr/local/lib/balena-cli/node_modules/resin-image-fs/build/driver.js:125:24)
at write (/usr/local/lib/balena-cli/node_modules/resin-image-fs/build/imagefs.js:170:31)
at /usr/local/lib/balena-cli/node_modules/resin-image-fs/build/imagefs.js:206:14
From previous event:
at Object.exports.write (/usr/local/lib/balena-cli/node_modules/resin-image-fs/build/imagefs.js:203:20)
at Object.exports.writeConfigJSON (/usr/local/lib/balena-cli/node_modules/balena-device-init/build/utils.js:179:18)
at /usr/local/lib/balena-cli/node_modules/balena-device-init/build/init.js:87:18
at runCallback (timers.js:705:18)
at tryOnImmediate (timers.js:676:5)
at processImmediate (timers.js:658:5)
at process.topLevelDomainCallback (domain.js:126:23)
From previous event:
at Object.exports.configure (/usr/local/lib/balena-cli/node_modules/balena-device-init/build/init.js:82:6)
at OsConfigureCmd.run (/usr/local/lib/balena-cli/build/commands/os/configure.js:75:55)
at process._tickCallback (internal/process/next_tick.js:68:7)
For further help or support, visit:
https://www.balena.io/docs/reference/balena-cli/#support-faq-and-troubleshooting
While inspecting the partitions and their content and comparing it to the stock image i could not see any differences. In this case i compared them not entirely only by visual inspection of some random files.
Other information on the environment
- I am currently using balena cli version
12.40.2and working on ubuntu (server and laptop). - Eventhough other modifications are planed (device tree, kernal, …) this happens with no configurations to the the layers.
I successfully build working images for the jetson nano one year ago and just wanted to upgrade to the new kernel, docker environment, … (i know i should have done this more often).
Can you help me debugging this problem?
.