Purchased 2 x Raspberry Pi Zero 2W last week. I’ve owned Pi 1s, 3Bs and Zeros for years and this is the first time I’ve encountered this error. MicroSD cards are new 64Gb Sandisk 90MB/s units (all I could get locally).
So far, every Pi OS image I’ve tried (both 32 and 64 bit, lite and full) has resulted in the “7 blink” error message which equates to “kernal.img not found”. In every case, the bootfs partition contains a file called “kernal8.img”. (renaming it didn’t help!). I’ve also created images from both the Windows and Linux imagers with the same result.
Can any one explain what is going on here and (hopefully) suggest a solution?
The “7 blink” error message you’re encountering on your Raspberry Pi Zero 2W indicates that the kernel image file (kernel.img) is not found during the boot process. This error typically occurs when the Raspberry Pi firmware fails to locate the necessary kernel image to initiate the operating system. I think you’ll need to rename the “kernal8.img” file to “kernel.img” on the boot partition of your SD card.
As per my initial message, I tried that numerous times with different images.
All to no avail.
Searching the web suggests it could be a corrupted image or card, so I’m going to try again with a fresh card.
The Pi Imager reads over the card after it’s done writing to make sure it matches the image, so that makes me think it’s not a bad card, but perhaps your image is corrupted?
Out of interest, what does your boot partition report as bytes used?
Have you reinstalled the Pi Imager by any chance?
This is using the 64-bit Lite version:
Happens with every microSD I have, with every image I’ve tried, whether using RasPi imager or Balena Etcher to create the image.
Most curious issue is that once I’ve tried to boot from the image in the Pi Zero 2 W, the card is no longer recognised by Windows as having a FAT bootfs image. Have tried renaming kernal8.img to kernal.img as suggested elsewhere with no result.
Both cards are about to be cast into the “some other time” drawer!
Still no joy.
I’ve ordered a card from the store today which will hopefully arrive on Monday or Tuesday.
If that doesn’t work, not sure what I’ll do then.
If you continue to have problems, let us know. If it looks like failed hardware, we’re happy to cover that with an RMA under warranty, however Pis are tested post-manufacture, so one failure is rare, 2 even rarer.
I found a thread suggesting that kernel8 is associated with 64-bit OSs, which can’t be run by older boards like the Zero W. I checked your store account, and I can see a recent order for 2 Zero Ws (not 2Ws), are you sure they are 2s?
FWIW I found that a 64-bit OS contained
kernel8.img and the 32-bit OS had
kernel.img among others.
Also couldn’t help but notice you’ve misspelled kernel a few times, so if you’re renaming files or googling things, getting that right may also help.
Could you report which kernel files are included in a freshly flashed Pi 32-bit Lite OS?
So who feels like a total goose right about now?
James advised me that I had purchased Pi Zero Ws rather than Zero 2Ws. Not sure how I did that but nevertheless, ensuring I restricted my efforts to the 32-bit version of Raspbian paid dividends.
Eventually, I was able to get a bootable system, albeit after a lot of fiddling about. Turns out that the MicroSD adapters that come with the microSD cards don’t always work…
I’ve got a box full of them and at least a third of them don’t seem to work. Good news is that the Sandisk brand seem to be most reliable.
So I’ve now got one working Pi Zero W. The other one doesn’t seem to keep the SSH password I used during the Pi Imager setup. They really need to add “Show Password” to the SSH section (they do for the wifi configuration).
Anyway, thanks to everyone who offered suggestions. It is greatly appreciated.
Now I’m just going to slink away and hide until my embarrassment fades…