Re: Kernel panic VFS mount root= status 0x00
Eu uso o LILO, mas estou seriamente pensando em instalar o GRUB, pois estou tendo alguns problemas como o Linux Loader. A questão do make-kpkg eu não o uso, uso o make convencional, vou baixa-lo e ver sua funcionalidade. Obrigado galera inteligente ps: inteligente = Usa LINUX On Tue, 22 Feb 2005 00:07:22 -0300, Fred Ulisses Maranhao [EMAIL PROTECTED] wrote: On Mon, 21 Feb 2005 23:51:46 -0300 joel [EMAIL PROTECTED] wrote: Alcione Ferreira escreveu: revisei toh a estrutura do config do kernel, recompilei ele mas continua dando o mesmo erro, começa assim: hda: bad acess: block=61239782, count=2 end_request: I/O error, dev hda, sector 61239782 EXT3-fs: unable to read superblock hda: bad acess: block=61239782, count=2 end_request: I/O error, dev hda, sector 61239782 EXT2-fs: unable to read superblock hda: bad acess: block=61239782, count=1 end_request: I/O error, dev hda, sector 61239782 FAT: unable to read boot sector VFS: Cannot open root device 304 or unknown-block(3,4) Please append a correct root= boot option Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(3,4) Segue em anexo meu .config do kernel 2.6.10, o qual esta com esse problema. Não veio anexo. Pode mandar anexo nesta lista? Já experimentou a opção --initrd do make-kpkg? Dê uma lida no man do make-kpkg. Pode ser que resolva. Você usa lilo ou grub? Paro por aqui, Fred -- Alcione Ferreira Sombra® 101080
Re: Kernel panic VFS mount root= status 0x00
Parece que vc está compilando seu kernel sem o initrd Dá uma olhada neste artigo acho que vai te ajudar! http://www.vivaolinux.com.br/artigos/verArtigo.php?codigo=2039pagina=5 Já tentei várias coisas para compilar o kernel, mas sempre termina com essa mensagem VFS: Cannot open root device hda8 or unknown-block(0,0) Please append a correct root= boot option Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) Já compilei com o initrd, como mostrado no artigo, sem o initrd (e depois o criei) entre outras. Não existe uma forma de criar um log mais detalhado para facilitar a detecção de onde se encontra o erro? O kernel está sendo compilado com suporta ao ext3 (não como modulo) que é o formato da partição root. Alguém já teve esse problema e conseguiu resolve-lo? Pergunto isso porque já vi muitas reclamações com essa mensagem de erro e várias sugestões do pode ser o problema, mas resolver mesmo não consegui com nenhuma. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Kernel panic VFS mount root= status 0x00
Onde eu acho o mkinitrd? eu não achei não! On Tue, 22 Feb 2005 16:50:54 -0300, Helder Pereira Cristo [EMAIL PROTECTED] wrote: Alcione Ferreira wrote: Onde eu acho o mkinitrd? eu não achei não! On Tue, 22 Feb 2005 16:09:49 -0300, Helder Pereira Cristo [EMAIL PROTECTED] wrote: Parece que vc está compilando seu kernel sem o initrd Dá uma olhada neste artigo acho que vai te ajudar! http://www.vivaolinux.com.br/artigos/verArtigo.php?codigo=2039pagina=5 Já tentei várias coisas para compilar o kernel, mas sempre termina com essa mensagem VFS: Cannot open root device hda8 or unknown-block(0,0) Please append a correct root= boot option Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) Já compilei com o initrd, como mostrado no artigo, sem o initrd (e depois o criei) entre outras. Não existe uma forma de criar um log mais detalhado para facilitar a detecção de onde se encontra o erro? O kernel está sendo compilado com suporta ao ext3 (não como modulo) que é o formato da partição root. Alguém já teve esse problema e conseguiu resolve-lo? Pergunto isso porque já vi muitas reclamações com essa mensagem de erro e várias sugestões do pode ser o problema, mas resolver mesmo não consegui com nenhuma. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] não sei ao certo mas deve estar no kerneltools, mande a pergunta para a lista que alguém te informa com mais certeza. -- Alcione Ferreira Sombra® 101080
Re: Kernel panic VFS mount root= status 0x00
http://packages.debian.org/cgi-bin/search_contents.pl?word=mkinitrdsearchmode=searchfilescase=insensitiveversion=stablearch=i386 On Tue, 22 Feb 2005 16:51:36 -0300, Alcione Ferreira [EMAIL PROTECTED] wrote: Onde eu acho o mkinitrd? eu não achei não! On Tue, 22 Feb 2005 16:50:54 -0300, Helder Pereira Cristo [EMAIL PROTECTED] wrote: Alcione Ferreira wrote: Onde eu acho o mkinitrd? eu não achei não! On Tue, 22 Feb 2005 16:09:49 -0300, Helder Pereira Cristo [EMAIL PROTECTED] wrote: Parece que vc está compilando seu kernel sem o initrd Dá uma olhada neste artigo acho que vai te ajudar! http://www.vivaolinux.com.br/artigos/verArtigo.php?codigo=2039pagina=5 Já tentei várias coisas para compilar o kernel, mas sempre termina com essa mensagem VFS: Cannot open root device hda8 or unknown-block(0,0) Please append a correct root= boot option Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) Já compilei com o initrd, como mostrado no artigo, sem o initrd (e depois o criei) entre outras. Não existe uma forma de criar um log mais detalhado para facilitar a detecção de onde se encontra o erro? O kernel está sendo compilado com suporta ao ext3 (não como modulo) que é o formato da partição root. Alguém já teve esse problema e conseguiu resolve-lo? Pergunto isso porque já vi muitas reclamações com essa mensagem de erro e várias sugestões do pode ser o problema, mas resolver mesmo não consegui com nenhuma. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] não sei ao certo mas deve estar no kerneltools, mande a pergunta para a lista que alguém te informa com mais certeza. -- Alcione Ferreira Sombra® 101080 -- Rodrigo M. Araujo [EMAIL PROTECTED]
Re: Kernel panic VFS mount root= status 0x00
Helder Pereira Cristo wrote: Parece que vc está compilando seu kernel sem o initrd Dá uma olhada neste artigo acho que vai te ajudar! http://www.vivaolinux.com.br/artigos/verArtigo.php?codigo=2039pagina=5 Já tentei várias coisas para compilar o kernel, mas sempre termina com essa mensagem VFS: Cannot open root device hda8 or unknown-block(0,0) Please append a correct root= boot option Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) Já compilei com o initrd, como mostrado no artigo, sem o initrd (e depois o criei) entre outras. Não existe uma forma de criar um log mais detalhado para facilitar a detecção de onde se encontra o erro? O kernel está sendo compilado com suporta ao ext3 (não como modulo) que é o formato da partição root. Alguém já teve esse problema e conseguiu resolve-lo? Pergunto isso porque já vi muitas reclamações com essa mensagem de erro e várias sugestões do pode ser o problema, mas resolver mesmo não consegui com nenhuma. Esse erro pode ser tanto do kernel (falta modulo, initrd, etc) como pode ser do seu boot loader... cansei de ver gente usar o partition magic, criar ou remover uma partição, e ai muita coisa se perde (fstab, bootloader, etc). verifique de novo se todos esses parametros estão corretos. Um tut. que eu achei legal pra compilar o kernel: http://lists.debian.org/debian-user-portuguese/2005/01/msg00972.html -- Marcos -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Kernel panic VFS mount root= status 0x00
Pela mensagem parece ser problema de HD. Em Seg, 2005-02-21 s 10:41, Alcione Ferreira escreveu: revisei toh a estrutura do config do kernel, recompilei ele mas continua dando o mesmo erro, comea assim: hda: bad acess: block=61239782, count=2 end_request: I/O error, dev hda, sector 61239782 EXT3-fs: unable to read superblock hda: bad acess: block=61239782, count=2 end_request: I/O error, dev hda, sector 61239782 EXT2-fs: unable to read superblock hda: bad acess: block=61239782, count=1 end_request: I/O error, dev hda, sector 61239782 FAT: unable to read boot sector VFS: Cannot open root device 304 or unknown-block(3,4) Please append a correct root= boot option Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(3,4) Segue em anexo meu .config do kernel 2.6.10, o qual esta com esse problema. On Sun, 20 Feb 2005 19:16:00 -0300, Alcione Ferreira [EMAIL PROTECTED] wrote: Valeus galera, amanh vou verificar tudo isso On Sun, 20 Feb 2005 15:29:15 -0300, Marcel Maximo [EMAIL PROTECTED] wrote: Alcione, Aconteceu esse problema comigo, eu tinha marcado o suporte a HD IDE como mdulo ao invs de ser parte do kernel. at mais, Marcel Alcione Ferreira escreveu: recompilei meu kernel na verso 2.6.10, e quando fui testar a inicializao do novo kernel, tive essa mensagem de erro, mas quando recompilei a verso original de meu debian (kernel 2.2.20) no ocorreu esse erro. Algum j passou por isso? Sabe o que devo fazer? Valeus desde j! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Alcione Ferreira Sombra 101080
Re: Kernel panic VFS mount root= status 0x00
tambem acho, mas como pode funcionar com a versão 2.2.20 e nao com a versão 2.6.10? On Mon, 21 Feb 2005 11:28:06 -0300, Marcos [EMAIL PROTECTED] wrote: Pela mensagem parece ser problema de HD. Em Seg, 2005-02-21 às 10:41, Alcione Ferreira escreveu: revisei toh a estrutura do config do kernel, recompilei ele mas continua dando o mesmo erro, começa assim: hda: bad acess: block=61239782, count=2 end_request: I/O error, dev hda, sector 61239782 EXT3-fs: unable to read superblock hda: bad acess: block=61239782, count=2 end_request: I/O error, dev hda, sector 61239782 EXT2-fs: unable to read superblock hda: bad acess: block=61239782, count=1 end_request: I/O error, dev hda, sector 61239782 FAT: unable to read boot sector VFS: Cannot open root device 304 or unknown-block(3,4) Please append a correct root= boot option Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(3,4) Segue em anexo meu .config do kernel 2.6.10, o qual esta com esse problema. On Sun, 20 Feb 2005 19:16:00 -0300, Alcione Ferreira [EMAIL PROTECTED] wrote: Valeus galera, amanhã vou verificar tudo issoOn Sun, 20 Feb 2005 15:29:15 -0300, Marcel Maximo [EMAIL PROTECTED] wrote: Alcione, Aconteceu esse problema comigo, eu tinha marcado o suporte a HD IDE como módulo ao invés de ser parte do kernel. até mais, Marcel Alcione Ferreira escreveu:recompilei meu kernel na versão 2.6.10, e quando fui testar ainicialização do novo kernel, tive essa mensagem de erro, mas quandorecompilei a versão original de meu debian (kernel 2.2.20) não ocorreuesse erro.Alguém já passou por isso? Sabe o que devo fazer? Valeus desde já! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Alcione Ferreira Sombra® 101080 -- Alcione Ferreira Sombra® 101080
Re: Kernel panic VFS mount root= status 0x00
Realmente estranho, a no ser que a area em que foi gravado novo kernel esteja danificada. Poderia como teste compilar o 2.2.20 mesmo e instalar pra ver se ocorre este mesmo erro. Em Seg, 2005-02-21 s 11:44, Alcione Ferreira escreveu: tambem acho, mas como pode funcionar com a verso 2.2.20 e nao com a verso 2.6.10? On Mon, 21 Feb 2005 11:28:06 -0300, Marcos [EMAIL PROTECTED] wrote: Pela mensagem parece ser problema de HD. Em Seg, 2005-02-21 s 10:41, Alcione Ferreira escreveu: revisei toh a estrutura do config do kernel, recompilei ele mas continua dando o mesmo erro, comea assim: hda: bad acess: block=61239782, count=2 end_request: I/O error, dev hda, sector 61239782 EXT3-fs: unable to read superblock hda: bad acess: block=61239782, count=2 end_request: I/O error, dev hda, sector 61239782 EXT2-fs: unable to read superblock hda: bad acess: block=61239782, count=1 end_request: I/O error, dev hda, sector 61239782 FAT: unable to read boot sector VFS: Cannot open root device 304 or unknown-block(3,4) Please append a correct root= boot option Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(3,4) Segue em anexo meu .config do kernel 2.6.10, o qual esta com esse problema. On Sun, 20 Feb 2005 19:16:00 -0300, Alcione Ferreira [EMAIL PROTECTED] wrote: Valeus galera, amanh vou verificar tudo issoOn Sun, 20 Feb 2005 15:29:15 -0300, Marcel Maximo [EMAIL PROTECTED] wrote: Alcione, Aconteceu esse problema comigo, eu tinha marcado o suporte a HD IDE como mdulo ao invs de ser parte do kernel. at mais, Marcel Alcione Ferreira escreveu:recompilei meu kernel na verso 2.6.10, e quando fui testar ainicializao do novo kernel, tive essa mensagem de erro, mas quandorecompilei a verso original de meu debian (kernel 2.2.20) no ocorreuesse erro.Algum j passou por isso? Sabe o que devo fazer? Valeus desde j! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Alcione Ferreira Sombra 101080
Re: Kernel panic VFS mount root= status 0x00
Alcione Ferreira escreveu: revisei toh a estrutura do config do kernel, recompilei ele mas continua dando o mesmo erro, comea assim: hda: bad acess: block=61239782, count=2 end_request: I/O error, dev hda, sector 61239782 EXT3-fs: unable to read superblock hda: bad acess: block=61239782, count=2 end_request: I/O error, dev hda, sector 61239782 EXT2-fs: unable to read superblock hda: bad acess: block=61239782, count=1 end_request: I/O error, dev hda, sector 61239782 FAT: unable to read boot sector VFS: Cannot open root device "304" or unknown-block(3,4) Please append a correct "root=" boot option Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(3,4) Segue em anexo meu .config do kernel 2.6.10, o qual esta com esse problema. On Sun, 20 Feb 2005 19:16:00 -0300, Alcione Ferreira [EMAIL PROTECTED] wrote: Valeus galera, amanh vou verificar tudo isso On Sun, 20 Feb 2005 15:29:15 -0300, Marcel Maximo [EMAIL PROTECTED] wrote: Alcione, Aconteceu esse problema comigo, eu tinha marcado o suporte a HD IDE como mdulo ao invs de ser parte do kernel. at mais, Marcel Alcione Ferreira escreveu: recompilei meu kernel na verso 2.6.10, e quando fui testar a inicializao do novo kernel, tive essa mensagem de erro, mas quando recompilei a verso original de meu debian (kernel 2.2.20) no ocorreu esse erro. Algum j passou por isso? Sabe o que devo fazer? Valeus desde j! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- Alcione Ferreira Sombra 101080 Parece que vc est compilando seu kernel sem o initrd D uma olhada neste artigo acho que vai te ajudar! http://www.vivaolinux.com.br/artigos/verArtigo.php?codigo=2039pagina=5
Re: Kernel panic VFS mount root= status 0x00
Opa Alcione, Sera que voce nao esqueceu de adcionar nenhum modulo ao novo kernel? Voce adcionou a nova imagem corretamente ao seu boot loader? Alcione, pra comecar, de uma verificada nesses dois itens. []s On Sun, 20 Feb 2005 10:08:35 -0300, Alcione Ferreira [EMAIL PROTECTED] wrote: recompilei meu kernel na versão 2.6.10, e quando fui testar a inicialização do novo kernel, tive essa mensagem de erro, mas quando recompilei a versão original de meu debian (kernel 2.2.20) não ocorreu esse erro. Alguém já passou por isso? Sabe o que devo fazer? Valeus desde já! -- Alcione Ferreira Sombra® 101080 -- -- Leonardo Marques http://analyx.afz.biz --
Re: Kernel panic VFS mount root= status 0x00
Alcione, Aconteceu esse problema comigo, eu tinha marcado o suporte a HD IDE como módulo ao invés de ser parte do kernel. até mais, Marcel Alcione Ferreira escreveu: recompilei meu kernel na versão 2.6.10, e quando fui testar a inicialização do novo kernel, tive essa mensagem de erro, mas quando recompilei a versão original de meu debian (kernel 2.2.20) não ocorreu esse erro. Alguém já passou por isso? Sabe o que devo fazer? Valeus desde já! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: kernel panic - VFS: Cannot open root device
Hallo Andreas (und alle anderen), Ihre Nachricht vom 18.01.2005: On 18.Jan 2005 - 17:33:32, Christoph Bohm wrote: Ihre Nachricht vom 18.01.2005: [wallace:/usr/src/linux] 17:30 # grep -i ide .config |grep -i blk CONFIG_BLK_DEV_IDE=y CONFIG_BLK_DEV_IDEDISK=y CONFIG_BLK_DEV_IDEPCI=y CONFIG_BLK_DEV_IDEDMA_PCI=y CONFIG_BLK_DEV_IDEDMA=y CONFIG_IDE_GENERIC=y Da fehlt noch ob du auch den passenden Treiber für deinen IDE-Controller drin hast.. CONFIG_BLK_DEV_PIIX für Intel PIIX Chipsätze z.B. Hmm. hab ich auch fest, aber dennoch hängt er :-( Ich weiß echt nicht, woran es noch liegen könnte. Irgendwelche Tips zur vorgehensweise in einem solchen Fall? Seltsamerweise legt er in /lib/modules das Verzeichnis 2.6.10y an (mit y am Ende - wtf?) Das hat zwar bei dir nichts mit dem Booten zu tun (du hast den Kram ja fest drin), aber wie baust du deinen Kernel? Hast du das Makefile vom Kernel geändert? Von alleine jedenfalls hängt er das y nicht an bei Vanilla's Argh - mein Fehler. Das stammt aus der neuen Option CONFIG_LOCALVERSION - da hab ich beim make oldconfig einfach ein y eingegeben... Damit hat sich dieser Punkt erledigt :-) Vielen Dank Christoph
Re: kernel panic - VFS: Cannot open root device
Hallo Heiko, ich hatte das selbe Problem. Bei mir lags daran, dass cramfs nicht im Kernel einkompiliert war. Das braucht Debian merkwürdigerweise, um zu booten. Ich habs dann durch Erstellung einer InitRD gelöst. Kernel musst Du dafür mit make-kpkg kernel_image --revision=m6800ne.0 --initrd backen. Damit hats bei mir funktioniert. Gruß, Jens. Heiko Brüning wrote: Hallo! Ich habe mir unter sarge einen modularen 2.6.9 gebaut. Booten bekomme ich nun eine kernel-panic mit dem Hinweis: VFS: Cannot open root device hdc1 or unknown-block(0,0) Please append a correct root= boot option Kernel panic - not syncing: VFS: unable to mount root fs on unknown-block(0,0) Der Original-Kernel wird aber gebootet! Hier mein /boot/grub/menu-lst (mit update-grub erstellt). Kann mir jemand helfen?? Grüße Heiko default 0 timeout 5 color cyan/blue white/blue #MEIN NEUER KERNEL title Debian GNU/Linux, kernel 2.6.8-modules root (hd0,0) kernel /boot/vmlinuz-2.6.8-modules root=/dev/hdc1 ro savedefault boot title Debian GNU/Linux, kernel 2.6.8-modules (recovery mode) root (hd0,0) kernel /boot/vmlinuz-2.6.8-modules root=/dev/hdc1 ro single savedefault boot #DER ALTE KERNEL title Debian GNU/Linux, kernel 2.4.27-1-386 root (hd0,0) kernel /boot/vmlinuz-2.4.27-1-386 root=/dev/hdc1 ro initrd /boot/initrd.img-2.4.27-1-386 savedefault boot title Debian GNU/Linux, kernel 2.4.27-1-386 (recovery mode) root (hd0,0) kernel /boot/vmlinuz-2.4.27-1-386 root=/dev/hdc1 ro single initrd /boot/initrd.img-2.4.27-1-386 savedefault boot title Other operating systems: root title Microsoft Windows 2000 Professional root (hd0,1) savedefault makeactive chainloader +1
Re: kernel panic - VFS: Cannot open root device
Am 2005-01-18 09:27:15, schrieb Jens Heidbüchel: Hallo Heiko, ich hatte das selbe Problem. Bei mir lags daran, dass cramfs nicht im Kernel einkompiliert war. Das braucht Debian merkwürdigerweise, um zu booten. Naja, wenn Du unbedingt eine initrd haben willst... Debian benötigt KEINE initrd, wenn Du Module wie ext3 oder Raidcontroller einkompilierst. Gruß, Jens. Greetings Michelle -- Linux-User #280138 with the Linux Counter, http://counter.li.org/ Michelle Konzack Apt. 917 ICQ #328449886 50, rue de Soultz MSM LinuxMichi 0033/3/8845235667100 Strasbourg/France IRC #Debian (irc.icq.com) signature.pgp Description: Digital signature
Re: kernel panic - VFS: Cannot open root device
Ihre Nachricht vom 18.01.2005: Hallo, ich schließe mich mal an: Ich habe genau das gleiche Problem mit 2.6.10 (vanilla): VFS: Cannot open root device hda5 or unknown-block(0,0) Please append a correct root= boot option Kernel panic - not syncing: VFS: unable to mount root fs on unknown-block(0,0) Der Original-Kernel wird aber gebootet! Grmpf. Schon x-mal neu den Kernel kompiliert, mit oder ohne initrd, nichts scheint zu funktionieren, aber die standard kernel-images von debian, die laufen ohne Sorgen... :-) hier meine config: [wallace:/usr/src/linux] 17:29 # grep -i ext[23] .config CONFIG_EXT2_FS=y CONFIG_EXT2_FS_XATTR=y CONFIG_EXT2_FS_POSIX_ACL=y CONFIG_EXT2_FS_SECURITY=y CONFIG_EXT3_FS=y CONFIG_EXT3_FS_XATTR=y CONFIG_EXT3_FS_POSIX_ACL=y CONFIG_EXT3_FS_SECURITY=y [wallace:/usr/src/linux] 17:30 # grep -i ide .config |grep -i blk CONFIG_BLK_DEV_IDE=y # CONFIG_BLK_DEV_IDE_SATA is not set # CONFIG_BLK_DEV_HD_IDE is not set CONFIG_BLK_DEV_IDEDISK=y # CONFIG_BLK_DEV_IDECS is not set CONFIG_BLK_DEV_IDECD=y CONFIG_BLK_DEV_IDETAPE=m CONFIG_BLK_DEV_IDEFLOPPY=m CONFIG_BLK_DEV_IDESCSI=m # CONFIG_BLK_DEV_IDEPNP is not set CONFIG_BLK_DEV_IDEPCI=y CONFIG_BLK_DEV_IDEDMA_PCI=y # CONFIG_BLK_DEV_IDEDMA_FORCED is not set CONFIG_BLK_DEV_IDEDMA=y ...und dann noch: CONFIG_IDE_GENERIC=y und CONFIG_CRAMFS=y Trotzdem verreckt er jedesmal beim booten mit o.g. Meldung. Seltsamerweise legt er in /lib/modules das Verzeichnis 2.6.10y an (mit y am Ende - wtf?) Was müßte ich denn nun noch in den Kern integrieren, damit er läuft? Dank und Gruß Christoph
Re: kernel panic - VFS: Cannot open root device
On 18.Jan 2005 - 17:33:32, Christoph Bohm wrote: Ihre Nachricht vom 18.01.2005: [wallace:/usr/src/linux] 17:30 # grep -i ide .config |grep -i blk CONFIG_BLK_DEV_IDE=y CONFIG_BLK_DEV_IDEDISK=y CONFIG_BLK_DEV_IDEPCI=y CONFIG_BLK_DEV_IDEDMA_PCI=y CONFIG_BLK_DEV_IDEDMA=y CONFIG_IDE_GENERIC=y Da fehlt noch ob du auch den passenden Treiber für deinen IDE-Controller drin hast.. CONFIG_BLK_DEV_PIIX für Intel PIIX Chipsätze z.B. Trotzdem verreckt er jedesmal beim booten mit o.g. Meldung. Seltsamerweise legt er in /lib/modules das Verzeichnis 2.6.10y an (mit y am Ende - wtf?) Das hat zwar bei dir nichts mit dem Booten zu tun (du hast den Kram ja fest drin), aber wie baust du deinen Kernel? Hast du das Makefile vom Kernel geändert? Von alleine jedenfalls hängt er das y nicht an bei Vanilla's Andreas -- You will be successful in love. -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: kernel panic - VFS: Cannot open root device
On 18.Jan 2005 - 00:17:17, Heiko Brüning wrote: Hallo! Ich habe mir unter sarge einen modularen 2.6.9 gebaut. Booten bekomme ich nun eine kernel-panic mit dem Hinweis: VFS: Cannot open root device hdc1 or unknown-block(0,0) Please append a correct root= boot option Kernel panic - not syncing: VFS: unable to mount root fs on unknown-block(0,0) Modularer Kernel heisst dein IDE-Treiber ist ein Modul? Wo ist dann deine initrd? Andreas -- Today is the last day of your life so far. -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: kernel panic - VFS: Cannot open root device
Hi... Hast Du die IDE-Treiber und das Filesystem in den Kern kompiliert? Nicht als Modul... Gruß Sebastian Heiko Brüning schrieb: Hallo! Ich habe mir unter sarge einen modularen 2.6.9 gebaut. Booten bekomme ich nun eine kernel-panic mit dem Hinweis: VFS: Cannot open root device hdc1 or unknown-block(0,0) Please append a correct root= boot option Kernel panic - not syncing: VFS: unable to mount root fs on unknown-block(0,0) Der Original-Kernel wird aber gebootet! Hier mein /boot/grub/menu-lst (mit update-grub erstellt). Kann mir jemand helfen?? Grüße Heiko default 0 timeout 5 color cyan/blue white/blue #MEIN NEUER KERNEL title Debian GNU/Linux, kernel 2.6.8-modules root (hd0,0) kernel /boot/vmlinuz-2.6.8-modules root=/dev/hdc1 ro savedefault boot title Debian GNU/Linux, kernel 2.6.8-modules (recovery mode) root (hd0,0) kernel /boot/vmlinuz-2.6.8-modules root=/dev/hdc1 ro single savedefault boot #DER ALTE KERNEL title Debian GNU/Linux, kernel 2.4.27-1-386 root (hd0,0) kernel /boot/vmlinuz-2.4.27-1-386 root=/dev/hdc1 ro initrd /boot/initrd.img-2.4.27-1-386 savedefault boot title Debian GNU/Linux, kernel 2.4.27-1-386 (recovery mode) root (hd0,0) kernel /boot/vmlinuz-2.4.27-1-386 root=/dev/hdc1 ro single initrd /boot/initrd.img-2.4.27-1-386 savedefault boot title Other operating systems: root title Microsoft Windows 2000 Professional root (hd0,1) savedefault makeactive chainloader +1 -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: kernel panic - VFS: Cannot open root device
Moin, * Heiko Brüning wrote (2005-01-18 00:17): Ich habe mir unter sarge einen modularen 2.6.9 gebaut. Booten bekomme ich nun eine kernel-panic mit dem Hinweis: VFS: Cannot open root device hdc1 or unknown-block(0,0) Please append a correct root= boot option Kernel panic - not syncing: VFS: unable to mount root fs on unknown-block(0,0) Hast Du den Kernel mit Support für MS-DOS-Partition (CONFIG_MSDOS_PARTITION) gebaut? Thorsten -- When there are too many policemen, there can be no liberty; When there are too many soldiers, there can be no peace; When there are too many lawyers, there can be no justice. - Lin Yutang pgp8cYdDu1crh.pgp Description: PGP signature
Re: kernel panic - VFS: Cannot open root device
Am 2005-01-18 00:17:17, schrieb Heiko Brüning: Hallo! Ich habe mir unter sarge einen modularen 2.6.9 gebaut. Booten bekomme ich nun eine kernel-panic mit dem Hinweis: VFS: Cannot open root device hdc1 or unknown-block(0,0) Please append a correct root= boot option Kernel panic - not syncing: VFS: unable to mount root fs on unknown-block(0,0) Der Original-Kernel wird aber gebootet! Wenn Du einen kernel baust, pack die Module für ext(2|3) sowie den Chipsatz IN DEN KERNEl. Bei Dir fehlt einwandfrei ext(2|3). Greetings Michelle -- Linux-User #280138 with the Linux Counter, http://counter.li.org/ Michelle Konzack Apt. 917 ICQ #328449886 50, rue de Soultz MSM LinuxMichi 0033/3/8845235667100 Strasbourg/France IRC #Debian (irc.icq.com) signature.pgp Description: Digital signature
Re: kernel panic - VFS: Cannot open root device
Heiko Brüning schrieb: VFS: Cannot open root device hdc1 or unknown-block(0,0) Please append a correct root= boot option Kernel panic - not syncing: VFS: unable to mount root fs on unknown-block(0,0) Was sagen: lspci egrep '^CONFIG.*_(IDE|BLK_DEV)' /boot/config-2.6.8-modules Ciao Walter -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Kernel Panic: VFS : Unable to mount root fs -AJUDA!!
Bom dia! Eu também passei por este problema do arquivo initrd. Com a opção --initrd do make-kpkg é criado um arquivo initrd com o nome especificado, então tu deve mover ou copiar este arquivo para o / ou /boot e referencia-lo corretamente no arquivo de configuração do gerenciador de boot, lilo.conf ou menu.conf, depois é só reinstalar o gerenciador de boot (não o pacote, mas sim na mbr mesmo) e estará pronto. O problema meu estava realmente em ter criado o arquivo initrd mas não estar referenciando ele corretamente. Espero poder ter ajudado. Abraços. -- Flavio Menezes dos Reis Sistemas de Informacao - ULBRA - Torres - RS [EMAIL PROTECTED]
Re: Kernel Panic: VFS : Unable to mount root fs -AJUDA!!
Tupinamba pegeui o .config que vc enviou, baixei o source do 2.6.7 e tentei compilar. Desmarquei a opcao referente a 'old disk-only' em ATA/ATAPI/MFM/RLL e o boot aconteceu. Mas apos a mensagem de inicio do apache os erros INIT: 1 respawing too fast: disable for 5 minutes INIT: 2 respawing too fast: disable for 5 minutes no more processes left in this runlevel To mandando o config em anexo _ Quer mais velocidade? Só com o acesso Aditivado iG, a velocidade que você quer na hora que você precisa. Clique aqui: http://www.acessoaditivado.ig.com.br ---BeginMessage--- # # Automatically generated make config: don't edit # CONFIG_X86=y CONFIG_MMU=y CONFIG_UID16=y CONFIG_GENERIC_ISA_DMA=y # # Code maturity level options # CONFIG_EXPERIMENTAL=y CONFIG_CLEAN_COMPILE=y CONFIG_STANDALONE=y CONFIG_BROKEN_ON_SMP=y # # General setup # CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_POSIX_MQUEUE=y CONFIG_BSD_PROCESS_ACCT=y CONFIG_SYSCTL=y # CONFIG_AUDIT is not set CONFIG_LOG_BUF_SHIFT=14 CONFIG_HOTPLUG=y # CONFIG_IKCONFIG is not set # CONFIG_EMBEDDED is not set CONFIG_KALLSYMS=y CONFIG_FUTEX=y CONFIG_EPOLL=y CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_AS=y CONFIG_IOSCHED_DEADLINE=y CONFIG_IOSCHED_CFQ=y # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set # # Loadable module support # CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y CONFIG_MODULE_FORCE_UNLOAD=y CONFIG_OBSOLETE_MODPARM=y # CONFIG_MODVERSIONS is not set CONFIG_KMOD=y # # Processor type and features # CONFIG_X86_PC=y # CONFIG_X86_ELAN is not set # CONFIG_X86_VOYAGER is not set # CONFIG_X86_NUMAQ is not set # CONFIG_X86_SUMMIT is not set # CONFIG_X86_BIGSMP is not set # CONFIG_X86_VISWS is not set # CONFIG_X86_GENERICARCH is not set # CONFIG_X86_ES7000 is not set # CONFIG_M386 is not set # CONFIG_M486 is not set # CONFIG_M586 is not set # CONFIG_M586TSC is not set # CONFIG_M586MMX is not set # CONFIG_M686 is not set # CONFIG_MPENTIUMII is not set # CONFIG_MPENTIUMIII is not set # CONFIG_MPENTIUMM is not set CONFIG_MPENTIUM4=y # CONFIG_MK6 is not set # CONFIG_MK7 is not set # CONFIG_MK8 is not set # CONFIG_MCRUSOE is not set # CONFIG_MWINCHIPC6 is not set # CONFIG_MWINCHIP2 is not set # CONFIG_MWINCHIP3D is not set # CONFIG_MCYRIXIII is not set # CONFIG_MVIAC3_2 is not set CONFIG_X86_GENERIC=y # CONFIG_X86_EMU486 is not set CONFIG_X86_CMPXCHG=y CONFIG_X86_XADD=y CONFIG_X86_L1_CACHE_SHIFT=7 CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y CONFIG_X86_BSWAP=y CONFIG_X86_POPAD_OK=y CONFIG_X86_GOOD_APIC=y CONFIG_X86_INTEL_USERCOPY=y CONFIG_X86_USE_PPRO_CHECKSUM=y CONFIG_HPET_TIMER=y # CONFIG_HPET_EMULATE_RTC is not set # CONFIG_SMP is not set CONFIG_PREEMPT=y CONFIG_X86_UP_APIC=y CONFIG_X86_UP_IOAPIC=y CONFIG_X86_LOCAL_APIC=y CONFIG_X86_IO_APIC=y CONFIG_X86_TSC=y # CONFIG_X86_MCE is not set # CONFIG_TOSHIBA is not set # CONFIG_I8K is not set CONFIG_MICROCODE=m CONFIG_X86_MSR=m CONFIG_X86_CPUID=m # # Firmware Drivers # # CONFIG_EDD is not set CONFIG_NOHIGHMEM=y # CONFIG_HIGHMEM4G is not set # CONFIG_HIGHMEM64G is not set CONFIG_MATH_EMULATION=y CONFIG_MTRR=y # CONFIG_EFI is not set CONFIG_HAVE_DEC_LOCK=y # CONFIG_REGPARM is not set # # Power management options (ACPI, APM) # # CONFIG_PM is not set # # ACPI (Advanced Configuration and Power Interface) Support # CONFIG_ACPI=y CONFIG_ACPI_BOOT=y CONFIG_ACPI_INTERPRETER=y CONFIG_ACPI_AC=m CONFIG_ACPI_BATTERY=m CONFIG_ACPI_BUTTON=m CONFIG_ACPI_FAN=m CONFIG_ACPI_PROCESSOR=m CONFIG_ACPI_THERMAL=m CONFIG_ACPI_ASUS=m CONFIG_ACPI_TOSHIBA=m # CONFIG_ACPI_DEBUG is not set CONFIG_ACPI_BUS=y CONFIG_ACPI_EC=y CONFIG_ACPI_POWER=y CONFIG_ACPI_PCI=y CONFIG_ACPI_SYSTEM=y CONFIG_X86_PM_TIMER=y # # CPU Frequency scaling # # CONFIG_CPU_FREQ is not set # # Bus options (PCI, PCMCIA, EISA, MCA, ISA) # CONFIG_PCI=y # CONFIG_PCI_GOBIOS is not set # CONFIG_PCI_GOMMCONFIG is not set # CONFIG_PCI_GODIRECT is not set CONFIG_PCI_GOANY=y CONFIG_PCI_BIOS=y CONFIG_PCI_DIRECT=y CONFIG_PCI_MMCONFIG=y # CONFIG_PCI_USE_VECTOR is not set # CONFIG_PCI_LEGACY_PROC is not set CONFIG_PCI_NAMES=y # CONFIG_ISA is not set # CONFIG_MCA is not set # CONFIG_SCx200 is not set # # PCMCIA/CardBus support # # CONFIG_PCMCIA is not set # # PCI Hotplug Support # # CONFIG_HOTPLUG_PCI is not set # # Executable file formats # CONFIG_BINFMT_ELF=y # CONFIG_BINFMT_AOUT is not set CONFIG_BINFMT_MISC=y # # Device Drivers # # # Generic Driver Options # CONFIG_FW_LOADER=m # # Memory Technology Devices (MTD) # # CONFIG_MTD is not set # # Parallel port support # CONFIG_PARPORT=m CONFIG_PARPORT_PC=m CONFIG_PARPORT_PC_CML1=m CONFIG_PARPORT_SERIAL=m CONFIG_PARPORT_PC_FIFO=y # CONFIG_PARPORT_PC_SUPERIO is not set # CONFIG_PARPORT_OTHER is not set CONFIG_PARPORT_1284=y # # Plug and Play support # # # Block devices # CONFIG_BLK_DEV_FD=m CONFIG_PARIDE=m CONFIG_PARIDE_PARPORT=m # # Parallel IDE high-level drivers # CONFIG_PARIDE_PD=m CONFIG_PARIDE_PCD=m CONFIG_PARIDE_PF=m #
Re: Kernel Panic: VFS : Unable to mount root fs -AJUDA!!
Oi Arthur. Isso. Compila ext3 como módulo e ext2 built-in. Bom para criaçao do initrd, eu preciso alterar o mkinitrd.conf de cramfs pra ext2fs ? Depende. Se o fonte do kernel foi baixado da net (www.kernel.org), daí precisa usar ext2fs. Se o fonte do kernel foi instalado pelo debian (deselect install kernel-source-2.x.x) , daí não precisa trocar pois o kernel da debian já vem com um patch que faz o linux suportar cramfs. a sintaxe de comando é mkinitrd -o /DIRETORIO OUTPUT/ARQUIVO OUTPUT ? Seria sim, mas o debian também tem um comando próprio para gerar essa imagem: # make-dpkg --initrd --bzimage make_image modules_image Estive lendo um pouco sobre o initrd agora, antes de te responder esse email... reparei que eu não entendi é nada do initrd. rs... Pra mim isso funcionou com certeza... agora, o pq funcionou eu não faço a menor idéia. Dá uma lida nessas 2 man pages: mkinitrd(8) e mkinitrd(5). Abraços, Leonardo Lourenço Crespilho - Original Message - From: Arthur_Henrique_Sommerhalder_Tupinamba [EMAIL PROTECTED] To: debian-user-portuguese debian-user-portuguese@lists.debian.org Sent: Friday, September 17, 2004 7:18 PM Subject: Re: Kernel Panic: VFS : Unable to mount root fs -AJUDA!! Primeiramente Leonardo, obrigado pela força: Vamos as dúvidas... (vamos dizer, que farei isso pelo menos em funcao de testes) - Se eu compilar o ext3 como módulo, jogo o ext2 como built-in ?? ou apenas o ext3 como módulo ? - Bom para criaçao do initrd, eu preciso alterar o mkinitrd.conf de cramfs pra ext2fs ? a sintaxe de comando é mkinitrd -o /DIRETORIO OUTPUT/ARQUIVO OUTPUT ? Tentarei fazer o que nosso amigo Rubens disse, mas gostaria que mais alguem desse uma ajuda referente ao problema Aos que já presenciaram o problema... por favor, deem uma forcinha... Pois afinal, nada melhor do que um kernel 100% enxuto, rolando. Abraços a todos e mais uma vez Obrigado! Arthur Citando Leonardo Lourenço Crespilho [EMAIL PROTECTED]: Oi Arthur. Faz o seguinte. Compila o suporte a ext3 como módulo. -- Também faz as configurações que o Ruben falou: * ATA/ATAPI/MFM/RLL support (CONFIG_IDE) * Enhanced IDE/MFM/RLL disk/cdrom/tape/floppy support (CONFIG_BLK_DEV_IDE) * Include IDE/ATA-2 DISK support (CONFIG_BLK_DEV_IDEDISK) * generic/default IDE chipset support (CONFIG_IDE_GENERIC) * PCI IDE chipset support (CONFIG_BLK_DEV_IDEPCI) * Generic PCI IDE Chipset Support (CONFIG_BLK_DEV_GENERIC) -- Olha... não consegui entender direito, mas tive muitos problemas com esse kernel também. Não só com ele, mas com a família 2.4 e 2.6. Fiz diversas combinações e constatei, impiricamente, que o problema - pelo menos no meu caso - estava em compilar ext3 no kernel, e não como módulo. Daí eu compilei como módulo e funcionou normal. Dessa experiência tirei algumas conclusões, que se alguém aqui souber explicar melhor, por favor o faça, que não encontrei isso nas man pages: O initrd é uma espécie de pré-kernel, que é carregado para dar suporte à alguns dispositivos, como, por exemplo o ext3fs. Uma vez podendo acessar ext3fs, o grub pode buscar o kernel propriamente dito, que é então carregado. Nesse ponto o initrd é liberado da memória e não mais utilizado. Daí o motivo do suporte a ext3 ser compilado como módulo, para que o initrd também possa incluir suporte a ext3. Pelo menos nos meus testes, quando eu compilava ext3 no kernel, minha imagem initrd não tinha suporte a ext3, daí não explodia na memória os drivers pra acessar esse tipo de partição. E, como no /etc/fstab a partição é indicada como ext3fs, o grub não enxerga corretamente e não consegue carregar o kernel sem que o initrd tenha carregado o suporte a ext3 anteriormente. Cara... imagino que eu tenha falado muita besteira pois tirei essas conclusões empiricamente após 1 semana de compilação em 2 computadores. E não encontrei documentação descente falando sobre isso, infelizmente. Por favor, se alguém manjar bastante disso, explique pra gente ou então indique alguma documentação boa... please. Abraços, Leonardo Lourenço Crespilho - Original Message - From: Arthur Tupinambá [EMAIL PROTECTED] To: debian-user-portuguese@lists.debian.org Sent: Friday, September 17, 2004 11:19 AM Subject: Kernel Panic: VFS : Unable to mount root fs -AJUDA!! Pessoal, Preciso de uma ajuda urgente de quem já passou por esse tipo de experiência: Baixei o kernel 2.6.8.1, do kernel.org, descompactei, dei um make menuconfig e configurei-o. após isso eu compilo e instalo do modo debian: #make-kpkg --revision=custom1.0 kernel_image #dpkg -i kernel_image-custom1.0.deb Tudo ocorre numa boa, porém na hora do boot... Kernel Panic: VFS : Unable to mount root fs on unknown-block(3,2) O que pode ser??? to perdido, já recompilei o kernel umas 30 vezes
Re: Kernel Panic: VFS : Unable to mount root fs -AJUDA!!
Ola Ja passei por isso. O que acredito ter resolvido foi saber em qual sistema de arquivos a particao root e montada na inicializacao. Umas 3 linhas acima de Kernel Panic deve dizer qual tipo de fs Veja o dmesg daqui: RAMDISK: Compressed image found at block 0 VFS: Mounted root (minix filesystem). kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. Freeing unused kernel memory: 164k freed A particao e montada primeiro em minix. E depois passada para ext3. [] - Original Message - From: Arthur_Henrique_Sommerhalder_Tupinamba To: debian-user-portuguese Sent: Friday, September 17, 2004 7:18 PM Subject: Re: Kernel Panic: VFS : Unable to mount root fs -AJUDA!! Tentarei fazer o que nosso amigo Rubens disse, mas gostaria que mais algueda referente ao problema Aos que já presenciaram o problema... por favor, deem uma forcinha... Pois afinal, nada melhor do que um kernel 100% enxuto, rolando. _ Quer mais velocidade? Só com o acesso Aditivado iG, a velocidade que você quer na hora que você precisa. Clique aqui: http://www.acessoaditivado.ig.com.br
Re: Kernel Panic: VFS : Unable to mount root fs -AJUDA!!
Olá, Tive esse mesmo problema quando testei o kernel 2.6 pela primeira vez. O que se passou foi que existem umas novas opções relativas a suporte IDE que eu não tinha reparado e não incluí no kernel. Sem suporte para IDE nada feito. Pelo vistos os kernel hackers utilizam SCSI. :-) As opções que têm de ser incluídas são: * ATA/ATAPI/MFM/RLL support (CONFIG_IDE) * Enhanced IDE/MFM/RLL disk/cdrom/tape/floppy support (CONFIG_BLK_DEV_IDE) * Include IDE/ATA-2 DISK support (CONFIG_BLK_DEV_IDEDISK) * generic/default IDE chipset support (CONFIG_IDE_GENERIC) * PCI IDE chipset support (CONFIG_BLK_DEV_IDEPCI) * Generic PCI IDE Chipset Support (CONFIG_BLK_DEV_GENERIC) Espero que ajude. Rúben On Fri, Sep 17, 2004 at 11:19:59AM -0300, Arthur Tupinambá wrote: Pessoal, Preciso de uma ajuda urgente de quem já passou por esse tipo de experiência: Baixei o kernel 2.6.8.1, do kernel.org, descompactei, dei um make menuconfig e configurei-o. após isso eu compilo e instalo do modo debian: #make-kpkg --revision=custom1.0 kernel_image #dpkg -i kernel_image-custom1.0.deb Tudo ocorre numa boa, porém na hora do boot... Kernel Panic: VFS : Unable to mount root fs on unknown-block(3,2) O que pode ser??? to perdido, já recompilei o kernel umas 30 vezes, de diversas formas... Lí que poderia ser o initrd, tentei compilar o kernel com #make-kpkg --initrd também (precisa pois tem gente que precisa, outros dizem que precisa da imagem apenas em kernels padrão???) Bom, antes que me perguntem, já vou responder: - Sim, eu compilei o ext3 dentro do Kernel - Sim, eu compilei suporte RAMDISK dentro do kernel Alguém por favor, me dê alguma luz para resolver isso... Obrigado à todos, Abraços Arthur Henrique S. Tupinambá [EMAIL PROTECTED] Synchro Sistemas de Informação www.synchro.com.br Fone : +55 ( 11 ) 3758 - 0021 / R. 187 Fone : +55 ( 11 ) 3758 - 0038 Fax : +55 ( 11 ) 3758 - 3773 Mob: +55 ( 11 ) 7718 - 5371 E-mail : [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Rúben Leote Mendes - [EMAIL PROTECTED]
Re: Kernel Panic: VFS : Unable to mount root fs -AJUDA!!
Oi Arthur. Faz o seguinte. Compila o suporte a ext3 como módulo. -- Também faz as configurações que o Ruben falou: * ATA/ATAPI/MFM/RLL support (CONFIG_IDE) * Enhanced IDE/MFM/RLL disk/cdrom/tape/floppy support (CONFIG_BLK_DEV_IDE) * Include IDE/ATA-2 DISK support (CONFIG_BLK_DEV_IDEDISK) * generic/default IDE chipset support (CONFIG_IDE_GENERIC) * PCI IDE chipset support (CONFIG_BLK_DEV_IDEPCI) * Generic PCI IDE Chipset Support (CONFIG_BLK_DEV_GENERIC) -- Olha... não consegui entender direito, mas tive muitos problemas com esse kernel também. Não só com ele, mas com a família 2.4 e 2.6. Fiz diversas combinações e constatei, impiricamente, que o problema - pelo menos no meu caso - estava em compilar ext3 no kernel, e não como módulo. Daí eu compilei como módulo e funcionou normal. Dessa experiência tirei algumas conclusões, que se alguém aqui souber explicar melhor, por favor o faça, que não encontrei isso nas man pages: O initrd é uma espécie de pré-kernel, que é carregado para dar suporte à alguns dispositivos, como, por exemplo o ext3fs. Uma vez podendo acessar ext3fs, o grub pode buscar o kernel propriamente dito, que é então carregado. Nesse ponto o initrd é liberado da memória e não mais utilizado. Daí o motivo do suporte a ext3 ser compilado como módulo, para que o initrd também possa incluir suporte a ext3. Pelo menos nos meus testes, quando eu compilava ext3 no kernel, minha imagem initrd não tinha suporte a ext3, daí não explodia na memória os drivers pra acessar esse tipo de partição. E, como no /etc/fstab a partição é indicada como ext3fs, o grub não enxerga corretamente e não consegue carregar o kernel sem que o initrd tenha carregado o suporte a ext3 anteriormente. Cara... imagino que eu tenha falado muita besteira pois tirei essas conclusões empiricamente após 1 semana de compilação em 2 computadores. E não encontrei documentação descente falando sobre isso, infelizmente. Por favor, se alguém manjar bastante disso, explique pra gente ou então indique alguma documentação boa... please. Abraços, Leonardo Lourenço Crespilho - Original Message - From: Arthur Tupinambá [EMAIL PROTECTED] To: debian-user-portuguese@lists.debian.org Sent: Friday, September 17, 2004 11:19 AM Subject: Kernel Panic: VFS : Unable to mount root fs -AJUDA!! Pessoal, Preciso de uma ajuda urgente de quem já passou por esse tipo de experiência: Baixei o kernel 2.6.8.1, do kernel.org, descompactei, dei um make menuconfig e configurei-o. após isso eu compilo e instalo do modo debian: #make-kpkg --revision=custom1.0 kernel_image #dpkg -i kernel_image-custom1.0.deb Tudo ocorre numa boa, porém na hora do boot... Kernel Panic: VFS : Unable to mount root fs on unknown-block(3,2) O que pode ser??? to perdido, já recompilei o kernel umas 30 vezes, de diversas formas... Lí que poderia ser o initrd, tentei compilar o kernel com #make-kpkg --initrd também (precisa pois tem gente que precisa, outros dizem que precisa da imagem apenas em kernels padrão???) Bom, antes que me perguntem, já vou responder: - Sim, eu compilei o ext3 dentro do Kernel - Sim, eu compilei suporte RAMDISK dentro do kernel Alguém por favor, me dê alguma luz para resolver isso... Obrigado à todos, Abraços Arthur Henrique S. Tupinambá [EMAIL PROTECTED] Synchro Sistemas de Informação www.synchro.com.br Fone : +55 ( 11 ) 3758 - 0021 / R. 187 Fone : +55 ( 11 ) 3758 - 0038 Fax : +55 ( 11 ) 3758 - 3773 Mob: +55 ( 11 ) 7718 - 5371 E-mail : [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Kernel Panic: VFS : Unable to mount root fs -AJUDA!!
Primeiramente Leonardo, obrigado pela força: Vamos as dúvidas... (vamos dizer, que farei isso pelo menos em funcao de testes) - Se eu compilar o ext3 como módulo, jogo o ext2 como built-in ?? ou apenas o ext3 como módulo ? - Bom para criaçao do initrd, eu preciso alterar o mkinitrd.conf de cramfs pra ext2fs ? a sintaxe de comando é mkinitrd -o /DIRETORIO OUTPUT/ARQUIVO OUTPUT ? Tentarei fazer o que nosso amigo Rubens disse, mas gostaria que mais alguem desse uma ajuda referente ao problema Aos que já presenciaram o problema... por favor, deem uma forcinha... Pois afinal, nada melhor do que um kernel 100% enxuto, rolando. Abraços a todos e mais uma vez Obrigado! Arthur Citando Leonardo Lourenço Crespilho [EMAIL PROTECTED]: Oi Arthur. Faz o seguinte. Compila o suporte a ext3 como módulo. -- Também faz as configurações que o Ruben falou: * ATA/ATAPI/MFM/RLL support (CONFIG_IDE) * Enhanced IDE/MFM/RLL disk/cdrom/tape/floppy support (CONFIG_BLK_DEV_IDE) * Include IDE/ATA-2 DISK support (CONFIG_BLK_DEV_IDEDISK) * generic/default IDE chipset support (CONFIG_IDE_GENERIC) * PCI IDE chipset support (CONFIG_BLK_DEV_IDEPCI) * Generic PCI IDE Chipset Support (CONFIG_BLK_DEV_GENERIC) -- Olha... não consegui entender direito, mas tive muitos problemas com esse kernel também. Não só com ele, mas com a família 2.4 e 2.6. Fiz diversas combinações e constatei, impiricamente, que o problema - pelo menos no meu caso - estava em compilar ext3 no kernel, e não como módulo. Daí eu compilei como módulo e funcionou normal. Dessa experiência tirei algumas conclusões, que se alguém aqui souber explicar melhor, por favor o faça, que não encontrei isso nas man pages: O initrd é uma espécie de pré-kernel, que é carregado para dar suporte à alguns dispositivos, como, por exemplo o ext3fs. Uma vez podendo acessar ext3fs, o grub pode buscar o kernel propriamente dito, que é então carregado. Nesse ponto o initrd é liberado da memória e não mais utilizado. Daí o motivo do suporte a ext3 ser compilado como módulo, para que o initrd também possa incluir suporte a ext3. Pelo menos nos meus testes, quando eu compilava ext3 no kernel, minha imagem initrd não tinha suporte a ext3, daí não explodia na memória os drivers pra acessar esse tipo de partição. E, como no /etc/fstab a partição é indicada como ext3fs, o grub não enxerga corretamente e não consegue carregar o kernel sem que o initrd tenha carregado o suporte a ext3 anteriormente. Cara... imagino que eu tenha falado muita besteira pois tirei essas conclusões empiricamente após 1 semana de compilação em 2 computadores. E não encontrei documentação descente falando sobre isso, infelizmente. Por favor, se alguém manjar bastante disso, explique pra gente ou então indique alguma documentação boa... please. Abraços, Leonardo Lourenço Crespilho - Original Message - From: Arthur Tupinambá [EMAIL PROTECTED] To: debian-user-portuguese@lists.debian.org Sent: Friday, September 17, 2004 11:19 AM Subject: Kernel Panic: VFS : Unable to mount root fs -AJUDA!! Pessoal, Preciso de uma ajuda urgente de quem já passou por esse tipo de experiência: Baixei o kernel 2.6.8.1, do kernel.org, descompactei, dei um make menuconfig e configurei-o. após isso eu compilo e instalo do modo debian: #make-kpkg --revision=custom1.0 kernel_image #dpkg -i kernel_image-custom1.0.deb Tudo ocorre numa boa, porém na hora do boot... Kernel Panic: VFS : Unable to mount root fs on unknown-block(3,2) O que pode ser??? to perdido, já recompilei o kernel umas 30 vezes, de diversas formas... Lí que poderia ser o initrd, tentei compilar o kernel com #make-kpkg --initrd também (precisa pois tem gente que precisa, outros dizem que precisa da imagem apenas em kernels padrão???) Bom, antes que me perguntem, já vou responder: - Sim, eu compilei o ext3 dentro do Kernel - Sim, eu compilei suporte RAMDISK dentro do kernel Alguém por favor, me dê alguma luz para resolver isso... Obrigado à todos, Abraços Arthur Henrique S. Tupinambá [EMAIL PROTECTED] Synchro Sistemas de Informação www.synchro.com.br Fone : +55 ( 11 ) 3758 - 0021 / R. 187 Fone : +55 ( 11 ) 3758 - 0038 Fax : +55 ( 11 ) 3758 - 3773 Mob: +55 ( 11 ) 7718 - 5371 E-mail : [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] This message was sent using IMP, the Internet Messaging Program.
Re: Kernel Panic: VFS : Unable to mount root fs -AJUDA!!
Arthur; * Musashi corta a msg que Arthur Tupinambá enviou para Still: Pessoal, Preciso de uma ajuda urgente de quem já passou por esse tipo de experiência: Baixei o kernel 2.6.8.1, do kernel.org, descompactei, dei um make menuconfig e configurei-o. após isso eu compilo e instalo do modo debian: #make-kpkg --revision=custom1.0 kernel_image #dpkg -i kernel_image-custom1.0.deb Tudo ocorre numa boa, porém na hora do boot... Kernel Panic: VFS : Unable to mount root fs on unknown-block(3,2) O que pode ser??? to perdido, já recompilei o kernel umas 30 vezes, de diversas formas... Lí que poderia ser o initrd, tentei compilar o kernel com #make-kpkg --initrd também (precisa pois tem gente que precisa, outros dizem que precisa da imagem apenas em kernels padrão???) Bom, antes que me perguntem, já vou responder: - Sim, eu compilei o ext3 dentro do Kernel - Sim, eu compilei suporte RAMDISK dentro do kernel E como está o seu /etc/fstab ? O / está montado como ext3 ? Eu tive problemas parecidos com o reiserfs na hora da instalação, mas bastou compilar com suporte a reiserfs built-in para funcionar. []'s, Still -- Nelson Luiz Campos .''`. | I hear; I forget. Engenheiro Eletricista : :' :| I see; I remember. Linux User #89621 UIN 11464303 `. `'` | I do; I understand. gnupgID: 55577339`- | Chinese Proverb signature.asc Description: Digital signature
Re: Kernel panic: VFS: Unable to mount root fs on 03:01
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Manuel Soukup schrieb: | Leute ich hab meine Paketliste zurück gespielt. Dabei hat er ein Paket | entfernt (konnte leider nicht sehen welches) und nun kommt beim booten: | | Kernel panic: VFS: Unable to mount root fs on 03:01 Naja, ich würde mal sagen, dass aus irgendeinem Grund plötzlich nicht mehr der richtige root=/dev/... Kernel-Parameter vom BootLoader übergeben wird - sprich ein falscher wird übergeben und der verweist auf eine Partition, die es gar nicht gibt/die er nicht mounten kann/dessen fs er nicht kennt/... | Was kann man da tun ? (Ich würde neu installieren oder gibts da ne | Möglichkeit mit Knoppix was zu ändern an der Bootreihenfolge oder sonst | wo?) Würde also mal sagen: GRUB bzw. Lilo Konfiguration überprüfen, ob denn da das richtige root-Device drinsteht. Das sollte mit Knoppix machbar sein. ~ Joachim -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBSTS3ZY86bR8HqNwRAlfvAJ9BfFC3QeHET5Pgyqt2g4UWWZEKIwCguNxW zZhbKO6NCIov+B+Pta1mIKE= =uB+4 -END PGP SIGNATURE- -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Kernel panic: VFS: Unable to mount root fs on 03:01
Manuel Soukup [EMAIL PROTECTED] writes: Hi Leute ich hab meine Paketliste zurück gespielt. Dabei hat er ein Paket entfernt (konnte leider nicht sehen welches) und nun kommt beim booten: Kernel panic: VFS: Unable to mount root fs on 03:01 Mit den Paketen direkt hat das nichts zu tun, sondern mit deiner Kernel-Konfiguration. 03:01 ist hda1. Wenn das nicht deine root-Partition ist, ist was an der lilo- oder grub-Konfiguration faul. Ansonsten musst die IDE-hd-Treiber und die fürs dortige Filesystem fest einkompilieren (Module gehen nur dann, wenn du eine initrd verwendest). Gruß, Heike -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Kernel Panic: VFS : Unable to mount rout fs on unknown-block(3,3)
On Sun, 16 May 2004 11:33:03 -0300 Savio Ramos [EMAIL PROTECTED] wrote: Respondendo a mim mesmo, para quem necessitar no futuro: Estou compilando o núcleo 2.6.5 com o config do kernel-image-2.6.5-k7. Deveria funcionar beleza, não? Claro que funciona! O problema é que por padrão as imagens oficiais do núcleo usam o initrd e eu compilei sem esta opção. Não funcionou, na hora do boot aparece a mensagem acima. A mensagem acima avisa que não foi possível montar o ram disk ( o rd do initrd) Solução: 1) na hora da compilação o comando é este: make-kpkg --initrd kernel_image 2) instale a imagem normalmente. Após, edite o lilo.conf para que ele localize a imagem do núcleo que será montada na memória ram, assim: initrd=/caminho/onde/está/a/imagem/initrd.img No meu o lilo.conf ficou assim: initrd=/boot/initrd.img-2.6.5 Ah! Rode o lilo antes do boot. Obs: durante a instalação aparece um aviso sobre o kernel-image.conf, não ligue para ele. É importante somente se você baixar uma imagem oficial Debian. Grato a todos que responderam. -- Savio Martins Ramos - Arquiteto Rio de Janeiro ICQ 174972645 Pirataria não, seja livre: Linux http://www.debian.org
Re: Kernel Panic: VFS : Unable to mount rout fs on unknown-block(3,3)
On Sun, 16 May 2004 15:18:04 -0300 Vordeph [EMAIL PROTECTED] wrote: É só um chute, mas na documentação do kernel 2.6.5 tem uma parte que fala dos requisitos para instalação, é o arquivo Changes no diretório Documentation, lá menciona as versões mínimas de alguns programas e bibliotecas que você deve ter antes de utilizar o kernel 2.6.x, tente verificar se você tem todos instalados, Estou usando a Sid e atualizei quinta passada. principalmente o module-init-tools. ii module-init-tools 3.0-pre10-2tools for managing Linux Caso positivo, tente verificar se você compilou o driver para o seu sistema de arquivos (ex: ReiserFS, Ext3, xfs) como embutido (não módulo) dentro do kernel. Talvez seja por aí... Veja como está a configuração: CONFIG_EXT3_FS=m CONFIG_EXT3_FS_XATTR=y CONFIG_EXT3_FS_POSIX_ACL=y CONFIG_EXT3_FS_SECURITY=y O primeiro é um módulo e os outros estão embutidos. Vou tentar mudar o primeiro. Grato. -- Savio Martins Ramos - Arquiteto Rio de Janeiro ICQ 174972645 Pirataria não, seja livre: Linux http://www.debian.org
Re: Kernel Panic: VFS : Unable to mount rout fs on unknown-block(3,3)
On Mon, 17 May 2004 07:08:35 -0300 Savio Ramos [EMAIL PROTECTED] wrote: O primeiro é um módulo e os outros estão embutidos. Vou tentar mudar o primeiro. Neca_de_pitibiriba ... -- Savio Martins Ramos - Arquiteto Rio de Janeiro ICQ 174972645 Pirataria não, seja livre: Linux http://www.debian.org
Re: Kernel Panic: VFS : Unable to mount rout fs on unknown-block(3,3)
--- Savio Ramos [EMAIL PROTECTED] escreveu: Você deve marcar as opções em Device, onde fica a opção do loopback uma opção quem sob titulo RAM [alguma coisa] lá dentro tem a opção de initrd e aí vc marca e pronto, ou pode marcar tudo dentro do kernel e marca automonter no próprio kernel. Bom! Eu fiz isso e funcionou. O primeiro é um módulo e os outros estão embutidos. Vou tentar mudar o primeiro. Neca_de_pitibiriba ... = O conhecimento deve ser livre sempre, pois é patrimônio da humanidade. Cobol-Utilits - http://cobol.sourceforge.net WesleyOliveira - http://wesley.tinycobol.org __ Yahoo! Messenger - Fale com seus amigos online. Instale agora! http://br.download.yahoo.com/messenger/
Re: Kernel Panic: VFS : Unable to mount rout fs on unknown-block(3,3)
Olá Savio. A partição root está com algum sistema de arquivos diferente do ext2? Se estiver, o suporte a esse sistema de arquivos está compilado diretamente no kernel? (não como módulo, mas sim estaticamente). Abraços, -- /*--* * Marcelo Drudi Miranda | Microelectronics Engineering Student * * Debian GNU/Linux User | Linux Registered User #177399* *--*/ On Sun, May 16, 2004 at 11:33:03AM -0300, Savio Ramos wrote: Olá, Estou compilando o núcleo 2.6.5 com o config do kernel-image-2.6.5-k7. Deveria funcionar beleza, não? Não funcionou, na hora do boot aparece a mensagem acima. Alguma luz? Grato.
Re: Kernel Panic: VFS : Unable to mount rout fs on unknown-block(3,3)
Savio Ramos escreveu: Olá, Estou compilando o núcleo 2.6.5 com o config do kernel-image-2.6.5-k7. Deveria funcionar beleza, não? Não funcionou, na hora do boot aparece a mensagem acima. Alguma luz? Saudações, É só um chute, mas na documentação do kernel 2.6.5 tem uma parte que fala dos requisitos para instalação, é o arquivo Changes no diretório Documentation, lá menciona as versões mínimas de alguns programas e bibliotecas que você deve ter antes de utilizar o kernel 2.6.x, tente verificar se você tem todos instalados, principalmente o module-init-tools. Caso positivo, tente verificar se você compilou o driver para o seu sistema de arquivos (ex: ReiserFS, Ext3, xfs) como embutido (não módulo) dentro do kernel. Espero que ajude, boa sorte. -- []s Pedro Desenvolvedor, Mestre Jedi, Slackwarrior Usuário Linux Registro no. 274710 Usuário Debian-BR GNU/Linux no. 606 'E que os fontes estejam com você !'
Re: Kernel Panic: VFS: Unable to mount root fs on unknown-block(0,0)
On Tue, Apr 20, 2004 at 03:10:58PM +0200, Philippe Dhont (Sea-ro) said My new kernel is compiled with ext2, ext3 and the others also. My filesystem is ext3. In the kernel or as modules? They have to be builtin for it boot. When i reboot my system i can choose to boot the debian2.6.5 but in the boot process i get this: Kernel Panic: VFS: Unable to mount root fs on unknown-block(0,0) Did you include support for your ide/scsi controller IN the kernel, too? -- Rob Weir [EMAIL PROTECTED] | [EMAIL PROTECTED] | Do I look like I want a CC? Words of the day: corporate security Bosnia Syria ICE Verisign SRI Nazi signature.asc Description: Digital signature
Re: Kernel Panic: VFS: Unable to mount root fs on unknown-block(0,0)
Philippe Dhont (Sea-ro) wrote: Hi, I installed debian SARGE with grub and everything works fine. I downloaded the latest stable kernel, compiled everything and put the boot lines in the grub configuration Menu.lst This was before: Title Debian 2.4.25 Root (hd0,0) Kernel /vmlinuz-2.4.25-1-386 root=/dev/hda3 ro Initrd /initrd.img-2.4.25-1.-386 Savedefault Boot THIS IS NOW: Title Debian 2.4.25 Root (hd0,0) Kernel /vmlinuz-2.4.25-1-386 root=/dev/hda3 ro Initrd /initrd.img-2.4.25-1.-386 Savedefault Boot ***I ADDED THE FOLLOWING*** Title Debian.2.6.5 Root (hd0,0) Kernel /bzImage2.6.5 root=/dev/hda3 ro Savedefault Boot My new kernel is compiled with ext2, ext3 and the others also. My filesystem is ext3. When i reboot my system i can choose to boot the debian2.6.5 but in the boot process i get this: Kernel Panic: VFS: Unable to mount root fs on unknown-block(0,0) How can i fix it so that i can boot with my 2.6.5 ?? Is your kernel really at /bzImage2.6.5 ? Does it have an initrd that you forgot to specify? -Roberto Sanchez signature.asc Description: OpenPGP digital signature
Re: Kernel Panic: VFS: Unable to mount root fs on hdh6
Moin, * Elimar Riesebieter [EMAIL PROTECTED] [2004-01-02 03:09]: Thorsten Haude told: - - - Schnipp - - - [EMAIL PROTECTED] # lilo / Warning: The boot sector and map file are on different disks. ^^ [...] Meine lilo.conf (ohne Kommentare): - - - Schnipp - - - bios=0x81 boot=/dev/hdg ^^^ root=/dev/hdh6 ^ install=/boot/boot-menu.b map=/boot/map ^ Aus der fstab: - - - Schnipp - - - /dev/hdh6 / ext3errors=remount-ro 0 1 /dev/hdg1 noneswapsw 0 0 /dev/hdh1 noneswapsw 0 0 /dev/hdh5 /boot ext3defaults0 2 Der Bootsector - hdg Der Mapfile in /boot- hdh5 Root Dir- hdh6 Warum willst Du vom hdg booten? Versuchs doch einfach mal von hdh ;-) Sarge ist nunmal auf hdh, was nunmal nicht die erste Platte ist. Ich werde aber gleich mal nachsehen, ob ich den Controller überreden kann, von der zweiten Platte zu booten. Oder machs richtig und richte auf hdg eine /boot partition ein. Dann gehts bestimmt! Oder stöpsel die Platten um, dh Tausche hdh mit hdg am Controller. Oder . Sach bloß, Lilo kann prinzipiell nicht von einer anderen Platte booten? Das war ja schon weiland mit OS/2's Bootmanager kein Problem, auch nicht um damit Lilo zo booten. Ist das auch der Grund für die Fehlermeldungen beim Booten? Vielen Dank schonmal, Thorsten -- Getting a thrill out of some stupid quote is a sign of idiocy. - turmeric pgp0.pgp Description: PGP signature
Re: Kernel Panic: VFS: Unable to mount root fs on hdh6
On Fri, 2 Jan 2004 12:02:41 +0100 Thorsten Haude [EMAIL PROTECTED] wrote: Moin, * Elimar Riesebieter [EMAIL PROTECTED] [2004-01-02 03:09]: Thorsten Haude told: - - - Schnipp - - - [EMAIL PROTECTED] # lilo / Warning: The boot sector and map file are on different disks. ^^ [...] Meine lilo.conf (ohne Kommentare): - - - Schnipp - - - bios=0x81 boot=/dev/hdg ^^^ root=/dev/hdh6 ^ install=/boot/boot-menu.b map=/boot/map ^ Aus der fstab: - - - Schnipp - - - /dev/hdh6 / ext3errors=remount-ro 0 1 /dev/hdg1 noneswapsw 0 0 /dev/hdh1 noneswapsw 0 0 /dev/hdh5 /boot ext3defaults0 2 Der Bootsector - hdg Der Mapfile in /boot- hdh5 Root Dir- hdh6 Warum willst Du vom hdg booten? Versuchs doch einfach mal von hdh ;-) Sarge ist nunmal auf hdh, was nunmal nicht die erste Platte ist. Ich werde aber gleich mal nachsehen, ob ich den Controller berreden kann, von der zweiten Platte zu booten. Oder machs richtig und richte auf hdg eine /boot partition ein. Dann gehts bestimmt! Oder stpsel die Platten um, dh Tausche hdh mit hdg am Controller. Oder . Sach blo, Lilo kann prinzipiell nicht von einer anderen Platte booten? Das war ja schon weiland mit OS/2's Bootmanager kein Problem, auch nicht um damit Lilo zo booten. Ist das auch der Grund fr die Fehlermeldungen beim Booten? Ich verwendete kernel-2.4.20 und bootete die ganze Zeit erfolgreich von hdc1. Mit Kernel 2.6.0 bekomme ich absolut die gl. Fehlermeldung, wie oben beschrieben, dabei habe ich den Kernel mit make bzlilo instaliert. Vlad -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Kernel Panic: VFS: Unable to mount root fs on hdh6
Moin, * Thorsten Haude [EMAIL PROTECTED] [2004-01-02 01:32]: ich habe gerade einen neuen Kernel gebacken und bekomme es nicht hin, den auch zu booten. Ok, ich habe jetzt mal Grub installiert. Damit ist es kein Problem, den alten Kernel zu booten, beim neuen gibt es den gleichen Fehler. Damit ist für mich klar, daß der Kernel ein Problem hat. Im Kernel sind folgende Optionen gesetzt (nicht als Modul): IDE BLK_DEV_IDE BLK_DEV_IDEDISK BLK_DEV_IDEPCI BLK_DEV_IDEDMA_PCI BLK_DEV_HPT366 BLK_DEV_VIA82CXXX EXT2_FS EXT3_FS Aber welches? Warum findet dieser Kernel nicht sein Rootdevice? Thorsten -- If people could put rainbows in zoos, they'd do it. - Hobbes pgp0.pgp Description: PGP signature
Re: Kernel Panic: VFS: Unable to mount root fs on hdh6
Hi Thorsten, On Fri, 02 Jan 2004 the mental interface of Thorsten Haude told: Moin, - - - Schnipp - - - [EMAIL PROTECTED] # lilo / Warning: The boot sector and map file are on different disks. ^^ [...] Meine lilo.conf (ohne Kommentare): - - - Schnipp - - - bios=0x81 boot=/dev/hdg ^^^ root=/dev/hdh6 ^ install=/boot/boot-menu.b map=/boot/map ^ Aus der fstab: - - - Schnipp - - - /dev/hdh6 / ext3errors=remount-ro 0 1 /dev/hdg1 noneswapsw 0 0 /dev/hdh1 noneswapsw 0 0 /dev/hdh5 /boot ext3defaults0 2 Der Bootsector - hdg Der Mapfile in /boot- hdh5 Root Dir- hdh6 Warum willst Du vom hdg booten? Versuchs doch einfach mal von hdh ;-) Oder machs richtig und richte auf hdg eine /boot partition ein. Dann gehts bestimmt! Oder stöpsel die Platten um, dh Tausche hdh mit hdg am Controller. Oder . Ciao Elimar -- Ersatz des Zufalls durch den Irrtum. -unknown- pgp0.pgp Description: PGP signature
Re: Kernel panic: VFS: Unable to mount root fs (Solved)
On Tuesday 26 August 2003 14:56, Joris Huizer wrote: --- Alphonse Ogulla [EMAIL PROTECTED] wrote: Hi all, Just compiled kernel 2.4.21 but cannot boot it despite creating the initrd image and respective links in / to files in /boot. The last 5 lines printed on screen before hang-up are printed below. RAMDISK: Couldn't find valid RAM disk image starting at 0. Freeing initrd memory: 2664k freed VFS: Cannot open root device 301 or 03:01 Please append a correct root= boot option Kernel panic: VFS: Unable to mount root fs on 03:01 Passing root=/dev/hda1 to lilo at boot time did not bear fruit. Created initrd as follows: # mkinitrd -o /boot/initrd.img-2.4.21 /lib/modules/2.4.21 Added the following lines in lilo.conf before running lilo. . image=/vmlinuz-2.4.21 initrd=/initrd.img-2.4.21 label=2.4.21 root=/dev/hda1 read-only Grateful for any assistance in resolving this difficulty. -- Alphonse Ogulla Nairobi, Kenya Check that: - under File systems, Second extended fs support has y - under Block devices, Normal PC floppy disk support has y - under ATA/IDE/MFM/RLL support, IDE, ATA and ATAPI Block devices has y - under submenu IDE, ATA and ATAPI Block Devices, Enhanced IDE/MFM/RLL disk/cdrom/tape/floppy support and Include IDE/ATA-2 DISK support have y clicked. This helped me to solve similar problems - I hope it'll help you too Yes it did. Coming to think of it, make exited with an error during the final step of kernel compilation - make modules_install because of dependancy issues with some *pmcia* and *mtd* modules. Therefore the resulting initrd.img created from /lib/modules/2.4.21 directory must have been lacking in some aspect. Building disk filesystem drivers directly into the kernel as per above instructions and forgetting about initrd.img did the trick. atlas:~# uname -a Linux atlas 2.4.21 #3 Tue Aug 26 20:01:03 EAT 2003 i686 unknown Thanks and regards -- Alphonse Ogulla Nairobi, Kenya -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Kernel panic: VFS: Unable to mount root fs
--- Alphonse Ogulla [EMAIL PROTECTED] wrote: Hi all, Just compiled kernel 2.4.21 but cannot boot it despite creating the initrd image and respective links in / to files in /boot. The last 5 lines printed on screen before hang-up are printed below. RAMDISK: Couldn't find valid RAM disk image starting at 0. Freeing initrd memory: 2664k freed VFS: Cannot open root device 301 or 03:01 Please append a correct root= boot option Kernel panic: VFS: Unable to mount root fs on 03:01 Passing root=/dev/hda1 to lilo at boot time did not bear fruit. Created initrd as follows: # mkinitrd -o /boot/initrd.img-2.4.21 /lib/modules/2.4.21 Added the following lines in lilo.conf before running lilo. . image=/vmlinuz-2.4.21 initrd=/initrd.img-2.4.21 label=2.4.21 root=/dev/hda1 read-only Grateful for any assistance in resolving this difficulty. -- Alphonse Ogulla Nairobi, Kenya Check that: - under File systems, Second extended fs support has y - under Block devices, Normal PC floppy disk support has y - under ATA/IDE/MFM/RLL support, IDE, ATA and ATAPI Block devices has y - under submenu IDE, ATA and ATAPI Block Devices, Enhanced IDE/MFM/RLL disk/cdrom/tape/floppy support and Include IDE/ATA-2 DISK support have y clicked. This helped me to solve similar problems - I hope it'll help you too Joris __ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Kernel panic: VFS: Unable to mount root fs
On Tue, Aug 26, 2003 at 12:40:44PM +0300, Alphonse Ogulla wrote: | Just compiled kernel 2.4.21 but cannot boot it | VFS: Cannot open root device 301 or 03:01 You probably forgot to include the driver for your hard disk when you built the kernel. Follow Joris' suggestion for enabling the driver for the most common type of disks. (BTW, I've done this before. It's a good way to learn to include the driver :-)) -D -- (A)bort, (R)etry, (T)ake down entire network? http://dman13.dyndns.org/~dman/ pgp0.pgp Description: PGP signature
Re: kernel panic: VFS: Unable to mount root fs on 03:02
El Sábado, 8 de Marzo de 2003 17:34, Borxa Varela escribió: ¿Como salgo de esta? No puedo arrancar ni con el diskete... ¿tengo que reinstalar? Si no tienes otra particion root por ahi yo creo q sí. Lo siento. -- Fernando Blat Peris http://ttt.inf.upv.es/~ferblape Polinux http://polinux.upv.es UPV - Valencia
Re: kernel panic: VFS: Unable to mount root fs on 03:02
Borxa Varela wrote: ¿Como salgo de esta? No puedo arrancar ni con el diskete... ¿tengo que reinstalar? Intenta dar un poco mas de información sobre tu sistema, como tipo de sistema de ficheros para la raíz, si has hecho algun cambio ultimamente, etc..., del error que indicas lo uúnico que se puede deducir es que intenta montar en / el dispositivo /dev/hda2, ¿ es esa la partición donde tienes instalado el linux ? -- On the side of the software box, in the 'System Requirements' section, it said 'Requires Windows 95 or better'. So I installed Linux. -Anonymous
Re: kernel panic: VFS: Unable to mount root fs on 03:02
Moviste el rigido de lugar ? si es asi, solo basta con bootear otro SO, aceder a la particion y cambiar la entrada / del fstab. JoloX El Sáb 08 Mar 2003 16:34, Borxa Varela escribió: ¿Como salgo de esta? No puedo arrancar ni con el diskete... ¿tengo que reinstalar? -- Powered by JoloX 0.01 GNU/Linux
Re: Kernel panic: VFS: Unable to mount root fs
On Sat, Dec 07, 2002 at 12:38:37AM +1300, Richard Hector wrote: It is? I thought that was the usual way to do it (with 2.4 kernels, anyway) ... should I look at recompiling my kernel with my SCSI drivers built in instead? Or are you specifically referring to filesystem drivers rather than all drivers necessary to mount the filesystem? Support for your root device hardware and filesystem should be part of your kernel for maximum ease and reliability. Pretty much everything else that can be moduled out should. -- .''`. Baloo [EMAIL PROTECTED] : :' :proud Debian admin and user `. `'` `- Debian - when you have better things to do than to fix a system msg17420/pgp0.pgp Description: PGP signature
Re: Kernel panic: VFS: Unable to mount root fs
Paul == Paul Johnson [EMAIL PROTECTED] writes: Paul Support for your root device hardware and filesystem should Paul be part of your kernel for maximum ease and reliability. Paul Pretty much everything else that can be moduled out should. Paul, To be fair, you should point out that this is an opinion that run's contrary to how Debian's 2.4 kernels are packaged. ~$ uname -r 2.4.18-k7 ~$ /sbin/lsmod | grep ^ext ext2 30848 1 (autoclean) ext3 57248 6 (autoclean) The Debian kernels do provide for maximum ease and reliability IMHO :-) Cheers! Shyamal -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Kernel panic: VFS: Unable to mount root fs
Just a thought, but do you have ide and/or scsi as modules instead of compiled into the kernel? You will get this message if the kernel can't mount the root partition because it doesn't have the necessary drivers to talk to the disk on which the root partition sits. That is, if / is on an ide disk you need ide compiled into the kernel, not a module. ap -- Andrew J Perrin - http://www.unc.edu/~aperrin Assistant Professor of Sociology, U of North Carolina, Chapel Hill [EMAIL PROTECTED] * andrew_perrin (at) unc.edu On Thu, 5 Dec 2002, Stig Are M. Botterli wrote: In article [EMAIL PROTECTED], Klaus Imgrund wrote: On Thu, 05 Dec 2002 15:16:29 + I had kernels bigger than 1 MB - no problem. It would help if you remember what things you configured as modules. Unfortunately, I don't. If you got i.e a driver for the wrong sound card compiled in the kernel it can give you a kernel panic.If it is compiled as module the module just doesn't load. Perhaps, but I doubt anything like that can cause this particular kernel panic. Anyway, I've been able to boot a vanilla 2.4.20 kernel, and I'll make my changes one by one, so that if I'm hit by this again I will hopefully be able to pinpoint what introduced it. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Kernel panic: VFS: Unable to mount root fs
In article 20021206045426.GA22017@ursine, Paul Johnson wrote: Wait, are you trying to boot a kernel that doesn't have ext3 compiled in on a system whose /etc/fstab specifies the / partition as being ext3? Nope, ext2/ext3 have been included in the vmlinuz-image all along. I'll throw in another question here: from /etc/fstab: /dev/hdc6 / ext2errors=remount-ro 0 1 from dmesg: kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. VFS: Mounted root (ext3 filesystem) readonly. ... EXT3 FS 2.4-0.9.19, 19 August 2002 on ide1(22,6), internal journal I know I initially created / as an ext2 partition, and I can't recall having converted it to ext3 (though I could be wrong, I've certainly thought about it, I just can't recall having actually done it yet), I also just tried adriot3:~# mount -v -t ext3 -o remount /dev/hdc6 / /dev/hdc6 on / type ext3 (rw) adriot3:~# mount /dev/hdc6 on / type ext2 (rw) So why the mount as EXT3 while booting? Anyway, I've now got 2.4.20, plus the patches I wanted, up and running fine, and hopefully this won't be an issue again. It was probably some silly mistake on my part. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Kernel panic: VFS: Unable to mount root fs
On Fri, Dec 06, 2002 at 08:26:48AM -0600, Shyamal Prasad wrote: Paul, To be fair, you should point out that this is an opinion that run's contrary to how Debian's 2.4 kernels are packaged. Yes, I realise this, however, when compiling one's own kernel from the kernel archive (oppose to the debian source) then it's easier to do it my way. People who are new to building kernels should do it the Debian way for simplicity, and newbies should stick to the kernel-image packages until the process makes sense without too much additional assistance. -- .''`. Baloo [EMAIL PROTECTED] : :' :proud Debian admin and user `. `'` `- Debian - when you have better things to do than to fix a system msg17568/pgp0.pgp Description: PGP signature
Re: Kernel panic: VFS: Unable to mount root fs
On Thu, Dec 05, 2002 at 01:04:34AM +, Stig Are M. Botterli wrote: Basically, if my /boot/vmlinuz image exceeds a certain size (the limit seems be somewhere around 90 bytes), the following occurs on boot: Whoa! Huge kernel! Module some of that stuff out and it should help if there's some hidden size limitation. I have a pretty big kernel, the bzImage is 644,225 bytes. hdc6: bad access: block=2, count=2 end_request: I/O error, dev 16:06 (hdc), sector 2 EXT3-fs: Unable to read superblock hdc6: bad access: block=2, count=2 end_request: I/O error, dev 16:06 (hdc), sector 2 EXT2-fs: Unable to read superblock hdc6: bad access: block=0, count=1 end_request: I/O error, dev 16:06 (hdc), sector 0 NTFS: Reading super block failed Kernel panic: VFS: Unable to mount root fs on 16:06 Is your drive going bad? Are the filesystems OK? -- .''`. Baloo [EMAIL PROTECTED] : :' :proud Debian admin and user `. `'` `- Debian - when you have better things to do than to fix a system msg17120/pgp0.pgp Description: PGP signature
Re: Kernel panic: VFS: Unable to mount root fs
In article 20021205080347.GE7442@ursine, Paul Johnson wrote: On Thu, Dec 05, 2002 at 01:04:34AM +, Stig Are M. Botterli wrote: Basically, if my /boot/vmlinuz image exceeds a certain size (the limit se= ems be somewhere around 90 bytes), the following occurs on boot: Whoa! Huge kernel! Module some of that stuff out and it should help if there's some hidden size limitation. I have a pretty big kernel, the bzImage is 644,225 bytes. I did this, and got the kernel down to 719kB. However, the exact same thing occurs on boot (minus the three last lines, as I included NTFS- support as a module), so a hidden size limitation is obviously not the problem. Now I'm really wondering what actually 'solved' it for me with 2.4.19 and 2.4.20-pre10. My 2.4.20-pre10 (+ RML's preemption patch) image at 865kB boots, whereas an image approx. 20kB bigger panicked, and the only thing I can recall changing was turning some non-essential things into modules. That's why I was certain the problem was related to the size of the kernel image. hdc6: bad access: block=3D2, count=3D2 end_request: I/O error, dev 16:06 (hdc), sector 2 EXT3-fs: Unable to read superblock hdc6: bad access: block=3D2, count=3D2 end_request: I/O error, dev 16:06 (hdc), sector 2 EXT2-fs: Unable to read superblock hdc6: bad access: block=3D0, count=3D1 end_request: I/O error, dev 16:06 (hdc), sector 0 NTFS: Reading super block failed Kernel panic: VFS: Unable to mount root fs on 16:06 Is your drive going bad? Are the filesystems OK? I've seen nothing to indicate that there's anything wrong with neither my drives nor my filesystems. The system operates fine once booted. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Kernel panic: VFS: Unable to mount root fs
On Thu, 05 Dec 2002 15:16:29 + Stig Are M. Botterli [EMAIL PROTECTED] wrote: In article 20021205080347.GE7442@ursine, Paul Johnson wrote: On Thu, Dec 05, 2002 at 01:04:34AM +, Stig Are M. Botterli wrote: Basically, if my /boot/vmlinuz image exceeds a certain size (the limit se= ems be somewhere around 90 bytes), the following occurs on boot: Whoa! Huge kernel! Module some of that stuff out and it should help if there's some hidden size limitation. I have a pretty big kernel, the bzImage is 644,225 bytes. I did this, and got the kernel down to 719kB. However, the exact same thing occurs on boot (minus the three last lines, as I included NTFS- support as a module), so a hidden size limitation is obviously not the problem. Now I'm really wondering what actually 'solved' it for me with 2.4.19 and 2.4.20-pre10. My 2.4.20-pre10 (+ RML's preemption patch) image at 865kB boots, whereas an image approx. 20kB bigger panicked, and the only thing I can recall changing was turning some non-essential things into modules. That's why I was certain the problem was related to the size of the kernel image. I had kernels bigger than 1 MB - no problem. It would help if you remember what things you configured as modules. If you got i.e a driver for the wrong sound card compiled in the kernel it can give you a kernel panic.If it is compiled as module the module just doesn't load. Have fun, Klaus -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Kernel panic: VFS: Unable to mount root fs
In article [EMAIL PROTECTED], Klaus Imgrund wrote: On Thu, 05 Dec 2002 15:16:29 + I had kernels bigger than 1 MB - no problem. It would help if you remember what things you configured as modules. Unfortunately, I don't. If you got i.e a driver for the wrong sound card compiled in the kernel it can give you a kernel panic.If it is compiled as module the module just doesn't load. Perhaps, but I doubt anything like that can cause this particular kernel panic. Anyway, I've been able to boot a vanilla 2.4.20 kernel, and I'll make my changes one by one, so that if I'm hit by this again I will hopefully be able to pinpoint what introduced it. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Kernel panic: VFS: Unable to mount root fs
On Thu, Dec 05, 2002 at 07:10:42PM +, Stig Are M. Botterli wrote: I had kernels bigger than 1 MB - no problem. It would help if you remember what things you configured as modules. Unfortunately, I don't. Wait, are you trying to boot a kernel that doesn't have ext3 compiled in on a system whose /etc/fstab specifies the / partition as being ext3? You can't get away with having your root partition being a filesystem for which you must load a module to support. Unless you use initrd, but that's messy and not very failproof. -- .''`. Baloo [EMAIL PROTECTED] : :' :proud Debian admin and user `. `'` `- Debian - when you have better things to do than to fix a system msg17357/pgp0.pgp Description: PGP signature
Re: Kernel panic: VFS: Unable to mount root fs on 03:41
On 29 Jul 2002 19:25:37 +0200 Nils Gundelach [EMAIL PROTECTED] wrote: letzte Nacht habe ich bei einem Freund Woody mit CD's von Liniso (von Mitte April) installiert, mit Kernel 2.4.18, ext3 (fstab auch geändert) und ide-scsi. Anschließend habe ich apt-get update und apt-get upgrade übers Internet laufen lassen. So weit lief alles glatt. Die grosse Überraschung kam dann beim Reboot, es kam folgende Meldung: VFS Cannot open root device 341 or 03:41 Please append a correct root= boot option Kernel panic: VFS: Unable to mount root fs on 03:41 Hier hilft dann nur noch der Netzschalter. Daraufhin habe ich versucht, mit dem Kernel 2.2.20 zu starten, das geht bis zu: Starting system log dämon: syslogd Da wartet man dann bis zum St. Nimmerleinstag. Mit der Bootdiskette passiert das Gleiche. Mit der CD 3 und der Angabe von rescue root=/dev/hdb1 konnte ich dann zwar das System starten, aber leider brachte mich das auch nicht weiter. Eine Suche im Mailinglistenarchiv und mit Google brachte nichts Brauchbares. Also 03:41 ist ttyr9 $: ll /dev/ | egrep 3,\ *41 crw-rw-rw-1 root tty3, 41 25. Nov 2001 ttyr9 Ich glaube nicht das deine root Partition dort liegt. $: ll /dev/ | egrep hdb1$ brw-rw1 root disk 3, 65 25. Nov 2001 hdb1 Richtig wäre 03:65 Du mußt den root Parameter setzen. z.B. in lilo.conf root=/dev/hdb1 und lilo neu installieren alternativ kannst du ja mal mit rdev am kernel image rumspielen. Bye, Markus -- Jeder kann denken, aber vielen bleibt es erspart. -- Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Kernel panic: VFS: Unable to mount root fs on 03:41
Markus Liebl [EMAIL PROTECTED] writes: Nils Gundelach [EMAIL PROTECTED] wrote: Kernel panic: VFS: Unable to mount root fs on 03:41 Also 03:41 ist ttyr9 $: ll /dev/ | egrep 3,\ *41 crw-rw-rw-1 root tty3, 41 25. Nov 2001 ttyr9 Ich glaube nicht das deine root Partition dort liegt. Nein. Die Angabe 03:41 beim Booten ist hex und bedeutet deshalb major number = 3, minor number = 65, also hdb1. - hcz -- Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Kernel panic: VFS: Unable to mount root fs on 03:41
Hi, hast du vielleicht einen SCSI oder IDE Controller der nicht gefunden wird ? On Sun, 2002-07-28 at 22:20, Hermann Moser wrote: Hallo, letzte Nacht habe ich bei einem Freund Woody mit CD's von Liniso (von Mitte April) installiert, mit Kernel 2.4.18, ext3 (fstab auch geändert) und ide-scsi. Anschließend habe ich apt-get update und apt-get upgrade übers Internet laufen lassen. So weit lief alles glatt. Die grosse Überraschung kam dann beim Reboot, es kam folgende Meldung: VFS Cannot open root device 341 or 03:41 Please append a correct root= boot option Kernel panic: VFS: Unable to mount root fs on 03:41 Hier hilft dann nur noch der Netzschalter. Daraufhin habe ich versucht, mit dem Kernel 2.2.20 zu starten, das geht bis zu: Starting system log dämon: syslogd Da wartet man dann bis zum St. Nimmerleinstag. Mit der Bootdiskette passiert das Gleiche. Mit der CD 3 und der Angabe von rescue root=/dev/hdb1 konnte ich dann zwar das System starten, aber leider brachte mich das auch nicht weiter. Eine Suche im Mailinglistenarchiv und mit Google brachte nichts Brauchbares. Ein fsck -f -p /dev/hdb1 von einer SuSE aus brachte ebenfalls nichts. Ich vermute, dass ich irgendwo einen Fehler gemacht habe, bloss wo? Vielleicht kann mir hier jemand helfen, sonst fange ich nochmal von vorne an. Servus, Hermann -- registrierter Linux-User #260646 auf Debian GNU/Linux Woody 2.4.18 gruss, Nils -- My Key gpg --keyserver wwwkeys.eu.pgp.net --recv-key 45CD0073 Fingerprint = F4D9 9274 6ED8 B227 A62A 33FA 0D2E 2414 45CD 0073 http://www.darktec.org /|\ darkbit@IRCNet on #irc.de #linux.de Premature optimization is the root of all evil. - D. Knuth -- Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Kernel panic: VFS: Unable to mount root fs on 03:41
Hallo Nils, Am Montag, 29. Juli 2002 19:25 schrieb Nils Gundelach: hast du vielleicht einen SCSI oder IDE Controller der nicht gefunden wird ? Ein SCSI Controller ist nicht vorhanden, dass der IDE Controller nicht gefunden wird, glaube ich eher nicht, denn sonst würde ja der Kernel 2.2.20 nicht bis zum Start vom syslogd kommen, oder? Servus, Hermann -- registrierter Linux-User #260646 auf Debian GNU/Linux Woody 2.4.18 -- Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
RE: Kernel panic: VFS: Unable to mount root fs on 03:41
Hallo Hermann, wie ist denn das ext3 vorhanden, als Modul oder fest im Kernel? Initial ramdisk mal probiert? Hast Du per apt-get auch nen Kernelupdate gemacht? Wenn Du von einem 2.2er Kernel updatest, brauchst Du auch neue modutils, die gibts bei kernel.org, falls Du die aus irgendeinem Grund noch nicht haben solltest. Gruß Sebastian -- Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Kernel panic: VFS: Unable to mount root fs on 03:41
Hallo Sebastian, Am Sonntag, 28. Juli 2002 22:31 schrieb Sebastian Wolfgarten: wie ist denn das ext3 vorhanden, als Modul Ein cat /proc/filesystems ergab unter anderem auch ext3, ich habe mich beim Einrichten an die Anweisung auf channel.debian.de gehalten. Als ich bei mir Woody installiert habe, hat es ja auch geklappt. Und soweit ich weiss, ist ext3 beim 2.4.18 fest im Kernel. oder fest im Kernel? Initial ramdisk mal Initial ramdisk sagt mir jetzt nichts, was kann ich da probieren? probiert? Hast Du per apt-get auch nen Kernelupdate gemacht? Wenn Du von einem 2.2er Kernel updatest, brauchst Du auch neue modutils, die gibts bei Ich habe den Kernel 2.4.18 von CD installiert, das hat einwandfrei geklappt, danach Sound, ISDN und ide-scsi eingerichtet, die sources.list geändert, damit ich übers Netz updaten kann. Beim upgrade wurde auch ein neueres Kernelimage eingespielt, vielleicht habe ich da etwas vermurkst. Servus, Hermann registrierter Linux-User #260646 auf Debian GNU/Linux Woody 2.4.18 -- Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: kernel panic VFS: free block list corrupted
Revisa que en el BIOS no se encuentre Activado (Enabled) la opcion UDMA - Original Message - From: Antxoka Gerrikabeitia Uriarte [EMAIL PROTECTED] To: Lista de Usuarios Debian debian-user-spanish@lists.debian.org Sent: Thursday, April 04, 2002 3:12 PM Subject: kernel panic VFS: free block list corrupted Buenas noches lista. Esta manaña mientras intentaba instalar el Linux a un amigo he tenido en siguiente problema: Después de comenzar la instalación a la hora de comprobar los sectores defectuosos en las particiones creadas me daba en siguiente error: writing inode tables: 9/29 kernel panic VFS: free block list corrupted y la instalación se quedaba colgada. Hemos intentado hacer la partición con un disquete arranque de win98 y nos hemos sorprendido en que todo iba bien (antes he desecho todas las particiones creadas con cfdisk), nos ha creado una partición sin rechistar. Vuelta a empezar, y el mismo error, hasta que después de comer, a la tercera va la vencida creiamos ;) pues esta vez tampoco pero el error a sido otro, esta vez hemos saltado la comprobación de sectores defectuosos y cuando parecía que ibamos a avanzar nos ha dicho: hda:lost interrupt Si alguien me puede dar alguna pista se lo agradecería mucho, nosotros lo primero que hemos pensado a sido de que el disco duro esta estropeado pero el ver que el fdisk de MS-DOS no da problemas nos mosquea un poco. Decir también que el linux detecta correctamente el modelo del disco y todo eso, lo que también hemos visto a sido que en la BIOS (aunque ya se que el Linux no utiliza la BIOS para acceder al Disco duro) teniamos las siguientes opciones: Pri 1st IDE Bloc Mode : Disabled LBA Mode: Disable 32-bit transfer : Disable Hemos comprobado que poniendo estos valores a enabled al arrancar el ordenador da un error en el disco, aunque luego el linux lo detecte todo bien. Bien aquí la pregunta del inexperto es si puede ser que el linux (siendo de 32-bits y por eso de 32-bit transfer disable) trate de acceder al disco duro de una forma que el disco no entienda las intrucciones o así (no se si estoy diciendo una burrada o no). Como he dicho antes, cualquier ayuda sería de agradecer. Muchas gracias por escuchar y perdón por la chapa -- Antxoka Gerrikabeitia Uriarte [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Kernel Panic :VFS : Unable to mount root fs on 03:07
On Thu, Mar 28, 2002 at 09:24:24AM -0300, Warning Rancid wrote: Hola lista ... Aca esta exactamente lo que me dice el Kernel Panik Kernel Panic :VFS : Unable to mount root fs on 03:07 ok. no puede montar tu dispositivo raiz ( / ). puede ser que tu kernel no tenga soporte para el sistema de archivos que tenga /dev/hda7. lo habras incluido como modulo? te habra faltado un initrd? trata de arrancar con un diskette de arranque e instalar un kernel que antes te funcionara. saludos, Diego. El unico cambio que realize fue en el archivo fstab le puse noauto, a la Grabadora SCSI. Intente ponerle LILO boot: linux root=/dev/hda7 PEro me da lo mismo, intente poner esto porque hace unos mese me paso algo similar y lo pude arreglar con eso... Bueno Gracias a todos, y buen fin de semana Pisa09 Conectate a Internet GRATIS con Yahoo! Conexión: http://conexion.yahoo.com.ar -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Caminito al costado del mundo por ahí he de andar buscándome un rumbo ser socio de esta sociedad me puede matar. ... La Renga. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Kernel panic: VFS: Unable to mount root fs on 03:41
Sorry, I've found the problem my fault I was playing with ext3 about the time it came in the kernel and for some reason the filesystem was identified as ext3 but was ext2. Sorry again Nick
Re: kernel panic: vfs: unable to mount root fs install errror 01:00
On Sat, Jan 12, 2002 at 05:56:37PM -0800, justin cunningham wrote: I'm trying to get a server built with 2.2r4 potato cd and keep getting the above error. I tried the boot options in f2-f8 and tried mounting various root.bins from specifying floppy0 at boot: then got kernel panic: no init found try passing init= option to kernel. I looked up the errors on the deb user list and found similar questions but no answers. Have you tried booting from one of the other CDs? Each one has a different kernel, and they don't all work properly for all users. You might also like to try the woody installer instead. Nobody is doing active development on the potato disks any more. p.
Re: kernel panic: vfs: unable to mount root fs install errror 01:00
Thus spake Philip Blundell: On Sat, Jan 12, 2002 at 05:56:37PM -0800, justin cunningham wrote: I'm trying to get a server built with 2.2r4 potato cd and keep getting the above error. I tried the boot options in f2-f8 and tried mounting various root.bins from specifying floppy0 at boot: then got kernel panic: no init found try passing init= option to kernel. I looked up the errors on the deb user list and found similar questions but no answers. Have you tried booting from one of the other CDs? Each one has a different kernel, and they don't all work properly for all users. You might also like to try the woody installer instead. Nobody is doing active development on the potato disks any more. 01:00 is not an ide drive - it should 03:01 or something. I tsounds like you're trying to using an initrd image without having an /initrd. Try a boot kernel that doesn't use initrd. HTH, Steve -- George Washington was first in war, first in peace -- and the first to have his birthday juggled to make a long weekend. -- Ashley Cooper pgp7v4T9e8ElD.pgp Description: PGP signature
Re: Kernel Panic: VFS unable to mount root fs
El dom, 30 de dic de 2001, a las 05:56:27 +0100, Resman comento ... Hola a todos, He estado instalando una debian en un 486 con 16 MB de RAM. Empecé instalando una Potato (y todo fue bien) y después, con el sistema básico, me decidí a actualizarlo a Woody. Una vez más todo fue sin problemas. El caso es que digo, bueno pos vamos a instalar un nucleo 2.4, así que hago un apt-get install kernel-image-2.4.16-386. Entonces me avisa de que tengo que modificar el lilo.conf con una linea que sea initrd=/initrd. El caso es q la línea no era correcta pero mirando en la documentación y eso me entero de lo que es el initrd y le añado la línea correcta al lilo.conf (que era initrd=/boot/initrd.img-2.4.16-386). Con todo esto reinicio y kernel panic: VFS unable to mount root fs y, evidentemente, ahi se queda. Hola, solamente anotar que si haces more /proc/filesystems te salen los sistemas de ficheros que estan incluidos en el nucleo. dios -- Baltasar Perez (aka 'ponto') | ETSIT - ULPGC Powered by Debian GNU/Linux Woody (Nucleo 2.4.17 con ReiserFS) Linux user: #198228; Machine: #112080; Libranet: #84615 Las Palmas - Canary Islands - Spain good cw is music, Pat Nicholls VE3DZZ
Re: Kernel Panic: VFS unable to mount root fs
On 30 Dec 2001, Resman wrote: Hola a todos, He estado instalando una debian en un 486 con 16 MB de RAM. Empecé instalando una Potato (y todo fue bien) y después, con el sistema básico, me decidí a actualizarlo a Woody. Una vez más todo fue sin problemas. El caso es que digo, bueno pos vamos a instalar un nucleo 2.4, así que hago un apt-get install kernel-image-2.4.16-386. Entonces me avisa de que tengo que modificar el lilo.conf con una linea que sea initrd=/initrd. El caso es q la línea no era correcta pero mirando en la documentación y eso me entero de lo que es el initrd y le añado la línea correcta al lilo.conf (que era initrd=/boot/initrd.img-2.4.16-386). Con todo esto reinicio y kernel panic: VFS unable to mount root fs y, evidentemente, ahi se queda. He probado a pasarle al lilo root=/dev/hda3 (q es donde tengo instalado el /), en ponerle root=/dev/ram0 o root=/dev/rd/0 (según leí en la documentación del kernel), pero nada. En debian-user he encontrado problemas similares pero que, por lo visto, se han solucionado poniendo correctamente la linea initrd=, pero ese no es mi caso... En fin, que a ver si alguien me puede indicar algo, porque estoy muy intigrado con eso (no podré volver a dormir tranquilo hasta que no lo solucione :-P ). Ta luego. Por que no compilas un kernel tu mismo sin usar initrd? No creo que lo necesites. Xavier
Re: Kernel Panic: VFS unable to mount root fs
On Sun, 2001-12-30 at 10:56, Resman wrote: Con todo esto reinicio y kernel panic: VFS unable to mount root fs Suponiendo que tu partición root tenga ReiserFS, no será porque tenías ReiserFS compilado en el kernel 2.2.x, y en el 2.4.16 viene como módulo? -- - | | |Cronos | | |No confies en nadie mayor de treinta | | | |Email: [EMAIL PROTECTED] | |WWW: http://www.geocities.com/cronos1_mx/ - pgpmyS5h6pMUu.pgp Description: PGP signature
Re: Kernel Panic: VFS unable to mount root fs
El dom, 30-12-2001 a las 17:56, Resman escribió: Hola a todos, He estado instalando una debian en un 486 con 16 MB de RAM. Empecé instalando una Potato (y todo fue bien) y después, con el sistema básico, me decidí a actualizarlo a Woody. Una vez más todo fue sin problemas. El caso es que digo, bueno pos vamos a instalar un nucleo 2.4, así que hago un apt-get install kernel-image-2.4.16-386. Entonces me avisa de que tengo que modificar el lilo.conf con una linea que sea initrd=/initrd. El caso es q la línea no era correcta pero mirando en la documentación y eso me entero de lo que es el initrd y le añado la línea correcta al lilo.conf (que era initrd=/boot/initrd.img-2.4.16-386). Con todo esto reinicio y kernel panic: VFS unable to mount root fs eso es que no sabe como montar el sistema de archivos raiz, posiblemente tengas como modulo de kernel el soporte para ese sistema de archivos. y, evidentemente, ahi se queda. He probado a pasarle al lilo root=/dev/hda3 (q es donde tengo instalado el /), en ponerle root=/dev/ram0 o root=/dev/rd/0 (según leí en la documentación del kernel), pero nada. En debian-user he encontrado problemas similares pero que, por lo visto, se han solucionado poniendo correctamente la linea initrd=, pero ese no es mi caso... En fin, que a ver si alguien me puede indicar algo, porque estoy muy intigrado con eso (no podré volver a dormir tranquilo hasta que no lo solucione :-P ). Ta luego. ¿que sistema de archivos tiene hda3?, comprueba que ese sistema de archivos esté compilado dentro del kernel y no como modulo. -- -- Resman [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] pgpvfC1YGM92j.pgp Description: PGP signature
Re: Kernel Panic: VFS unable to mount root fs
El dom, 30-12-2001 a las 18:34, Dios del Tiempo escribió: On Sun, 2001-12-30 at 10:56, Resman wrote: Con todo esto reinicio y kernel panic: VFS unable to mount root fs Suponiendo que tu partición root tenga ReiserFS, no será porque tenías ReiserFS compilado en el kernel 2.2.x, y en el 2.4.16 viene como módulo? No, mi partición root es ext2 -- -- Resman [EMAIL PROTECTED]
Re: Kernel Panic: VFS unable to mount root fs
El dom, 30-12-2001 a las 18:54, Brain Killer escribió: eso es que no sabe como montar el sistema de archivos raiz, posiblemente tengas como modulo de kernel el soporte para ese sistema de archivos. ya, pero es que no lo he compilado yo, sino que es el kernel-image-2.4.16-386 de woody.. me extraña que tenga ese problema. ¿que sistema de archivos tiene hda3?, comprueba que ese sistema de archivos esté compilado dentro del kernel y no como modulo. hda3 tiene ext2 -- -- Resman [EMAIL PROTECTED]
Re: Kernel panic: VFS: unable to mount...
Ola pessoal, o problema estava no meu grub root (hd0,1) kernel=/vmlinuz root=/dev/hda == aqui estava o erro (deveria estar hda2) Em 28 Dec 2001, [EMAIL PROTECTED] escreveu: Ola pessoal, peguei recentemente os fontes do kernel 2.2.19 (apos a correcao do bug). apt-get install kernel-source-2.2.19 make xconfig make-kpkg clean make-kpkg -revision Custom1.2 kernel_image dpkg -i kernel*1.2* e quando estou compilando estou com problemas, quando o kernel inicia ele da kernel panic. a mensagem e a seguinte: .. .. Partition tables hda: hda1, hda2, hda3 hda5 Kernel panic: VFS: Unable to mount fs on 03:00 Bom eu inclui no kernel o suporte a Second Extended File Sistem (logico) tenho o windows, em hda1 e linux em hda2. Obs: com o boot floppy do kernel 2.2.19pre17 da tudo OK. Kleber _ Oi! Você quer um iG-mail gratuito? Então clique aqui: http://registro.ig.com.br/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- _ Oi! Você quer um iG-mail gratuito? Então clique aqui: http://registro.ig.com.br/
Re: Kernel panic: VFS: Unable to mount root fs on 01:00
Dell Latitude CPi D300XT 128MB Ram PII 300Mhz lilo.conf vga=1 append=apm=on default=Linux22 # kernel 2.4.12 image=/vmlinuz initrd=/boot/initrd label=LinuxNew read-only # kernel 2.4.10 image=/vmlinuz.old initrd=/boot/initrd-2.4.10-686 label=LinuxOld read-only # kernel 2.2.18pre image=/vmlinuz.2.2 label=Linux22 read-only Well, shoot. I cleaned up my lilo.conf, found a mistake when going over it this time and presto, the 2.4.12 kernel booted and the modules loaded but not pcmcia. Well, I take that back, the pcmcia_core module loaded, but not the module for my pcmcia NIC. In fact, here are the modules loaded by 2.2.18pre21 af_packet xirc2ps_cs serial_cs ds i82365 pcmcia_core serial nfs lockd sunrpc smbfs vfat unix And here are the modules loaded by 2.4.12 pcmcia_core nfs lockd sunrpc smbfs vfat fat rtc unix ide-disk ide-probe-mod ide-mod ext2 I tried to insmod i82365.o from /lib/modules/2.4.12-686/pcmcia and got i82365.o: unresolved symbol isapnp_find_dev_R7651deff . I got similar messages when try to load the other missing modules. = - [EMAIL PROTECTED] Hacking is a Good Thing! See http://www.tuxedo.org/~esr/faqs/hacker-howto.html No sure but looks like something to do with the fact that 2.4.x has Plug and Play support built in. Is there some module or kernel config option like isapnp or pnp? Maybe you got the isapnp tools which should be removed or configured otherwise for a 2.4.x kernels? Isn't there any reference in the kernel documentation? Perhaps there is a reference in the isapnp package docs? My 2.2.19pre17 has files that looks related: [14:33:07 tmp]$ ls /lib/modules/2.2.19pre17/*pnp* /lib/modules/2.2.19pre17/modules.isapnpmap /lib/modules/2.2.19pre17/modules.pnpbiosmap [14:34:14 tmp]$ Yet I have never touched them and I do not know how they are related. Hopefully someone else on debian-user can fill in the missing parts better then I can. -- Shaul Karl email: shaulka (replace these parenthesis with @) bezeqint, delete the comma and the white space characters and add .net
Re: Kernel panic: VFS: Unable to mount root fs on 01:00
--- Xeno Campanoli [EMAIL PROTECTED] wrote: Shaul Karl wrote: As my subject line indicates, I'm getting the diagnostic: Kernel panic: VFS: Unable to mount root fs on 01:00 when I try to boot up with my home grown kernel. I've tried several things with lilo on this, but I'm stumped. rdev indicates the root partition is /dev/hda1, which is what I expect, and I seem to have good lilo entries, as follows: image=/vmlinuz label=Linux read-only initrd=/boot/initrd Okay, you were right about initrd. I took that out and it works. Thank you. SNIP Now, I'm really confused. I haven't been able to get any of the 2.4.x debian kernel packages to boot and everything I had read previously in the list archives indicated that the initrd line was necessary for 2.4.x kernels. I never had any problems with 2.0.x or 2.2.x kernels. I never tried a 2.4.x kernel and I do not know if there is a default configuration for the 2.4.x debian kernel packages. In case there is none, could it be that you are expected to have ram disk support when configuring the 2.4.x debian kernel? And since you were asking, why won't you add more details about what you have done and where does the booting process stop? = - [EMAIL PROTECTED] Hacking is a Good Thing! See http://www.tuxedo.org/~esr/faqs/hacker-howto.html __ Do You Yahoo!? Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month. http://geocities.yahoo.com/ps/info1 -- Shaul Karl email: shaulka (replace these parenthesis with @) bezeqint, delete the comma and the white space characters and add .net
Re: Kernel panic: VFS: Unable to mount root fs on 01:00
--- Shaul Karl [EMAIL PROTECTED] wrote: --- Xeno Campanoli [EMAIL PROTECTED] wrote: Shaul Karl wrote: As my subject line indicates, I'm getting the diagnostic: Kernel panic: VFS: Unable to mount root fs on 01:00 when I try to boot up with my home grown kernel. I've tried several things with lilo on this, but I'm stumped. rdev indicates the root partition is /dev/hda1, which is what I expect, and I seem to have good lilo entries, as follows: image=/vmlinuz label=Linux read-only initrd=/boot/initrd Okay, you were right about initrd. I took that out and it works. Thank you. SNIP Now, I'm really confused. I haven't been able to get any of the 2.4.x debian kernel packages to boot and everything I had read previously in the list archives indicated that the initrd line was necessary for 2.4.x kernels. I never had any problems with 2.0.x or 2.2.x kernels. I never tried a 2.4.x kernel and I do not know if there is a default configuration for the 2.4.x debian kernel packages. In case there is none, could it be that you are expected to have ram disk support when configuring the 2.4.x debian kernel? And since you were asking, why won't you add more details about what you have done and where does the booting process stop? I will when I get home this evening. I've been down this road on the list before with no relief. I've been too busy doing some other stuff to go on a I've got to make this 2.4.x kernel work type binge, especially since my 2.2.x kernel is working nicely. I did however provide quite a few details on one of my attempts. In fact here is the message in the archives: http://lists.debian.org/debian-user/2001/debian-user-200110/msg00635.html I have since tried with a 2.4.10 and 2.4.12 kernel with the same results, and then I had problems with modules as well on the 2.4.12. But like I said, I will try again tonight and give more details. BTW, these problems were with the stock debian kernel packages. I haven't even tried to compile 2.4.x for myself yet using the traditional methods or the debian way. = - [EMAIL PROTECTED] Hacking is a Good Thing! See http://www.tuxedo.org/~esr/faqs/hacker-howto.html __ Do You Yahoo!? Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month. http://geocities.yahoo.com/ps/info1
Re: Kernel panic: VFS: Unable to mount root fs on 01:00
SNIP Now, I'm really confused. I haven't been able to get any of the 2.4.x debian kernel packages to boot and everything I had read previously in the list archives indicated that the initrd line was necessary for 2.4.x kernels. I never had any problems with 2.0.x or 2.2.x kernels. I never tried a 2.4.x kernel and I do not know if there is a default configuration for the 2.4.x debian kernel packages. In case there is none, could it be that you are expected to have ram disk support when configuring the 2.4.x debian kernel? And since you were asking, why won't you add more details about what you have done and where does the booting process stop? I will when I get home this evening. I've been down this road on the list before with no relief. I've been too busy doing some other stuff to go on a I've got to make this 2.4.x kernel work type binge, especially since my 2.2.x kernel is working nicely. I did however provide quite a few details on one of my attempts. In fact here is the message in the archives: http://lists.debian.org/debian-user/2001/debian-user-200110/msg00635.html I have since tried with a 2.4.10 and 2.4.12 kernel with the same results, and then I had problems with modules as well on the 2.4.12. But like I said, I will try again tonight and give more details. BTW, these problems were with the stock debian kernel packages. I haven't even tried to compile 2.4.x for myself yet using the traditional methods or the debian way. Dell Latitude CPi D300XT 128MB Ram PII 300Mhz lilo.conf vga=1 append=apm=on default=Linux22 # kernel 2.4.12 image=/vmlinuz initrd=/boot/initrd label=LinuxNew read-only # kernel 2.4.10 image=/vmlinuz.old initrd=/boot/initrd-2.4.10-686 label=LinuxOld read-only # kernel 2.2.18pre image=/vmlinuz.2.2 label=Linux22 read-only Well, shoot. I cleaned up my lilo.conf, found a mistake when going over it this time and presto, the 2.4.12 kernel booted and the modules loaded but not pcmcia. Well, I take that back, the pcmcia_core module loaded, but not the module for my pcmcia NIC. In fact, here are the modules loaded by 2.2.18pre21 af_packet xirc2ps_cs serial_cs ds i82365 pcmcia_core serial nfs lockd sunrpc smbfs vfat unix And here are the modules loaded by 2.4.12 pcmcia_core nfs lockd sunrpc smbfs vfat fat rtc unix ide-disk ide-probe-mod ide-mod ext2 I tried to insmod i82365.o from /lib/modules/2.4.12-686/pcmcia and got i82365.o: unresolved symbol isapnp_find_dev_R7651deff . I got similar messages when try to load the other missing modules. = - [EMAIL PROTECTED] Hacking is a Good Thing! See http://www.tuxedo.org/~esr/faqs/hacker-howto.html __ Do You Yahoo!? Buy the perfect holiday gifts at Yahoo! Shopping. http://shopping.yahoo.com
Re: Kernel panic: VFS: Unable to mount root fs on 01:00
quote who=Xeno Campanoli As my subject line indicates, I'm getting the diagnostic: Kernel panic: VFS: Unable to mount root fs on 01:00 i would say the #1 cause of this is lack of support for the disk controller which the root drive is hooked to compiled into the kernel(it can't be a module). first thing to check is to see if the drive is detected on boot ...if it is we can go from there.. also make sure the filesystem your using is compiled into the kernel. nate
Re: Kernel panic: VFS: Unable to mount root fs on 01:00
Make sure that you have compiled the ide and ext2 into the kernel and not just made them loadable mods. Xeno Campanoli wrote: Subject: Kernel panic: VFS: Unable to mount root fs on 01:00 From: Xeno Campanoli [EMAIL PROTECTED] Date: Thu, 29 Nov 2001 14:57:45 -0800 To: debian-user@lists.debian.org As my subject line indicates, I'm getting the diagnostic: Kernel panic: VFS: Unable to mount root fs on 01:00when I try to boot up with my home grown kernel. I've tried severalthings with lilo on this, but I'm stumped. rdev indicates the rootpartition is /dev/hda1, which is what I expect, and I seem to have goodlilo entries, as follows:image=/vmlinuzlabel=Linuxread-onlyinitrd=/boot/initrdand in fact with the dist kernel this lilo entry works fine, but withthe one I get with make bzImage I get stuck on boot as stated. Cansomeone point me to a specific doc to read on this problem, or is mymistake obvious?-- http://www.eskimo.com/~xeno[EMAIL PROTECTED]-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Kernel panic: VFS: Unable to mount root fs on 01:00
As my subject line indicates, I'm getting the diagnostic: Kernel panic: VFS: Unable to mount root fs on 01:00 when I try to boot up with my home grown kernel. I've tried several things with lilo on this, but I'm stumped. rdev indicates the root partition is /dev/hda1, which is what I expect, and I seem to have good lilo entries, as follows: image=/vmlinuz label=Linux read-only initrd=/boot/initrd and in fact with the dist kernel this lilo entry works fine, but with the one I get with make bzImage I get stuck on boot as stated. Can someone point me to a specific doc to read on this problem, or is my mistake obvious? -- http://www.eskimo.com/~xeno [EMAIL PROTECTED] The mistake is not obvious to me. Just guessing: (1) Are you sure you need the initrd line? Do you actually have /boot/initrd? This line is not shown in /usr/share/doc/lilo/examples/conf.sample. (2) Have you run lilo after you installed the new kernel and before you rebooted? (3) Does the fs driver for the root device in the new kernel compiled as a module? (4) Could it be that you have not installed the new kernel properly? One way to avoid this is to use Debian kernel-package. -- Shaul Karl email: shaulka (replace these parenthesis with @) bezeqint, delete the comma and the white space characters and add .net
Re: Kernel panic: VFS: Unable to mount root fs on 01:00
Shaul Karl wrote: As my subject line indicates, I'm getting the diagnostic: Kernel panic: VFS: Unable to mount root fs on 01:00 when I try to boot up with my home grown kernel. I've tried several things with lilo on this, but I'm stumped. rdev indicates the root partition is /dev/hda1, which is what I expect, and I seem to have good lilo entries, as follows: image=/vmlinuz label=Linux read-only initrd=/boot/initrd Okay, you were right about initrd. I took that out and it works. Thank you. Now however I have another problem with two of my four NIC drivers not showing up in dmesg. I'll start another thread for that one. Sincerely, Xeno -- Shaul Karl email: shaulka (replace these parenthesis with @) bezeqint, delete the comma and the white space characters and add .net -- http://www.eskimo.com/~xeno [EMAIL PROTECTED]
Re: Kernel panic: VFS: Unable to mount root fs on 01:00
--- Xeno Campanoli [EMAIL PROTECTED] wrote: Shaul Karl wrote: As my subject line indicates, I'm getting the diagnostic: Kernel panic: VFS: Unable to mount root fs on 01:00 when I try to boot up with my home grown kernel. I've tried several things with lilo on this, but I'm stumped. rdev indicates the root partition is /dev/hda1, which is what I expect, and I seem to have good lilo entries, as follows: image=/vmlinuz label=Linux read-only initrd=/boot/initrd Okay, you were right about initrd. I took that out and it works. Thank you. SNIP Now, I'm really confused. I haven't been able to get any of the 2.4.x debian kernel packages to boot and everything I had read previously in the list archives indicated that the initrd line was necessary for 2.4.x kernels. I never had any problems with 2.0.x or 2.2.x kernels. = - [EMAIL PROTECTED] Hacking is a Good Thing! See http://www.tuxedo.org/~esr/faqs/hacker-howto.html __ Do You Yahoo!? Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month. http://geocities.yahoo.com/ps/info1
Re: Kernel panic: VFS: Unable to mount root fs on 01:00
Thus spake Charles Baker: --- Xeno Campanoli [EMAIL PROTECTED] wrote: Shaul Karl wrote: As my subject line indicates, I'm getting the diagnostic: Kernel panic: VFS: Unable to mount root fs on 01:00 when I try to boot up with my home grown kernel. I've tried several things with lilo on this, but I'm stumped. rdev indicates the root partition is /dev/hda1, which is what I expect, and I seem to have good lilo entries, as follows: image=/vmlinuz label=Linux read-only initrd=/boot/initrd Okay, you were right about initrd. I took that out and it works. Thank you. SNIP Now, I'm really confused. I haven't been able to get any of the 2.4.x debian kernel packages to boot and everything I had read previously in the list archives indicated that the initrd line was necessary for 2.4.x kernels. I never had any problems with 2.0.x or 2.2.x kernels. Not _necessary_ but an option. I personally don't use the initrd method with my kernels, as I found the boost in boot time to be negligable and therefor more trouble than it was worth, but I don't use the make-kpkg method, it may be easier. You can use it or not, is what I have found - neither is 'The Right Way'(TM) although the make-kpkg way is 'The Dbian Way'(TM) and I am _not_ advising against, just throwing in my 2¢. HTH, Steve -- Boucher's Observation: He who blows his own horn always plays the music several octaves higher than originally written. pgpHAnpAO0dDX.pgp Description: PGP signature
Re: Kernel Panic: VFS Unable to mount root fs on 21:04
On Sat, Oct 06, 2001 at 02:17:20PM -0400, Stan Brown wrote: I'm trying to set up a new machine this weekend, and i'm in trouble. I know you needed a solution by Monday, so this is a bit late, but I haven't seen anyone else post an explanation of what the error actually means, so... Now, I have a problem. The machine will no longer boot from the hard disk. I get the message from the subject line. I can boot it from the boot floppy. lilo (or something else) is telling the kernel to mount / from device 21:04 and the kernel doesn't know how to do that. According to Documentation/devices.txt in my kernel source tree, major device 21 is the generic SCSI subsystem and minor device 04 in that system is the fifth device, so 21:04 would be /dev/sg4 (or /dev/sge). Either a) you don't have generic SCSI support in your kernel, b) you don't have five generic SCSI devices, or c) you have to boot off a SCSI drive (/dev/sd*), not a generic SCSI device (/dev/sg*). Although a) and b) are both possible, I suspect that c) is also true, so your machine will continue to fail to boot until you tell it to use a device of the correct type. During the install of the 2.4 kernel package. I goot a message about needing to add a initrd line to lilo.conf. That's really only necessary if you use the stock kernel or roll your own and have certain things built as modules; I know filesystem drivers fall into this category, but can't say what else does. I don't use modules much, so I haven't had to deal with initrd. -- When we reduce our own liberties to stop terrorism, the terrorists have already won. - reverius Innocence is no protection when governments go bad. - Mr. Slippery
Re: Kernel Panic: VFS Unable to mount root fs on 21:04
During the install of the 2.4 kernel package. I goot a message about needing to add a initrd line to lilo.conf. This is probably the cause of your problem. I had the same problem the first time I installed a 2.4 kernel package with apt-get. Just follow the instructions and edit your lilo.conf file to point to the initrd file and your machine should work again. HTH
Re: Kernel Panic: VFS Unable to mount root fs on 21:04
- Original Message - From: Dave Sherohman [EMAIL PROTECTED] To: Debian User List debian-user@lists.debian.org Sent: Monday, October 08, 2001 4:52 PM Subject: Re: Kernel Panic: VFS Unable to mount root fs on 21:04 On Sat, Oct 06, 2001 at 02:17:20PM -0400, Stan Brown wrote: I'm trying to set up a new machine this weekend, and i'm in trouble. I know you needed a solution by Monday, so this is a bit late, but I haven't seen anyone else post an explanation of what the error actually means, so... Now, I have a problem. The machine will no longer boot from the hard disk. I get the message from the subject line. I can boot it from the boot floppy. lilo (or something else) is telling the kernel to mount / from device 21:04 and the kernel doesn't know how to do that. According to Documentation/devices.txt in my kernel source tree, major device 21 is the generic SCSI subsystem and minor device 04 in that system is the fifth device, so 21:04 would be /dev/sg4 (or /dev/sge). Either a) you don't have generic SCSI support in your kernel, b) you don't have five generic SCSI devices, or c) you have to boot off a SCSI drive (/dev/sd*), not a generic SCSI device (/dev/sg*). Hmm, maybe the kernel has no support for your scsi card/devices, yes. BTW, probably the magic number written to the real-root-dev file is the magic number description for your root device (every device in Linux can be described by such a number combination - for the numbering system see attached file devices.txt, the format in the real-root-dev file is for example for /dev/hdb1: 0x365). Cheers, Stephan attachment: devices.zip
Re: Kernel Panic: VFS Unable to mount root fs on 21:04
- Original Message - From: Stan Brown [EMAIL PROTECTED] To: Debian User List debian-user@lists.debian.org Sent: Saturday, October 06, 2001 8:17 PM Subject: Kernel Panic: VFS Unable to mount root fs on 21:04 I'm trying to set up a new machine this weekend, and i'm in trouble. I installed a minimal stable over the network. then upgraded to Progeny. Then I wen to istall the 2.4 kernel packages from http://people.debian.org/~bunk (thanks for the good work on these BTW). Now, I have a problem. The machine will no longer boot from the hard disk. I get the message from the subject line. I can boot it from the boot floppy. During the install of the 2.4 kernel package. I goot a message about needing to add a initrd line to lilo.conf. It sufested puting a line in /etc/kern-img.conf (from memory). I have tried this, and also tried adding the sugested initrd line to /etc/lilo.conf. But nieht gets me to the point where I can boot from the hard disk. Help Please! Hi! Have you called the command lilo once at the command line after changing lilo.conf? Maybe that'll do it. Cheers, Stephan
Re: Kernel Panic!..VFS.....
Hi, Mark! Problems solved, thanks! I found what happened to lead to the problem was - I changed the hard disk from secondary master to primary master, lilo was looking for '/' in /dev/hdc5, rather /dev/hda5. From your tips, I first tried to put 'rescue root=/dev/hda5' at the boot prompt when the rescue disk was loaded. Then typed in the root password to doo the maintenance jobs. But the system did not allow me to edit any files at all. It was still looking for /dev/hdc5 and /dev/hdc6 (swap partition). So, I used the rescue disk and the root disk to mount the '/' fs and edit the /etc/lilo.conf, fstab and mtab where all hdc were changed to hda. And this time, it worked! Thank you very for deciphering the meaning of the numbers in the error message so that I understand what was the problem and find the right direction to fix it. Best regards, Wilson : ) Mark Suter wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Wilson, Yes, thank you for reminding me the missing bits (The machine with broken O/S is not with me at the moment, I'm sorry that I have not jotted them down properly). Now, presuming what you said is right and once I've checked out the number,x in the error message VFS: Unable to mount root fs on 3:0x. What command should I do to fix the problem and get the O/S back to live? The basic procedure to fix most boot problems is easy to describe. The devil is in the details ;) 1) Boot the system by manually specifying the root fs. 2) Reconfigure your boot method with correct the root fs. 3) Reboot to be certain that you have fixed the problem. Based on what you wrote about using the rescue disk, I believe you are able to boot this system manually. Step 2 is should be editing /etc/lilo.conf and running /sbin/lilo - you should ensure the boot= and root= lines are correct. Yours sincerely, - -- Mark John Suter | I know that you believe you understand [EMAIL PROTECTED] | what you think I said, but I am not sure GPG key id F2FEBB36 | you realise that what you heard is not Ph: +61 4 1126 2316 | what I meant. anonymous -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.1 (GNU/Linux) Comment: Public key available from Keyservers or http://www.uq.edu.au/~suter/ iD8DBQE5RPEF7EsZXfL+uzYRAu6tAJ9ATaJ/k61Brws1TJuo+Y5QmN30+wCghjWx j/8y6KoAGeAEQI+qeqsN65g= =jcXd -END PGP SIGNATURE- -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: Kernel Panic!..VFS.....
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Wilson, When my machine boots up, Linux is auto-probing the hardware, then it stops and pops up an error message Kernel Panic..VFS I tried to use a 'rescue' disk and did the e2fsck, but it said the '/' partition was clean. I could mount the '/' partition and navigate the directories, but just can't boot up? What could be wrong? It is probable that the filesystem you tested is not the same one the kernel is trying to mount as the root filesystem. The error message should include the filesystem that was being tested, as in the following example. VFS: Unable to mount root fs on 3:05 These numbers, 3 and 5, are the major and minor device numbers, that is /dev/hda5, as follows $ ls -l /dev/hda? brw-rw1 root disk 3, 1 Mar 29 15:25 /dev/hda1 brw-rw1 root disk 3, 2 Mar 29 15:25 /dev/hda2 brw-rw1 root disk 3, 3 Mar 29 15:25 /dev/hda3 brw-rw1 root disk 3, 4 Mar 29 15:25 /dev/hda4 brw-rw1 root disk 3, 5 Mar 29 15:25 /dev/hda5 brw-rw1 root disk 3, 6 Mar 29 15:25 /dev/hda6 brw-rw1 root disk 3, 7 Mar 29 15:25 /dev/hda7 brw-rw1 root disk 3, 8 Mar 29 15:25 /dev/hda8 brw-rw1 root disk 3, 9 Mar 29 15:25 /dev/hda9 Yours sincerely, - -- Mark John Suter | I know that you believe you understand [EMAIL PROTECTED] | what you think I said, but I am not sure GPG key id F2FEBB36 | you realise that what you heard is not Ph: +61 4 1126 2316 | what I meant. anonymous -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.1 (GNU/Linux) Comment: Public key available from Keyservers or http://www.uq.edu.au/~suter/ iD8DBQE5RNeb7EsZXfL+uzYRAk4KAJwLxMXjeGaGgGYTHsIrn3wrWhYfkwCfWWik NRup/oPb3b+hB/TcMj+lkbg= =OIUv -END PGP SIGNATURE-
Re: Kernel Panic!..VFS.....
Mark, Yes, thank you for reminding me the missing bits (The machine with broken O/S is not with me at the moment, I'm sorry that I have not jotted them down properly). Now, presuming what you said is right and once I've checked out the number,x in the error message VFS: Unable to mount root fs on 3:0x. What command should I do to fix the problem and get the O/S back to live? Cheers, Wilson Mark Suter wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Wilson, When my machine boots up, Linux is auto-probing the hardware, then it stops and pops up an error message Kernel Panic..VFS I tried to use a 'rescue' disk and did the e2fsck, but it said the '/' partition was clean. I could mount the '/' partition and navigate the directories, but just can't boot up? What could be wrong? It is probable that the filesystem you tested is not the same one the kernel is trying to mount as the root filesystem. The error message should include the filesystem that was being tested, as in the following example. VFS: Unable to mount root fs on 3:05 These numbers, 3 and 5, are the major and minor device numbers, that is /dev/hda5, as follows $ ls -l /dev/hda? brw-rw1 root disk 3, 1 Mar 29 15:25 /dev/hda1 brw-rw1 root disk 3, 2 Mar 29 15:25 /dev/hda2 brw-rw1 root disk 3, 3 Mar 29 15:25 /dev/hda3 brw-rw1 root disk 3, 4 Mar 29 15:25 /dev/hda4 brw-rw1 root disk 3, 5 Mar 29 15:25 /dev/hda5 brw-rw1 root disk 3, 6 Mar 29 15:25 /dev/hda6 brw-rw1 root disk 3, 7 Mar 29 15:25 /dev/hda7 brw-rw1 root disk 3, 8 Mar 29 15:25 /dev/hda8 brw-rw1 root disk 3, 9 Mar 29 15:25 /dev/hda9 Yours sincerely, - -- Mark John Suter | I know that you believe you understand [EMAIL PROTECTED] | what you think I said, but I am not sure GPG key id F2FEBB36 | you realise that what you heard is not Ph: +61 4 1126 2316 | what I meant. anonymous -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.1 (GNU/Linux) Comment: Public key available from Keyservers or http://www.uq.edu.au/~suter/ iD8DBQE5RNeb7EsZXfL+uzYRAk4KAJwLxMXjeGaGgGYTHsIrn3wrWhYfkwCfWWik NRup/oPb3b+hB/TcMj+lkbg= =OIUv -END PGP SIGNATURE-
Re: Kernel Panic!..VFS.....
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Wilson, Yes, thank you for reminding me the missing bits (The machine with broken O/S is not with me at the moment, I'm sorry that I have not jotted them down properly). Now, presuming what you said is right and once I've checked out the number,x in the error message VFS: Unable to mount root fs on 3:0x. What command should I do to fix the problem and get the O/S back to live? The basic procedure to fix most boot problems is easy to describe. The devil is in the details ;) 1) Boot the system by manually specifying the root fs. 2) Reconfigure your boot method with correct the root fs. 3) Reboot to be certain that you have fixed the problem. Based on what you wrote about using the rescue disk, I believe you are able to boot this system manually. Step 2 is should be editing /etc/lilo.conf and running /sbin/lilo - you should ensure the boot= and root= lines are correct. Yours sincerely, - -- Mark John Suter | I know that you believe you understand [EMAIL PROTECTED] | what you think I said, but I am not sure GPG key id F2FEBB36 | you realise that what you heard is not Ph: +61 4 1126 2316 | what I meant. anonymous -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.1 (GNU/Linux) Comment: Public key available from Keyservers or http://www.uq.edu.au/~suter/ iD8DBQE5RPEF7EsZXfL+uzYRAu6tAJ9ATaJ/k61Brws1TJuo+Y5QmN30+wCghjWx j/8y6KoAGeAEQI+qeqsN65g= =jcXd -END PGP SIGNATURE-
RE: kernel panic: VFS: Unable to mount root fs on 03:06
Ese problema suele ocurrir si, al compilar el kernel, se selecciona (en filesystems) el ext2fs como modulo, que no puede ser. El ext2fs tiene que incluirse directamente en el kernel, no como modulo Miguel Gracias por tu rápida respuesta. Era lo de hacer como módulo el ext2fs. Le he comentado a Barbie que el otro día me comentaba uno que trabaja para Mocosoft que no teníamos soporte técnico detrás. Pues que venga Dios y lo vea. La pena que me queda es el no haber consultado antes.. Gracias Juanma
Re: kernel panic: VFS: Unable to mount root fs on 03:06
Si puedes seguir botando con el kernel antiguo pero no con el nuevo, seguramente se te ha olvidado ejectuar 'lilo' a secas después de haber modifcado el 'lilo.conf' El día 23/02/00 Juanma decía: Estimados amigos: Llevo una semana desesperado pues quiero compilar el kernel a la versión 2.2.12, es la que tengo disponible aunque me imagino que habrá otra más reciente. La antigua es 2.0.36. Pues bien cuando termino de compilar, modifico el lilo (con cuidado de no eliminar la antigua configuración) e intento cargar la nueva. No se que haré mal pero al final me da estos mensajer: Partition check request_module [ide- disk] :root fs not mounted hda: driver not present VFS: can not open root device 03:06 kernel panic: VFS: Unable to mount root fs on 03:06 y se detiene. -- La mayoría de los caminos mas transitados no conducen a ninguna parte. -- Primera Regla de Patología.
Re: kernel panic: VFS: Unable to mount root fs on 03:06
Ese problema suele ocurrir si, al compilar el kernel, se selecciona (en filesystems) el ext2fs como modulo, que no puede ser. El ext2fs tiene que incluirse directamente en el kernel, no como modulo Miguel Barbie Dominatrix wrote: Si puedes seguir botando con el kernel antiguo pero no con el nuevo, seguramente se te ha olvidado ejectuar 'lilo' a secas después de haber modifcado el 'lilo.conf' El día 23/02/00 Juanma decía: Estimados amigos: Llevo una semana desesperado pues quiero compilar el kernel a la versión 2.2.12, es la que tengo disponible aunque me imagino que habrá otra más reciente. La antigua es 2.0.36. Pues bien cuando termino de compilar, modifico el lilo (con cuidado de no eliminar la antigua configuración) e intento cargar la nueva. No se que haré mal pero al final me da estos mensajer: Partition check request_module [ide- disk] :root fs not mounted hda: driver not present VFS: can not open root device 03:06 kernel panic: VFS: Unable to mount root fs on 03:06 y se detiene. -- La mayoría de los caminos mas transitados no conducen a ninguna parte. -- Primera Regla de Patología. -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null -- = Miguel Rodriguez Penabad[EMAIL PROTECTED] Laboratorio de Bases de Datos http://emilia.dc.fi.udc.es/labBD Facultade de InformáticaUniversidade da Coruña (Spain) Debian 2.1 [2.2.13] Usuario Linux 124962 =
Re: kernel panic: VFS: Unable to mount root fs on 03:06
On Wed, 23 Feb 2000, Miguel Rodriguez Penabad wrote: Ese problema suele ocurrir si, al compilar el kernel, se selecciona (en filesystems) el ext2fs como modulo, que no puede ser. El ext2fs tiene que incluirse directamente en el kernel, no como modulo Miguel Barbie Dominatrix wrote: [...] El día 23/02/00 Juanma decía: [...] Partition check request_module [ide- disk] :root fs not mounted hda: driver not present VFS: can not open root device 03:06 kernel panic: VFS: Unable to mount root fs on 03:06 En este caso en particular, lo que parece es que no hay soporte para discos IDE en el núcleo. Juanma: compruébalo y a ver si es eso. -- Eloy _ Eloy Rafael Sanz Tapia -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] - -- http://www.uco.es/~ma1satae -- --- GPG ID: 190169A0 / finger [EMAIL PROTECTED] -- Córdoba _ España ___ Debian 2.1 GNU/Linux 2.2.13 rabinf50
Re: Kernel panic VFS ...
At 01:54 AM 10/22/99 +0200, Jocke wrote: Hi all, I did something stupid today :( While recompiling my kernel to add scsi support for my cdrw I accidently forgot some ide stuff and now I can't boot. If you want to change something important like a...*hmmm* a kernel or something ALWAYS make lilo PROMPT you for a kernel! So you can ALWAYS boot the OLD one and TEST the new one. Also make always a custom boot flop when you install Debian (it is an installation option ;-) These two precautions can make your life a whole lot easier. For your problem you can use the standard rescue flop. Mount your HD and repair your mistake... Onno
