[prev in list] [next in list] [prev in thread] [next in thread]
List: busybox
Subject: RE: Kernel panic - not syncing: No working init found
From: Vered Zvi <veredz () elta ! co ! il>
Date: 2016-11-01 15:27:04
Message-ID: 1EFFBDE6584C794F8A0ADF2CAC8D60E09F8AB974 () eltidex1 ! elta ! co ! il
[Download RAW message or body]
Hello,
The solution:
I had an invalid symbolic link in /lib64 to ld-2.9.so
I should have a link to ld-2.22.so
Thank you,
Z.V
_____________________________________
From: busybox [busybox-bounces@busybox.net] on behalf of Mattias Schlenker \
[ms@mattiasschlenker.de]
Sent: Tuesday, November 01, 2016 5:00 PM
To: busybox@busybox.net
Subject: Re: Kernel panic - not syncing: No working init found
Am 01.11.2016 um 15:15 schrieb Vered Zvi:
> Hello,
>
> Where should I run:
> chroot /bin/busybox ?
>
> under the host PC ?
Yes, under the host PC. I assume, host PC and target architecture for
initramfs are the same architecture, busybox is installed with all
necessary symlinks and the files are all residing in some directory
"/path/to/initramfs", then you execute
chroot /path/to/initramfs /bin/busybox
and probably afterwards:
chroot /path/to/initramfs /bin/ash
To get a shell in the initramfs and look around there. If the host and the initramfs \
target are same architecture, but host is 64 bit and initramfs is 32 bit, you want to \
use:
linux32 chroot /path/to/initramfs /bin/busybox
Regards,
Mattias
>
> Thank you,
> Z.V
> ________________________________________
> From: busybox [busybox-bounces@busybox.net] on behalf of Mattias Schlenker \
> [ms@mattiasschlenker.de]
> Sent: Tuesday, November 01, 2016 2:58 PM
> To: busybox@busybox.net
> Subject: Re: Kernel panic - not syncing: No working init found
>
> Am 01.11.2016 um 13:41 schrieb Vered Zvi:
> > Hello,
> >
> > I'm working with kernel 3.18.24, busybox 1.24.2
> >
> > /lib contains the following files:
> >
> > ld-2.22.so
> > ld-linux-x86-64.so.2 -> ld-2.22.so
> > libc-2.22.so
> > libcrypt-2.22.so
> > libcrypt.so.1 -> libcrypt-2.22.so
> > libc.so.6 -> libc-2.22.so
> > libdl-2.22.so
> > libdl.so.2 -> libdl-2.22.so
> > libgcc_s.so
> > libgcc_s.so.1
> > libm-2.22.so
> > libm.so.6 -> libm-2.22.so
> > libpthread-2.22.so
> > libpthread.so.0 -> libpthread-2.22.so
> > libresolv-2.22.so
> > libresolv.so.2 -> libresolv-2.22.so
> > librt.so.1
> > libstdc++.so.6
> > libthread_db.so.1
> > libutil-2.22.so
> > libutil.so.1 -> libutil-2.22.so
> >
> > /lib64 contains the following files:
> >
> > ld-linux-x86-64.so.2 -> /lib/ld-2.9.so
> > libc.so.6 -> /lib/libc.so.6
> > libm.so.6 -> /lib/libm.so.6
> >
> > Upon boot I'm getting:
> > Kernel panic - not syncing: No working init found. Try passing init=option
> >
> > Are there any files missing ?
> > How can I debug such error ?
> First: Put everything that's in your initramfs to a directory and try to
> run busybox via chroot from outside, like "chroot /my/root/dir
> /bin/busybox". You either get a list of compiled in applets or an error
> telling you which files are missing.
>
> Second: If that worked, try to run with "init=/bin/ash" to drop you to a
> shell. In this shell you can mount filesystems and stuff... Make notes
>
> Third: there should be a symlink /init -> /bin/busybox if you are
> running busybox in inittab mode and of course an inittab and startup
> scripts. If you are using busybox to pivot root you should use an
> /linuxrc script to make sure the exec'ed init keeps PID 1.
>
> If you want to see how to build a minimal BSD Gentoo like RC script
> system upon busybox' inittab that is easily readable take a look at one
> of my side projects - it should also explain which filesystems have to
> be mounted when, how to invoke the dhcp client and stuff:
> https://github.com/mschlenker/TinyCrossLinux
>
> Regards,
> Mattias
>
> --
> Mattias Schlenker - Redaktion + EDV-Beratung + Linux-CD/DVD-Konzepte
> August-Bebel-Str. 74 - 04275 LEIPZIG - GERMANY
>
> Telefon (VoIP "ueberall"), geschaeftlich: +49 341 39290767
> Telefon (Festnetz), privat und Fax: +49 341 30393578
> Mobil: +49 163 6953657
>
> Bitte fuer geschaeftliche Telefonate vorzugsweise die VoIP-Telefonnummer
> +49 341 39290767 verwenden, da ich diese aufs Mobiltelefon routen kann!
>
> http://blog.rootserverexperiment.de/ http://news.mattiasschlenker.de/
>
> _______________________________________________
> busybox mailing list
> busybox@busybox.net
> http://lists.busybox.net/mailman/listinfo/busybox
>
> This Email and the attachments were emulated by Check Point ThreatEmulation \
> Service. The information contained in this communication is proprietary to Israel \
> Aerospace Industries Ltd. and/or third parties, may contain confidential or \
> privileged information, and is intended only for the use of the intended addressee \
> thereof. If you are not the intended addressee, please be aware that any use, \
> disclosure, distribution and/or copying of this communication is strictly \
> prohibited. If you receive this communication in error, please notify the sender \
> immediately and delete it from your computer.
--
Mattias Schlenker - Freier IT-Fachredakteur und -autor
redaktion@mattiasschlenker.de
Mattias Schlenker - IT-Consulting, Softwareentwicklung
consulting@mattiasschlenker.de
Address__ August-Bebel-Str. 74 - D-04275 LEIPZIG - GERMANY
Phone: +49 341 39290767 Fax: +49 341 30393578
Mobile: +49 163 6953657 Another mobile: +49 159 03160327
VATIN_________________________________________ DE240998538
Fork me!____________________ https://github.com/mschlenker
Website.__________________ http://www.mattiasschlenker.de/
My books!___________ http://www.arduino-hausautomation.de/
_______________________________________________
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
This Email and the attachments were emulated by Check Point ThreatEmulation Service.
The information contained in this communication is proprietary to Israel Aerospace \
Industries Ltd. and/or third parties, may contain confidential or privileged \
information, and is intended only for the use of the intended addressee thereof. If \
you are not the intended addressee, please be aware that any use, disclosure, \
distribution and/or copying of this communication is strictly prohibited. If you \
receive this communication in error, please notify the sender immediately and delete \
it from your computer.
_______________________________________________
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic