Rootfs Resize Issue - Jetson Nano 4GB Dev Version - Rootfs Partition Limited to 14–16GB

I’m facing an issue when flashing Jetson OS images onto SD cards of different capacities (32GB and 128GB). After flashing, the root filesystem (APP partition) is always limited to around 14–16GB, regardless of the actual SD card size.

  • Example:

    • On a 32GB SD card, rootfs shows ~12–14GB, rest of the space is not accessible.

    • On a 128GB SD card, only ~16GB is seen, the remaining >100GB is missing.

I’ve tried the following without success:

  • resize2fs

  • parted / fdisk / growpart

  • Manually expanding partitions from host and Jetson

On the host PC (GParted), I can see the full device size (example: /dev/sda = 119GB). However, after flashing and booting into the Jetson, the system still only shows the ~16GB rootfs, and the extra space doesn’t appear even as “unallocated.”

It seems like the flashing script (or default partition layout) caps the rootfs at ~16GB no matter the SD card size.

My questions:

  1. Is this a known limitation of Jetson OS images (default partition table)?

  2. Can I modify flash.sh or the partition configuration to allow using the full SD card capacity for the APP partition?

  3. What’s the correct procedure to resize/expand the rootfs after flashing so that Jetson sees the entire storage?

Any help or pointers to documentation would be greatly appreciated.

Apparently most of the forums here have solution for the SD cards that have space detected mine. is straight up saying that I have a 16GB card and not a 32GB card.

Hi,

The first boot of Jetson shall give out a GUI prompt for you to adjust the size.

no it didnt work. I reflashed multiple times and I never got the first boot page GUI

What did you see in your UART log? Does it directly give you login prompt to login?

yes it gives direct login prompt. The GUI to let me configure the nano only comes when I am flashing with SDK manager when I do a flash with manual flash.sh or etcher or dd it doesnt take the new image. it shows me the previous image. so I use SDK manager to manually flash it w a image that gives 16GB to root. so in the GUI I said earlier it doesnt have any option to resize root.

now I am trying to figure out if there is another way to flash my nano (which is not eMMC it is dev kit) with a custom image or command like ./flash.sh through SDK manager in recovery mode.

cause outside of recovery mode I am unable to flash a new image. it simply isnt working.

Hi,

If the system does not ask you to configure account in your first boot, it means there was a default user account created on the BSP package on your host PC.

You could remove that thing and let sdkmanager download it again.

Default patch is under ~/nvidia on your Linux host.

this came up and no GUI config for resizing root showed up and after that…

this came up and login came up. with new username

Oh. Sorry. I just realize something here.

Could you share your full dmesg from uart?

or share your flash log from sdkmanager.

I am not using an eMMC device. I think I made a mistake by flashing using SDK Manager because it made my rootfs size to 16GB and in now way I am able to resize it.

right now I am flashing using these instructions for on-board QSPI + SD card.

https://developer.download.nvidia.com/embedded/L4T/r32_Release_v1.0/Docs/l4t_quick_start_guide.txt?t=eyJscyI6ImdzZW8iLCJsc2QiOiJodHRw

now I am waiting for the ./flash.sh to complete and I am here since an hour

Right now, I am looking into how to fully reset a Jetson Nano 4GB Developer Kit that was previously flashed via SDK Manager (which wrote an eMMC-style partition layout), so it stops treating new SD cards as eMMC-based and correctly boots from a freshly written official SD card image.

Hi,

I just want to point something here.

Sdkmanager won’t make a mistake that recognize that “your NV devkit” is a emmc module and flash emmc partition to it.

The reason that sdkmanager did that is because you are really using a emmc module.

Where is your sdcard slot located? Is it on the carrier board or the module itself?

We’ve seen lots of users thinking they are using sdcard module but turns out they are not…’

The SD card is on the carrier board.

Then this is a custom board with emmc module…

I wrote a post before to explain, please check this.

So how do I proceed with this board. what is the solution?

please check with the board vendor. This is also mentioned in the post.

Hi,

Thank you for clarifying. I am using a Seeed Studio J101 Carrier Board (custom board with eMMC).
I found a working solution here in this website for my board:

1 Like