Raspberry pi kernel panic init

Содержание

Raspberry pi kernel panic init

My RaspberryPi arrived today so I have been busy installing the opperating system (Debian), I managed to follow all the instructions and get the RaspberryPi working etc. However then when I turned it off and sometime later restarted (first time it had been turned on after the installation had finished and was working) I got the following error: Kernel Panic — not syncing: No init found.

I have googled the error and found many references to Kernel Panic but usually with a different error message. I just wondered if anyone had any ideas? Is this still likely to be an issue with the SD card?

Re: Kernel Panic No init found

Likewise — I got my Pi yesterday, just put Debian on a 4GB SD card and am getting the Kernel Panic — No init found error.

It looks like you could have more success with the previous build according to this post:
http://www.raspberrypi.org/phpBB3/viewt . it+#p83592
I’m going to give it a go — but not planning on any longterm use of it as the thought of it using up your 10,000 write cycles within 4 days is a little concerning (if Barry’s observations are correct).

Re: Kernel Panic No init found

It may not be any help to you, but I had the Kernel Panic error when I was setting up my Pi earlier today. I swapped the SD card (PNY Class 4 8Gb) for another one I had around (Kingston Class 4 8 Gb, but still had the same issue. Made sure I had gone to the latest version (19-04) of the Debian OS, but still problems with Kernel Panic error.

In frustration I removed the mouse and keyboard and tried again and it worked! Trying them one at a time it transpired that the Pi didn’t like the wired USB keyboard I had picked up at PC world — presumably a driver issue. So when I swapped the keyboard from the one my Dell was using, everything started just fine.

It may be worth trying to boot with no kb or mouse to eliminate these as potential sources of your problem.

Источник

Raspberry pi kernel panic init

I am experiencing an issue where my Raspberry Pi 3 is no longer able to boot. The image runs apache, WordPress, NextCloud, and an email server. Everything was working fine for around a month and a half and then today I received a Jetpack report saying the WordPress site was down. Going to the website resulted in a blank page — however, NextCloud and the email server still worked without any problems. Logging in via SSH gave the message *** stack smashing detected ***, so I restarted the pi. However, on booting I now receive the following error message:

Tried the sd card on a Raspberry Pi 2 and receive the same output. Unfortunately the text scrolls too fast to read what precedes it and it looks like it is not possible to scroll back up via the keyboard — the power light on it doesn’t even turn on anymore.

Re: Pi not booting. «end Kernel panic — not syncing: Attempted to kill init!»

Googling the term stack smashing on arch Linux gave lots of results https://www.google.co.uk/search?q=stack . istgfUt5Io
but one that stood out https://en.wikipedia.org/wiki/Buffer_ov . protection because of this line

«Stack buffer overflow can be caused deliberately as part of an attack known as stack smashing. «

because you said you were running apache, WordPress, and you said «I received a Jetpack report saying the WordPress site was down», is it possible that some one has tried to hack your pi and caused your system to be come corrupted ?

This could mean there is no way to recover your system, unless you have a backup you could flash to a replacement SD card or the current SD card.

Re: Pi not booting. «end Kernel panic — not syncing: Attempted to kill init!»

I will tell you my story about «end kernal panic», and you may find if it is your problem.

I want to make a 32-bit os for rpi4b 2G version. My 64-bit OS work fine except it can not support hardware-acculator.(Or you can say I can not find the useful way to use hardware accleration for UVC decoding in opencv.) So I switch to 32-bit and want to use mmal or openmax il.
Everything is ok until I plug my U-stick to rpi4b. (Why I use U-stick cause I broken my SD card. Why I can broken it it is because of my bad box design and the bad sd-card-slot disign on pi. It is aother story.) Yes the same error:

I try to change uuid in cmdline.txt // try to check sha256 // switch rpi os to noods // make a new u-stick , Neither can be work.
OK, now let’s me describe my U-stick. It is actually a «tf card + card reader». And my new u-stick is also a new tf card with the same card reader. I don’t know why it can be work in win10 when I burn new os in it. But I just can not work when I plug it in rpi. So I finially find a rpi2. And plug my tf card to its card slot. It works. And I try to plug the same tf card via card reader. It can not work. So I realize the card reader may be broken.

I find a good quality( a little large one) card reader. plug it into rpi4b. Yes, it worked. Spent a whole afternoon and suffer many stress just because bad-quality card ready.

All in all, I think you should try to check you tf-card or you u-stick or card-reader. One of them maybe is broken.

Re: Pi not booting. «end Kernel panic — not syncing: Attempted to kill init!»

My dear friends

I had the same problem End Kernal Panic. not booting
And ik got an Answer

Download (on this side) >> Imager to a working computer
Install it and Run it
Click on and scroll to
@ operation system select the file with the rasp logo
Now select SD Card and Upload the file to you’re SD Card

Put the SD card in you’re Raspberry Pi and Startup.
After a few seconds the screen turn Green and the green active LED blinks regularly

You’re Raspberry System is recorerd and accessible again

Источник

Raspberry pi kernel panic init

I am trying to boot the mainline Linux kernel on the Raspberry Pi 2. But it looks like I get a kernel panic when the kernel tries to launch the init process:

Any ideas, what is going wrong here?

Edit: I should mention, that I am using the bcm2835_defconfig and the bcm2836-rpi-2-b.dtb without modifications.

Re: Kernel Panic with mainline Linux 4.5 on RPi2

Languages using left-hand whitespace for syntax are ridiculous

DMs sent on https://twitter.com/DougieLawson or LinkedIn will be answered next month.
Fake doctors — are all on my foes list.

The use of crystal balls and mind reading is prohibited.

Re: Kernel Panic with mainline Linux 4.5 on RPi2

I tried, but the result was the same. But the Yocto/OpenEmbedded build scripts compile a cross compiler for me, so I do not need the precompiled ones.

As the mainline kernel does boot on my Pi 2, I see two possible reasons for my issues: The mainline u-boot is not compatible with the mainline kernel or the defconfig of the mainline kernel is missing something that I need.

Источник

Kernel panic: No working init found. Try passing init= option to kernel.

Операционка стоит на raspberry pi, я отключил ее от питания и после включения стала выдавать это сообщение. Более сделать кроме как выключить и включить с ней нельзя.

Что делать, прошу, помогите! Если всё-таки вариантов нет, то как можно файлы хотя-б скопировать?

Более сделать кроме как выключить и включить с ней нельзя

Ну если ничего другого сделать нельзя, то остается только включать/выключать до посинения.

Что, прямо таки совсем нельзя? Даже в командную строку загрузчика нельзя?

читал по поводу этого, у raspberry загрузчик находится в виде файла config.txt.

Файлы скопировать можно с microsd карточки в линуксе, если нет другого линукса можно загрузиться с livecd или usb.

загрузчик находится в виде файла config.txt.

Во-первых, загрузчик не может быть в текстовом файле, это бинарник. Во-вторых, какая нахрен разница где он там находится, важно как он запускается, и есть ли у него своя консоль.

И кстати ты не пробовал банально вынуть sd, вставить в другой комп, и посмотреть все ли там в порядке?

Там не граб, по-моему там нет консоли

Ядро загрузилось, init — нет. Вероятно, повреждена ФС на SD-карте. Попробуй передать ядру init=/bin/sh , либо смонтировать и посмотреть на другой системе.

По идее даже можно вставить карточку в смартфон и все прочитается, лул.

вставляю карточку в компьютер, появляются два раздела: boot и rootfs. как понимаю файлы должны быть в rootfs, но там ничего нет, хотя размер 0 байт, написано что используется 4%.

Какая ОС на компьютере?

Да, файлы должны быть в rootfs, вся линуксовая структура, куда все делось — хз

Воткни SD-карту в компьютер с линуксом и сделай в GParted проверку с устранением ошибок. У тебя обычный сбой карты.

Кстати, эти SD-карты вобще хлипкие, я не советую на них что-то регулярно писать — мне пришлось все логи в своих скрпитах автоматики отключить.

Если нужно писать логи, то пиши либо по сети, либо на USB-винт, либо на USB-флэшку (её не жалко).

Очевидно, у тебя посыпалась память как раз в том месте, где инит был. Всё, что тебе нужно — это заново поставить систему. Raspberry Pi — очень ненадёжная штука.

Попробуй photorec тогда, если надо файлы оттуда извлечь, но файловая система сдохла.

Источник

Raspberry pi kernel panic init

I am trying to build and use my own Bootloader and Linux version on a Raspberry Pi 4B hardware. I am facing a Kernel panic from which I am not able to solve my way out.

Kernel panic — not syncing: Attempted to kill init! exitcode=0x00007f00 — Not able to resolve

I saw some posts regarding the same but none seems to be conclusive.

U-Boot: v2020.07
Linux Kernel: v5.8.9

Used busybox to prepare my Root-FS which seems to be mounted, as per what I see on console. This is where I get stuck at the end:

Re: Raspberry Pi 4B — Kernel panic — not syncing: Attempted to kill init!

I get this when I run file init inside the /sbin folder:

init: symbolic link to ../bin/busybox

And the ../bin folder has the busybox file too. Any idea what is normally expected?

Re: Raspberry Pi 4B — Kernel panic — not syncing: Attempted to kill init!

This is what I see:

busybox: ELF 64-bit LSB executable, ARM aarch64, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-aarch64.so.1, for GNU/Linux 4.20.8, stripped

file -L init
init: ELF 64-bit LSB executable, ARM aarch64, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-aarch64.so.1, for GNU/Linux 4.20.8, stripped

Re: Raspberry Pi 4B — Kernel panic — not syncing: Attempted to kill init!

Yes, it is a 64-bit kernel I built with the arm64 toolchain.

When I provide iminfo 00080000 in U-Boot command prompt, this is what I get:

## Checking Image at 00080000 .
Legacy image found
Image Name: 15Oct2020LinuxImage
Image Type: AArch64 Linux Kernel Image (uncompressed)
Data Size: 34241024 Bytes = 32.7 MiB
Load Address: 00200000
Entry Point: 00200000
Verifying Checksum . OK
U-Boot>

Re: Raspberry Pi 4B — Kernel panic — not syncing: Attempted to kill init!

Yes, I guess it did, since I had configured the /dev/mmcblk1p2 as the root in cmdline.txt , which is the rootfs partition of my 32GB SD Card. And this is what I see on the log:

[ 6.473890] Waiting for root device /dev/mmcblk1p2.
[ 6.562961] mmc1: new ultra high speed DDR50 SDHC card at address aaaa
[ 6.577512] mmcblk1: mmc1:aaaa SC32G 29.7 GiB
[ 6.598088] mmcblk1: p1 p2
[ 6.618752] usb 1-1: new high-speed USB device number 2 using xhci_hcd
[ 6.675074] EXT4-fs (mmcblk1p2): mounted filesystem with ordered data mode. Opts: (null)
[ 6.683924] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
[ 6.696399] devtmpfs: mounted

Re: Raspberry Pi 4B — Kernel panic — not syncing: Attempted to kill init!

An update: Apparently I came across another post elsewhere which seemed to imply that busybox needs to be statically linked and not dynamic, which seemed to be the issue for me as well. I changed the build config to make it static linking and then the kernel panic disappeared.

I now am able to reach the Kernel console successfully, but I have a strange problem now. I reach /sbin/init and then the UART output to the host PC freezes. But when I connect HDMI to the Raspberry Pi, all is good and I get the console on the HDMI display.

Do you know of any solution to this problem? This seems to be reported here already but no one seems to have a conclusive solution for it .(viewtopic.php?t=270723)

Re: Raspberry Pi 4B — Kernel panic — not syncing: Attempted to kill init!

if busybox is dynamic, then you must also copy all of the dynamic libraries it depends on, thats true for any dynamic binary

you can test things by using chroot to run the binary in an isolated environment

Источник