I would really appreciate your help regarding the issue I am having with updating to a new minor release from 35.2 to 35.3 using the sudo apt dist-upgrade command from the documentation.
I am facing this:
WARNING: rootfs A/B is enabled, can not update using Debian OTA, quit.
dpkg: error processing archive /tmp/apt-dpkg-install-tWm26u/6-nvidia-l4t-core_35.3.1-20230319081403_arm64.deb (--unpack):
new nvidia-l4t-core package pre-installation script subprocess returned error exit status 1
Errors were encountered while processing:
/tmp/apt-dpkg-install-tWm26u/6-nvidia-l4t-core_35.3.1-20230319081403_arm64.deb
This is the first time that I have been flashing the Jetson Linux 35.x. version and upgrading.
So far I have done with the 32.6. and 32.7 versions and there were no issues also with the AB update enabled. Is there something new here?
This is the command I have been using for flashing the device:
Regarding the disableing of A/B. I maybe got something wrong. I found a command: sudo nv_update_engine --disable-ab
I want to flash the AGX with the version 35.2 and using sudo apt dist-upgrade update it to 35.3. After that to create a Golden image of that updated version and use it for fleet update.
I cannot update to version 35.3. sudo apt dist-upgrade I get this error:
WARNING: rootfs A/B is enabled, can not update using Debian OTA, quit.
dpkg: error processing archive /tmp/apt-dpkg-install-tWm26u/6-nvidia-l4t-core_35.3.1-20230319081403_arm64.deb (--unpack):
new nvidia-l4t-core package pre-installation script subprocess returned error exit status 1
Errors were encountered while processing:
/tmp/apt-dpkg-install-tWm26u/6-nvidia-l4t-core_35.3.1-20230319081403_arm64.deb
Also I did not create a Golden Image using the version 35 because of the above issues. That’s the next step.
I did it using the 32 version and had no problems.
For my use-case it’s a lot easier to update in terminal then to do the flashing process each time I decide to do a update + all the apps already installed.
Can you also please help with the questions above regarding the AB. I also want to be able to have a rollback solution in case something goes south.
It’s a bit strange because when I did the same thing ( updating from R32.6 to R32.7 ) I had no problems. The AGX was also flashed with A/B. Is Debian update with A/B enabled for older Jetpack versions maybe?
Is there maybe a “hack” to disable the block_deb_update()?
My idea would be to do the Debian update on the A partition, create a Golden image and deploy this same image to the B partition so that they would be 1:1. Does that make sense?
Also sudo nvbootctrl set-active-boot-slot { partition No.} why do I get an error when I try to switch between partitions? I had no problems on the older Jetpack versions.
I don’t see the block_deb_update() in rootfs/opt/nvidia/l4t-bootloader-config/nv-l4t-bootloader-config.sh or anywhere similar. Can you please give me a link to where this was mentioned for JP5?
How do you mean verify? The first thing I did after flashing the AGX with A/B was trying to swap from A to B partition. That was the first try as soon the system booted up with any app installation or anything. I got the error:
sudo nvbootctrl set-active-boot-slot 0
mount: /opt/nvidia/esp: can't find UUID=.
Error: check and mount esp partition failed.
Error: open fail errno = 2 reason = No such file or directory
Error: write variable BootChainFwNext failed!
It’s in another script to check if rootfs_ab is enabled and it seems not the public source for JP5.
What I mean is to flash R35.3.1 directly with rootfs A/B enabled, and then use nvbootctrl to switch slot.
You could run the following command first to check current slot status.
I ran the same command on versions R35.1 and R35.2 and now I flashed R35.3.1 on the device and got the same error. I am not sure what was your aim here?
# R35 (release), REVISION: 3.1, GCID: 32827747, BOARD: t186ref, EABI: aarch64, DATE: Sun Mar 19 15:19:21 UTC 2023
by running: sudo nvbootctrl -t rootfs dump-slots-info
Can you please help me with the issue? I am not quite sure what I’m doing wrong here? Is the flashing process to the external SSD different then when doing the same thing one the older software versions like R32?
Asking becuase of this mount: /opt/nvidia/esp: can't find UUID=I[.
I used this command for flashing the device. The same command I used for R32. sudo ROOTFS_AB=1 ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1 -c ./tools/kernel_flash/flash_l4t_nvme_rootfs_ab.xml --external-only -S 30GiB --showlogs jetson-agx-xavier-devkit external
I created arbitrary 2x 30GB partitions for A and B.
I used the lsblk command aslo when i go to the “disks” I can see two partitions with 30GB.
After I run the flashing process for the R35…takes around 20mins to finish. The first thing after the system goes up I run that command and each time the same error. On R32 not. Goes fine.