Raspberry Pi 5B 8 GB, 128 GB SD card, official power supply. All was running fine up until a full-upgrade and a reboot, then it hung in a sad state:The boot filesystem was fine, the root one had mild corruption that could be fixed automatically. Still won't boot though.
Apart from re-imaging the card and sticking a backup of /home onto the new system, is there a better way in future to recover from this kind of event? I've never had this happen before.
Code:
[ 0.753428] Failed to execute /init (error -2)[ 0.758060] Kernel panic - not syncing: No working init found. Try passing init= option to kernel. See Linux Documentation/admin-guide/init.rst for guidance[ 0.772313] CPU: 3 PID: 1 Comm: swapper/0 Not tainted 6.6.51+rpt-rpi-2712 #1 Debian 1:6.6.51-1+rpt3[ 0.780522] mmc1: new ultra high speed DDR50 SDIO card at address 0001[ 0.788054] Hardware name: Raspberry Pi 5 Model B Rev 1.0 (DT)[ 0.793913] Call trace:[ 0.796365] dump_backtrace+0xa0/0x100[ 0.800134] show_stack+0x20/0x38[ 0.803460] dump_stack_lul+0x48/0x60[ 0.807143] dump_stack+0x18/0x28[ 0.810470] panic+0x330/0x398[ 0.813537] kernel_init+0x1ac/0x1f8 [ 0.817128] ret_from_fork+0x10/0x20[ 0.820717] SMP: stopping secondary CPUs[ 0.824658] Kernel Offset: 0x100004000000 from 0xffffc00080000000[ 0.8307801 PHYS_OFFSET: 0x0[ 0.833668] CPU features: 0x1,00000001,70028143,0000720b[ 0.839004] Memory Limit: none[ 0.842070] ---[ end Kernel panic not syncing: No working init found. Try passing init= option to kernel. See Linux Documentation/admin-guide/init.rst for guidance ]---Apart from re-imaging the card and sticking a backup of /home onto the new system, is there a better way in future to recover from this kind of event? I've never had this happen before.
Statistics: Posted by scruss — Sat Oct 12, 2024 9:44 pm — Replies 0 — Views 35