Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: baruch@tkos.co.il (Baruch Siach)
To: linux-arm-kernel@lists.infradead.org
Subject: Kernel panic - not syncing: No init found
Date: Wed, 19 Sep 2012 08:04:22 +0300	[thread overview]
Message-ID: <20120919050421.GB11255@sapphire.tkos.co.il> (raw)
In-Reply-To: <1347882577.12909.YahooMailNeo@web133203.mail.ir2.yahoo.com>

Hi Ellis,

On Mon, Sep 17, 2012 at 12:49:37PM +0100, Ellis Andrew wrote:
> I have done a bit of searching around, and I'm not sure how to boot into 
> initrmafs. Can you please point me towards some instructions on how to do 
> this.

See Documentation/filesystems/ramfs-rootfs-initramfs.txt in (recent) kernel 
source tree. See also http://www.landley.net/writing/rootfs-howto.html by the 
same author.

baruch

> ________________________________
>  From: Baruch Siach <baruch@tkos.co.il>
> To: Ellis Andrew <ajellisuk@yahoo.co.uk> 
> Cc: "linux-arm-kernel at lists.infradead.org" <linux-arm-kernel@lists.infradead.org> 
> Sent: Saturday, 15 September 2012, 20:04
> Subject: Re: Kernel panic - not syncing: No init found
>  
> Hi Ellis,
> 
> On Wed, Sep 12, 2012 at 05:18:22PM +0100, Ellis Andrew wrote:
> > After a lot of searching with Google I have found this is a common problem, 
> > unfortunately none of the solutions I have found, fix the problem.
> > 
> > The original error I got was:
> > 
> > Kernel panic - not syncing: No init found.? Try passing init= option to kernel.
> > 
> > The command line option was:
> > root=/dev/mtdblock3 rootfstype=jffs2 rw console=ttyMCS mem=64M at 0x0
> > 
> > I after digging around with google, I found a suggestion which I tried, I made my command line:
> > root=/dev/mtdblock3 rootfstype=jffs2 rw console=ttyMCS mem=64M at 0x0 init=/sbin/init panic=4
> > 
> > But I now get the following error:
> > 
> > Freeing init memory: 88K
> > Failed to execute /sbin/init.? Attempting defaults...
> > Kernel panic - not syncing: No init found.? Try passing init= option to kernel.
> > 
> > I can see that the Root drive is being mounted.
> > 
> > The contents of the init file is:
> > 
> > #!/bin/busybox ash
> > /bin/busybox mount -t sysfs /dev/sys /sys
> > /bin/busybox mount -t proc? /proc
> > /bin/busybox mount -t devpts /dev/pts
> > # Populate /dev according to /sys
> > /bin/busybox mdev -s
> > /bin/busybox --install -s
> > /linuxrc
> > exec /sbin/init "$@"?? </dev/console >/dev/console 2>&1
> > 
> > Does anyone have any suggestions on how to fix this please? 
> 
> The most common reason for this failure is that your root filesystem layout is 
> not what you think it is. Try booting into initramfs and mounting your jffs2 
> filesystem from there to examine it directly on your running system.
> 
> baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -

      reply	other threads:[~2012-09-19  5:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-12 16:18 Kernel panic - not syncing: No init found Ellis Andrew
2012-09-15 19:04 ` Baruch Siach
2012-09-17 11:49   ` Ellis Andrew
2012-09-19  5:04     ` Baruch Siach [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120919050421.GB11255@sapphire.tkos.co.il \
    --to=baruch@tkos.co.il \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox