Rootfs is no longer A/B after a capsule update

Robotics & Edge Computing Jetson Systems Jetson Orin NX
,
1

My system relies on the ROOTFS_AB mechanism and before doing any update this is working but as soon as I perform an OTA update for the UEFI bootloader (using 35.6.2) then after I reboot the system, the capsule update is performed as expected but when I check the status using:

nvbootctrl dump-slot-info then it indicates the capsule update status, that current slot is now B and there are 2 slots, so far so good but when I check for the rootfs, I get:

RootFS A/B is not enabled

So my questions are:

  • What could explain this behavior.
  • What can be done make an attempt to fix this problem? Is it an issue with the OTA payload itsefl (generated using option -b)?
  • Is there some script that can reactivate rootfs A/B as the rootfs partitions are still valid

Is this a known limitation with 35,6.2 when use with secure boot and full disk encryption?

Thanks

4

hello sebastien.schertenleib,

that’s usually due to you’re created OTA payload without rootfs-ab prefixes.
please double check you have ROOTFS_AB=1 included in your commands.

5

Hello,

I added it in front of most of the scripts involved and this did the trick. Still I do not foresee why for bootloader only this is required. I think the document should be improved in that regards.

Thanks anyway.

6

just an FYI, we did have documentation update of adding ROOTFS_AB=1 options for generating multi-spec BUP section.