Sorry I am late to this thread.[ 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
Your system panicked before mounting the rootfs, while trying to launch /init, a shell script in the initramfs. (In the final rootfs, we run /sbin/init, not /init.) The error is ENOENT, which means either /init or /bin/sh was missing. (/bin/sh in initramfs should be statically linked.)
Although initramfs is built from files in the root, I do not see a reason to suspect that the corruption occurred in the root first and then propagated to the initramfs. Especially when the error is ENOENT.
If you do not have any special kernel module requirements on your Pi5, you may have been able to boot just by renaming initramfs_2712.
Using btrfs instead of ext4 would not have helped in this case. I do not see how it would ever help, unless we are supposed to be in the habit of scrubbing immediately before every reboot, in the hope of finding corruption while the system is still running. We could just as easily use debsums for that.
Statistics: Posted by jojopi — Mon Oct 14, 2024 1:36 am
