How to change ROOTFSSIZE from 55GiB to 88Gib, or bigger one?

It seems that the APP size is also limited to 55GiB in tegrahost_v2, so if I make it bigger than 60GiB, there is no effect.
For orin nano or orin NX,When I change ROOTFSSIZE from 55GiB to a 88Gib in Linux_for_Tegra\p3767.conf.common, a problem occurs when doing l4t_initrd_flash.sh.
[ 4.2169 ] Copying signatures
[ 4.2174 ] tegrahost_v2 --chip 0x23 0 --partitionlayout flash.xml.bin --updatesig images_list_signed.xml
[ 4.2188 ] tegraparser_v2 --generategpt --pt flash.xml.bin
[ 4.2194 ] End sector for APP, expected at: 119537630, actual: 0
Error: Return value 4
Command tegraparser_v2 --generategpt --pt flash.xml.bin
cp: cannot stat ‘signed/*’: No such file or directory
cp: cannot stat ‘signed/flash.xml.tmp’: No such file or directory

After do l4t_initrd_flash.sh,the start location of secondary_gpt is always 61203267072, so the ROOTFSSIZE is limited.
78, 6:0:secondary_gpt, 61203267072, 16896, gpt_secondary_6_0.bin, 16896, fixed--0, 3786addac7a4a5c52ba79176a451df8340b151d2

please provide the full flash log as attachment.

What’s the full flash log?

Those things printed on your terminal when you run the flash command.

When I change ROOTFSSIZE from 55GiB to a 88Gib in Linux_for_Tegra\p3767.conf.common,build with l4t_initrd_flash.sh will fail.
The whole log is as follows:
20241008-nvidia-build-01.log (149.8 KB)

Is this still an issue to support? Any result can be shared?

This issue is not solved now, and it happens exactly.
Can the technology engineers of Nvidia give some
solution ideas?

Hi smb_5,

Are you using the devkit or custom board?
What’s the Jetpack version in use?

You should also specify the NUM_SECTORS in partition layout XML file.
Please refer to How to solve the issue that ssd are not entiely availiable after full disk encryption - #5 by KevinFFF for their relationship.

Or you can let us know what the physical size of your NVMe SSD and what’s the desired size you want to use for rootfs.

Hi KevinFFF

NVIDIA Jetson Orin NX Engineering Reference Developer Kit - Jetpack 6.0 [L4T 36.3.0]
The physical size of nvme is 256GiB, and the desired size for rootfs should be 88Gib or any more .

How to solve the problem listed above?

You question is already answered by this statement.

You should also specify the NUM_SECTORS in partition layout XML file.
Please refer to How to solve the issue that ssd are not entiely availiable after full disk encryption - #5 by KevinFFF for their relationship.
Or you can let us know what the physical size of your NVMe SSD and what’s the desired size you want to use for rootfs.

1 Like

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.