2/8/2024 5:02 PM | |
Joined: 8/24/2023 Last visit: 7/17/2024 Posts: 2 Rating: (2) |
Greetings, Relevant UART logs during booting [ 3.112588] EXT4-fs (mmcblk0p1): INFO: recovery required on readonly filesystem [ 3.119925] EXT4-fs (mmcblk0p1): write access will be enabled during recovery [ 3.153755] JBD2: journal transaction 1808595 on mmcblk0p1-8 is corrupt. [ 3.160486] EXT4-fs (mmcblk0p1): error loading journal [ 3.166203] VFS: Cannot open root device "PARTUUID=392f622e-1c44-4158-bda4-f2e988b3a5f6" or unknown-block(179,1): error -117 [ 3.177421] Please append a correct "root=" boot option; here are the available partitions: [ 3.185778] 0100 4096 ram0 [ 3.185782] (driver?) [ 3.191894] 0101 4096 ram1 [ 3.191898] (driver?) [ 3.198001] 0102 4096 ram2 [ 3.198004] (driver?) [ 3.204113] 0103 4096 ram3 [ 3.204116] (driver?) [ 3.210227] 0104 4096 ram4 [ 3.210230] (driver?) [ 3.216330] 0105 4096 ram5 [ 3.216333] (driver?) [ 3.222442] 0106 4096 ram6 [ 3.222445] (driver?) [ 3.228547] 0107 4096 ram7 [ 3.228550] (driver?) [ 3.234668] 0108 4096 ram8 [ 3.234671] (driver?) [ 3.240771] 0109 4096 ram9 [ 3.240775] (driver?) [ 3.246884] 010a 4096 ram10 [ 3.246887] (driver?) [ 3.253076] 010b 4096 ram11 [ 3.253079] (driver?) [ 3.259274] 010c 4096 ram12 [ 3.259278] (driver?) [ 3.265463] 010d 4096 ram13 [ 3.265466] (driver?) [ 3.271667] 010e 4096 ram14 [ 3.271671] (driver?) [ 3.277868] 010f 4096 ram15 [ 3.277871] (driver?) [ 3.284094] b300 15558144 mmcblk0 [ 3.284099] driver: mmcblk [ 3.290903] b301 10035200 mmcblk0p1 392f622e-1c44-4158-bda4-f2e988b3a5f6 [ 3.290906] [ 3.299866] b302 5478400 mmcblk0p2 1b3c14a9-e2bc-4d61-9ed3-6dfbdd0f08d3 [ 3.299869] [ 3.308829] b303 43008 mmcblk0p3 bb97f2e4-a518-4164-a684-6ccf96ddb0ad [ 3.308832] [ 3.317796] 1f00 1536 mtdblock0 [ 3.317800] (driver?) [ 3.324343] 1f01 2048 mtdblock1 [ 3.324347] (driver?) [ 3.330895] 1f02 3072 mtdblock2 [ 3.330899] (driver?) [ 3.337435] 1f03 128 mtdblock3 [ 3.337438] (driver?) [ 3.343982] 1f04 128 mtdblock4 [ 3.343985] (driver?) [ 3.350528] 1f05 64 mtdblock5 [ 3.350532] (driver?) [ 3.357065] 1f06 7872 mtdblock6 [ 3.357068] (driver?) [ 3.363611] 1f07 1536 mtdblock7 [ 3.363614] (driver?) [ 3.370171] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,1) [ 3.378597] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 5.10.145-cip17 #1 [ 3.385196] Hardware name: SIMATIC IOT2050 Basic PG2 (DT) [ 3.390582] Call trace: [ 3.393035] dump_backtrace+0x0/0x1b0 [ 3.396692] show_stack+0x18/0x70 [ 3.400002] dump_stack+0xd0/0x12c [ 3.403399] panic+0x16c/0x334 [ 3.406449] mount_block_root+0x1c8/0x258 [ 3.410450] mount_root+0x104/0x138 [ 3.413931] prepare_namespace+0x130/0x170 [ 3.418019] kernel_init_freeable+0x25c/0x2a0 [ 3.422367] kernel_init+0x14/0x11c [ 3.425849] ret_from_fork+0x10/0x30 [ 3.429421] SMP: stopping secondary CPUs [ 3.433341] Kernel Offset: disabled [ 3.436823] CPU features: 0x00040002,2000200c [ 3.441169] Memory Limit: none [ 3.444236] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,1) ]---
In regards of changes we did to the example image, we only added some apt packages, openvpn and some python scripts that only interface with the watchdog and serial ports. Nothing that directly edits anything regarding filesystem or native firmware provided. I also added a .txt file with the full Logs until error for further analysis. AttachmentfullBootLogs.txt (216 Downloads) |
Follow us on