jetson xavier build missing partitions?

Product support balenaOS
, ,
1

Hi,
I have been having issues flashing the BalenaOS jetson-xavier image built using barys. After mounting the image to loop device using sudo losetup -fP and comparing the image built with barys with the jetson xavier image downloaded from balena cloud. I noticed the image built with barys is missing partitions. I built another jetson-xavier image using balena-build.sh and the same issue arises.

built image using balena-yocto-scripts/build/barys -d --rm-work -b build -m jetson-xavier

sean@env:~$ sudo losetup -fP /home/sean/balena-jetson/build/tmp/deploy/images/jetson-xavier/balena-image-flasher-jetson-xavier-20230728104444.rootfs.balenaos-img
[sudo] password for sean: 
sean@env:~$ dmesg | tail
[25222.638385] e1000: enp0s3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
[25256.939495] e1000: enp0s3 NIC Link is Down
[25258.855713]  loop29: p1 p2 p3 p4 p5
[25260.971685] e1000: enp0s3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
[31448.207138]  loop14: p1 p2 p3 p4 p5
[195076.007466] e1000: enp0s3 NIC Link is Down
[195082.054972] e1000: enp0s3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
[195112.294674] e1000: enp0s3 NIC Link is Down
[195118.343213] e1000: enp0s3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
[259893.471700]  loop27: p1 p2 p3 p4 p5

jetson xavier image downloaded from balena cloud

sean@env:~$ sudo losetup -fP /home/sean/Downloads/jetson-xavier-2.99.27+rev1-v14.0.8.img
sean@env:~$ dmesg | tail
[25256.939495] e1000: enp0s3 NIC Link is Down
[25258.855713]  loop29: p1 p2 p3 p4 p5
[25260.971685] e1000: enp0s3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
[31448.207138]  loop14: p1 p2 p3 p4 p5
[195076.007466] e1000: enp0s3 NIC Link is Down
[195082.054972] e1000: enp0s3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
[195112.294674] e1000: enp0s3 NIC Link is Down
[195118.343213] e1000: enp0s3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
[259893.471700]  loop27: p1 p2 p3 p4 p5
[260114.041693]  loop14: p1 p2 p3 p4 p5 p6 p7 p8 p9 p10 p11 p12 p13 p14 p15 p16 p17 p18 p19 p20 p21 p22 p23 p24 p25 p26 p27 p28 p29 p30 p31 p32 p33 p34 p35 p36 p37 p38 p39 p40 p41

balena-jetson version: v2.115.18+rev1
Steps used to build image:

  1. git clone --recursive https://github.com/balena-os/balena-jetson.git
  2. cd balena-jetson
  3. balena-yocto-scripts/build/barys -d --rm-work -b build -m jetson-xavier

I originally noticed this when trying to use balena os configure on the barys built image and getting an issue that partition 37 was not found.

Am I missing a step somewhere?

2

Fixed: Mounting wrong .balenaos-image file, ran into the same issue when doing a custom build and the fix for that was to check machine overrides in /layers/meta-balena-jetson/conf/machine/<custom_machine>.conf file.