Lsblk difference between sdkmanager flash and initrd flash

[kd61370]

Hi,

I have Jetson AGX Orin 64 gb developer kit.
With using R35.4.1

I observed that there are differences in nvmen0 partitions between sdkmanager flash and initrd flash. I would like to know why there is difference and what these differences matter?

SDKManager flashed device lsblk command

lsblk
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    55G  0 part 
├─mmcblk0p2  179:2    0   128M  0 part 
├─mmcblk0p3  179:3    0   768K  0 part 
├─mmcblk0p4  179:4    0  31.6M  0 part 
├─mmcblk0p5  179:5    0   128M  0 part 
├─mmcblk0p6  179:6    0   768K  0 part 
├─mmcblk0p7  179:7    0  31.6M  0 part 
├─mmcblk0p8  179:8    0    80M  0 part 
├─mmcblk0p9  179:9    0   512K  0 part 
├─mmcblk0p10 179:10   0    64M  0 part 
├─mmcblk0p11 179:11   0    80M  0 part 
├─mmcblk0p12 179:12   0   512K  0 part 
├─mmcblk0p13 179:13   0    64M  0 part 
├─mmcblk0p14 179:14   0   400M  0 part 
└─mmcblk0p15 179:15   0 479.5M  0 part 
zram0        251:0    0   7.7G  0 disk [SWAP]
zram1        251:1    0   7.7G  0 disk [SWAP]
zram2        251:2    0   7.7G  0 disk [SWAP]
zram3        251:3    0   7.7G  0 disk [SWAP]
nvme0n1      259:0    0 465.8G  0 disk 
├─nvme0n1p1  259:1    0 464.3G  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

and this is initrd headless flash

lsblk
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    55G  0 part 
├─mmcblk0p2  179:2    0   128M  0 part 
├─mmcblk0p3  179:3    0   768K  0 part 
├─mmcblk0p4  179:4    0  31.6M  0 part 
├─mmcblk0p5  179:5    0   128M  0 part 
├─mmcblk0p6  179:6    0   768K  0 part 
├─mmcblk0p7  179:7    0  31.6M  0 part 
├─mmcblk0p8  179:8    0    80M  0 part 
├─mmcblk0p9  179:9    0   512K  0 part 
├─mmcblk0p10 179:10   0    64M  0 part 
├─mmcblk0p11 179:11   0    80M  0 part 
├─mmcblk0p12 179:12   0   512K  0 part 
├─mmcblk0p13 179:13   0    64M  0 part 
├─mmcblk0p14 179:14   0   400M  0 part 
└─mmcblk0p15 179:15   0 479.5M  0 part 
zram0        251:0    0   3.9G  0 disk [SWAP]
zram1        251:1    0   3.9G  0 disk [SWAP]
zram2        251:2    0   3.9G  0 disk [SWAP]
zram3        251:3    0   3.9G  0 disk [SWAP]
zram4        251:4    0   3.9G  0 disk [SWAP]
zram5        251:5    0   3.9G  0 disk [SWAP]
zram6        251:6    0   3.9G  0 disk [SWAP]
zram7        251:7    0   3.9G  0 disk [SWAP]
nvme0n1      259:0    0 465.8G  0 disk 
├─nvme0n1p1  259:1    0 464.9G  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   300M  0 part 
├─nvme0n1p11 259:11   0    64M  0 part 
├─nvme0n1p12 259:12   0    80M  0 part 
├─nvme0n1p13 259:13   0   512K  0 part 
└─nvme0n1p14 259:14   0    64M  0 part 

The initrd method that I use

wget https://developer.nvidia.com/downloads/embedded/l4t/r35_release_v4.1/release/jetson_linux_r35.4.1_aarch64.tbz2

wget https://developer.nvidia.com/downloads/embedded/l4t/r35_release_v4.1/release/tegra_linux_sample-root-filesystem_r35.4.1_aarch64.tbz2

tar xf jetson_linux_r35.4.1_aarch64.tbz2

sudo tar xpf tegra_linux_sample-root-filesystem_r35.4.1_aarch64.tbz2 -C Linux_for_Tegra/rootfs/

cd Linux_for_Tegra/

sudo ./apply_binaries.sh

sudo ./tools/l4t_flash_prerequisites.sh

sudo ./tools/l4t_create_default_user.sh -u username -p password -n hostname 

 sudo ./tools/kernel_flash/l4t_initrd_flash.sh --network usb0 --external-device nvme0n1p1 -c tools/kernel_flash/flash_l4t_nvme.xml --external-only --showlogs jetson-agx-orin-devkit nvme0n1p1

I will share if any file or logs are needed.

[linuxdev]

I don’t know what the differences are. I will suggest though that you use “lsblk -f” to see labels and partition ID information. Labels are often used to pick partitions, and sometimes the PUID.

Also, there are several .conf and/or .xml configurations (starting with a .conf that can include other configuration files) which actually specify partition layout. Any time you flash on command line you will find it useful to save a log. You can do this by appending this to the end of your command line:
" 2>&1 | tee log_flash.txt"
(the leading space is important)

You should see a series of messages during the flash which will explain conf and xml content as they are used.