Issues With Image-Based OTA, Failure To Mount Rootfs "ERROR: PARTUUID Mount Fail"

[lphillips]

We are trying to perform OTA update from 35.2.1 to 35.4.1 on Jetson Orin NX16GB modules with L4T 35.2.1on an NVMe drive with an Orin NX devkit.

When generating an OTA payload to update to 35.4.1, we are capturing the rootfs from another Orin NX with 35.4.1 in a devkit with the following method: Flashing Support — Jetson Linux Developer Guide documentation

I generate the OTA payload for 35.4.1 using the following command:

 sudo -E ./tools/ota_tools/version_upgrade/l4t_generate_ota_package.sh -s -f system.img --external-device nvme0n1 jetson-orin-nano-devkit R35-2

The image-based OTA is uploaded to the Orin and I initiate the update according to the instructions here: Software Packages and the Update Mechanism — Jetson Linux Developer Guide documentation

After the ota payload is ran, i run a sudo reboot command and I see the following error in the UART logs and the system doesn’t complete boot.

What does this error mean and how can I fix it?

[   10.701588] nvme nvme0: Shutdown timeout set to 8 seconds
[   10.722802] nvme nvme0: 8/0/0 default/read/poll queues
[   10.736075]  nvme0n1: p1 p2 p3 p4 p5 p6 p7 p8 p9 p10 p11 p12 p13 p14
[   10.746905] Freeing unused kernel memory: 3968K
[   10.758722] Run /init as init process
[   10.774965] Root device found: PARTUUID=123924e5-cd65-4f0e-bb98-d8fa0723d2f9
[   23.157381] ERROR: PARTUUID=123924e5-cd65-4f0e-bb98-d8fa0723d2f9 mount fail...

I have attached full UART logs below of the update process as well as the failure to boot after the update completes.
out_intitrd_clone_x1.txt (827.9 KB)

[KevinFFF]

Hi lphillips,

@lphillips

I generate the OTA payload for 35.4.1 using the following command:

I would like to check the full flash log from host when you run this command.

and it seems you don’t need to specify -f system.img in this command.

[lphillips]

Thanks for the reccomendation!

We are using the -f option to specify a file path to the image that we clone from another system.

I have solved this problem by editing the extlinux.conf file before generating the OTA payload.

I edit the APPEND line to include root=/dev/nvme0n1p1 instead of the partition UUID being hardcoded root=PARTUUID=123924e5-cd65-4f0e-bb98-d8fa0723d2f9

Fixing that one line solved this problem for me. The system can now boot properly after image-based OTA from L4T 35.2.1 to L4T 35.4.1.