of libc-bin (2.11.2-13 -> 2.11.2-12)
#615839 - Kernel panic - not syncing: No init found (Fixed: eglibc/2.11.2-13)
Merged with: 615806
Summary:
libc-bin(1 bug)
Looks good. Hopefully this tool does not slow down a dist-upgrade too
much if it looks up bugs for almost 2.3k packages. I'm
On Mon, Feb 28, 2011 at 16:40 +0100, dirkydirk wrote:
> On Mon, 2011-02-28 at 15:17 +, Wolodja Wentland wrote:
> > On Mon, Feb 28, 2011 at 15:37 +0100, dirkydirk wrote:
> > Which version of libc-bin do you have installed (dpkg -l libc-bin). If you
> > have 2.11.2-12 you might have run into
[..
On Mon, 2011-02-28 at 15:17 +, Wolodja Wentland wrote:
> On Mon, Feb 28, 2011 at 15:37 +0100, dirkydirk wrote:
>
> > I conclude then, there's an issue with the update script. (I'm running
> > Debian sid, btw.)
>
> An important piece of information. Which version of libc-bin do you have
> inst
Wolodja Wentland wrote:
On Mon, Feb 28, 2011 at 15:37 +0100, dirkydirk wrote:
I conclude then, there's an issue with the update script. (I'm running
Debian sid, btw.)
An important piece of information. Which version of libc-bin do you have
installed (dpkg -l libc-bin). If you have 2.11.2-12 y
On Mon, Feb 28, 2011 at 9:54 AM, dirkydirk wrote:
>
> I suspect the script that generates the ramdisc to be faulty. See my
> other reply here:
> http://lists.debian.org/debian-user/2011/02/msg02902.html
Have you tried running update-initramfs one kernel at a time rather
than "update-initramfs -k
Hmm, interestingly only swap and tmp were listed with an UUID. But alas,
it did not work out to list the other partitions with their UUID.
Should I mention that software raid and lvm is used?
KR, m
On Mon, 2011-02-28 at 16:57 +0200, Andrei Popescu wrote:
> On Lu, 28 feb 11, 15:54:38, dirkydirk w
On Mon, Feb 28, 2011 at 15:37 +0100, dirkydirk wrote:
> I conclude then, there's an issue with the update script. (I'm running
> Debian sid, btw.)
An important piece of information. Which version of libc-bin do you have
installed (dpkg -l libc-bin). If you have 2.11.2-12 you might have run into
[
On Lu, 28 feb 11, 15:54:38, dirkydirk wrote:
> It's grub2 and UUIDs are used; and grub finds the kernel and the ramdisc
> file. (If it would not find them, grub would show a different msg.
> Already encountered and solved that a while ago when grub had an issue
> with wanting "/boot" in the path ;)
It's grub2 and UUIDs are used; and grub finds the kernel and the ramdisc
file. (If it would not find them, grub would show a different msg.
Already encountered and solved that a while ago when grub had an issue
with wanting "/boot" in the path ;)
I suspect the script that generates the ramdisc to
Hi,
yes, there's init in it. But the directory structure of the ramdisc
looks quite different from a 2.6.31 ramdisc on another computer.
Unfortunately I did run update-initramfs -k all, and now even the 2.6.26
kernel refuses to boot. Same error.
>From the recent grml live-distro I copied kernel
On Lu, 28 feb 11, 13:09:20, dirkyd...@gmx.net wrote:
> Hi all,
>
> after updating my Debian box, it ceases to boot with above error. I
> use kernel 2.6.32. Booting older 2.6.28 seems to run the init process
> well (but has other issues).
>
> Somebody has an idea what went wrong?
I suspect prob
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 28/02/11 12:09, dirkyd...@gmx.net wrote:
> Hi all,
hi
> after updating my Debian box, it ceases to boot with above error. I use
> kernel 2.6.32. Booting older 2.6.28 seems to run the init process well (but
> has other issues).
>
> Somebody has
Hi all,
after updating my Debian box, it ceases to boot with above error. I use kernel
2.6.32. Booting older 2.6.28 seems to run the init process well (but has other
issues).
Somebody has an idea what went wrong?
KR, m
--
NEU: FreePhone - kostenlos mobil telefonieren und surfen!
Hello!
Im trying to make a root floppy and got the messages:
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory x kb
kernel panic: No init found
But there is an init in /sbin.
Thanks for advance
Robert
I have the same problem, I'm using Reiserfs (3.6) on a Gentoo 2005.1
installation.
I can mount the root-partition and start bash manually, but not with
chroot. Also I cannot start the system, because init cannott be started
by the kernel.
/Rasmus
Bill Marcum wrote:
On Fri, Sep 09, 2005 at 10:13:06PM +0100, wackojacko wrote:
UPDATE
I downloaded the Ubuntu Live CD and tried to chroot into the partition
as follows
mount -t ext3 /dev/sda2 /mnt
chroot /mnt
and get the error
chroot: cannot execute '/bin/bash':
On Fri, Sep 09, 2005 at 10:13:06PM +0100, wackojacko wrote:
>
> UPDATE
>
> I downloaded the Ubuntu Live CD and tried to chroot into the partition
> as follows
>
> mount -t ext3 /dev/sda2 /mnt
> chroot /mnt
>
> and get the error
>
> chroot: cannot execute '/bin/bash': file no
Wackojacko wrote:
Hi all
I am receiving the above error on my amd64 sid system. All was well
until I tried to recompile my kernel to add some extra ide modules into
the kernel. I forgot the append-to-version flag and created a new
kernel-image with the same name as a previous one. I realis
Hi all
I am receiving the above error on my amd64 sid system. All was well
until I tried to recompile my kernel to add some extra ide modules into
the kernel. I forgot the append-to-version flag and created a new
kernel-image with the same name as a previous one. I realised the
mistake but
brodul wrote:
First I start linux26. But there was an error
.
.
.
<0>Kernel panic Attempted to kill init!
Then I just press Enter. And there is an error to:
.
.
.
Freeing unused kernel memory: 96 k freed
Kernel panic: No init found. Try passing init= option to kernel.
So you ar
-Original Message-
From: Michael Spang [mailto:[EMAIL PROTECTED]
Sent: 30. avgust 2005 23:39
To: debian-user@lists.debian.org
Subject: Re: Install problem: Kernel panic: No init found. Try passing init=
option to kernel.
brodul wrote:
>I am installing DEBIAN, I press Enter to b
brodul wrote:
I am installing DEBIAN, I press Enter to boot, but then:
.
.
.
Freeing unused kernel memory: 96 k freed
Kernel panic: No init found. Try passing init= option to kernel.
I am a n00b please explain clear.
Sorry for my EN.
First off, "n00b" tends to a derog
I am installing DEBIAN, I press Enter to boot, but then:
.
.
.
Freeing unused kernel memory: 96 k freed
Kernel panic: No init found. Try passing init= option to
kernel.
I am a n00b please explain clear.
Sorry for my EN.
I am installing DEBIAN, I press Enter to boot, but then:
.
.
.
Freeing unused kernel memory: 96 k freed
Kernel panic: No init found. Try passing init= option to
kernel.
I am a n00b please explain clear.
Sorry for my EN.
checktime reached, running e2fsck is recommended
> VFS: Mounted root (ext2 filesystem).
> VFS: Mounted root (ext2 filesystem) readonly.
> change_root: old root has d_count=1
> Trying to unmount old root ... okay
> Freeing unused kernel memory: 156k freed
> Kernel panic: No init
warning: checktime reached, running e2fsck is recommended
> > > > VFS: Mounted root (ext2 filesystem).
> > > > VFS: Mounted root (ext2 filesystem) readonly.
> > > > change_root: old root has d_count=1
> > > > Trying to unmount old root ... okay
> > > >
On Wed, 12 Mar 2003 13:09:50 -0500 (EST)
Reid Mumford <[EMAIL PROTECTED]> wrote:
> I have a problem that has brought my laptop down.
>
> Any ideas on how to save this system without having to reinstall?
Your filesystem was corrupted and you've lost some files (or pieces of files).
You may be a
root (ext2 filesystem) readonly.
> change_root: old root has d_count=1
> Trying to unmount old root ... okay
> Freeing unused kernel memory: 156k freed
> Kernel panic: No init found. Try passing init= option to kernel
>
> this is basically the same thing that i get when i boot without
stem).
> > > VFS: Mounted root (ext2 filesystem) readonly.
> > > change_root: old root has d_count=1
> > > Trying to unmount old root ... okay
> > > Freeing unused kernel memory: 156k freed
> > > Kernel panic: No init found. Try passing init= option to ke
ilesystem).
> > > VFS: Mounted root (ext2 filesystem) readonly.
> > > change_root: old root has d_count=1
> > > Trying to unmount old root ... okay
> > > Freeing unused kernel memory: 156k freed
> > > Kernel panic: No init found. Try passing init= option t
Warwick Brown wrote:
tbh it looks like you have lost some vital system binaries, your best bet is
to boot off the rescue disk, back up yer data files and reinstall, but make
sure u bad block check the disks when u reformat them, coz lappies do get
bounced around a fair bit, so disk damage shoul
; change_root: old root has d_count=1
> > Trying to unmount old root ... okay
> > Freeing unused kernel memory: 156k freed
> > Kernel panic: No init found. Try passing init= option to kernel
> >
> > Any ideas on how to save this system without having to reinstall?
&g
d root ... okay
> Freeing unused kernel memory: 156k freed
> Kernel panic: No init found. Try passing init= option to kernel
>
> Any ideas on how to save this system without having to reinstall?
try booting up with init=/bin/sh and see if you can get yourself
a root prompt. if so, you&#x
tbh it looks like you have lost some vital system binaries, your best bet is
to boot off the rescue disk, back up yer data files and reinstall, but make
sure u bad block check the disks when u reformat them, coz lappies do get
bounced around a fair bit, so disk damage shouldnt be ruled out
rega
ay
Freeing unused kernel memory: 156k freed
Kernel panic: No init found. Try passing init= option to kernel
this is basically the same thing that i get when i boot without the cd
too.
Any ideas on how to save this system without having to reinstall?
thanks
reid mumford
--
To UNSUBSCRIBE, email
eeing unused kernel momory 208k freed
>> kernel panic: No init found. Try passing init= option to kernel.
>>
>> I use GRUB and have tried adding the kernel parameters
>>'init=/sbin/init'
>> and 'init=/bin/bash'. No dice.
>>Booting older
reeing unused kernel momory 208k freed
>> kernel panic: No init found. Try passing init= option to kernel.
>>
>> I use GRUB and have tried adding the kernel parameters
>>'init=/sbin/init'
>> and 'init=/bin/bash'. No dice.
>>Booting older kerne
Rich <[EMAIL PROTECTED]> writes:
> I can no longer boot my Woody laptop. Here are the last few lines of
> boot up:
>
> VFS: Mounted root (ext3 filesystem) readonly.
> Freeing unused kernel momory 208k freed
> kernel panic: No init found. Try passing init=
All,
I can no longer boot my Woody laptop. Here are the last few lines of
boot up:
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel momory 208k freed
kernel panic: No init found. Try passing init= option to kernel.
I use GRUB and have tried adding the kernel parameters
On Mon, Apr 22, 2002 at 11:54:18PM -0500, dman wrote:
> On Mon, Apr 22, 2002 at 11:29:25PM -0400, Jerome Acks Jr wrote:
> | On Mon, Apr 22, 2002 at 04:24:54PM -0400, Alessandro Ghigi wrote:
> | > Hi!
> | >
> | > Thank you for your answer. I have tried passing to the boot prompt
> | >
> | > linux
On Wed, Apr 24, 2002 at 01:59:00AM -0500, Gary Turner wrote:
...
| In re using links, would you also use full file name for the kernel
| image rather than an alias? And, is a magical transformation very
| likely? If so, what would do it?
Yes, I use the full file name for both kernel and initrd
#include
Alessandro Ghigi wrote on Mon Apr 22, 2002 um 03:08:40AM:
> partition on the hard disk: /sbin/init is there and is ok (I have
> replaced it with a copy from another system), and also inittab looks
> ok. But the original root partition still does not work and gives the
> same message.
On Tue, 23 Apr 2002 23:47:11 -0500, dman wrote:
>On Tue, Apr 23, 2002 at 03:22:56AM -0500, Gary Turner wrote:
>| On Tue, 23 Apr 2002 00:16:01 -0400, Andy Saxena wrote:
>| >On Mon, Apr 22, 2002 at 08:08:41PM -0500, dman wrote:
>| >> On Mon, Apr 22, 2002 at 05:21:23PM +0800, Crispin Wellington wrote
On Tue, Apr 23, 2002 at 03:22:56AM -0500, Gary Turner wrote:
| On Tue, 23 Apr 2002 00:16:01 -0400, Andy Saxena wrote:
| >On Mon, Apr 22, 2002 at 08:08:41PM -0500, dman wrote:
| >> On Mon, Apr 22, 2002 at 05:21:23PM +0800, Crispin Wellington wrote:
| >> | On Mon, 2002-04-22 at 15:08, Alessandro Ghig
On Tue, Apr 23, 2002 at 12:16:01AM -0400, Andy Saxena wrote:
| On Mon, Apr 22, 2002 at 08:08:41PM -0500, dman wrote:
| > On Mon, Apr 22, 2002 at 05:21:23PM +0800, Crispin Wellington wrote:
| > | On Mon, 2002-04-22 at 15:08, Alessandro Ghigi wrote:
| >
| > | > Kernel panic: no
On Tue, 23 Apr 2002 00:16:01 -0400, Andy Saxena wrote:
>On Mon, Apr 22, 2002 at 08:08:41PM -0500, dman wrote:
>> On Mon, Apr 22, 2002 at 05:21:23PM +0800, Crispin Wellington wrote:
>> | On Mon, 2002-04-22 at 15:08, Alessandro Ghigi wrote:
>>
snip
>> Something or other like that. After upgrading
On Mon, Apr 22, 2002 at 11:33:18PM -0400, Andy Saxena wrote:
| On Mon, Apr 22, 2002 at 04:24:54PM -0400, Alessandro Ghigi wrote:
| > Thank you for your answer. I have tried passing to the boot prompt
| >
| > linux root=/dev/hda9 init=/sbin/init,
| >
| > but the result is the same as before. Actu
On Mon, Apr 22, 2002 at 11:29:25PM -0400, Jerome Acks Jr wrote:
| On Mon, Apr 22, 2002 at 04:24:54PM -0400, Alessandro Ghigi wrote:
| > Hi!
| >
| > Thank you for your answer. I have tried passing to the boot prompt
| >
| > linux root=/dev/hda9 init=/sbin/init,
| >
| > but the result is the same
On Mon, Apr 22, 2002 at 08:08:41PM -0500, dman wrote:
> On Mon, Apr 22, 2002 at 05:21:23PM +0800, Crispin Wellington wrote:
> | On Mon, 2002-04-22 at 15:08, Alessandro Ghigi wrote:
>
> | > Kernel panic: no init found. Try passing init= option to kernel.
>
> Hey, cool (sorta
On Tue, 2002-04-23 at 04:24, Alessandro Ghigi wrote:
> Hi!
>
> Thank you for your answer. I have tried passing to the boot prompt
>
> linux root=/dev/hda9 init=/sbin/init,
>
> but the result is the same as before. Actually /sbin is on the root
> partition.
>
> I guess the reason why my system h
On Mon, Apr 22, 2002 at 04:24:54PM -0400, Alessandro Ghigi wrote:
>
>
> Hi!
>
> Thank you for your answer. I have tried passing to the boot prompt
>
> linux root=/dev/hda9 init=/sbin/init,
>
> but the result is the same as before. Actually /sbin is on the root
> partition.
>
> I guess the rea
> > > My laptop hanged, and I shut it down. Afterwards it cannot boot.
> > > After loading linux, it stops saying roughly
> > >
> > >
> > > Partition check
> > > hda: hda1
> > > apm: Bios version ...
> > > VFS: Mounted root (
On Mon, Apr 22, 2002 at 05:21:23PM +0800, Crispin Wellington wrote:
| On Mon, 2002-04-22 at 15:08, Alessandro Ghigi wrote:
| > Kernel panic: no init found. Try passing init= option to kernel.
Hey, cool (sorta) -- someone else has this problem too. I've got a
kernel that does this too.
hda: hda1
> > apm: Bios version ...
> > VFS: Mounted root (ext2 filesyustem) readonly.
> > Freeing unused memory ...
> >
> > Kernel panic: no init found. Try passing init= option to kernel.
> >
> >
> > I have tried passing the option init=/sbi
ted root (ext2 filesyustem) readonly.
> Freeing unused memory ...
>
> Kernel panic: no init found. Try passing init= option to kernel.
>
>
> I have tried passing the option init=/sbin/init, and also init=/bin/sh. It
> did not work. So I downloaded a rescue image, and with tha
Hi.
My laptop hanged, and I shut it down. Afterwards it cannot boot.
After loading linux, it stops saying roughly
Partition check
hda: hda1
apm: Bios version ...
VFS: Mounted root (ext2 filesyustem) readonly.
Freeing unused memory ...
Kernel panic: no init found. Try passing init
ing of the root floppy it hangs:
Kernel panic: No init found. Try passing init= option to kernel
I was told to put init into one of the disks using rdev. But how?
___
Medovarszky Zoltan
began...only to end in failure yet again! kernel
panic: no init found.
I wonder if the panic is due to the scsi not being there. but i really
don't have any clue as to what it could be. any suggestions?
i can boot from floppy just fine, and I believe it's the same exact kernel
that&#x
; I was having a problem with LILO hanging at "LI", and i deemed it a problem
> with my SCSI drive. I unplugged the SCSI drive, rebooted, and the MBR was
> found and the boot process began...only to end in failure yet again! kernel
> panic: no init found.
>
> I wonder if the
. I unplugged the SCSI drive,
> rebooted, and the MBR was found and the boot process began...only to
> end in failure yet again! kernel panic: no init found.
>
> I wonder if the panic is due to the scsi not being there. but i
> really don't have any clue as to what it could be. any s
ilure yet again! kernel
panic: no init found.
I wonder if the panic is due to the scsi not being there. but i really
don't have any clue as to what it could be. any suggestions?
i can boot from floppy just fine, and I believe it's the same exact kernel
that's on the HD (i created th
Hey there!
whenever i run lilo and install a newly compiled kernel
(2.2.17 or 2.4.2) to the harddrive.
For both kernels i get this error message:
Warning: unable to open an initial console
Kernel panic: No init found. Try passing init= parameter ..
what is the problem and what is the
Chris Majewski wrote:
> [milos]14:39:41[bin]$ ldd busybox
> libc.so.6 => /lib/libc.so.6 (0x4001b000)
> /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x4000)
>
> Aha! Thanks! (I assumed this thing would link statically by default --
> still can't see why it doesn't..)
It's often
[milos]14:39:41[bin]$ ldd busybox
libc.so.6 => /lib/libc.so.6 (0x4001b000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x4000)
Aha! Thanks! (I assumed this thing would link statically by default --
still can't see why it doesn't..)
-chris
On Fri, 2 Feb 2001, Joey Hess wrote:
Chris Majewski wrote:
> 1) rdev the kernel on the floppy to /dev/fd0, mkfs.ext2 on a second floppy,
> install Busybox on this floppy (Busybox is a really tiny
> implementation of various unix essentials, like /bin/sh and
> /sbin/init.) Boots fine, then prompts for root dis
ot (ext2) filesystem read-only
Kernel panic: no init found":
1) rdev the kernel on the floppy to /dev/fd0, mkfs.ext2 on a second floppy,
install Busybox on this floppy (Busybox is a really tiny
implementation of various unix essentials, like /bin/sh and
/sbin/init.)
** On Apr 02, Bob Nielsen scribbled:
> I just compiled a new 2.2.14 kernel after doing a new potato install and got
> the message:
>
> Kernel panic: No init found. Try passing init= option to kernel.
You compiled the kernel with wrong root partition, it happens sometimes. The
best b
On Sun, Apr 02, 2000 at 09:30:07PM -0400, Mike Werner wrote:
> On Sun, Apr 02, 2000 at 09:15:34PM -0500, eric k. wolven wrote:
> > I have had the same problem as Bob N. and ext2 is IN the kernel, not
> > a module and I have a Pentium III. Is there some bug either in kpkg
> > or latest kernel vers
On Sun, Apr 02, 2000 at 09:15:34PM -0500, eric k. wolven wrote:
> I have had the same problem as Bob N. and ext2 is IN the kernel, not
> a module and I have a Pentium III. Is there some bug either in kpkg
> or latest kernel version of 2.2.14?
For what it's worth, I'm running 2.2.14 on two of my m
TED]> writes:
Paul> One thing to check: Make sure that you have ext2 support
Paul> compiled in the kernel, and not as a module.
Paul> Paul
Paul> On 02-Apr-2000 Bob Nielsen wrote:
>> I just compiled a new 2.2.14 kernel after doing a new potato
>>
One thing to check: Make sure that you have ext2 support compiled in the
kernel, and not as a module.
Paul
On 02-Apr-2000 Bob Nielsen wrote:
> I just compiled a new 2.2.14 kernel after doing a new potato install and got
> the message:
>
> Kernel panic: No init found. Try passing i
ompiled a new 2.2.14 kernel after doing a new potato
> Bob> install and got the message:
>
> Bob> Kernel panic: No init found. Try passing init= option to
> Bob> kernel.
>
> Bob> Does anyone know what is causing this? The 2.2.14-compact
> Bob&
>>>>> "Bob" == Bob Nielsen <[EMAIL PROTECTED]> writes:
Bob> --mP3DRpeJDSE+ciuQ Content-Type: text/plain; charset=us-ascii
Bob> I just compiled a new 2.2.14 kernel after doing a new potato
Bob> install and got the message:
Bob> Ker
I just compiled a new 2.2.14 kernel after doing a new potato install and got
the message:
Kernel panic: No init found. Try passing init= option to kernel.
Does anyone know what is causing this? The 2.2.14-compact kernel
installed from the boot-floppies as part of the installation boots
Jianming YOU wrote:
>
> Hi, Paul,
>
> Thank you very much.
>
> I followed your suggestion. Here is what I did and what I got:
>
> Boot from a floppy, with kernel 2.0.35
> login as root
>
> > mount /dev/hda2 /mnt
> > cd mnt
> > rm vmlinuz
> > ln -s boot/vmlinuz-2.0.34 vmlinuz
> > ls -l sbin/lil
- James
On Tue, 16 Mar 1999, Paul Miller wrote:
> Jianming YOU wrote:
> >
> > Hi, Experts,
> >
> > I just upgraded my box from 2.0.34 to 2.2.1 and I got
> > "kernel panic, no init found..." when I tried to boot with the new
> > kernel. The proble
Jianming YOU wrote:
>
> Hi, Experts,
>
> I just upgraded my box from 2.0.34 to 2.2.1 and I got
> "kernel panic, no init found..." when I tried to boot with the new
> kernel. The problem have been reported by several people. However, I
> still don't know how
Hi, Experts,
I just upgraded my box from 2.0.34 to 2.2.1 and I got
"kernel panic, no init found..." when I tried to boot with the new
kernel. The problem have been reported by several people. However, I
still don't know how to recover the system after reading those replies,
:(.
I&
78 matches
Mail list logo
