Unable to resize APP partition on Jetson Orin NX NVMe SSD after JetPack 6.2 installation

[rutvikvyas1224]

Hi NVIDIA Team,

I am using a Jetson Orin NX running:

JetPack 6.2 (L4T R36.4.3)
Ubuntu 22.04.5 LTS
Boot device: NVMe SSD

The system is already fully configured with JetPack, CUDA, TensorRT, DeepStream, ROS 2 Humble, Docker, and several other applications. I do not want to reflash the device because I would like to preserve the current installation.

My customer requires the SSD to be partitioned as follows:

120 GB → Root (/)
300 GB → /data
20 GB → Reserved

To avoid modifying the running system, I booted GParted Live from an external drive and attempted to resize the existing APP (root) partition.

However, I am unable to successfully resize the APP partition. The resize operation does not complete as expected.

Could you please advise:

Is it officially supported to resize the APP partition on an already installed JetPack 6.2 system?
Is there any NVIDIA-recommended method to repartition the NVMe SSD without reflashing the board?
Is there any limitation related to the Jetson partition layout or GPT that prevents resizing?
Would you recommend any NVIDIA tools or procedures for achieving the required partition layout while preserving the existing installation?

Any guidance would be greatly appreciated.

Thank you.

[MarkusHoHo]

Hello @rutvikvyas1224!

Based on the title and content of your topic, it looks like it may receive better visibility and feedback in a different category. We took the liberty of moving it for you.

If this was an incorrect assessment, please send me a direct message.

Disclaimer: this moderation suggestion and message were generated with AI assistance.

[DavidDDD]

Hi,

@rutvikvyas1224

Is it officially supported to resize the APP partition on an already installed JetPack 6.2 system?

Please add -S <rootfs size> as Flashing Support — NVIDIA Jetson Linux Developer Guide 1 documentation show when you run the flashing commands.

We officially not support APP resize after flashing.

Thanks

[rutvikvyas1224]

but i use this coomand ;
sudo ./tools/kernel_flash/l4t_initrd_flash.sh
-S 100GiB
–external-device nvme0n1p1
-c tools/kernel_flash/flash_l4t_t234_nvme.xml
-p “-c bootloader/generic/cfg/flash_t234_qspi.xml”
–showlogs
–network usb0
jetson-orin-nano-devkit-super internal

it give me error

*** no-flash flag enabled. Exiting now… ***

User can run above saved command in factory environment without
providing pkc and sbk keys to flash a device

Example:

$ cd bootloader 
$ sudo bash ./flashcmd.txt

Error: /home/rutvik/OS/Ealge201_Leetop/Linux_for_Tegra/bootloader/signed/flash.idx is not found
Error: failed to relocate images to /home/rutvik/OS/Ealge201_Leetop/Linux_for_Tegra/tools/kernel_flash/images
Cleaning up…

and this same command run before succesfully

[DavidDDD]

Hi,

Please try

sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 \
  -c tools/kernel_flash/flash_l4t_t234_nvme.xml -p "-c bootloader/generic/cfg/flash_t234_qspi.xml" \
  -S 100GiB --showlogs --network usb0 jetson-orin-nano-devkit-super internal

Thanks

[rutvikvyas1224]

same errror i have 500gib ssd neveme

[DavidDDD]

Hi,

We ensure the above commands work properly in our developer kit.
Please follow the quick start guide to set up the BSP.

Quick Start — NVIDIA Jetson Linux Developer Guide

$ tar xf ${L4T_RELEASE_PACKAGE}
$ sudo tar xpf ${SAMPLE_FS_PACKAGE} -C Linux_for_Tegra/rootfs/
$ cd Linux_for_Tegra/
$ sudo ./tools/l4t_flash_prerequisites.sh
$ sudo ./apply_binaries.sh

Thanks

[rutvikvyas1224]

@DavidDDD

$ tar xf ${L4T_RELEASE_PACKAGE}
$ sudo tar xpf ${SAMPLE_FS_PACKAGE} -C Linux_for_Tegra/rootfs/
$ cd Linux_for_Tegra/
$ sudo ./tools/l4t_flash_prerequisites.sh
$ sudo ./apply_binaries.sh

We use same step for extracting the file and all but whenever we use reguler command like this
sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -c tools/kernel_flash/flash_l4t_t234_nvme.xml -p “-c bootloader/generic/cfg/flash_t234_qspi.xml” --showlogs --network usb0 jetson-orin-nano-devkit-super internal

this work ok but no partion
but when we use this coomand
sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1
-c tools/kernel_flash/flash_l4t_t234_nvme.xml -p “-c bootloader/generic/cfg/flash_t234_qspi.xml”
-S 100GiB --showlogs --network usb0 jetson-orin-nano-devkit-super internal

first time we get good output withwith partion as we mention but second time it not work same error

[DavidDDD]

HI,

So, do you mean that the commands below work the first time but fail the second time?

sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1
-c tools/kernel_flash/flash_l4t_t234_nvme.xml -p “-c bootloader/generic/cfg/flash_t234_qspi.xml”
-S 100GiB --showlogs --network usb0 jetson-orin-nano-devkit-super internal

Thanks

[rutvikvyas1224]

Yes sir

[carolyuu]

Thank you for confirming that the -S 100GiB command works on the first run but fails on the second run. This pattern is helpful for diagnosis.

To understand why the second invocation fails when the first succeeds, please provide the following information:

1. Complete error output from the second failed flash attempt: Please provide the full console output starting from when you run the command until the error occurs. This will help us identify the exact failure point and whether it’s related to state/cleanup, BSP setup, or a tool limitation.

2. Cleanup steps between attempts: Have you cleaned up any temporary files or directories between the first and second flash attempts? If so, what did you clean? (For example, did you remove /tmp files, the Linux_for_Tegra/tools/kernel_flash working directory, or other build artifacts?)

3. BSP directory reuse: Are you using the same Linux_for_Tegra (BSP) directory for both attempts, or did you extract a fresh copy for the second attempt?

Once we have these details, we can determine whether this is a known issue with the flash tool’s state management or a configuration problem specific to your setup.

[DavidDDD]

Hi,

Please try to add EXT_NUM_SECTORS environment

sudo EXT_NUM_SECTORS=1048576000 ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1
-c tools/kernel_flash/flash_l4t_t234_nvme.xml -p “-c bootloader/generic/cfg/flash_t234_qspi.xml”
-S 100GiB --showlogs --network usb0 jetson-orin-nano-devkit-super internal

Also please provide the full log, not just the error message.

Thanks

[rutvikvyas1224]

when i run this it give me error
rutvik@rutvik-Dell-G15-5520:~/OS/orin-modules/Linux_for_Tegra$ sudo EXT_NUM_SECTORS=1048576000 ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1
-c tools/kernel_flash/flash_l4t_t234_nvme.xml -p “-c bootloader/generic/cfg/flash_t234_qspi.xml”
-S 100GiB --showlogs --network usb0 jetson-orin-nano-devkit-super internal
[sudo] password for rutvik:
Flashing external device requires -c option to specify device partition layout
-c: command not found
-S: command not found
rutvik@rutvik-Dell-G15-5520:~/OS/orin-modules/Linux_for_Tegra$

[DavidDDD]

Hi,

It looks like there may be a typo in the commands. Please refer to the developer guide and copy the commands directly from the website.

Quick Start — NVIDIA Jetson Linux Developer Guide 1 documentation

Thanks