-
Notifications
You must be signed in to change notification settings - Fork 51
Description
Hello,
I am currently trying to generate my own Petalinux image (Version 2024.1) with ROS2 integration and some further dependencies.
I can add all dependencies and configurations except the ros2-dev dependencies and successfully build a wic image and use it on the board, but when I try to add the ros2-dev packagegroup or manually add its dependencies the process works out fine but the generated image contains a corrupted rootfs partition.
When booting, I see the following error message:
[ 6.275596] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 6.285553] sda: sda1 sda2
[ 6.288574] sd 0:0:0:0: [sda] Attached SCSI removable disk
root contains a file system with errors, check forced.
fsck.ext4: Inode checksum does not match inode while reading bad blocks inode
root: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(i.e., without -a or -p options)
Warning: fsck failed, try running fsck manua[ 7.518822] EXT4-fs error (device sda2): __ext4_fill_super:5474: inode #2: comm mount: iget: checksum invalid
lly
[ 7.532587] EXT4-fs (sda2): get root inode failed
[ 7.537290] EXT4-fs (sda2): mount failed
mount: mounting /dev/sda2 on /rootfs failed: Bad message
Failed to mount selected root filesystem (/dev/sda2)
umount: can't unmount /rootfs: Invalid argument
There's no '/dev' on ext4(/dev/sda2) partition.
udhcpc: started, v1.35.0
I can however, successfully mount the rootfs.ext4 and inspect the files locally on my machine.
I did not notice any warnings/errors during the petalinux-build,.. commands.
Can you provide me some help on how to fix it or manually perform the petalinux-package command to obtain a working rootfs partition?
Let me know if you need any details regarding logs or configuration options