Hi, when i boot my device can’t find the root file system in mmcblk0 (default) and it only finds initrd work as the root file system. Then go into recover mode. Here is my log from Systemlog.
log_boot-failed.txt (58.5 KB)
Hi chudat1204,
Are you using the devkit or custom board for Xavier NX?
Is that the eMMC or SD module?
Have you tried to reflash the board?
From the log you shared, it seems you boot into recovery kernel.
I am using custom board and eMMC module. If i reflash it doesn’t have problem. Now,
What can I do to keep my device not boot into recovery kernel?
Thanks.
Do you know the detailed reproduce steps to enter into recovery kernel?
Are you trying to perform reboot test continuously?
Normally, it will enter into this state if it can not boot from the device successfully.
You can refer to the following thread for the details of our mechanism.
Reset Timing of Boot Retry Count - #7 by KevinFFF
i don’t know the reason lead to my problem. After a long time, i use my device and rebooted it and appear the problem. Now when i reboot it still go into recovery mode.
What we care is only why this happened. We don’t really care about recover image mechanism because we already knew how it worked. That is a mechanism we provided.
To recover from recovery image, please read this pst.
Once it is back to normal boot, if it fails to boot into Linux, it will go back to recovery image again. We need the log why it fails to boot into Linux.
Also, this is not recovery mode. This is recovery image.
But i wanna trace the original problem that lead to my device go into recovery mode. So how i can do to check log do something to trace this.
Wayne has suggested that we would need the serial console log to check the reason to enter into recovery kernel.
Could you reproduce the issue again?
If so, please provide the full serial console log for further check.
Here is my serial log. Thanks.
log_boot-failed.txt (58.5 KB)
The new log you shared is still useless…
Please tell me what is your understanding of this comment…
We already explained what to do here but it seems you don’t understand.
I don’t need your recovery boot log. I need you to follow the step first, make it able to go back to normal boot again. Try to reproduce the error and share me the log before the next recover boot happens. It could be some kernel panic or something else that leads to recovery boot. That is what we care.
Okay I understand but when I do like this post my device runs xavier-nx don’t have the same option when go into UEFI Menu. My device don’t have NIDIA configuration it only has some options like the image below.
ìf i choose NVIDIA Resource Configuration it just have like this image. It don’t like your guide. Thanks.
Is it NV devkit or custom board? Are you able to upgrade the BSP?
Log indicates the version seems to old.
it’s hard for me. My device was bought for my customer and can’t update the new BSP. Now my device has a problem like my post. How can you have another way to boot into normal mode
Hi,
Then could you reflash the board with your version and monitor the UART log before entering recovery boot? The other method to recover from recovery boot could be hardware to implement. I mean it is possible, but maybe too difficult to you.
Hope you understand what I mean here.
i was reflash with another device with the same problem. It boot without go into recovery mode. So now What must I do to trace the original problem? Because if I reflash my device, it isn’t running the old state i can’t reproduce the same problem. Thanks
Then just wait until next time you hit the same issue.
If this is intermittent issue then you need to be patient and try to figure out the error pattern.
If you want some help from us, upgrade your BSP first.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.