Archive Handler, Meta-Swupdate
549 views
Skip to first unread message
Tyler Landle
Mar 20, 2017, 1:38:35 PM3/20/17
to swup...@googlegroups.com
Hey Stefano,
I am trying to install a tarball into an Ext4 FS on an SD card. However, whenever I do this I get this error:
Searching for custom LUA handlers :[string "require ("swupdate_handlers")"]:1: m odule 'swupdate_handlers' not found:
no field package.preload['swupdate_handlers']
no file '/usr/share/lua/5.3/swupdate_handlers.lua'
no file '/usr/share/lua/5.3/swupdate_handlers/init.lua'
no file '/usr/lib/lua/5.3/swupdate_handlers.lua'
no file '/usr/lib/lua/5.3/swupdate_handlers/init.lua'
no file './swupdate_handlers.lua'
no file './swupdate_handlers/init.lua'
no file '/usr/lib/lua/5.3/swupdate_handlers.so'
no file '/usr/lib/lua/5.3/loadall.so'
no file './swupdate_handlers.so'
Custom handlers not found, no error, skipping...
Running on ge-mca-tcd-zynqmp Revision REV1
Registered handlers:
flash
raw
rawfile
lua
shellscript
preinstall
postinstall
uboot
Main loop Daemon
Version 0.1.0
[ 31.115165] random: nonblocking pool is initialized
Cannot parse config file '/etc/fw_env.config': No such file or directory
Error: environment not initialized
[ 39.196447] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 0, blo ck_bitmap = 1952788270
[ 39.217238] EXT4-fs error (device mmcblk1p2): ext4_mb_generate_buddy:758: gro up 1, block bitmap and bg descriptor inconsistent: 30328 vs 1161 free clusters
[ 39.231243] EXT4-fs error (device mmcblk1p2): ext4_mb_generate_buddy:758: gro up 2, block bitmap and bg descriptor inconsistent: 30359 vs 784 free clusters
[ 39.245146] EXT4-fs error (device mmcblk1p2): ext4_mb_generate_buddy:758: gro up 3, block bitmap and bg descriptor inconsistent: 30358 vs 189 free clusters
[ 39.258919] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 4, blo ck_bitmap = 808464432
[ 39.279440] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 5, blo ck_bitmap = 1953066601
[ 39.299985] EXT4-fs error (device mmcblk1p2): ext4_mb_generate_buddy:758: gro up 6, block bitmap and bg descriptor inconsistent: 30322 vs 32768 free clusters
[ 39.314047] EXT4-fs error (device mmcblk1p2): ext4_mb_generate_buddy:758: gro up 7, block bitmap and bg descriptor inconsistent: 30352 vs 31881 free clusters
[ 39.327986] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 8, blo ck_bitmap = 1953723648
[ 39.348683] EXT4-fs error (device mmcblk1p2): ext4_mb_generate_buddy:758: gro up 9, block bitmap and bg descriptor inconsistent: 30320 vs 31881 free clusters
[ 44.201318] EXT4-fs error: 3435 callbacks suppressed
[ 44.206211] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 4, blo ck_bitmap = 808464432
[ 44.226662] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 5, blo ck_bitmap = 1953066601
[ 44.247046] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 8, blo ck_bitmap = 1953723648
[ 44.267503] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 16, bl ock_bitmap = 1952788270
[ 44.288048] EXT4-fs error (device mmcblk1p2): ext4_mb_mark_diskspace_used:292 9: comm kworker/u8:3: Allocating blocks 593345-593346 which overlap fs metadata
[ 44.306523] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 0, blo ck_bitmap = 1952788270
[ 44.326853] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 4, blo ck_bitmap = 808464432
[ 44.347206] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 5, blo ck_bitmap = 1953066601
[ 44.367674] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 8, blo ck_bitmap = 1953723648
[ 44.388154] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 16, bl ock_bitmap = 1952788270
[ 49.232829] EXT4-fs error: 1524 callbacks suppressed
[ 49.237722] EXT4-fs error (device mmcblk1p2): ext4_mb_mark_diskspace_used:292 9: comm kworker/u8:3: Allocating blocks 593600-593601 which overlap fs metadata
[ 49.262278] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 0, blo ck_bitmap = 1952788270
[ 49.288626] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 4, blo ck_bitmap = 808464432
[ 49.314952] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 5, blo ck_bitmap = 1953066601
[ 49.341208] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 8, blo ck_bitmap = 1953723648
[ 49.367658] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 16, bl ock_bitmap = 1952788270
[ 49.393963] EXT4-fs error (device mmcblk1p2): ext4_mb_mark_diskspace_used:292 9: comm kworker/u8:3: Allocating blocks 593601-593602 which overlap fs metadata
[ 49.418165] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 0, blo ck_bitmap = 1952788270
[ 49.444560] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 4, blo ck_bitmap = 808464432
[ 49.471116] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 5, blo ck_bitmap = 1953066601
[ 54.308267] EXT4-fs error: 948 callbacks suppressed
[ 54.313062] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 8, blo ck_bitmap = 1953723648
[ 54.340028] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 16, bl ock_bitmap = 1952788270
[ 54.366746] EXT4-fs error (device mmcblk1p2): ext4_mb_mark_diskspace_used:292 9: comm kworker/u8:3: Allocating blocks 593760-593761 which overlap fs metadata
[ 54.391317] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 0, blo ck_bitmap = 1952788270
[ 54.417893] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 4, blo ck_bitmap = 808464432
[ 54.444103] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 5, blo ck_bitmap = 1953066601
[ 54.470829] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 8, blo ck_bitmap = 1953723648
[ 54.497311] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 16, bl ock_bitmap = 1952788270
[ 54.523878] EXT4-fs error (device mmcblk1p2): ext4_mb_mark_diskspace_used:292 9: comm kworker/u8:3: Allocating blocks 593761-593762 which overlap fs metadata
[ 54.548369] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 0, blo ck_bitmap = 1952788270
[ 59.340665] EXT4-fs error: 2507 callbacks suppressed
[ 59.345552] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 0, blo ck_bitmap = 1952788270
[ 59.365946] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 4, blo ck_bitmap = 808464432
[ 59.386284] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 5, blo ck_bitmap = 1953066601
[ 59.406710] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 8, blo ck_bitmap = 1953723648
[ 59.427144] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 16, bl ock_bitmap = 1952788270
[ 59.447516] EXT4-fs error (device mmcblk1p2): ext4_mb_mark_diskspace_used:292 9: comm kworker/u8:3: Allocating blocks 594180-594181 which overlap fs metadata
[ 59.465953] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 0, blo ck_bitmap = 1952788270
[ 59.487597] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 4, blo ck_bitmap = 808464432
[ 59.507939] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 5, blo ck_bitmap = 1953066601
[ 59.528265] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 8, blo ck_bitmap = 1953723648
[ 64.369715] EXT4-fs error: 3291 callbacks suppressed
[ 64.374596] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 4, blo ck_bitmap = 808464432
[ 64.395259] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 5, blo ck_bitmap = 1953066601
[ 64.415950] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 8, blo ck_bitmap = 1953723648
[ 64.436631] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 16, bl ock_bitmap = 1952788270
[ 64.457295] EXT4-fs error (device mmcblk1p2): ext4_mb_mark_diskspace_used:292 9: comm kworker/u8:3: Allocating blocks 594730-594731 which overlap fs metadata
[ 64.475965] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 0, blo ck_bitmap = 1952788270
[ 64.496637] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 4, blo ck_bitmap = 808464432
[ 64.517228] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 5, blo ck_bitmap = 1953066601
[ 64.537755] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 8, blo ck_bitmap = 1953723648
[ 64.558454] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 16, bl ock_bitmap = 1952788270
[ 69.396604] EXT4-fs error: 2445 callbacks suppressed
[ 69.401488] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 5, blo ck_bitmap = 1953066601
[ 69.427172] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 8, blo ck_bitmap = 1953723648
[ 69.453179] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 16, bl ock_bitmap = 1952788270
[ 69.478942] EXT4-fs error (device mmcblk1p2): ext4_mb_mark_diskspace_used:292 9: comm kworker/u8:3: Allocating blocks 595139-595140 which overlap fs metadata
[ 69.502496] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 0, blo ck_bitmap = 1952788270
[ 69.527931] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 4, blo ck_bitmap = 808464432
[ 69.548271] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 5, blo ck_bitmap = 1953066601
[ 69.568700] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 8, blo ck_bitmap = 1953723648
[ 69.589129] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 16, bl ock_bitmap = 1952788270
[ 69.609499] EXT4-fs error (device mmcblk1p2): ext4_mb_mark_diskspace_used:292 9: comm kworker/u8:3: Allocating blocks 595140-595141 which overlap fs metadata
[ 74.433696] EXT4-fs error: 2046 callbacks suppressed
[ 74.438580] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 0, blo ck_bitmap = 1952788270
[ 74.465052] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 4, blo ck_bitmap = 808464432
[ 74.491481] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 5, blo ck_bitmap = 1953066601
[ 74.517916] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 8, blo ck_bitmap = 1953723648
[ 74.544133] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 16, bl ock_bitmap = 1952788270
[ 74.570773] EXT4-fs error (device mmcblk1p2): ext4_mb_mark_diskspace_used:292 9: comm kworker/u8:3: Allocating blocks 595482-595483 which overlap fs metadata
[ 74.595284] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 0, blo ck_bitmap = 1952788270
[ 74.621779] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 4, blo ck_bitmap = 808464432
[ 74.647968] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 5, blo ck_bitmap = 1953066601
[ 74.674428] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 8, blo ck_bitmap = 1953723648
[ 79.498234] EXT4-fs error: 2969 callbacks suppressed
[ 79.503116] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 8, blo ck_bitmap = 1953723648
[ 79.655726] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 16, bl ock_bitmap = 1952788270
[ 79.825433] EXT4-fs error (device mmcblk1p2): ext4_mb_mark_diskspace_used:292 9: comm kworker/u8:3: Allocating blocks 595978-595979 which overlap fs metadata
[ 80.001386] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 0, blo ck_bitmap = 1952788270
[ 80.110612] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 4, blo ck_bitmap = 808464432
[ 80.137221] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 5, blo ck_bitmap = 1953066601
[ 80.163525] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 8, blo ck_bitmap = 1953723648
[ 80.190157] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 16, bl ock_bitmap = 1952788270
[ 80.216640] EXT4-fs error (device mmcblk1p2): ext4_mb_mark_diskspace_used:292 9: comm kworker/u8:3: Allocating blocks 595979-595980 which overlap fs metadata
[ 80.240787] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 0, blo ck_bitmap = 1952788270
[ 84.656953] EXT4-fs error: 1857 callbacks suppressed
[ 84.661847] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 16, bl ock_bitmap = 1952788270
[ 84.682440] EXT4-fs error (device mmcblk1p2): ext4_mb_mark_diskspace_used:292 9: comm kworker/u8:3: Allocating blocks 596289-596290 which overlap fs metadata
[ 84.700832] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 0, blo ck_bitmap = 1952788270
[ 84.721067] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 4, blo ck_bitmap = 808464432
[ 84.741426] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 5, blo ck_bitmap = 1953066601
[ 84.761872] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 8, blo ck_bitmap = 1953723648
[ 84.782309] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 16, bl ock_bitmap = 1952788270
[ 84.802733] EXT4-fs error (device mmcblk1p2): ext4_mb_mark_diskspace_used:292 9: comm kworker/u8:3: Allocating blocks 596290-596291 which overlap fs metadata
[ 84.821171] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 0, blo ck_bitmap = 1952788270
[ 84.841610] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 4, blo ck_bitmap = 808464432
[ 89.684725] EXT4-fs error: 3118 callbacks suppressed
[ 89.689609] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 0, blo ck_bitmap = 1952788270
[ 89.710101] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 4, blo ck_bitmap = 808464432
[ 89.730443] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 5, blo ck_bitmap = 1953066601
[ 89.751754] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 8, blo ck_bitmap = 1953723648
[ 89.772197] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 16, bl ock_bitmap = 1952788270
[ 89.792733] EXT4-fs error (device mmcblk1p2): ext4_mb_mark_diskspace_used:292 9: comm kworker/u8:3: Allocating blocks 596811-596812 which overlap fs metadata
[ 89.811172] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 0, blo ck_bitmap = 1952788270
[ 89.831506] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 4, blo ck_bitmap = 808464432
[ 89.851853] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 5, blo ck_bitmap = 1953066601
[ 89.872243] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 8, blo ck_bitmap = 1953723648
[ 94.713467] EXT4-fs error: 3691 callbacks suppressed
[ 94.718350] EXT4-fs error (device mmcblk1p2): ext4_mb_mark_diskspace_used:292 9: comm kworker/u8:3: Allocating blocks 597427-597428 which overlap fs metadata
[ 94.736897] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 0, blo ck_bitmap = 1952788270
[ 94.757230] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 4, blo ck_bitmap = 808464432
[ 94.777569] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 5, blo ck_bitmap = 1953066601
[ 94.797996] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 8, blo ck_bitmap = 1953723648
[ 94.818426] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 16, bl ock_bitmap = 1952788270
[ 94.838795] EXT4-fs error (device mmcblk1p2): ext4_mb_mark_diskspace_used:292 9: comm kworker/u8:3: Allocating blocks 597428-597429 which overlap fs metadata
[ 94.857246] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 0, blo ck_bitmap = 1952788270
[ 94.877692] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 4, blo ck_bitmap = 808464432
[ 94.898041] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 5, blo ck_bitmap = 1953066601
[ 99.740603] EXT4-fs error: 3566 callbacks suppressed
[ 99.745485] EXT4-fs error (device mmcblk1p2): ext4_mb_mark_diskspace_used:292 9: comm kworker/u8:3: Allocating blocks 598023-598024 which overlap fs metadata
[ 99.764063] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 0, blo ck_bitmap = 1952788270
[ 99.784393] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 4, blo ck_bitmap = 808464432
[ 99.804732] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 5, blo ck_bitmap = 1953066601
[ 99.825163] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 8, blo ck_bitmap = 1953723648
[ 99.845588] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 16, bl ock_bitmap = 1952788270
[ 99.865974] EXT4-fs error (device mmcblk1p2): ext4_mb_mark_diskspace_used:292 9: comm kworker/u8:3: Allocating blocks 598024-598025 which overlap fs metadata
[ 99.884472] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 0, blo ck_bitmap = 1952788270
[ 99.905013] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 4, blo ck_bitmap = 808464432
[ 99.925467] EXT4-fs error (device mmcblk1p2): ext4_read_block_bitmap_nowait:4 31: comm kworker/u8:3: Cannot get buffer for block bitmap - block_group = 5, blo ck_bitmap = 1953066601
[ 100.289038] jbd2_journal_bmap: journal block not found at offset 24 on mmcblk 1p2-8
[ 100.296521] Aborting journal on device mmcblk1p2-8.
[ 100.310994] EXT4-fs (mmcblk1p2): Delayed block allocation failed for inode 52 3490 at logical offset 0 with max blocks 1 with error 30
[ 100.322909] EXT4-fs (mmcblk1p2): This should not happen!! Data will be lost
[ 100.322909]
[ 100.339730] EXT4-fs error (device mmcblk1p2): ext4_journal_check_start:56: De tected aborted journal
[ 100.348680] EXT4-fs (mmcblk1p2): Remounting filesystem read-only
[ 100.359234] EXT4-fs (mmcblk1p2): ext4_writepages: jbd2_start: 1024 pages, ino 262003; err -30
Cannot parse config file '/etc/fw_env.config': No such file or dir[ 127.785416] EXT4-fs error: 268 callbacks suppressed
ectory
Error: environment not initialized
Software updated suc[ 127.795022] EXT4-fs error (device mmcblk1p2): ext4_map_bl ocks:549: inode #261761: block 1056786: comm sh: lblock 0 mapped to illegal pblo ck (length 1)
cessfully
Please reboot the device to start the new software
In addition, I noticed that the archive handle isn't present(which may explain this issue).
Can you help?
Thanks,Tyler
Stefano Babic
Mar 20, 2017, 3:17:16 PM3/20/17
to Tyler Landle, swup...@googlegroups.com
Hi Tyler,
LOG reports errors from kernel - it looks like that the SD card has no
filesystem. In addition, a tarball is extracted by the archive handler,
and you have not built it.
Best regards,
Stefano Babic
> --
> You received this message because you are subscribed to the Google
> Groups "swupdate" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to swupdate+u...@googlegroups.com
> <mailto:swupdate+u...@googlegroups.com>.
> To post to this group, send email to swup...@googlegroups.com
> <mailto:swup...@googlegroups.com>.
> For more options, visit https://groups.google.com/d/optout.
--
=====================================================================
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sba...@denx.de
=====================================================================
LOG reports errors from kernel - it looks like that the SD card has no
filesystem. In addition, a tarball is extracted by the archive handler,
and you have not built it.
Best regards,
Stefano Babic
> You received this message because you are subscribed to the Google
> Groups "swupdate" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to swupdate+u...@googlegroups.com
> <mailto:swupdate+u...@googlegroups.com>.
> To post to this group, send email to swup...@googlegroups.com
> <mailto:swup...@googlegroups.com>.
> For more options, visit https://groups.google.com/d/optout.
--
=====================================================================
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sba...@denx.de
=====================================================================
Tyler Landle
Mar 20, 2017, 4:39:21 PM3/20/17
to Stefano Babic, swup...@googlegroups.com
Hey Stefano,
I built the archive, and created a new sw-description to match. However, I am getting this error:
Licensed under GPLv2. See source distribution for detailed copyright notices.
Searching for custom LUA handlers :[string "require ("swupdate_handlers")"]:1: module 'swupdate_handlers' not found:
no field package.preload['swupdate_handlers']
no file '/usr/share/lua/5.3/swupdate_handlers.lua'
no file '/usr/share/lua/5.3/swupdate_handlers/init.lua'
no file '/usr/lib/lua/5.3/swupdate_handlers.lua'
no file '/usr/lib/lua/5.3/swupdate_handlers/init.lua'
no file './swupdate_handlers.lua'
no file './swupdate_handlers/init.lua'
no file '/usr/lib/lua/5.3/swupdate_handlers.so'
no file '/usr/lib/lua/5.3/loadall.so'
no file './swupdate_handlers.so'
Custom handlers not found, no error, skipping...
Running on ge-mca-tcd-zynqmp Revision REV1
Registered handlers:
archive
tar
flash
raw
rawfile
lua
shellscript
preinstall
postinstall
uboot
Main loop Daemon
[NOTIFY] : SWUPDATE running : [extract_sw_description] : Found file:
filename sw-description
size 221
checksum 0x3e90 VERIFIED
Version 0.1.0
[NOTIFY] : SWUPDATE running : [parse_hw_compatibility] : Accepted Hw Revision : REV1
[NOTIFY] : SWUPDATE running : [parse_images] : Found Image : image.tar.gz in device : /dev/mmcblk1p2 for handler archive
[NOTIFY] : SWUPDATE running : [check_hw_compatibility] : Hardware ge-mca-tcd-zynqmp Revision: REV1
[NOTIFY] : SWUPDATE running : [check_hw_compatibility] : Hardware compatibility verified
[NOTIFY] : SWUPDATE running : [cpio_scan] : Found file:
filename image.tar.gz
size 145313088
REQUIRED
[ 25.329986] random: nonblocking pool is initialized
Cannot parse config file '/etc/fw_env.config': No such file or directory
Error: environment not initialized
[NOTIFY] : SWUPDATE running : [install_single_image] : Found installer for stream image.tar.gz archive
[NOTIFY] : SWUPDATE running : [install_archive_image] : Missing path attribute
[NOTIFY] : SWUPDATE running : [install_single_image] : Installer for archive not successful !
Software updated failed
Cannot parse config file '/etc/fw_env.config': No such file or directory
Error: environment not initialized
My Sw- description looks like this:
Do you know why this could be happening?
Thanks,
Tyler Landle
> an email to swupdate+unsubscribe@googlegroups.com
> <mailto:swupdate+unsubscribe@googlegroups.com>.
> To post to this group, send email to swup...@googlegroups.com
> <mailto:swupdate@googlegroups.com>.
Stefano Babic
Mar 20, 2017, 6:13:02 PM3/20/17
to Tyler Landle, Stefano Babic, swup...@googlegroups.com
Hi Tyler,
On 20/03/2017 21:39, Tyler Landle wrote:
> Hey Stefano,
>
> Inline image 1
>
Please use txt only when posting to this ML.
> Do you know why this could be happening?
>
Yes, you are misusing the handler. If it is a tarball, it must be
extracted into a filesystem - you have to use "files" instead "of
images". Move your description to the files section.
Best regards,
Stefano Babic
On 20/03/2017 21:39, Tyler Landle wrote:
> Hey Stefano,
>
>
Please use txt only when posting to this ML.
> Do you know why this could be happening?
>
extracted into a filesystem - you have to use "files" instead "of
images". Move your description to the files section.
Best regards,
Stefano Babic
redso...@gmail.com
Mar 21, 2017, 3:50:21 PM3/21/17
to swupdate, tyler....@gmail.com, sba...@denx.de
Hey Stefano,
I have moved it to the files section, and swupdate is running.
However, this is not causing any update of the FS. I am trying to update to a previous version, but all of my files are still there. I have tried path="/" and path="home/root" but there is no difference.
Is it possible I need to do a different path? or in general load this differently?
Thanks,
Tyler Landle
tyler....@gmail.com
Mar 24, 2017, 11:57:28 AM3/24/17
to swupdate, tyler....@gmail.com, sba...@denx.de, redso...@gmail.com
Hey Stefano,
Do you have any idea about this? I noticed it is decompressing(supposedly) into the /tmp/datadst path...is that a path variable? Should I somehow get rid of it before I run swupdate?
Thanks,
Tyler Landle
Stefano Babic
Mar 24, 2017, 1:01:56 PM3/24/17
to tyler....@gmail.com, swupdate, sba...@denx.de, redso...@gmail.com
is the reason.
Tyler Landle
Mar 24, 2017, 1:13:56 PM3/24/17
to Stefano Babic, Tyler Landle, swup...@googlegroups.com
Stefano,
I have run this in verbose mode. It does state it is sending to /tmp/datadst folder but I cannot figure out where it finds this.
It says it completes successfully but not much has changed, and it has definitely not unpacked everything I had in there. I can attach a log if you'd like. I was just wondering where it gets the /tmp/datadst folder from. I cannot find the variable associated.
Thanks,
Tyler Landle
Stefano Babic
Mar 24, 2017, 1:29:53 PM3/24/17
to Tyler Landle, Stefano Babic, Tyler Landle, swup...@googlegroups.com
On 24/03/2017 18:13, Tyler Landle wrote:
> Stefano,
>
> I have run this in verbose mode. It does state it is sending to
> /tmp/datadst folder but I cannot figure out where it finds this.
>
> It says it completes successfully but not much has changed, and it has
> definitely not unpacked everything I had in there. I can attach a log if
> you'd like. I was just wondering where it gets the /tmp/datadst folder
> from. I cannot find the variable associated.
/tmp/datadst is used to temporary store artifacts when streaming is not
> Stefano,
>
> I have run this in verbose mode. It does state it is sending to
> /tmp/datadst folder but I cannot figure out where it finds this.
>
> It says it completes successfully but not much has changed, and it has
> definitely not unpacked everything I had in there. I can attach a log if
> you'd like. I was just wondering where it gets the /tmp/datadst folder
> from. I cannot find the variable associated.
set. It has nothing to do with "path" and it is just for internal use.
If log says success, means that you have not set the board name / board
revision, but you want hardware-compatibility check. The parser is not
finding anything to install, and at the end you get SUCCESS=nothing was
successfully installed.
Regards,
Stefano
Tyler Landle
Mar 24, 2017, 2:27:57 PM3/24/17
to Stefano Babic, Tyler Landle, swup...@googlegroups.com
Stefano,.
This is the log that I get:
Swupdate v2017.1.0
size 248
checksum 0x4402 VERIFIED
Version 0.1.0
[NOTIFY] : SWUPDATE running : [parse_hw_compatibility] : Accepted Hw Revision : REV1
[NOTIFY] : SWUPDATE running : [parse_files] : Found File : filesys.tar.gz --> / (/dev/mmcblk1p2)
[NOTIFY] : SWUPDATE running : [check_hw_compatibility] : Hardware ge-mca-tcd-zynqmp Revision: REV1
[NOTIFY] : SWUPDATE running : [check_hw_compatibility] : Hardware compatibility verified
[NOTIFY] : SWUPDATE running : [cpio_scan] : Found file:
filename filesys.tar.gz
size 144830894
REQUIRED
[ 35.692905] random: nonblocking pool is initialized
Cannot parse config file '/etc/fw_env.config': No such file or directory
Error: environment not initialized
[NOTIFY] : SWUPDATE running : [install_single_image] : Found installer for stream filesys.tar.gz archive
[NOTIFY] : SWUPDATE running : [install_archive_image] : Installing file filesys.tar.gz on /tmp/datadst//
Cannot parse config file '/etc/fw_env.config': No such file or directory
Error: environment not initialized
Software updated successfully
Please reboot the device to start the new software
[NOTIFY] : SWUPDATE successful !
This is my swupdate bash script:
#!/bin/bash CONTAINER_VER="0.1.0" PRODUCT_NAME="ge-mca-tcd-update" FILES="sw-description filesys.tar.gz" for i in $FILES;do echo $i;done | cpio -ov -H crc > ${PRODUCT_NAME}_${CONTAINER_VER}.swu
This is my sw-description
software = { version = "0.1.0"; hardware-compatibility: [ "REV1" ]; ge-mca-tcd-zynqmp ={ files: ( { filename = "filesys.tar.gz"; device = "/dev/mmcblk1p2"; type="archive"; filesystem="ext4"; path="/"; } ); }; }
This is my hwrevision file
ge-mca-tcd-zynqmp REV1
Thanks,
Tyler Landle
tyler....@gmail.com
Mar 27, 2017, 12:35:26 PM3/27/17
to swupdate, sba...@denx.de, redso...@gmail.com, tyler....@gmail.com
> software =
> {
> version = "0.1.0";
>
> hardware-compatibility: [ "REV1" ];
>
> ge-mca-tcd-zynqmp ={
> files: (
> {
> filename = "filesys.tar.gz";
> device = "/dev/mmcblk1p2";
> type="archive";
> filesystem="ext4";
> path="/";
> }
> );
> };
> }
> This is my hwrevision file
> ge-mca-tcd-zynqmp REV1
> Thanks,Tyler Landle
> {
> version = "0.1.0";
>
> hardware-compatibility: [ "REV1" ];
>
> ge-mca-tcd-zynqmp ={
> files: (
> {
> filename = "filesys.tar.gz";
> device = "/dev/mmcblk1p2";
> type="archive";
> filesystem="ext4";
> path="/";
> }
> );
> };
> }
> This is my hwrevision file
> ge-mca-tcd-zynqmp REV1
>
>
> On Fri, Mar 24, 2017 at 12:29 PM, Stefano Babic <sba...@denx.de> wrote:
> On 24/03/2017 18:13, Tyler Landle wrote:
>
> > Stefano,
>
> >
>
> > I have run this in verbose mode. It does state it is sending to
>
> > /tmp/datadst folder but I cannot figure out where it finds this.
>
> >
>
> > It says it completes successfully but not much has changed, and it has
>
> > definitely not unpacked everything I had in there. I can attach a log if
>
> > you'd like. I was just wondering where it gets the /tmp/datadst folder
>
> > from. I cannot find the variable associated.
>
>
>
> /tmp/datadst is used to temporary store artifacts when streaming is not
>
> set. It has nothing to do with "path" and it is just for internal use.
>
>
>
> If log says success, means that you have not set the board name / board
>
> revision, but you want hardware-compatibility check. The parser is not
>
> finding anything to install, and at the end you get SUCCESS=nothing was
>
> successfully installed.
>
>
>
> Regards,
>
> Stefano
>
>
>
>
>
>
>
> --
>
> =====================================================================
>
> DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
>
> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
>
> Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sba...@denx.de
>
> =====================================================================
Hey Stefano,
>
> On Fri, Mar 24, 2017 at 12:29 PM, Stefano Babic <sba...@denx.de> wrote:
> On 24/03/2017 18:13, Tyler Landle wrote:
>
> > Stefano,
>
> >
>
> > I have run this in verbose mode. It does state it is sending to
>
> > /tmp/datadst folder but I cannot figure out where it finds this.
>
> >
>
> > It says it completes successfully but not much has changed, and it has
>
> > definitely not unpacked everything I had in there. I can attach a log if
>
> > you'd like. I was just wondering where it gets the /tmp/datadst folder
>
> > from. I cannot find the variable associated.
>
>
>
> /tmp/datadst is used to temporary store artifacts when streaming is not
>
> set. It has nothing to do with "path" and it is just for internal use.
>
>
>
> If log says success, means that you have not set the board name / board
>
> revision, but you want hardware-compatibility check. The parser is not
>
> finding anything to install, and at the end you get SUCCESS=nothing was
>
> successfully installed.
>
>
>
> Regards,
>
> Stefano
>
>
>
>
>
>
>
> --
>
> =====================================================================
>
> DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
>
> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
>
> Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sba...@denx.de
>
> =====================================================================
Just wondering if you were able to take a look at this. I appreciate your help.
Thanks,
Tyler Landle
Stefano Babic
Mar 27, 2017, 12:37:59 PM3/27/17
to tyler....@gmail.com, swupdate, sba...@denx.de, redso...@gmail.com
files. Why are you saying that the update failed and how have you verified ?
Best regards,
Stefano Babic
tyler....@gmail.com
Mar 27, 2017, 12:42:53 PM3/27/17
to swupdate, tyler....@gmail.com, sba...@denx.de, redso...@gmail.com
Hey Stefano,
I did not see any errors either, but it is apparent that the files are being unpacked in the wrong location or something similar. I might be misunderstanding how this utility is intended to be used. I am attempting to unpack the tar.gz FS on top of my current system to replace the files in the FS. I have been checking by adding files(not in the updated FS) on the first FS(FS to be updated), and then checking if they are still there after the update and reboot. It appears that they are still there. Other updated files have not been changed as well, which made me think they may be unpacking to an improper location.
Am I testing the functionality incorrectly?
Thanks,
Tyler Landle
Stefano Babic
Mar 28, 2017, 2:23:49 AM3/28/17
to tyler....@gmail.com, swupdate, sba...@denx.de, redso...@gmail.com
So you are replacing files on the filesystem you are currently running ?
This is generally a *bad* idea.
Anyway, you are asking SWUpdate to mount a new filesystem, but as you
state the filesystem is already mounted. Drop "device" and "filesystem"
from your sw-description:
software =
{
version = "0.1.0";
hardware-compatibility: [ "REV1" ];
ge-mca-tcd-zynqmp ={
files: (
{
filename = "filesys.tar.gz";
path=<path where you want to install>;
}
);
};
}
> I have been checking by adding files(not
> in the updated FS) on the first FS(FS to be updated),
Not understood what you mean, sorry.
> I have been checking by adding files(not
> in the updated FS) on the first FS(FS to be updated),
> and then
> checking if they are still there after the update and reboot. It
> appears that they are still there. Other updated files have not been
> changed as well, which made me think they may be unpacking to an
> improper location.
tyler....@gmail.com
Mar 28, 2017, 12:29:40 PM3/28/17
to swupdate, tyler....@gmail.com, sba...@denx.de, redso...@gmail.com
Hey Stefano,
I appreciate the quick response, and I really appreciate your support on this. I see that replacing files on my own filesystem is bad. Is it a better idea to create(or install) a new filesystem, and mount this as the root filesystem instead?
My task is to use swupdate in order to "update" the root filesystem with new releases. Currently we have a boot.bin, "Image", and device tree in the FAT32 partition of an SD Card, and the FS in the Ext4 partition. I am trying to update the FS in the Ext4 partition.
How would you suggest going about it instead?
To test, I was just seeing if the files that had changed between the old and new filesystems had actually changed. The filesystem on the unit that we have is an "older" file system, and the new one contains changes including added and removed files in specific folders. I simply checked to see if those files were added and removed.
Thanks,
Tyler Landle
tyler....@gmail.com
Mar 28, 2017, 1:17:52 PM3/28/17
to swupdate, tyler....@gmail.com, sba...@denx.de, redso...@gmail.com
Also, after making the changes that were suggested, I am getting kernel panic on bootup...and system crashes. Is is to be expected for the way I am doing things?
Mohamed Belouarga
Sep 26, 2022, 9:00:19 AM9/26/22
to swupdate
Hey,
How did you resolve the problem of kernel panic?
I'm trying to update the root file system, but when I did it, I had a kernel panic.
software =
{
description = "Firmware update for raspberry pi rootfs"
raspberrypi3 = {
hardware-compatibility: [ "1.0"];
version = "0.1.0";
images: (
{
filename = "raspkar-image-raspberrypi3-64.rootfs.ext4";
device = "/dev/mmcblk0p2";
type = "raw";
}
);
}
}
{
description = "Firmware update for raspberry pi rootfs"
raspberrypi3 = {
hardware-compatibility: [ "1.0"];
version = "0.1.0";
images: (
{
filename = "raspkar-image-raspberrypi3-64.rootfs.ext4";
device = "/dev/mmcblk0p2";
type = "raw";
}
);
}
}
Thanks
Mohamed Belouarga
Sep 26, 2022, 9:01:42 AM9/26/22
to swupdate
This kernel panic is due to ext4-fs error (device mmcblk0p2), apparently it has an invalid checksum.
Tyler Landle
Sep 26, 2022, 9:48:35 AM9/26/22
to Mohamed Belouarga, swupdate
My issue ended up being that I was trying to update the currently running filesystem that was running in emmc. To successfully do this you have to if running in mmc, use a strategy such as A/B loading, boot from a separate disk, or you can successfully update a different underlying fs type such as a ram disk, etc.
--
You received this message because you are subscribed to a topic in the Google Groups "swupdate" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/swupdate/qjlswK1guws/unsubscribe.
To unsubscribe from this group and all its topics, send an email to swupdate+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/swupdate/e497ff2c-172d-464a-96ab-2c0134d4d4acn%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages