Hello @fmslcf30319
The "Kernel panic - not syncing: No working init found" error on your Raspberry Pi usually means the kernel can't find the initial program to run after it boots. This is often due to a missing, corrupted, or misconfigured init process. Since you've already tried re-downloading and re-copying the image, let's explore some other potential causes and solutions:
1. Device Tree Issues (Most Likely Cause with Custom OS Images):
-
Incorrect Device Tree Blob (DTB): The Raspberry Pi uses Device Tree files to describe the hardware. If the wrong DTB is being loaded, the kernel might not be able to initialize properly. This is especially common if the OS image was built for a different Raspberry Pi model or a different hardware configuration.
- Solution: Check the
config.txt file on the boot partition of your SD card. Look for the dtoverlay= and dtparam= lines. Make sure they are appropriate for your Raspberry Pi 3B. If you're using a custom overlay, ensure it's correctly configured. If you're unsure, try commenting out any dtoverlay= lines to see if the default configuration works. For a Raspberry Pi 3B, you might not need any dtoverlay= lines at all for basic functionality.
-
Missing Device Tree: The DTB file itself might be missing from the boot partition.
- Solution: Ensure that a
.dtb file (e.g., bcm2710-rpi-3-b.dtb or similar) exists in the boot partition. If it's missing, you'll need to obtain it from a working image or a Raspberry Pi OS image and copy it to the boot partition.
2. Corrupted Filesystem:
-
Even though you re-imaged the SD card, there's a small chance the filesystem on the rootfs partition is corrupted.
-
Solution: After flashing the SD card, try running a filesystem check on the rootfspartition (the second partition, usually). You'll need to mount the partition on another Linux system. Use fsck (filesystem check) from a Linux environment. Important:Unmount the partition before running fsck. The command would look something like this (replace /dev/sdX2 with the correct device and partition):
sudo umount /dev/sdX2
sudo fsck -y /dev/sdX2
The -y option automatically answers "yes" to any prompts to fix errors. Be careful using this, but it's generally safe for minor corruption.
3. init Path Problems:
-
The kernel might be looking for init in the wrong location.
- Solution: You can try specifying the
init path on the kernel command line. Edit the cmdline.txt file on the boot partition. Add init=/sbin/init or init=/bin/init to the end of the line. Try both. The cmdline.txt file is a single line. Don't add a newline.
4. Kernel Command Line Issues:
-
The cmdline.txt file might be missing essential parameters.
-
Solution: Compare the contents of your cmdline.txt file with a known-good cmdline.txt file from a standard Raspberry Pi OS image (like Raspberry Pi OS Lite). Make sure you have at least the following:
console=serial0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait
Adjust /dev/mmcblk0p2 if your root partition is different.
5. SD Card Issues:
-
Although less likely since you've re-imaged, the SD card itself could be faulty.
- Solution: Try a different SD card. Use a reputable brand and a card known to work well with Raspberry Pi.
6. Power Supply Issues:
-
An underpowered power supply can sometimes cause strange errors during boot.
- Solution: Ensure you're using a 5V 2.5A (or higher) power supply specifically designed for the Raspberry Pi.
7. Image Creation Problems (PL-App Launcher Specific):
-
Since you're using PL-App Launcher, there might be a bug in how it creates the image.
- Solution: Check the PL-App Launcher documentation for any known issues or troubleshooting steps related to creating images for the Raspberry Pi 3B. Contact the PL-App Launcher support or community forums for assistance. Try creating a basic Raspberry Pi OS image (using Raspberry Pi Imager) to rule out hardware problems.
Troubleshooting Steps:
- Start with the
config.txt and cmdline.txt files. These are the most common culprits. Carefully examine them for errors.
- Try a known-good Raspberry Pi OS image. Flash a standard Raspberry Pi OS image (like Raspberry Pi OS Lite) to the SD card using Raspberry Pi Imager. If it boots, you know the hardware is working correctly, and the problem is definitely with the PL-App Launcher image or its configuration.
- Check the boot partition contents. Make sure the necessary
.dtb, .img, and .elf files are present.
- Use a serial console. Connecting a serial console to the Raspberry Pi will give you more detailed boot messages, which can help pinpoint the exact cause of the error. You'll need a USB-to-TTL serial adapter.
By systematically checking these potential causes, you should be able to identify and resolve the "Kernel panic - not syncing: No working init found" error.
Hope This Helps!!!
AshSe
Community Etiquette:
- Insert photos/images inline - don't attach.
- Always mark helpful and correct answers, it helps others find what they need.
- For a prompt reply, kindly tag @name. An email will be automatically sent to the member.
