I generate core Ubuntu image using gadget snap and kernel snap and flash the image into SD card , insert SD card into board and connect the board to system …
i got this error on serial port through Tera Term.
Please have a Look , Thanks
ashutosh:
I generate core Ubuntu image using gadget snap and kernel snap and flash the image into SD card , insert SD card into board and connect the board to system …
i got this error on serial port through Tera Term.
Please have a Look , Thanks
[ 2501.691801] EXT4-fs error (device mmcblk1p2): __ext4_find_entry:1534: inode #46487: comm crond: reading directory lblock 0
[ 2501.703018] EXT4-fs error (device mmcblk1p2): __ext4_find_entry:1534: inode #174: comm crond: reading directory lblock 0
[ 2501.714038] EXT4-fs error (device mmcblk1p2): __ext4_find_entry:1534: inode #174: comm crond: reading directory lblock 0
[ 2501.725091] EXT4-fs error (device mmcblk1p2): __ext4_find_entry:1534: inode #174: comm crond: reading directory lblock 0
[ 2501.736097] EXT4-fs error (device mmcblk1p2): __ext4_find_entry:1534: inode #46487: comm crond: reading directory lblock 0
[ 2529.497417] EXT4-fs error (device mmcblk1p2): __ext4_find_entry:1534: inode #174: comm weston-desktop-: reading directory lblock 0
[ 2536.051574] mmc1: host does not support reading read-only switch, assuming write-enable
[ 2536.189715] mmc1: new ultra high speed SDR104 SDHC card at address 0001
[ 2536.197060] EXT4-fs error (device mmcblk1p2): __ext4_find_entry:1534: inode #174: comm systemd-udevd: reading directory lblock 0
[ 2536.197390] mmcblk1: mmc1:0001 GB1QT 29.8 GiB
[ 2536.208739] EXT4-fs error (device mmcblk1p2): __ext4_find_entry:1534: inode #17177: comm systemd-udevd: reading directory lblock 0
[ 2536.214193] mmcblk1: p1 p2
[ 2536.224916] EXT4-fs warning: 10 callbacks suppressed
[ 2536.224921] EXT4-fs warning (device mmcblk1p2): dx_probe:767: inode #20879: lblock 0: comm systemd-udevd: error -5 reading directory block
[ 2536.232789] debugfs: Directory ‘mmcblk1’ with parent ‘block’ already present!
[ 2536.245223] EXT4-fs error (device mmcblk1p2): __ext4_find_entry:1534: inode #2472: comm systemd-udevd: reading directory lblock 0
[ 2536.263963] EXT4-fs error (device mmcblk1p2): __ext4_find_entry:1534: inode #174: comm systemd-udevd: reading directory lblock 0
[ 2536.275574] EXT4-fs error (device mmcblk1p2): __ext4_find_entry:1534: inode #17177: comm systemd-udevd: reading directory lblock 0
[ 2536.287348] EXT4-fs warning (device mmcblk1p2): dx_probe:767: inode #20879: lblock 0: comm systemd-udevd: error -5 reading directory block
[ 2536.299811] EXT4-fs error (device mmcblk1p2): __ext4_find_entry:1534: inode #2072: comm systemd-udevd: reading directory lblock 0
[ 2561.745923] EXT4-fs error (device mmcblk1p2): __ext4_find_entry:1534: inode #174: comm crond: reading directory lblock 0
[ 2561.756926] EXT4-fs error (device mmcblk1p2): __ext4_find_entry:1534: inode #46487: comm crond: reading directory lblock 0
[ 2561.768111] EXT4-fs error (device mmcblk1p2): __ext4_find_entry:1534: inode #174: comm crond: reading directory lblock 0
[ 2561.779131] EXT4-fs error (device mmcblk1p2): __ext4_find_entry:1534: inode #174: comm crond: reading directory lblock 0
[ 2561.790095] EXT4-fs error (device mmcblk1p2): __ext4_find_entry:1534: inode #174: comm crond: reading directory lblock 0
[ 2561.801053] EXT4-fs error (device mmcblk1p2): __ext4_find_entry:1534: inode #46487: comm crond: reading directory lblock 0
[ 2589.495406] EXT4-fs error (device mmcblk1p2): __ext4_find_entry:1534: inode #174: comm weston-desktop-: reading directory lblock 0
[ 2620.810941] EXT4-fs error (device mmcblk1p2): __ext4_find_entry:1534: inode #174: comm crond: reading directory lblock 0
[ 2620.821906] EXT4-fs error (device mmcblk1p2): __ext4_find_entry:1534: inode #46487: comm crond: reading directory lblock 0
[ 2620.833079] EXT4-fs error (device mmcblk1p2): __ext4_find_entry:1534: inode #174: comm crond: reading directory lblock 0
[ 2620.844101] EXT4-fs error (device mmcblk1p2): __ext4_find_entry:1534: inode #174: comm crond: reading directory lblock 0
[ 2620.855067] EXT4-fs error (device mmcblk1p2): __ext4_find_entry:1534: inode #174: comm crond: reading directory lblock 0
[ 2620.866025] EXT4-fs error (device mmcblk1p2): __ext4_find_entry:1534: inode #46487: comm crond: reading directory lblock 0
[ 2649.493700] EXT4-fs error (device mmcblk1p2): __ext4_find_entry:1534: inode #174: comm weston-desktop-: reading directory lblock 0
ogra
September 2, 2021, 10:16am
2
that looks like a broken SD card to me … do you have a fresh one you could try with ?
1 Like
After this error logs I had flashed yocto image through the same SD card and on the same board but the board was booting up.
ogra
September 2, 2021, 11:50am
4
well, perhaps your kernel is missing options for the controller or ext4 attributes then … though the above read error really looks more like hardware (could also be a power issue btw …)
have you logged in yet and checked the journal ?
1 Like