`nvsdkmanager_flash` doesn't partition as expected

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

The command I used is

sudo -E ROOTFS_AB=1 ROOTFSSIZE=240GiB ./nvsdkmanager_flash.sh --storage nvme0n1p1

I expected nvme0n1p1 and nvme0n1p2 to be both 120GiB, instead I have nothing that is 120GiB and my rootfs partition is on mmcblk0p1 and mmcblk0p2.

A followup question is:

  1. Can I adjust partitions via a rootfs.tar based OTA?
  2. Can I encrypt my disk and do an OTA? I read documentation say this is possible, but someone (I think a mod, not sure) on the forum say r35 onwards it isn’t possible. Not sure which source to follow (source: Disk Encryption Feature Support - #11 by JerryChang)

I am running AGX Orin DevKit with r35_release_v5.0/release/ota_tools_R35.5.0_aarch64.tbz2

Just want to know which part I’m messing up in!

Thanks for the patience and help folks!

3

Hi sabhinav,

What’s your Jetpack version in use?

Partition is determined from the partition layout XML. We don’t suggest you modify it if you are not familiar with how it works.

Disk-encryption for OTA is supported from R35.5.0. (i.e. you can flash your board with disk-encryption in R35.4.1 and perform image-based OTA updating to R35.5.0)

Please use initrd flash command and -S option to specify the size for rootfs to flash your NVMe SSD.
If you want to enable rootfs a/b and get 120GiB for each rootfs partition, please just specify -S 120GiB in the initrd flash command.

4

SDK Manager never supports ROOTFS_AB.

5

Thanks @KevinFFF - sudo ROOTFS_AB=1 ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1 -S 120GiB -c ./tools/kernel_flash/flash_l4t_t234_nvme.xml jetson-agx-orin-devkit external is what I ran right now.

NAME         MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
loop0          7:0    0    16M  1 loop 
mmcblk0      179:0    0  59.3G  0 disk 
├─mmcblk0p1  179:1    0    27G  0 part 
├─mmcblk0p2  179:2    0    27G  0 part 
├─mmcblk0p3  179:3    0   128M  0 part 
├─mmcblk0p4  179:4    0   768K  0 part 
├─mmcblk0p5  179:5    0  31.6M  0 part 
├─mmcblk0p6  179:6    0   128M  0 part 
├─mmcblk0p7  179:7    0   768K  0 part 
├─mmcblk0p8  179:8    0  31.6M  0 part 
├─mmcblk0p9  179:9    0    80M  0 part 
├─mmcblk0p10 179:10   0   512K  0 part 
├─mmcblk0p11 179:11   0    64M  0 part 
├─mmcblk0p12 179:12   0    80M  0 part 
├─mmcblk0p13 179:13   0   512K  0 part 
├─mmcblk0p14 179:14   0    64M  0 part 
├─mmcblk0p15 179:15   0   400M  0 part 
└─mmcblk0p16 179:16   0 479.5M  0 part 
zram0        251:0    0   2.6G  0 disk [SWAP]
zram1        251:1    0   2.6G  0 disk [SWAP]
zram2        251:2    0   2.6G  0 disk [SWAP]
zram3        251:3    0   2.6G  0 disk [SWAP]
zram4        251:4    0   2.6G  0 disk [SWAP]
zram5        251:5    0   2.6G  0 disk [SWAP]
zram6        251:6    0   2.6G  0 disk [SWAP]
zram7        251:7    0   2.6G  0 disk [SWAP]
zram8        251:8    0   2.6G  0 disk [SWAP]
zram9        251:9    0   2.6G  0 disk [SWAP]
zram10       251:10   0   2.6G  0 disk [SWAP]
zram11       251:11   0   2.6G  0 disk [SWAP]
nvme0n1      259:0    0 931.5G  0 disk 
├─nvme0n1p1  259:1    0 930.1G  0 part /
├─nvme0n1p2  259:2    0   128M  0 part 
├─nvme0n1p3  259:3    0   768K  0 part 
├─nvme0n1p4  259:4    0  31.6M  0 part 
├─nvme0n1p5  259:5    0   128M  0 part 
├─nvme0n1p6  259:6    0   768K  0 part 
├─nvme0n1p7  259:7    0  31.6M  0 part 
├─nvme0n1p8  259:8    0    80M  0 part 
├─nvme0n1p9  259:9    0   512K  0 part 
├─nvme0n1p10 259:10   0    64M  0 part 
├─nvme0n1p11 259:11   0    80M  0 part 
├─nvme0n1p12 259:12   0   512K  0 part 
├─nvme0n1p13 259:13   0    64M  0 part 
├─nvme0n1p14 259:14   0   400M  0 part 
└─nvme0n1p15 259:15   0 479.5M  0 part

Is what is generated. Instead I want 1 50GiB MMC partition and two 120GiB NVME partitions.

6

It seems there’s only one rootfs in your NVMe drive (i.e. rootfs a/b is not enabled).
Do you mean the result you shared is from above command?
If so, please share the full flash log for further check.

7

It is the result of the flash, I get that on running lsblk.

Here’s the logs: Flash Log for initrd Jetson AGX Orin DevKit - Pastebin.com

8

It seems you’ve flash the board successfully and check the disk is encrypted in How do I verify if my Jetson AGX Orin Devkit was encrypted? - #2

10

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