Firstly, thank you for work! I have been using this package on a Pi Zero 2 successfully as a portable file server for the last year with no problems. I have just got a Raspberry Pi 5B 2GB and decided to use the latest comitup image (2026-04-25). I've noticed it boots fine the first time only, after the first reboot/shutdown, a "Kernel panic" occurs. On a fresh image, once booted, I simply reboot or shutdown on the terminal and this occurs consistently.
...
PM: genpd: Disabling unused power domains
Freeing unused kernel memory: 2048k
Run /Init as init process
Failed to execute /init (error -26)
Run /sbin/init as init process
Starting init: /sbin/init exists but couldn't execute it )error -26)
Run /etc/init as init process
Run /bin/init as init process
Run /bin/sh as init process
Starting init: /bin/sh exists but couldn't execute it (error -26)
Kernel panic - not syncing: No working init found. Try passing init= option to kernel. See Linux Documentation/admin-guide/init.rst for guidance.
CPU: 3 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.12.75+rpt-rpi-v8 #1. Debian 1:6.12.75-1+rpt1
Hardware Name: Raspberry Pi 5 Model B Rev 1.1 (DT)
...
I have seen suggestions online about using e2fsck and repairing the boot partitions, but this is perhaps repairable through configuration. I'm unfortunately not experienced enough to offer much more than this. Please let me know if there is anything else I can do to help.
Thank you
Firstly, thank you for work! I have been using this package on a Pi Zero 2 successfully as a portable file server for the last year with no problems. I have just got a Raspberry Pi 5B 2GB and decided to use the latest comitup image (2026-04-25). I've noticed it boots fine the first time only, after the first reboot/shutdown, a "Kernel panic" occurs. On a fresh image, once booted, I simply reboot or shutdown on the terminal and this occurs consistently.
...
PM: genpd: Disabling unused power domains
Freeing unused kernel memory: 2048k
Run /Init as init process
Failed to execute /init (error -26)
Run /sbin/init as init process
Starting init: /sbin/init exists but couldn't execute it )error -26)
Run /etc/init as init process
Run /bin/init as init process
Run /bin/sh as init process
Starting init: /bin/sh exists but couldn't execute it (error -26)
Kernel panic - not syncing: No working init found. Try passing init= option to kernel. See Linux Documentation/admin-guide/init.rst for guidance.
CPU: 3 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.12.75+rpt-rpi-v8 #1. Debian 1:6.12.75-1+rpt1
Hardware Name: Raspberry Pi 5 Model B Rev 1.1 (DT)
...
I have seen suggestions online about using e2fsck and repairing the boot partitions, but this is perhaps repairable through configuration. I'm unfortunately not experienced enough to offer much more than this. Please let me know if there is anything else I can do to help.
Thank you