I have a board that fails to enter the system properly when it is connected to the system. After connecting the serial port, the error message is as follows：
[ 10.871122] Root device found: mmcblk0p1
[ 10.879302] Found dev node: /dev/mmcblk0p1
[ 10.904333] exFAT-fs (mmcblk0p1): invalid boot record signature
[ 10.910432] exFAT-fs (mmcblk0p1): failed to read boot sector
[ 10.916298] exFAT-fs (mmcblk0p1): failed to recognize exfat type
[ 10.949762] ERROR: mmcblk0p1 mount fail…
[ 42.491874] vdd-12v-sys: disabling
[ 42.495380] vdd-1v8-sys: disabling
[ 42.498884] vdd-3v3-ftdi: disabling
The complete log is as follows： DEBUG_2025-07-29_11_22_26.log (171.2 KB)
I would like to ask, what caused the mmcplk0p1 mounting failure? Is it possible to correct the error without ./flash.sh ?
*** Please note that this reply is generated by LLM automatically ***
The error message you provided indicates that the Jetson AGX Orin board is unable to mount the root file system on mmcblk0p1, which is the first partition of the SD card or eMMC storage. The error messages suggest that the boot record signature is invalid, and the exFAT file system is not recognized.
There are several possible causes for this error:
Corrupted file system: The file system on mmcblk0p1 might be corrupted, which prevents the board from mounting it. This could be due to a power failure during writing, a faulty SD card or eMMC, or other factors.
Incorrect file system type: The error message mentions exFATfs, which is a file system type. However, the Jetson AGX Orin typically uses ext4 or other Linux file systems. If the file system type is incorrect, the board might not be able to mount it.
Boot record signature issue: The boot record signature is a critical part of the boot process. If it’s invalid, the board might not be able to boot properly.
Partitioning issue: The partitioning of the SD card or eMMC might be incorrect, which could prevent the board from mounting the root file system.
To correct the error without reflashing the entire board, you can try the following:
Check the file system: Use a tool like fsck to check the file system on mmcblk0p1 for errors and try to repair it.
Verify the file system type: Check the file system type on mmcblk0p1 using blkid or lsblk commands. If it’s not ext4 or another supported file system, you might need to reformat the partition.
Update the boot record signature: Use a tool like mkfs to update the boot record signature on mmcblk0p1.
Repartition the SD card or eMMC: If the partitioning is incorrect, you might need to re partition the SD card or eMMC using a tool like fdisk or gdisk.
Before attempting any of these steps, make sure to backup any important data on the SD card or eMMC to prevent data loss.
In comparison to other issues mentioned in the context, this error is similar to the “Boot failed” issue on Jetson Xavier NX, where the board is unable to boot due to a corrupted file system or incorrect partitioning. However, the specific error messages and causes might differ.
It’s also worth noting that the Rin Nano 8GB Developer Kit and Custom board PMIC issues mentioned in the context are unrelated to this specific error, as they deal with different hardware and software configurations.
*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***
Thanks，
This module functions properly after being placed in the ./flash directory. However, after conducting numerous experiments of power loss and restart, it is unable to enter.
Currently, the module cannot be integrated into the system, so commands like lsblk are unavailable. Therefore, it seems that we can only re-flash the device.