Updating disk partitioning while flashing

Robotics & Edge Computing Jetson & Embedded Systems Jetson Orin NX
1

I am flashing a Jetson Orin NX 16GB with A/B partitioning.

I updated the flash_l4t_t234_nvme_rootfs_ab.xml with the following

<partition name="UDA" id="20" type="data"> <allocation_policy> sequential </allocation_policy> <filesystem_type> basic </filesystem_type> <size> 0xFFFFFFFFFFFFFFFF </size> <file_system_attribute> 0 </file_system_attribute> <allocation_attribute> 0x808 </allocation_attribute> <percent_reserved> 0 </percent_reserved> <filename> UDAFILE </filename> <align_boundary> 16384 </align_boundary> <description> **Required.** This partition may be mounted and used to store user data. </description> </partition>

And moved this after the partition APP_B. I still do not have the UDA to use the remaining space. It only has 2 GB.

I am using an image snapshot from a device where i manually updated the partitions and the fstab. But when i reflashed my machine with the snapshot it doesnt have the disk partitions as i had done manually on the device before creating a snapshot.
If I can get the disk to be partitioned with the Jetpack 36.4.3 plain image, that would also work, I can reinstall the tools and create an image again.

How I flash the device

sudo ROOTFS_AB=1 ./tools/kernel_flash/l4t_initrd_flash.sh 
–network usb0 
–no-flash 
–showlogs 
-p “-c bootloader/generic/cfg/flash_t234_qspi.xml” 
jetson-orin-nano-devkit internal

sudo ROOTFS_AB=1 ./tools/kernel_flash/l4t_initrd_flash.sh 
–showlogs 
–no-flash 
–external-device nvme0n1p1 
-c ./tools/kernel_flash/flash_l4t_t234_nvme_rootfs_ab.xml 
–external-only 
–append 
–network usb0 
jetson-orin-nano-devkit external

sudo ./tools/kernel_flash/l4t_initrd_flash.sh 
–showlogs 
–network usb0 
–flash-only 
jetson-orin-nano-devkit

What am I missing here?

2

*** Please note that this reply is generated by LLM automatically ***

Based on the provided context, it appears that you are experiencing issues with flashing a Jetson Orin NX 16GB device with AB partitioning. You have updated the device with a new image, but the remaining space is not being utilized, and the device only has 2 GB of available space.

To resolve this issue, let’s break down the steps you’ve taken and compare them to the available options in the context:

  1. Flashing the device: You have flashed the device with a snapshot image from a device where you manually updated the partitions and the fstab. However, when you reflashed the machine with the snapshot, it didn’t retain the disk partitions as you had done manually on the device before creating the snapshot.
  2. Using an image snapshot: You are using an image snapshot from a device where you manually updated the partitions and the fstab. This might be the cause of the issue, as the snapshot may not be capturing the updated partition layout.
  3. AB partitioning: You are using AB partitioning, which is a common partitioning scheme for Jetson devices. However, you haven’t specified the exact partition layout you are trying to achieve.

To resolve the issue, you can try the following:

  1. Use the Jetpack 3.6.4 plain image: You mentioned that if you can get the disk to be partitioned with the Jetpack 3.6.4 plain image, that would also work. You can try flashing the device with the plain image and then reinstalling the tools and creating a new image.
  2. Manually set up the NVMe drive: You can try manually setting up the NVMe drive for booting or as a root file system using the instructions provided in the context. This might help you achieve the desired partition layout.
  3. Use the initrd flash tool: You can try using the initrd flash tool to flash the device. This tool allows you to clone the rootfs with initrd, which might help you achieve the desired partition layout.
  4. Check the fstab: Make sure that the fstab file is correctly configured to reflect the updated partition layout.

In terms of what you might be missing, here are a few possibilities:

  1. Incorrect partition layout: You might not have correctly configured the partition layout to utilize the remaining space on the device.
  2. Missing fstab updates: You might not have updated the fstab file to reflect the changes to the partition layout.
  3. Incorrect image snapshot: You might not have captured the correct partition layout in the image snapshot.

To further troubleshoot the issue, you can try the following:

  1. Check the partition layout: Use tools like fdisk or parted to check the current partition layout on the device.
  2. Check the fstab: Verify that the fstab file is correctly configured to reflect the updated partition layout.
  3. Try a different flashing method: Try using a different flashing method, such as the initrd flash tool, to see if that resolves the issue.

By trying these different approaches, you should be able to resolve the issue and get the device to utilize the remaining space correctly.

*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***

5

hello vini,

you may omit the <size> attribute, please set <allocation_attribute> to 0x808, and place the UDA partition before the secondary GPT. this configuration will allow UDA to take all remaining space.

you may see-also backup-restore tools $OUT/Linux_for_Tegra/tools/backup_restore.

6

yes i got it working. thanks