Unexpected power loss and reboot issues during Thor OTA updates

If the A/B partition mode is not enabled, will an unexpected power failure during the OTA process cause the OTA to fail?

hello cuihao.123,

let me have confirmation,
bootloader A/B (i.e. Bootloader redundancy) is enabled by default.
did you meant Root File System Redundancy?

BTW,
please visit L4T page, Jetson Linux Archive | NVIDIA Developer to download the JP-7.1/r38.4 OTA Tools.
you may see-also readme file for reference,
for instance,
$OUT/Linux_for_Tegra/tools/ota_tools/version_upgrade/Image_based_OTA_Examples.txt

Yes, I’m referring to root filesystem redundancy. If root filesystem redundancy is not enabled, will a power outage or reboot during the OTA process cause the OTA to fail?

Actual testing found that after an abnormal power loss during the OTA process, the OTA cannot be resumed upon power‑on again.

uart_log.txt (178.4 KB)

Decompress rootfs image into /dev/nvme0n1p1 ...
tar -xpf /mnt/ota_work/external_device/system.img --checkpoint=10000 --warning=no-timestamp --numeric-owner --xattrs --xattrs-include=* -C /tmp/mnt/
..
tar: Read checkpoint 60000
tar: Read checkpoint 70000
tar: Read checkpoint 80000
tar: Read checkpoint 90000

Error reading from serial device
..
.▒▒.▒▒.▒▒.▒▒.▒▒.▒▒.▒▒L4TLauncher: Attempting Recovery Boot▒▒L4TL▒▒
..
insmod /lib/modules/6.8.12-tegra/updates/drive[    5.310246] Mount initrd as rootfs and enter recovery mode
..
[    7.144852] Internal storage device(/dev/mmcblk0p1) does not exist
[    7.151115] OTA work directory is not found on internal and external storage devices
bash: no job control in this shell
bash-5.2#

From the log you shared, the “abnormal power loss” happens when it is writing the /dev/nvme0n1p1(i.e. APP partition) so it boots into recovery kernel in next boot.

It is expected as your rootfs is corrupted.
As it boots into recovery kernel and you can run command there, please connect a USB stick and use dd command to repair the APP partition.
You can refer to Flashing Support — Cloning rootfs with initrd to clone the rootfs to USB storage on a working device.

The problem occurred due to an unexpected power loss during OTA. According to the document, the update should be resumable after reboot, but this mechanism did not work. Why?

hello cuihao.123,

unfortunately, it can not recovery from a hard power loss in the middle of the update, your APP partition has been written.