HI
The original version of my orin nano jetpack was 6.2.0, and the L4T version was: R36 (release), REVISION: 4.3. After performing online update and upgrade, the L4T version became: R36 (release), REVISION: 4.7. However, after running the “reboot” command and completing the update, the system failed to boot up. The boot log indicated:
[ 13.584968] ERROR: Failed to mount PARTUUID=3f728058-323c-4adb-8f2c-03bc70eefff7 as /mnt…
[ 13.587944] ERROR: PARTUUID=3f728058-323c-4adb-8f2c-03bc70eefff7 mounting failed…
Here is my complete boot log. Please help me solve this issue.
*** Please note that this reply is generated by LLM automatically ***
Based on the provided boot log, it appears that the issue is related to the boot process failing to mount a partition with the PARTUUID 3f728058-323c-4adb-8f2c-03bc70eefff7. This partition is likely the root file system.
After reviewing the boot log, I noticed that the error message indicates a failure to mount the partition, followed by a message indicating that the mounting failed. This suggests that there might be an issue with the file system or the partition table.
Since you mentioned that the L4T version was updated from R36 release REVISION 43 to R36 release REVISION 47, it’s possible that the update process might have caused some changes to the file system or partition table that are not compatible with the current boot configuration.
To troubleshoot this issue, I would recommend the following steps:
Check the partition table: Use the fdisk or gdisk command to verify the partition table and ensure that the partition with the PARTUUID 3f728058-323c-4adb-8f2c-03bc70eefff7 is correctly defined and not corrupted.
Verify file system integrity: Run the fsck command to check the file system for any errors or inconsistencies. This might help identify any issues with the file system that could be preventing the boot process from completing.
Check the boot configuration: Review the boot configuration files (e.g., /boot/extlinux/extlinux.conf) to ensure that the correct root file system is specified and that the PARTUUID is correctly defined.
Try booting with a different kernel: If possible, try booting with a different kernel version to see if the issue is specific to the updated kernel.
Revert to a previous version: If none of the above steps resolve the issue, you might need to revert to a previous version of the L4T release (R36 release REVISION 43) to see if the issue is specific to the updated version.
It’s also worth noting that the Jetson Orin Nano has a known issue with booting after updating to L4T R36 release REVISION 47, which is related to a change in the boot configuration. You can try applying the workaround described in the NVIDIA forums to see if it resolves the issue.
If none of these steps resolve the issue, please provide more information about your system configuration, and I’ll do my best to assist you further.
*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***
HI
Thank you for your reply. I checked the nvme file that couldn’t be booted. The partition and the file are both present. Reverting the L4T version to 36.4.3, the Orin Nano still couldn’t boot and the error message was the same as before. However, using a new NVME solid-state drive, it was possible to boot. The UUID names mentioned in the comparison log are the same. I suspect that the upgrade caused some abnormalities in the NVME. Could you please help confirm the solution?
/usr/sbin/nv-update-initrd: line 127: cpio: command not found
Cleaning up the temporary directory for updating the initrd..
dpkg: error processing package nvidia-l4t-initrd (--configure):
installed nvidia-l4t-initrd package post-installation script subprocess returned error exit status 127
Errors were encountered while processing:
nvidia-l4t-initrd
E: Sub-process /usr/bin/dpkg returned an error code (1)
