During my testing, I saw that the uefi bootloader started a recovery boot.
Do you know what triggers the uefi bootloader to perform a recovery boot opposed to presenting the menu in /boot/extlinux/extlinux.conf?
I’d like to understand why this happens, as I may need to report to the vendor of the carrier board the circumstances if this continues to occur.
If the nv-l4t-bootloader-config.service fails to run or fail to successfully finishes for consecutive 3 times, then it will enter recovery boot.
sudo systemctl status nv-l4t-bootloader-config
This could be any kind of reason. For example, if there is kernel panic happened and make your board unable to boot rootfs, and it happens 3 times consecutively, then it will trigger recovery boot.
I don’t understand. How does the script both fail to run and finish successfully? I’ll run the script with set -x and see what’s happening. Thanks for the pointer.
Hi,
Sorry that my comment was not precise.
It should be " fails to run or fail to successfully finishes".
I would suggest you just run your normal usecase and enable serial console to monitor the log.
Generally, this issue is mostly happened after kernel panic.
Run this script alone will not help in debugging this issue. The root cause of such issue is mostly from others.
Hi Wanye,
Thank you for the information.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.