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!
-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 an
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 problems
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
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
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 ;)
And
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
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
On Mon, Feb 28, 2011 at 9:54 AM, dirkydirk dirkyd...@gmx.net 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
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
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
installed
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 17:13 +, Wolodja Wentland wrote:
A quick look at the manpage reveals that you have to specify one of the
supported commands. Let's try list:
$ apt-listbugs list apt/0.8.11.5
serious bugs of apt (0.8.11.5 - 0.8.11.5) unfixed
#558784 - apt: re-adds removed keys
-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 boot
brodul wrote:
First I start linux26. But there was an error
.
.
.
0Kernel 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 are just booting
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.
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 derogatory term
bonjour,
Le lundi 07 juin 2004, Toorop a écrit...
Je dois avoir ete marabouté car :
# mount -o dev /mnt/hda1
# chroot /mnt/hda1 lilo
Et. bim :
chroot: lilo: Aucun fichier ou repertoire de ce type
Je me demande si il n'y aurait pas autre chose comme probleme, car ça
Bonjour,
[]
Je me demande si il n'y aurait pas autre chose comme probleme, car ça
ressemble aux symptomes que j'avais avant que tout crash : il ne trouvait
plus d'executables (pourtant ils sont la est ont les bons droits).
JMO Il m'est arrivé d'avoir des trucs du genre avec chroot sur
* Toorop [EMAIL PROTECTED] [2004-06-08 09:50] :
Bonjour,
[]
Je me demande si il n'y aurait pas autre chose comme probleme, car ça
ressemble aux symptomes que j'avais avant que tout crash : il ne trouvait
plus d'executables (pourtant ils sont la est ont les bons droits).
JMO Il
/usr/bin/top file not found
Et ça pour toute les commandes, plus d'autre solution que de violenter le
bete, couic je coupe l'alim.
Le boot se lance et la boum :
kernel panic : No init found. Try passing init= option to kernel
Je precise que je n'ais pas touche au kernel ni a lilo depuis le
Le Mon, 07 Jun 2004 20:50:08 +0200, Toorop a écrit :
Et ça pour toute les commandes, plus d'autre solution que de violenter le
bete, couic je coupe l'alim.
Le boot se lance et la boum :
kernel panic : No init found. Try passing init= option to kernel
À mon avis tu as installé un noyau 2.4
Bonjour,
Et ça pour toute les commandes, plus d'autre solution que de violenter le
bete, couic je coupe l'alim.
Le boot se lance et la boum :
kernel panic : No init found. Try passing init= option to kernel
n À mon avis tu as installé un noyau 2.4.qqch et le script de
n post-installation
estava inicializando o
sistema deu o seguinte erro:
kernel panic: No init found. Try passing init= option
to kernel.
Resetei a maquina, no lilo tentei passar o
parametro init=/bin/sh e o erro permaneceu.
Como tenho o Conectiva instalado em outra particao
do mesmo hd, entrei
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 the cd
too.
Any ideas on how
Salve!
Estava eu utilizando normalmente o meu debian qndo
de repente o KDE travou. Achei normal, pq o meu
hardware da uns tilt as vezes.
Rebootei a maquina, e qndo estava inicializando o
sistema deu o seguinte erro:
kernel panic: No init found. Try passing init= option
to kernel
É init mesmo.
- Mensagem Original
De: Eduardo [EMAIL PROTECTED]
Para: debian-user-portuguese@lists.debian.org
debian-user-portuguese@lists.debian.org
Assunto: Re: Kernel Panic. No init found. Try passing init= option to kernel
Data: 17/03/03 19:09
---Mauricio Bruns
Após executar um apt-get dist-upgrade na distribuição debian unstable e
reiniciar minha máquina passei a receber esta mensagem: Kernel Panic.
No init found. Try passing init= option to kernel.
Alguém pode me ajudar?
Obrigado,
Mauricio Bruns
---Mauricio Bruns wrote:
Após executar um apt-get dist-upgrade na distribuição debian unstable e
reiniciar minha máquina passei a receber esta mensagem: Kernel Panic.
No init found. Try passing init= option to kernel.
Alguém pode me ajudar?
Obrigado,
Mauricio Bruns
É init mesmo.
- Mensagem Original
De: Eduardo [EMAIL PROTECTED]
Para: debian-user-portuguese@lists.debian.org
debian-user-portuguese@lists.debian.org
Assunto: Re: Kernel Panic. No init found. Try passing init= option to kernel
Data: 17/03/03 19:09
---Mauricio Bruns
Após executar um apt-get dist-upgrade na distribuição debian unstable e
reiniciar minha máquina passei a receber esta mensagem: Kernel Panic.
No init found. Try passing init= option to kernel.
Alguém pode me ajudar?
Obrigado,
Mauricio Bruns
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 to [EMAIL
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
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're golden. you might need to
reinstall
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?
try booting up with init=/bin/sh and see if you can get yourself
a root prompt
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
) 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
Any ideas on how to save this system without having to reinstall?
try booting up with init
.
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 the cd
too.
Any ideas on how to save this system
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 able
: 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 found. Try passing init= option to kernel
Any ideas on how
way to do it?
I've got a log of most of the updates I've done.
Thanks again,
Rich B
Original post:
I can no longer boot my Sarge 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
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
image auf block XXX gefunden hatt, läd dies und bricht
dann ab:
RAMDISK: Compressed Image found at Block XXX
VFS: Mountet root (ext2 filesystem)
Kernel Panic: No Init found. Try passing bla ..
ich bin dem Tutorial wirklich fast eins zu eins gefolgt, und es will
einfach nicht, ich habs echt schon
On Mit, Jul 17, 2002 at 10:11:45 +0200, Ablassmeier, Michael wrote:
hi,
sali michael,
RAMDISK: Compressed Image found at Block XXX
VFS: Mountet root (ext2 filesystem)
Kernel Panic: No Init found. Try passing bla ..
eine ramdisk startet (soviel ich weiss) nicht den init, sondern das
auf block XXX gefunden hatt, läd dies und bricht
dann ab:
RAMDISK: Compressed Image found at Block XXX
VFS: Mountet root (ext2 filesystem)
Kernel Panic: No Init found. Try passing bla ..
Versuch es mal mit init=/bin/sh und erforsche dann dein Dateisystem. Es
gibt da diverse Dateisystem
On Wed, Jul 17, 2002 at 10:32:55AM +0200, Mathias Gygax wrote:
eine ramdisk startet (soviel ich weiss) nicht den init, sondern das
programm /initrc. das kann (wenn möglich) ein statisch gelinktes binary
sein oder auch ein shell script. evt. bringt es schon was, wenn du einen
symlink von init
Mathias Gygax schrieb:
eine ramdisk startet (soviel ich weiss) nicht den init, sondern das
programm /initrc. das kann (wenn möglich) ein statisch gelinktes
Das Ding heisst /linuxrc, ist optional, kann auch ein Skript sein und
betrifft nur den initrd-Mechanismus.
--
[EMAIL PROTECTED]
--
On Wed, Jul 17, 2002 at 11:01:54AM +0200, Rainer Ellinger wrote:
Mehr als nur das Banalste auf einer einzigen Disk unterzubringen, ist
schon wirklich die höchste Form der Bootkunst. Geht's nicht auch mit
einer CD? isolinux (Paket syslinux) ist recht bequem und man muss nicht
um jedes Byte
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 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 init found. Try passing
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 Ghigi
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:
| |
#include hallo.h
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
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
: 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=/sbin/init, and also init=/bin/sh. It
did not work. So I downloaded a rescue image
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 reason why my
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 hanged,
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 as
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. Actually
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 to
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
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 that I was able to
boot with a root on the floppy. I have checked the root
) 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 that I was able to
boot with a root on the floppy. I have
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. I
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
hola:
Asi es, el problema se me presenta en la minidistro(o algo por el
estilo), va todo bien y me larga ese error
Try passing init=option to kernel
Mas que todo me gustaria me dieran una mano a ver como solucionarlo
Desde ya gracias
Las 386 estan anciosas
Saludos
Daniel Cabello
: Mounted root (ext2 filesystem) readonly
Freeing unused kernel memory: 140k freed
kernel panic: No init found. Try passing init= option to kernel.
___
boot: rescue root=/dev/hda3 init=/sbin/init
y
boot: rescue root=/dev/hda3 init=/bin/bash
ambos me mandan errores de
PROTECTED]
Imobach González Sosa [EMAIL PROTECTED]Cc:
debian-user-spanish@lists.debian.org
Re: URGENTE. kernel panic: No init found
On Mon, 7 Jan 2002, Imobach González Sosa wrote:
El 05 de ene de 2002 (sáb), freedom :) escribió:
Buen dia a todos
Aqui esta mi problema:
Tenia
configuro bien.. :(
Inicio con is discos de rescate poner en lilo.conf
root=/dev/hda3 --- como debe ser
pero me manda el siguiente error
___
VFS: Mounted root (ext2 filesystem) readonly
Freeing unused kernel memory: 140k freed
kernel panic: No init found. Try passing init= option
: 140k freed
kernel panic: No init found. Try passing init= option to kernel.
___
boot: rescue root=/dev/hda3 init=/sbin/init
y
boot: rescue root=/dev/hda3 init=/bin/bash
ambos me mandan errores de no encontrar el init...
ya trate desde discos de rescate de potato y de woody y
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's on the HD (i created them both
! 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 them both when i installed
, 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 suggestions?
i can boot from floppy just fine, and I
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 panic is due to the scsi not being there. but i really
On Sun, 30 Sep 2001, David Felipe Arias Ochoa wrote:
Estoy reparando un sistema que tiene sectores defectuosos irrecuperables
como consecuencia de una serie de apagones. Lo que he pensado es
formatear a bajo nivel la partición para reparar todo ese disco.
Antes hago una copia de seguridad
a arrancar desde esa nueva
particion. He probado con lilo, loadlin y nada.
Siempre me da el siguiente error:
VFS: Mounted root (ext2 filesystem) readonly
Freeing unused kernel memory: 140k freed
kernel panic: No init found. Try passing init= option to kernel.
También he probado
unused kernel memory: 140k freed
kernel panic: No init found. Try passing init= option to kernel.
Me parece que el problema que tienes es simplemente que el programa
/sbin/init no lo encuentra o no es correcto.
Gracias carlos pero fué lo primero que pensé.
He comparado mediante md5sum y
Antonio Castro, martes 25 de septiembre de 2001 a la(s) 22:22:54 +0200:
Vamos a ganarnos el flame del día ;^).
cd / ; find . | cpio -pdm /hdc1
Y parece que está bien copiada
4) boot: rescue root=/dev/hdc1 init=/bin/bash
(*ERR*)
¿fstab? ¿Permisos? Es lo único que se me
On Wed, 26 Sep 2001, Hue-Bond wrote:
Vamos a ganarnos el flame del día ;^).
cd / ; find . | cpio -pdm /hdc1
Y parece que está bien copiada
4) boot: rescue root=/dev/hdc1 init=/bin/bash
(*ERR*)
¿fstab? ¿Permisos? Es lo único que se me ocurre.
'cpio -pdm' respeta
En mié, 2001-09-26 a 20:17, Antonio Castro escribio:
On Wed, 26 Sep 2001, Hue-Bond wrote:
Vamos a ganarnos el flame del día ;^).
cd / ; find . | cpio -pdm /hdc1
Y parece que está bien copiada
4) boot: rescue root=/dev/hdc1 init=/bin/bash
(*ERR*)
¿fstab?
esa nueva
particion. He probado con lilo, loadlin y nada.
Siempre me da el siguiente error:
VFS: Mounted root (ext2 filesystem) readonly
Freeing unused kernel memory: 140k freed
kernel panic: No init found. Try passing init= option to kernel.
También he probado desde el disco de
lectura del
disco. El caso es que el equipo se niega a arrancar desde esa nueva
particion. He probado con lilo, loadlin y nada.
Siempre me da el siguiente error:
VFS: Mounted root (ext2 filesystem) readonly
Freeing unused kernel memory: 140k freed
kernel panic: No init found. Try
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
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.) Boots fine, then prompts
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
[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:
[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 much
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
install and got the message:
Kernel panic: No init found. Try passing init= option to
kernel
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
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 version of
** 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 bet is to use
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
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 Kernel panic: No init found. Try passing init= option to
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 kernel installed from the boot-floppies as part of the
Bob installation boots without any problems. /etc
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 init= option
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/lilo
-rwxr-xr-x 1
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 to recover the system after reading those
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 problem have been reported by several people. However, I
still don't know how to recover the system after
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'd appreciate
100 matches
Mail list logo
