kernel panic - not syncing: No init found

kernel panic - not syncing: No init found

[Francis Meyvis]

Hello,

I probably miss something trivial.
I cloned the git://git.yoctoproject.org/poky.git
I build on a 64 bit machine a qemux86-64
(. ./oe-init-build-env qemux86-64 and changing the conf/local.conf)
I build the core-image-sato & core-image-minimal.
Then I try to run with
runqemu qemux86-64 core-image-sato ext3

But both sato and minimal give me this message:
Kernel panic - not syncing: No init found.

As runqemu showed me the full command line I tried to add the --append
command line option
init=/sbin/init and /sbin/init.sysvinit
But that did not help (there's a message saying Failed to execute
/sbin/init. Attempting defaults...)
I verified by mounting these ext3 images on a loop device that there's
really a /sbin/init present.

Can somebody tell what I'm doing wrong?

BTW is there any way to not have to run qemu with root permissions?
I ran the android emulator and it does not require me to be root.
Should I configure something on my Ubuntu machine to get qemu to function?

Thanks,
francis

Re: kernel panic - not syncing: No init found

[Bruce Ashfield]

On 11-07-31 3:44 PM, Francis Meyvis wrote:
> Hello,
>
> I probably miss something trivial.
> I cloned the git://git.yoctoproject.org/poky.git
> I build on a 64 bit machine a qemux86-64
> (. ./oe-init-build-env qemux86-64 and changing the conf/local.conf)
> I build the core-image-sato&  core-image-minimal.
> Then I try to run with
> runqemu qemux86-64 core-image-sato ext3
>
> But both sato and minimal give me this message:
> Kernel panic - not syncing: No init found.
>
> As runqemu showed me the full command line I tried to add the --append
> command line option
> init=/sbin/init and /sbin/init.sysvinit
> But that did not help (there's a message saying Failed to execute
> /sbin/init. Attempting defaults...)
> I verified by mounting these ext3 images on a loop device that there's
> really a /sbin/init present.
>
> Can somebody tell what I'm doing wrong?

Can you send a full bootlog, or paste it somewhere accessible ? It's hard
to say what's with the information you've given.

Is this the latest yocto master ?

If you are seeing that message it typically means that the the
device that is being used as the root isn't ready (fixed by
rootwait/rootdelay) or isn't supported (i.e. NFS root without
the right ethernet device). Changing what init is, won't change
the result if either one of those is the case.

Cheers,

Bruce

>
> BTW is there any way to not have to run qemu with root permissions?
> I ran the android emulator and it does not require me to be root.
> Should I configure something on my Ubuntu machine to get qemu to function?
>
> Thanks,
> francis
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

Re: kernel panic - not syncing: No init found

[Tom Zanussi]

On Sun, 2011-07-31 at 19:42 -0700, Bruce Ashfield wrote:
> On 11-07-31 3:44 PM, Francis Meyvis wrote:
> > Hello,
> >
> > I probably miss something trivial.
> > I cloned the git://git.yoctoproject.org/poky.git
> > I build on a 64 bit machine a qemux86-64
> > (. ./oe-init-build-env qemux86-64 and changing the conf/local.conf)
> > I build the core-image-sato&  core-image-minimal.
> > Then I try to run with
> > runqemu qemux86-64 core-image-sato ext3
> >
> > But both sato and minimal give me this message:
> > Kernel panic - not syncing: No init found.
> >
> > As runqemu showed me the full command line I tried to add the --append
> > command line option
> > init=/sbin/init and /sbin/init.sysvinit
> > But that did not help (there's a message saying Failed to execute
> > /sbin/init. Attempting defaults...)
> > I verified by mounting these ext3 images on a loop device that there's
> > really a /sbin/init present.
> >
> > Can somebody tell what I'm doing wrong?
> 
> Can you send a full bootlog, or paste it somewhere accessible ? It's hard
> to say what's with the information you've given.
> 
> Is this the latest yocto master ?
> 
> If you are seeing that message it typically means that the the
> device that is being used as the root isn't ready (fixed by
> rootwait/rootdelay) or isn't supported (i.e. NFS root without
> the right ethernet device). Changing what init is, won't change
> the result if either one of those is the case.
> 

I'm also seeing this on both sugarbay and jasperforest with the latest
master.  rootwait doesn't help.

rtc_cmos 00:07: setting system clock to 2010-01-02 05:35:34 UTC
(1262410534)
Freeing unused kernel memory: 720k freed
Failed to execute /init
Kernel panic - not syncing: No init found.  Try passing init= option to
kernel. 
See Linux Documentation/init.txt for guidance.
Pid: 1, comm: swapper Not tainted 3.0.0-rc7-yocto-standard+ #1
Call Trace:
 [<ffffffff81541b77>] panic+0x9b/0x191
 [<ffffffff81540862>] init_post+0xc0/0xc0
 [<ffffffff8188bcef>] kernel_init+0x17b/0x17b
 [<ffffffff8154b234>] kernel_thread_helper+0x4/0x10
 [<ffffffff8188bb74>] ? start_kernel+0x377/0x377
 [<ffffffff8154b230>] ? gs_change+0xb/0xb

I thought initially it had something to do with the -live image changes,
but reverting the two -live patches didn't help.

The problem seems to coincide with the tune file changes, but that may
be a red herring.

Tom


> Cheers,
> 
> Bruce
> 
> >
> > BTW is there any way to not have to run qemu with root permissions?
> > I ran the android emulator and it does not require me to be root.
> > Should I configure something on my Ubuntu machine to get qemu to function?
> >
> > Thanks,
> > francis
> > _______________________________________________
> > yocto mailing list
> > yocto@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/yocto
> 
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

Re: kernel panic - not syncing: No init found

[Bruce Ashfield]

On 11-07-31 11:30 PM, Tom Zanussi wrote:
> On Sun, 2011-07-31 at 19:42 -0700, Bruce Ashfield wrote:
>> On 11-07-31 3:44 PM, Francis Meyvis wrote:
>>> Hello,
>>>
>>> I probably miss something trivial.
>>> I cloned the git://git.yoctoproject.org/poky.git
>>> I build on a 64 bit machine a qemux86-64
>>> (. ./oe-init-build-env qemux86-64 and changing the conf/local.conf)
>>> I build the core-image-sato&   core-image-minimal.
>>> Then I try to run with
>>> runqemu qemux86-64 core-image-sato ext3
>>>
>>> But both sato and minimal give me this message:
>>> Kernel panic - not syncing: No init found.
>>>
>>> As runqemu showed me the full command line I tried to add the --append
>>> command line option
>>> init=/sbin/init and /sbin/init.sysvinit
>>> But that did not help (there's a message saying Failed to execute
>>> /sbin/init. Attempting defaults...)
>>> I verified by mounting these ext3 images on a loop device that there's
>>> really a /sbin/init present.
>>>
>>> Can somebody tell what I'm doing wrong?
>>
>> Can you send a full bootlog, or paste it somewhere accessible ? It's hard
>> to say what's with the information you've given.
>>
>> Is this the latest yocto master ?
>>
>> If you are seeing that message it typically means that the the
>> device that is being used as the root isn't ready (fixed by
>> rootwait/rootdelay) or isn't supported (i.e. NFS root without
>> the right ethernet device). Changing what init is, won't change
>> the result if either one of those is the case.
>>
>
> I'm also seeing this on both sugarbay and jasperforest with the latest
> master.  rootwait doesn't help.
>
> rtc_cmos 00:07: setting system clock to 2010-01-02 05:35:34 UTC
> (1262410534)
> Freeing unused kernel memory: 720k freed
> Failed to execute /init
> Kernel panic - not syncing: No init found.  Try passing init= option to
> kernel.
> See Linux Documentation/init.txt for guidance.
> Pid: 1, comm: swapper Not tainted 3.0.0-rc7-yocto-standard+ #1
> Call Trace:
>   [<ffffffff81541b77>] panic+0x9b/0x191
>   [<ffffffff81540862>] init_post+0xc0/0xc0
>   [<ffffffff8188bcef>] kernel_init+0x17b/0x17b
>   [<ffffffff8154b234>] kernel_thread_helper+0x4/0x10
>   [<ffffffff8188bb74>] ? start_kernel+0x377/0x377
>   [<ffffffff8154b230>] ? gs_change+0xb/0xb
>
> I thought initially it had something to do with the -live image changes,
> but reverting the two -live patches didn't help.
>
> The problem seems to coincide with the tune file changes, but that may
> be a red herring.

Nope. I don't think it's a red herring:

Both of these:

   Freeing unused kernel memory: 720k freed
   Failed to execute /init

Indicate that the device came up and init was loaded, the kernel
passed control to userspace and then things went bad. i.e. you just
ran init of the wrong arch or something incompatible with the
kernel support, etc.

Since I'm having no trouble with old rootfs and new kernels, that's
another sign. I'm assuming that old userspace's boot for you ?

Bruce

>
> Tom
>
>
>> Cheers,
>>
>> Bruce
>>
>>>
>>> BTW is there any way to not have to run qemu with root permissions?
>>> I ran the android emulator and it does not require me to be root.
>>> Should I configure something on my Ubuntu machine to get qemu to function?
>>>
>>> Thanks,
>>> francis
>>> _______________________________________________
>>> yocto mailing list
>>> yocto@yoctoproject.org
>>> https://lists.yoctoproject.org/listinfo/yocto
>>
>> _______________________________________________
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>
>

Re: kernel panic - not syncing: No init found

[Francis Meyvis]

[-- Attachment #1: Type: text/plain, Size: 4377 bytes --]

Hello,

When I mounted the root image on loop back device, I actually ran the init
program. It executed and complained about missing params. I tried with the
5, like for network connected inittab. Then init complained there was no
/dev/initctl. So combining this with the replies I got, I think the latest
/sbin/init on yocto master does not support a default run level? I think the
architecture of my root image is for x86 cause my pc could exec it.

Any suggestions on how to continue?

Groetjes,
Francis
On Aug 1, 2011 6:04 AM, "Bruce Ashfield" <bruce.ashfield@windriver.com>
wrote:
> On 11-07-31 11:30 PM, Tom Zanussi wrote:
>> On Sun, 2011-07-31 at 19:42 -0700, Bruce Ashfield wrote:
>>> On 11-07-31 3:44 PM, Francis Meyvis wrote:
>>>> Hello,
>>>>
>>>> I probably miss something trivial.
>>>> I cloned the git://git.yoctoproject.org/poky.git
>>>> I build on a 64 bit machine a qemux86-64
>>>> (. ./oe-init-build-env qemux86-64 and changing the conf/local.conf)
>>>> I build the core-image-sato& core-image-minimal.
>>>> Then I try to run with
>>>> runqemu qemux86-64 core-image-sato ext3
>>>>
>>>> But both sato and minimal give me this message:
>>>> Kernel panic - not syncing: No init found.
>>>>
>>>> As runqemu showed me the full command line I tried to add the --append
>>>> command line option
>>>> init=/sbin/init and /sbin/init.sysvinit
>>>> But that did not help (there's a message saying Failed to execute
>>>> /sbin/init. Attempting defaults...)
>>>> I verified by mounting these ext3 images on a loop device that there's
>>>> really a /sbin/init present.
>>>>
>>>> Can somebody tell what I'm doing wrong?
>>>
>>> Can you send a full bootlog, or paste it somewhere accessible ? It's
hard
>>> to say what's with the information you've given.
>>>
>>> Is this the latest yocto master ?
>>>
>>> If you are seeing that message it typically means that the the
>>> device that is being used as the root isn't ready (fixed by
>>> rootwait/rootdelay) or isn't supported (i.e. NFS root without
>>> the right ethernet device). Changing what init is, won't change
>>> the result if either one of those is the case.
>>>
>>
>> I'm also seeing this on both sugarbay and jasperforest with the latest
>> master. rootwait doesn't help.
>>
>> rtc_cmos 00:07: setting system clock to 2010-01-02 05:35:34 UTC
>> (1262410534)
>> Freeing unused kernel memory: 720k freed
>> Failed to execute /init
>> Kernel panic - not syncing: No init found. Try passing init= option to
>> kernel.
>> See Linux Documentation/init.txt for guidance.
>> Pid: 1, comm: swapper Not tainted 3.0.0-rc7-yocto-standard+ #1
>> Call Trace:
>> [<ffffffff81541b77>] panic+0x9b/0x191
>> [<ffffffff81540862>] init_post+0xc0/0xc0
>> [<ffffffff8188bcef>] kernel_init+0x17b/0x17b
>> [<ffffffff8154b234>] kernel_thread_helper+0x4/0x10
>> [<ffffffff8188bb74>] ? start_kernel+0x377/0x377
>> [<ffffffff8154b230>] ? gs_change+0xb/0xb
>>
>> I thought initially it had something to do with the -live image changes,
>> but reverting the two -live patches didn't help.
>>
>> The problem seems to coincide with the tune file changes, but that may
>> be a red herring.
>
> Nope. I don't think it's a red herring:
>
> Both of these:
>
> Freeing unused kernel memory: 720k freed
> Failed to execute /init
>
> Indicate that the device came up and init was loaded, the kernel
> passed control to userspace and then things went bad. i.e. you just
> ran init of the wrong arch or something incompatible with the
> kernel support, etc.
>
> Since I'm having no trouble with old rootfs and new kernels, that's
> another sign. I'm assuming that old userspace's boot for you ?
>
> Bruce
>
>>
>> Tom
>>
>>
>>> Cheers,
>>>
>>> Bruce
>>>
>>>>
>>>> BTW is there any way to not have to run qemu with root permissions?
>>>> I ran the android emulator and it does not require me to be root.
>>>> Should I configure something on my Ubuntu machine to get qemu to
function?
>>>>
>>>> Thanks,
>>>> francis
>>>> _______________________________________________
>>>> yocto mailing list
>>>> yocto@yoctoproject.org
>>>> https://lists.yoctoproject.org/listinfo/yocto
>>>
>>> _______________________________________________
>>> yocto mailing list
>>> yocto@yoctoproject.org
>>> https://lists.yoctoproject.org/listinfo/yocto
>>
>>
>

[-- Attachment #2: Type: text/html, Size: 6023 bytes --]

Re: kernel panic - not syncing: No init found

[Bruce Ashfield]

On 08/02/11 01:38, Francis Meyvis wrote:
> Hello,
>
> When I mounted the root image on loop back device, I actually ran the
> init program. It executed and complained about missing params. I tried
> with the 5, like for network connected inittab. Then init complained
> there was no /dev/initctl. So combining this with the replies I got, I
> think the latest /sbin/init on yocto master does not support a default
> run level? I think the architecture of my root image is for x86 cause my
> pc could exec it.
>
> Any suggestions on how to continue?

Interesting, since this is failing on multiple image types,
there should be different init scripts at play, each with
different requirements that should be met by the rootfs
generation.

Have you tried updating master and re-building ? Some of
the issues from last week should be resolved at this point.

The boards are known to boot, and boot out of the box, so
either this is something transient, or unique to your setup
at the moment.

Bruce

>
> Groetjes,
> Francis
>
> On Aug 1, 2011 6:04 AM, "Bruce Ashfield" <bruce.ashfield@windriver.com
> <mailto:bruce.ashfield@windriver.com>> wrote:
>  > On 11-07-31 11:30 PM, Tom Zanussi wrote:
>  >> On Sun, 2011-07-31 at 19:42 -0700, Bruce Ashfield wrote:
>  >>> On 11-07-31 3:44 PM, Francis Meyvis wrote:
>  >>>> Hello,
>  >>>>
>  >>>> I probably miss something trivial.
>  >>>> I cloned the git://git.yoctoproject.org/poky.git
> <http://git.yoctoproject.org/poky.git>
>  >>>> I build on a 64 bit machine a qemux86-64
>  >>>> (. ./oe-init-build-env qemux86-64 and changing the conf/local.conf)
>  >>>> I build the core-image-sato& core-image-minimal.
>  >>>> Then I try to run with
>  >>>> runqemu qemux86-64 core-image-sato ext3
>  >>>>
>  >>>> But both sato and minimal give me this message:
>  >>>> Kernel panic - not syncing: No init found.
>  >>>>
>  >>>> As runqemu showed me the full command line I tried to add the --append
>  >>>> command line option
>  >>>> init=/sbin/init and /sbin/init.sysvinit
>  >>>> But that did not help (there's a message saying Failed to execute
>  >>>> /sbin/init. Attempting defaults...)
>  >>>> I verified by mounting these ext3 images on a loop device that there's
>  >>>> really a /sbin/init present.
>  >>>>
>  >>>> Can somebody tell what I'm doing wrong?
>  >>>
>  >>> Can you send a full bootlog, or paste it somewhere accessible ?
> It's hard
>  >>> to say what's with the information you've given.
>  >>>
>  >>> Is this the latest yocto master ?
>  >>>
>  >>> If you are seeing that message it typically means that the the
>  >>> device that is being used as the root isn't ready (fixed by
>  >>> rootwait/rootdelay) or isn't supported (i.e. NFS root without
>  >>> the right ethernet device). Changing what init is, won't change
>  >>> the result if either one of those is the case.
>  >>>
>  >>
>  >> I'm also seeing this on both sugarbay and jasperforest with the latest
>  >> master. rootwait doesn't help.
>  >>
>  >> rtc_cmos 00:07: setting system clock to 2010-01-02 05:35:34 UTC
>  >> (1262410534)
>  >> Freeing unused kernel memory: 720k freed
>  >> Failed to execute /init
>  >> Kernel panic - not syncing: No init found. Try passing init= option to
>  >> kernel.
>  >> See Linux Documentation/init.txt for guidance.
>  >> Pid: 1, comm: swapper Not tainted 3.0.0-rc7-yocto-standard+ #1
>  >> Call Trace:
>  >> [<ffffffff81541b77>] panic+0x9b/0x191
>  >> [<ffffffff81540862>] init_post+0xc0/0xc0
>  >> [<ffffffff8188bcef>] kernel_init+0x17b/0x17b
>  >> [<ffffffff8154b234>] kernel_thread_helper+0x4/0x10
>  >> [<ffffffff8188bb74>] ? start_kernel+0x377/0x377
>  >> [<ffffffff8154b230>] ? gs_change+0xb/0xb
>  >>
>  >> I thought initially it had something to do with the -live image changes,
>  >> but reverting the two -live patches didn't help.
>  >>
>  >> The problem seems to coincide with the tune file changes, but that may
>  >> be a red herring.
>  >
>  > Nope. I don't think it's a red herring:
>  >
>  > Both of these:
>  >
>  > Freeing unused kernel memory: 720k freed
>  > Failed to execute /init
>  >
>  > Indicate that the device came up and init was loaded, the kernel
>  > passed control to userspace and then things went bad. i.e. you just
>  > ran init of the wrong arch or something incompatible with the
>  > kernel support, etc.
>  >
>  > Since I'm having no trouble with old rootfs and new kernels, that's
>  > another sign. I'm assuming that old userspace's boot for you ?
>  >
>  > Bruce
>  >
>  >>
>  >> Tom
>  >>
>  >>
>  >>> Cheers,
>  >>>
>  >>> Bruce
>  >>>
>  >>>>
>  >>>> BTW is there any way to not have to run qemu with root permissions?
>  >>>> I ran the android emulator and it does not require me to be root.
>  >>>> Should I configure something on my Ubuntu machine to get qemu to
> function?
>  >>>>
>  >>>> Thanks,
>  >>>> francis
>  >>>> _______________________________________________
>  >>>> yocto mailing list
>  >>>> yocto@yoctoproject.org <mailto:yocto@yoctoproject.org>
>  >>>> https://lists.yoctoproject.org/listinfo/yocto
>  >>>
>  >>> _______________________________________________
>  >>> yocto mailing list
>  >>> yocto@yoctoproject.org <mailto:yocto@yoctoproject.org>
>  >>> https://lists.yoctoproject.org/listinfo/yocto
>  >>
>  >>
>  >
>
>
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

Kernel panic - not syncing: No init found

[Baruch Siach]

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 -

Kernel panic - not syncing: No init found

[Ellis Andrew]

Hi Baruch

Thank you for your reply.

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.

Kind regards

Andrew




________________________________
 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 -
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120917/43ba1442/attachment.html>

Kernel panic - not syncing: No init found

[Baruch Siach]

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 -

Kernel panic - not syncing: No init found

[Ellis Andrew]

Hi,

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? 


Kind regards

Andrew Ellis
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120912/a9a75241/attachment-0001.html>

Re: Kernel panic - not syncing: No init found.

[Steve Iribarne (GMail)]

On 5/10/06, hangtoo <hangtoo@163.com> wrote:
>
> I try to make a new uRamdisk for my bubinga board(linux-2.6.14,PPC405EP).
> actully I just copy the most of the files in the board,and compiled busyb=
ox with ppc tools.
> but when I use the new uRamdisk for a try,it just showed up this errors(a=
s follow),then reboot,back and forth...
> **************************************************
> RAMDISK: incomplete write (-28 !=3D 32768) 4194304
>


I'm pretty sure this tells me that your ramdisk is not big enough.
Take a look at
http://www.vanemery.com/Linux/Ramdisk/ramdisk.html

If you are using LILO like in the example listed at the link above,
you need to make sure your ramdisk_size parameter is big enough.

