Error upgrading Jetkack 5.1.1 to 5.1.2 on Xavier NX - Failed to get number of rootfs slots

Autonomous Machines Jetson & Embedded Systems Jetson Xavier NX
, ,
1

Hi there, I have a NVIDIA Jetson Xavier NX Developer Kit - Jetpack 5.1.1 [L4T 35.3.1]
Am following the steps to upgrade to 5.1.2, 1.3 section from here
https://docs.nvidia.com/jetson/jetpack/install-jetpack/index.html#package-management-tool

~$ sudo dpkg --configure nvidia-l4t-kernel
Setting up nvidia-l4t-kernel (5.10.120-tegra-35.4.1-20230801124926) …
Using the existing boot entry ‘primary’
3668-100—1–jetson-xavier-nx-devkit-
Info. Active boot storage: mmcblk0
Info. Legacy mode: false
TNSPEC 3668-200-0000-J.0-1-2-jetson-xavier-nx-devkit-
COMPATIBLE_SPEC 3668-100—1–jetson-xavier-nx-devkit-
TEGRA_LEGACY_UPDATE false
TEGRA_BOOT_STORAGE mmcblk0
TEGRA_EMMC_ONLY false
TEGRA_CHIPID 0x19
TEGRA_OTA_BOOT_DEVICE /dev/mtdblock0
TEGRA_OTA_GPT_DEVICE /dev/mtdblock0
Info: Write TegraPlatformCompatSpec with 3668-100—1–jetson-xavier-nx-devkit-.
Starting kernel post-install procedure.
ERROR. Failed to get number of rootfs slots. Exiting…
dpkg: error processing package nvidia-l4t-kernel (–configure):
installed nvidia-l4t-kernel package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
nvidia-l4t-kernel

not sure how to continue? I appreciate any guidance on the issue, thanks

3

Hi,

what was the full workflow you used?
Why did you need to configure the package manually?
Can you then please try a full re-flash with SDK Manager?

4

I was trying to skip the reflash operation as I will need to reinstall/setup everything. I would need to redo the operation in other machines (we cannot just clone a SD card).

I followed the 1.3. Package Management Tool section as detailed. Do not remember exactly when it started to happen the problem, I tried to isolate it ad tested different alternatives to configure nvidia-l4t-kernel package but without success. I was hoping to get some direction on files to check, manually do some change if possible and retry.

5

Hi,

if we don’t have the full log when the OTA fails, then it’s hard to further debug.
I’d suggest a clean re-flash with 35.4.1.

Or maybe check the 4191596 issue in the release note:

7

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