Error in AGX Xavier Kirkstone (Using recent update for JetPack5)

Hello,

I am currently trying to use Mender for OTA updates on a Jetson AGX Xavier devkit machine. It works well with dunfell (MenderHub-AGX Xavier)

According to the recent meeting notes (OE4T Meeting Notes 2024‐08‐08), Mender is supposed to support JetPack 5 Kirkstone.

Following this, I conducted a basic build using the meta-mender-community with the following command:

git clone -b kirkstone https://github.com/mendersoftware/meta-mender-community.git
mkdir -p meta-mender-community/my-build && cd meta-mender-community/my-build
kas build ../kas/jetson-agx-xavier-devkit

However, when I applied the resulting image to the Xavier devkit, I encountered the following error:

[FAILED] Failed to start Mender ser…e to grow data partition size.
See 'systemctl status mender-grow-data.service' for details.
         Mounting /data...
[   55.190773] exFAT-fs (mmcblk0p42): invalid boot record signature
[   55.191952] exFAT-fs (mmcblk0p42): failed to read boot sector
[   55.193082] exFAT-fs (mmcblk0p42): failed to recognize exfat type
[FAILED] Failed to mount /data.
See 'systemctl status data.mount' for details.
[DEPEND] Dependency failed for Grow File System on /data.
[DEPEND] Dependency failed for Local File Systems.
[  OK  ] Stopped Dispatch Password …ts to Console Directory Watch.
[  OK  ] Stopped Forward Password R…uests to Wall Directory Watch.
[  OK  ] Closed Syslog Socket.
         Starting Record Runlevel Change in UTMP...
[  OK  ] Started Emergency Shell.
[  OK  ] Reached target Emergency Mode.
[  OK  ] Finished Record Runlevel Change in UTMP.
You are in emergency mode. After logging in, type "journalctl -xb" to view
system logs, "systemctl reboot" to reboot, "systemctl default" or "exit"
to boot into default mode.

Cannot open access to console, the root account is locked.
See sulogin(8) man page for more details.

Press Enter to continue.

Could you help me identify what might be my fault, or offer any advice?

Hi @gyuhwan-park,

Strange, there definitely should not be an exFAT filesystem be involved as far as I can tell. I’ll try to reproduce this one, at least the build as I don’t have the board available. Will get back to you once I know something, but it will be some days.

Maybe @zach-welch-aquabyte has an immediate pointer?

Greets,
Josef

1 Like

Hi @TheYoctoJester

Thanks for taking a look. I’ll keep following this error and the post closely to resolve the problem, so feel free to reply anytime. I appreciate your response.