That's what my gues is.

-stv

Kernel panic - not syncing: No init found.

[hangtoo]

I try to make a new uRamdisk for my bubinga board(linux-2.6.14,PPC405EP).
actully I just copy the most of the files in the board,and compiled busybox with ppc tools.
but when I use the new uRamdisk for a try,it just showed up this errors(as follow),then reboot,back and forth...
**************************************************
RAMDISK: incomplete write (-28 != 32768) 4194304

EXT2-fs warning: checktime reached, running e2fsck is recommended

VFS: Mounted root (ext2 filesystem).

Freeing unused kernel memory: 116k init

attempt to access beyond end of device  //this is where the error begins.

ram0: rw=0, want=10330, limit=8192

Buffer I/O error on device ram0, logical block 5164

attempt to access beyond end of device

ram0: rw=0, want=10330, limit=8192

Buffer I/O error on device ram0, logical block 5164

attempt to access beyond end of device

ram0: rw=0, want=10330, limit=8192

Buffer I/O error on device ram0, logical block 5164

attempt to access beyond end of device

ram0: rw=0, want=10330, limit=8192

Buffer I/O error on device ram0, logical block 5164

Kernel panic - not syncing: No init found.  Try passing init= option to kernel.
//according to this note,is there something I have to do with my kernel??
 <0>Rebooting in 1 seconds..
*************************************************

Any help is appreciated.

regards
tony