Kernel Panic: VFS: Unable to mount root fs on 08:03
Ok, fiz besteira. Acabei de instalar o Debian (Woody r3)pela primeira vez, e estava tentando atualizar o kernel. Rodei o comando apt-get install kernel-2.4.18-1-k7, e em algum ponto, quando ele falava algo sobre o LILO eu respondi sim, e acho que devia ter respondido não... Depois rodei /sbin/lilo Aí veio esse problema... Tenho um Athlon e estou rodando o VMWare Workstation 5, com a configuração para um Linux Kernel 2.4 Já tentei dar boot pelo CD e rodar rescbf24 root=dev/sda3 (que é minha partição root) mas não consigo, e não consigo dar boot de nenhuma outra maneira. Alguém poderia me indicar um HOWTO ou uma solução para isso? Eu sou totalmente novato em Linux, e acho que vou precisar de algo bem detalhado. Obrigado.
Re: after power outage: Kernel panic: VFS: unable to mount root fs :(
How do I interpret 03:04? If I boot off the boot floppy, everything is It's /dev/hda4 (the 3 and 4 are the major and minor numbers; do 'ls -ld /dev/hda4' to see this). fine. Have poked around for answers in the archives, but haven't figured it out. boot drive: hda1 - /boot hda2 - swap hda3 - / second disk: hdd1 - /disk1 But you don't have an hda4? What's in your lilo.conf or menu.lst (for lilo or grub respectively) and what's in fstab? Alexis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: after power outage: Kernel panic: VFS: unable to mount root fs :(
On Thu, 21 Oct 2004 09:22:40 + (UTC), Alexis Huxley [EMAIL PROTECTED] wrote: How do I interpret 03:04? If I boot off the boot floppy, everything is It's /dev/hda4 (the 3 and 4 are the major and minor numbers; do 'ls -ld /dev/hda4' to see this). fine. Have poked around for answers in the archives, but haven't figured it out. boot drive: hda1 - /boot hda2 - swap hda3 - / second disk: hdd1 - /disk1 But you don't have an hda4? What's in your lilo.conf or menu.lst (for lilo or grub respectively) and what's in fstab? # lilo.conf (snippets - not showing lot of commented out stuff from default lilo) # Support LBA for large hard disks. lba32 boot=/dev/hda root=/dev/hda3 install=/boot/boot-menu.b map=/boot/map delay=20 vga=normal default=Linux image=/vmlinuz label=Linux read-only # restricted # alias=1 image=/vmlinuz.old label=LinuxOLD read-only optional # restricted # alias=2 ~ # /etc/fstab: static file system information. # # file system mount point type options dump pass /dev/hda3 / ext2errors=remount-ro 0 1 /dev/hda2 noneswapsw 0 0 proc/proc procdefaults0 0 /dev/fd0/floppy autouser,noauto 0 0 /dev/cdrom /cdrom iso9660 ro,user,noauto 0 0 /dev/hda1 /boot ext2defaults0 2 /dev/hdd2 /disk1 ext2errors=remount-ro 0 1 I didn't see anything suspicious here and haven't edited these files recently. Royce -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
after power outage: Kernel panic: VFS: unable to mount root fs :(
Had a power outage, and when I brought my Debian 3 system back up it was hosed: --- EXT2-fs: unable to read superblock Attempt to access beyond device . . . FAT bread failed Invalid session number or type of track . . . Kernel panic: VFS: unable to mount root fs on 03:04 --- How do I interpret 03:04? If I boot off the boot floppy, everything is fine. Have poked around for answers in the archives, but haven't figured it out. boot drive: hda1 - /boot hda2 - swap hda3 - / second disk: hdd1 - /disk1 Thanks in advance for any tips, Royce -- 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!!
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 #
RES: Kernel Panic: VFS : Unable to mount root fs -AJUDA!!
Olá, Obrigado pela ajuda que vocês tem dado! Creio que eu devo ter tirado suporte ao MINIX por não saber a que se refere (poderia ser isso o gerador do problema??) Eu deixei somente suporte ao ext3 como built-in... Em anexo, estou enviando o meu .config para vocês darem uma avaliada :) Obrigado pela força, Arthur Tupinambá -Mensagem original- De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Enviada em: sábado, 18 de setembro de 2004 11:42 Para: debian-user-portuguese@lists.debian.org Assunto: 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 .configUSING Description: Binary data
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
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]
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: RES: Kernel Panic: VFS : Unable to mount root fs -AJUDA!!
Arthur; * Musashi corta a msg que Arthur Tupinambá enviou para Still: Nelson e Rubens, Obrigado! Ao Nelson: - Como estou trabalhando, mandarei meu .config à noite para vocês avaliarem... (obrigado pela paciencia) - Fiz alguns testes com o initrd, mas achei muito porco, até onde eu sei, ele carrega modulos para que seja carregado o kernel certo? Se incluirmos tudo built-in não há essa necessidade correto??? - Eu utilizo grub... Abaixo segue minha config: title Debian 2.6.8.1 root (hd0,1) kernel /boot/vmlinuz-2.6.8.1 root=/dev/hda2 ro boot Ao Rubens: - Eu andei lendo e vi que essas opções de IDE/Chipsets estão um pouco chatinhas mesmo Você está utilizando o initrd também ou não precisou??? Bom, o meu grub está diferente do seu por causa do initrd: title Leah Debian GNU/Linux - kernel 2.6.8 kernel /boot/vmlinuz-2.6.8 ro root=/dev/hda1 vga=791 splash=silent\ hdc=ide-scsi hdd=ide-scsi initrd /boot/initrd.splash Só por curiosidade, vc instalou o grub no /dev/hda2 ao invés da MBR, não ? []'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
RES: RES: Kernel Panic: VFS : Unable to mount root fs -AJUDA!!
Não, instalei o Grub na MBR porque? isso implica em alguma coisa?? Eu preciso fazer um initrd ??? com o make-dpkg kernel_image --initrd , ele menciona um erro de cramfs e pergunta se realmente eu quero continuar.. por isso pergunto se é realmente preciso o initrd... Obrigado, Arthur -Mensagem original- De: Nelson Luiz Campos [mailto:[EMAIL PROTECTED] Enviada em: sexta-feira, 17 de setembro de 2004 15:49 Para: debian-user-portuguese@lists.debian.org Assunto: Re: RES: Kernel Panic: VFS : Unable to mount root fs -AJUDA!! Arthur; * Musashi corta a msg que Arthur Tupinambá enviou para Still: Nelson e Rubens, Obrigado! Ao Nelson: - Como estou trabalhando, mandarei meu .config à noite para vocês avaliarem... (obrigado pela paciencia) - Fiz alguns testes com o initrd, mas achei muito porco, até onde eu sei, ele carrega modulos para que seja carregado o kernel certo? Se incluirmos tudo built-in não há essa necessidade correto??? - Eu utilizo grub... Abaixo segue minha config: title Debian 2.6.8.1 root (hd0,1) kernel /boot/vmlinuz-2.6.8.1 root=/dev/hda2 ro boot Ao Rubens: - Eu andei lendo e vi que essas opções de IDE/Chipsets estão um pouco chatinhas mesmo Você está utilizando o initrd também ou não precisou??? Bom, o meu grub está diferente do seu por causa do initrd: title Leah Debian GNU/Linux - kernel 2.6.8 kernel /boot/vmlinuz-2.6.8 ro root=/dev/hda1 vga=791 splash=silent\ hdc=ide-scsi hdd=ide-scsi initrd /boot/initrd.splash Só por curiosidade, vc instalou o grub no /dev/hda2 ao invés da MBR, não ? []'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
Re: RES: Kernel Panic: VFS : Unable to mount root fs -AJUDA!!
Olá Arthur, On Fri, Sep 17, 2004 at 03:00:32PM -0300, Arthur Tupinambá wrote: Ao Rubens: - Eu andei lendo e vi que essas opções de IDE/Chipsets estão um pouco chatinhas mesmo Você está utilizando o initrd também ou não precisou??? Não estou a utilizar o initrd. Boa sorte. -- Rúben Leote Mendes - [EMAIL PROTECTED]
Re: RES: RES: Kernel Panic: VFS : Unable to mount root fs -AJUDA!!
Arthur; * Musashi corta a msg que Arthur Tupinambá enviou para Still: Não, instalei o Grub na MBR porque? isso implica em alguma coisa?? Eu preciso fazer um initrd ??? com o make-dpkg kernel_image --initrd , ele menciona um erro de cramfs e pergunta se realmente eu quero continuar.. por isso pergunto se é realmente preciso o initrd... Bom, aqui para criar o initrd eu fiz, dá primeira vez: mkinitrd -o /boot/initrd Só que depois que instalei o bootsplash, eu o mudei coforme está no site http://www.bootsplash.org Quanto ao root (hd0,1), não tenho certeza se está certo, mas provavelmente está. Tente criar o initrd com o comando acima e diga o que acontece. []'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 -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: RES: Kernel Panic: VFS : Unable to mount root fs -AJUDA!!
Arthur; * Musashi corta a msg que Arthur Tupinambá enviou para Still: minha fstab está montado para ext3... você precisou utilizar o initrd ??? já to perdido de tanto q compilei e não funcionou.. Mande o seu .config do seu kernel para podermos avaliar. Outra coisa, vc usa o lilo ou o grub ? Como está a linha para chamar o initrd ? Está apontando para onde ? Existe o arquivo initrd ? []'s, -- 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
RES: Kernel Panic: VFS : Unable to mount root fs -AJUDA!!
minha fstab está montado para ext3... você precisou utilizar o initrd ??? já to perdido de tanto q compilei e não funcionou.. -Mensagem original- De: Nelson Luiz Campos [mailto:[EMAIL PROTECTED] Enviada em: sexta-feira, 17 de setembro de 2004 13:36 Para: debian-user-portuguese@lists.debian.org Assunto: 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
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
RES: Kernel Panic: VFS : Unable to mount root fs -AJUDA!!
Nelson e Rubens, Obrigado! Ao Nelson: - Como estou trabalhando, mandarei meu .config à noite para vocês avaliarem... (obrigado pela paciencia) - Fiz alguns testes com o initrd, mas achei muito porco, até onde eu sei, ele carrega modulos para que seja carregado o kernel certo? Se incluirmos tudo built-in não há essa necessidade correto??? - Eu utilizo grub... Abaixo segue minha config: title Debian 2.6.8.1 root (hd0,1) kernel /boot/vmlinuz-2.6.8.1 root=/dev/hda2 ro boot Ao Rubens: - Eu andei lendo e vi que essas opções de IDE/Chipsets estão um pouco chatinhas mesmo Você está utilizando o initrd também ou não precisou??? Obrigado pela força, Abraços Arthur -Mensagem original- De: Ruben Leote Mendes [mailto:[EMAIL PROTECTED] Enviada em: sexta-feira, 17 de setembro de 2004 14:39 Para: debian-user-portuguese@lists.debian.org Assunto: 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] -- 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: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)
Kernel panic: VFS: Unable to mount root fs on 03:01
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 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?) Thx for any Help. cu Manuel -- .''`. Ich nutze Debian Sarge. --- GNU/Linux : :' : Mach Dir das Betriebssystem untertan! `. `'` Nicht, weil die Dinge schwierig sind, wagen wir sie nicht, sondern weil wir sie nicht wagen, sind sie schwierig. `-
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
Kernel Panic: VFS: Unable to mount root fs on unknown-block(0,0)
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 ?? GrtZ, Phil.
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
Kernel Panic: VFS: Unable to mount root fs on hdh6
Moin, ich habe gerade einen neuen Kernel gebacken und bekomme es nicht hin, den auch zu booten. Ich habe hier zwei Festplatten an einem HPT370. Die beiden Platten werden im laufenden Betrieb ohne Problem erkannt, sowohl von Sarge (darum geht's hier) als auch von meinem alten SuSE. Jetzt habe ich einen neuen Kernel (2.6.0) gebacken und mittels 'make install' installiert. Der Kernel findet sich auch brav in /boot. Wenn bei dieser Aktion allerdings lilo(8) aufgerufen wird, gibt's schon Probleme mit unterschiedlichen Geometriedaten der Festplatte. Danach habe ich lilo(8) nochmal händisch aufgerufen: - - - Schnipp - - - [EMAIL PROTECTED] # lilo -P ignore / Warning: The boot sector and map file are on different disks. Added Linux * Added LinuxOLD Device 0x2200: Inconsistent partition table, 2nd entry CHS address in PT: 519:0:1 -- LBA (8337735) LBA address in PT: 523152 -- CHS (32:144:1) The partition table is *NOT* being adjusted. - - - Schnapp - - - Der Fehler wird daraufhin nicht mehr gemeldet: - - - Schnipp - - - [EMAIL PROTECTED] # lilo / Warning: The boot sector and map file are on different disks. Added Linux * Added LinuxOLD - - - Schnapp - - - Wenn ich jetzt aber versuche zu booten, klappt das nicht wirklich, der Kernel reagiert panisch. Mal ein paar abgetippte Details: - - - Schnipp - - - HPT370: IDE controller at PCI slot :00:13.0 hdg: IC35L060AVER07-0, ATA DISK drive hdh: SAMSUNG SV1604N, ATA DISK drive hdg: unknown partition table hdh: unknown partition table VFS: Cannot open roo device 2246 or hdh6 Please append a correct root= boot option Kernel panic: VFS: Unable to mount root fs on hdh6 - - - Schnapp - - - Interessant ist der Mittelteil: Beide Festplatten werden erkannt, für beide wird aber eine unbekannte Partitionstabelle gemeldet. Habe ich in dem neuen Kernel einen Schalter übersehen? Meine lilo.conf (ohne Kommentare): - - - Schnipp - - - bios=0x81 boot=/dev/hdg root=/dev/hdh6 install=/boot/boot-menu.b map=/boot/map delay=50 prompt timeout=50 vga=extended default=Linux image=/vmlinuz label=Linux read-only root=/dev/hdh6 image=/vmlinuz.old label=LinuxOLD read-only optional - - - Schnapp - - - Die zweite Zeile 'root=/dev/hdh6' habe ich nachträglich hinzugefügt, das hat aber nichts gebracht. 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 /dev/hdh7 /usrext3defaults0 2 /dev/hdh8 /home ext3defaults0 2 - - - Schnapp - - - 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 So, es ist also entweder der falsche Kernel oder ein verhackstückter Lilo. Mit dem alten Kernel (2.4.22-bf2.4) und der alten Konfiguration konnte ich ohne Probleme booten. Google kennt den Geometriefehler, die entsprechenden Seiten haben mich aber nicht weitergebracht. Über den Kernel panic sind auch Seiten vorhanden, aber ebenfalls nichts, was für mich interessant aussieht. Wie kann ich nun vorgehen, um den Fehler weiter einzugrenzen? Thorsten -- If something is so complicated that you can't explain it in 10 seconds, then it's probably not worth knowing anyway. - Calvin 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]
Kernel panic: VFS: Unable to mount root fs
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 -- 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
--- 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
kernel panic: VFS: Unable to mount root fs on 03:02
¿Como salgo de esta? No puedo arrancar ni con el diskete... ¿tengo que reinstalar?
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
Kernel panic: VFS: Unable to mount root fs
Basically, if my /boot/vmlinuz image exceeds a certain size (the limit seems be somewhere around 90 bytes), the following occurs on boot: 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 While some googling revealed that I'm certainly not the only one being hit by this particular type of kernel panic, I found no solutions that seemed applicable to my situation. This has happened with 2.4.19, 2.4.20-pre10, and now 2.4.20-ck1, all compiled from kernel.org sources (ck1 from http://members.optusnet.com.au/ckolivas/kernel/). I have not tested any 2.4-kernel prior to 2.4.19. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Lsung! Kernel panic: VFS: Unable to mount root fs on 03:41
Hallo, das Problem liess sich auf einfache Weise lösen, allerdings bin ich erst nach langem Nachdenken darauf gekommen, wohl weil es zu einfach war: Booten mit der CD3: rescue root=/dev/hdb1 dpgk-reconfigure kernel-image-2.4.18-686, lilo, es läuft wieder. Danke an alle, die versucht haben, mir zu helfen. 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
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)
Kernel panic: VFS: Unable to mount root fs on 03:41
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 -- 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)
Error: Kernel panic: VFS: Unable to mount root fs on 03:03 AND the fix
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Greetings: This post is for archives and google searches. No help required. On booting new compiled 2.4.18 kernel, I incurred a kernel panic: VFS: Cannot open root device or 03:03 Please append a correct root= boot option Kernel panic: VFS: Unable to mount root fs on 03:03 Before you start to tweak a lilo.conf file, do make sure you *include* ATA-ATAPI disk support in the kernel config prior to compiling! :)_ Main menu: ATA/IDE/MFM/RLL support --- Then: IDE, ATA and ATAPI Block devices --- * Include IDE/ATA-2 DISK support It is painfully easy to build kernels for your *own* box, but other peoples boxen might just use IDE, and require the driver support. :) tatah - -- Jaye Inabnit\ARS ke6sls\/A GNU-Debian linux user\/ http://www.qsl.net/ke6sls If it's stupid, but works, it ain't stupid. I SHOUT JUST FOR FUN. Free software, in a free world, for a free spirit. Please Support freedom! -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8xNeEZHBxKsta6kMRAq4zAKC45lyZabx3oglbdTxFpS6E+9uXQACfU3y9 eEF8SLNLBKfNw5Nxh6NoQVY= =1fTA -END PGP SIGNATURE- -- 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]
Kernel Panic :VFS : Unable to mount root fs on 03:07
Hola lista ... Aca esta exactamente lo que me dice el Kernel Panik Kernel Panic :VFS : Unable to mount root fs on 03:07 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]
Kernel panic: VFS: Unable to mount root fs on 03:41
Hi, I tried using a stock debian 2.4 kernel (kernel-image-2.4.17-k7) for the first time before now I've been compiling vanilla kernels. I get the following message while booting (after the LVM probing devices message) cramfs: wrong message Kernel panic: VFS: Unable to mount root fs on 03:41 I know this has been mentioned before but I can't see any solution, I've added initrd=/initrd.img (which points to /boot/initrd.img-2.4.17-k7) to lilo.conf and run lilo - below is my lilo.conf Thanks Nick -- # Generated by liloconfig # Specifies the boot device boot=/dev/hda # Specifies the device that should be mounted as root. # If the special name CURRENT is used, the root device is set to the # device on which the root file system is currently mounted. If the root # has been changed with -r , the respective device is used. If the # variable ROOT is omitted, the root device setting contained in the # kernel image is used. It can be changed with the rdev program. root=/dev/hdb1 # Enables map compaction: # Tries to merge read requests for adjacent sectors into a single # read request. This drastically reduces load time and keeps the map # smaller. Using COMPACT is especially recommended when booting from a # floppy disk. compact # Install the specified file as the new boot sector. # If INSTALL is omitted, /boot/boot.b is used as the default. install=/boot/boot.b # Specifies the number of _tenths_ of a second LILO should # wait before booting the first image. LILO # doesn't wait if DELAY is omitted or if DELAY is set to zero. delay=20 # Specifies the location of the map file. If MAP is # omitted, a file /boot/map is used. map=/boot/map initrd=/initrd.img # Specifies the VGA text mode that should be selected when # booting. The following values are recognized (case is ignored): # NORMAL select normal 80x25 text mode. # EXTENDED select 80x50 text mode. The word EXTENDED can be # abbreviated to EXT. # ASK stop and ask for user input (at boot time). # number use the corresponding text mode. A list of available modes # can be obtained by booting with vga=ask and pressing [Enter]. vga=normal default=2.4.16 image=/vmlinuz label=linux append= hdd=ide-scsi read-only image=/vmlinuz.old label=old append= hdd=ide-scsi read-only image=/boot/vmlinuz-2.4.16 label=2.4.16 append= hdd=ide-scsi read-only other=/dev/hda1 label=win ---
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
kernel panic: vfs: unable to mount root fs install errror 01:00
Hi, Problem: 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. One posting says: 'Your kernel does not support initrd and/or ramdisk.' But the suggestion is dependant on a shell and I can't get a console started. Another says: This is a common problem and it has only a few causes. First, check the device XX:YY against the list of device codes in /usr/src/linux/Documentation/devices.txt. If it is incorrect, you probably didn't do an rdev -R, or you did it on the wrong image. If the device code is correct, then check carefully the device drivers compiled into your kernel. Make sure it has floppy disk, ramdisk and ext2 filesystem support built-in. -- informative but doesn't help right now. I have a rh7.2 disk I tried to boot with to test and had no problem other than not wanting a rh install. Another post I found via google said the only way that user got around the error was to compile the kernel elseware and then move it to the failing system but I don't know how to do that. Kernel-image is 2.2.19-4potato.2 Hardware: dell poweredge 350 1u server p3850 512 sdram ecc 2 20gig ide drives which are being detected by install script 2 intel pro 100 isa nics and one intell pro 100 pci nic. Thanks for any help, Justin PS: if anyone replies from the debian-boot list can they please post to the debian-user list since I'm not subscribed to the boot list.
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
Kernel Panic: VFS unable to mount root fs
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. -- -- Resman [EMAIL PROTECTED]
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 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
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]
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
Custom kernel: Kernel panic: VFS: Unable to mount root fs on 21:05
Hi, it seems like similar problems have happened to other people on this list, but I could not determine a solution for my special case: After making and installing a custom kernel with kernel-package my box will not boot any longer. Here is what I did: * installed Debian potato with kernel 2.2.18pre21-ide (ABIT BE6-II motherboard, HPT366 chipset with UDMA) * upgraded to kernel-image-2.2.19-ide, everything works fine * got the 2.2.19 kernel-sources with apt-get install kernel-source-2.2.19 and the ide-kernel-path with apt-get install kernel-patch-2.2.19-ide * untarred the kernel-sources and copied /boot/config-2.2.19-ide to .config in top-level kernel-source directory * in toplevel kernel-source directory export PATCH_THE_KERNEL=YES make-kpkg clean make-kpkg --revision=custom.1.0 kernel_image Everything seems to work fine - the kernel gets patched and after answering a few questions the compile-process starts and runs through without any problems. The options I had to set manually: NS87415 chipset support (EXPERIMENTAL) (CONFIG_BLK_DEV_NS87415)=y VIA82C586 chipset support (EXPERIMENTAL) (CONFIG_BLK_DEV_VIA82C586)=y CMD646 chipset support (EXPERIMENTAL) (CONFIG_BLK_DEV_CMD646)=y Here is my first question: Why are there any options which are not set by the config-file in /boot? If the kernel-image was made with the same sources and (kernel-source and patch) and the config-file in /boot I shouldn't get any questions after calling 'make-kpkg kernel_image' (which calls 'make oldconfig'), right? * next I installed the new kernel with 'dpkg -i kernel-image-2.2.19_custom1.0_i386.deb * now after trying to reboot I get the following messages: ... loop: registered device at major 7 PIIX4: IDE controller on PCI bus 00 dev 39 PIIX4: not 100% native mode: will probe irqs later ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:pio ide1: BM-DMA at 0xf008-Oxf00f, BIOS settings: hdc:pio, hdd:pio hda: CD-540E, ATAPI CDROM drive ide0 at 0x1f0-0x1f7,0x3f6 on irq14 hda: ATAPI 40X CD-ROM drive, 128kB Cache Uniform CD-ROM driver Revision: 3.11 Floppy drive(s): fd0 is 1.44M FDC 0 is a post-1991 82077 md driver0.36.6 MAX_MD_DEV=4, MAX_REAL=8 Partition check: apm: BIOS version 1.2 Flags 0x07 (Driver verion 1.13) apm: diabled on user request. request_module[block-major-33]: Root fs not mounted VFS: Cannot open root device 21:05 Kernel panic: VFS: Unable to mount root fs on 21:05 It looks as if my Harddisk on the UDMA-controller is not found. The startup sequence with the debian kernel-image-2.2.19-ide looks something like this: ... loop: registered device at major 7 Uniform Multi-Platform E-IDE driver Revision: 6.30 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx PIIX4: IDE controller on PCI bus 00 dev 39 PIIX4: chipset revision 1 PIIX4: not 100% native mode: will probe irqs later ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:pio ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:pio, hdd:pio HPT366: onboard version of chipset, pin1=1 pin2=2 PCI: HPT366: Fixing interrupt 11 pin 2 to ZERO HPT366: IDE controller on PCI bus 00 dev 98 HPT366: chipset revision 1 HPT366: not 100% native mode: will probe irqs later ide2: BM-DMA at 0xe000-0xe007, BIOS settings: hde:DMA, hdf:pio HPT366: IDE controller on PCI bus 00 dev 99 HPT366: chipset revision 1 HPT366: not 100% native mode: will probe irqs later ide3: BM-DMA at 0xec00-0xec07, BIOS settings: hdg:pio, hdh:pio hda: CD-540E, ATAPI CDROM drive hde: ST310212A, ATA DISK drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 ide2 at 0xd800-0xd807,0xdc02 on irq 11 hde: ST310212A, 9768MB w/512kB Cache, CHS=19846/16/63, UDMA(33) hda: ATAPI 40X CD-ROM drive, 128kB Cache Uniform CD-ROM driver Revision: 3.11 Floppy drive(s): fd0 is 1.44M FDC 0 is a post-1991 82077 md driver 0.36.6 MAX_MD_DEV=4, MAX_REAL=8 Partition check: hde: [PTBL] [1245/255/63] hde1 hde2 hde5 hde6 hde7 hde8 apm: BIOS version 1.2 Flags 0x07 (Driver version 1.13) apm: disabled on user request. VFS: Mounted root (ext2 filesystem) readonly. ... Any ideas? Questions: * Why do I not get the same kernel as kernel-image-2.2.19-ide? Am I patching incorrectly? * Where is the 'Uniform Multi-Platform E-IDE driver' in my custom kernel? How do I activate it? Matthias
Re: Custom kernel: Kernel panic: VFS: Unable to mount root fs on 21:05
Ohlemeyer Matthias said: * in toplevel kernel-source directory export PATCH_THE_KERNEL=YES make-kpkg clean make-kpkg --revision=custom.1.0 kernel_image Everything seems to work fine - the kernel gets patched and after answering a few questions the compile-process starts and runs through without any problems. im not famillar with PATCH_THE_KERNEL and getting the system to patch it ..do you have the IDE patch? i download it from www.linux-ide.org. The options I had to set manually: NS87415 chipset support (EXPERIMENTAL) (CONFIG_BLK_DEV_NS87415)=y VIA82C586 chipset support (EXPERIMENTAL) (CONFIG_BLK_DEV_VIA82C586)=y CMD646 chipset support (EXPERIMENTAL) (CONFIG_BLK_DEV_CMD646)=y none of these are related to the Highpoint controller. the option(s) you want are probably: # CONFIG_BLK_DEV_HPT34X is not set # CONFIG_BLK_DEV_HPT366 is not set (copied/pasted from my own custom kernel) the above is not available without the IDE patch, if your using 2.2 which you appear to be doing It looks as if my Harddisk on the UDMA-controller is not found. yes..probably because you don't have the IDE patch. or its not patched correctly. i patch my kernels manually patch -p0 patchname Any ideas? see above :) my current method for installing a kernel: download source from kernel.org download openwall patch from openwall.com download ide patch(if its an ide system) from linux-ide.org download eepro update(if needed) from sycld.com(sp?) patch up, run make menuconfig(ive heard about oldconfig but im tied to menuconfig i like to go over every option to be sure its what i want everytime). run make-kpkg clean run make-kpkg --revision=30:30.0+ow3+ide+eepro binary (the revision changes of course and the stuff at the end tells me what patches/modifications i did to the kernel. my latest kernel filename is pretty big - kernel-image-2.2.19_36.0+ide+scsi+3ware+reiserfs+firewall+eepro117b+loopback+ow3_i386.deb) nate
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
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! -- Stan Brown [EMAIL PROTECTED]843-745-3154 Charleston SC. -- Windows 98: n. useless extension to a minor patch release for 32-bit extensions and a graphical shell for a 16-bit patch to an 8-bit operating system originally coded for a 4-bit microprocessor, written by a 2-bit company that can't stand for 1 bit of competition. - (c) 2000 Stan Brown. Redistribution via the Microsoft Network is prohibited.
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
Help! Kernel Panic: VFS Unable to mount root fs on 21:04
I've tried grub _and_ lilo. Grub just comes up in the interactive menu. Lilo starts loading the kernel and then the kernel spits out this meesage. This hapened just after I upgraded to the 2.4 kernel from the kernel packages for that. I desperately need to have this machine working by Monday. Can anyone sugest what to other that starting all over? -- Stan Brown [EMAIL PROTECTED]843-745-3154 Charleston SC. -- Windows 98: n. useless extension to a minor patch release for 32-bit extensions and a graphical shell for a 16-bit patch to an 8-bit operating system originally coded for a 4-bit microprocessor, written by a 2-bit company that can't stand for 1 bit of competition. - (c) 2000 Stan Brown. Redistribution via the Microsoft Network is prohibited.
Re: Help! Kernel Panic: VFS Unable to mount root fs on 21:04
On Sat, Oct 06, 2001 at 05:42:19PM -0400, Stan Brown wrote: | I've tried grub _and_ lilo. Grub just comes up in the interactive menu. | Lilo starts loading the kernel and then the kernel spits out this meesage. Is this the same machine you just asked about the initrd stuff for? To boot with an initrd (as Herbert's packages require) you need the following sort of layout in grub : title Debian GNU/Linux (stock kernel 2.4.9) root(hd0,0) kernel /boot/vmlinuz-2.4.9-686 root=/dev/hda4 read-only initrd=/boot/initrd-2.4.9-686 apm=on initrd /boot/initrd-2.4.9-686 Note that you need an initrd= for the kernel and to use 'initrd' instead of 'boot' at the end of the section. | This hapened just after I upgraded to the 2.4 kernel from the kernel | packages for that. You still have the older kernel to boot so you can fix your setup, right? Have you ever booted a 2.4 kernel before? Do the stock 2.2 kernels work for you? Do you have any weird IDE controllers? When I first compiled my own 2.4 kernel on this system I accidentally disabled by IDE controller, thus it couldn't find the disks. HTH, -D
Re: MAS DETALLES RE: Partition magic + administrador de discos de wnt = kernel panic : VFS : UNable to mount root fs on 03:02
El mié, 26 abr 2000, Alex Fredes escribió: Adjunto mas detalles que me aparecen en pantalla: Partition check: hda: hda1 hda3 hda4 hda5 [...] Hola lista resumo: hda1 ntfs hda2 linux hda5 swap Por alguna razón, la partición hda2 donde estaba el Linux ha cambiado de nombre, y presuponemos que ahora es hda3 ó hda4. Lo mejor sería arrancar desde un disquete de inicio, e intentar montar las particiones hda3 y hda4. Por prudencia yo las montaría en sólo lectura. Una vez que localices cual es la que tiene el Linux, y compruebes que está todo bien (puedes pasarle un fsck por si acaso), puedes volver a arrancar, esta vez desde disco duro, y poner, cuando salga el prompt del LILO, lo siguiente: linux root=/dev/hda3 (ó hda4) Con esto el kernel debería encontrar la partición raíz y montarla. Una vez dentro deberás modificar el archivo lilo.conf y sustituir la línea: root=/dev/hda2 por: root=/dev/hda3 (ó hda4) y después volver a ejecutar 'lilo'. A partir de aquí ya deberías poder arrancar normalmente sin problemas. Si no encuentras tu antigua partición de Linux ni en hda3 ni en hda4, entonces sí que hay un grave problema.
Partition magic + administrador de discos de wnt = kernel panic : VFS : UNable to mount root fs on 03:02
Hola lista
resumo:
hda1 ntfs
hda2 linux
hda5 swap
Funcionaban correctamente, y tenia copado todo el disco con las particiones.
Yo sabia que con el partirion magic se podian cambiar el tamaño de
particiones para liberar espacio. Cambie el tamaño de la particion hda1
(ntfs) y luego al reiniciar la maquina (tengo por defecto el booteo para
nt), me levanto el nt y dijeme a mi mismo acá creo la unidad fat16 que
necesito. Entoncres echo a correr el administrador de disco, me alega de
que necesita escribir en el disco para acceder y de que no provocará
problemas con otras particiones y bla bla bla, bueno, será. Hace todo el
proceso, reparticiono al unidad previamente liberada, creo una particion
fat16, la formateo... ¡¡Listo :)!!
Reinicio la maquina, entro al debian y
kernel panic : VFS : Unable to mount root fs on 03:02
y ahi se me queda pegado.
probé con el cfdisk, elimine la particion de fat16, le cree por acá, la
volvi a recrear, etc y nada de nada
Como puedo solucionar esto??
Alex Fredes
Roxi Ingeneria y Servicios
http://www.roxi.cl
begin 666 ATT00023.htm
M/%$3T-465!%([EMAIL PROTECTED]3$E#((M+R]7,T,O+T141!(5$U,(#0N,!4
MF%NVET:6]N86PO+T5.(CX-CQ(5$U,/CQ(14%$/@T*/[EMAIL PROTECTED]U%
M455)5CTB0V]N=5N=U47!E(B!#3TY414Y4/2)T97AT+VAT;6P[(-H87)S
M970]:[EMAIL PROTECTED],2(^#0H-@T*/[EMAIL PROTECTED]5N=#TB35-(5$U,(#4N
M,# N,C,Q-XQ,# P(B!N86UE/4=%3D52051/4CX\+TA%040^#0H\0D]$62!B
M9T-O;]R/2-F9F9F9F8^#0H\1$E6/CQ3TY4(-O;]R/2,P,# [EMAIL PROTECTED]
M93TB0V]UFEEB!.97B('-IF4],CX\4U!!3B -F-L87-S/3DT.3(X,[EMAIL PROTECTED]
M-RTR-C T,C P,#Y(;VQA(QIW1A/]34$%./CPO1D].5#X\+T1)5CX-CQ$
M258^/$9/[EMAIL PROTECTED];W(](S P,#!F9B!F86-E/2)#;W5R:65R($YE=R(@VEZ
M93TR/CQ34$%.( T*8VQAW,].30Y,[EMAIL PROTECTED](V,#0R,# P/CPO4U!!3CX\
M+T9/3E0^)FYBW [/]$258^#0H\1$E6/CQ3TY4(-O;]R/2,P,# P9F8@
M9F%C93TB0V]UFEEB!.97B('-IF4],CX\4U!!3B -F-L87-S/3DT.3(X
M,[EMAIL PROTECTED] T,C P,#YR97-U;6\Z/]34$%./CPO1D].5#X\+T1)5CX-CQ$
M258^/$9/[EMAIL PROTECTED];W(](S P,#!F9B!F86-E/2)#;W5R:65R($YE=R(@VEZ
M93TR/CQ34$%.( T*8VQAW,].30Y,[EMAIL PROTECTED](V,#0R,# P/CPO4U!!3CX\
M+T9/3E0^)FYBW [/]$258^#0H\1$E6/CQ3TY4(-O;]R/2,P,# P9F8@
M9F%C93TB0V]UFEEB!.97B('-IF4],CX\4U!!3B -F-L87-S/3DT.3(X
M,[EMAIL PROTECTED] T,C P,#YH9$Q(YT9G,\+U-004X^/]3TY4/CPO1$E6/@T*
M/$1)5CX\1D].5!C;VQOCTC,# P,9F(9A8V4](D-O=7)I97(@3F5W(B!S
M:7IE/3(^/[EMAIL PROTECTED];%SSTY-#DR.#$X,3M,C8P-#(P,# ^:1A,B!L
M:6YU#PO4U!!3CX\+T9/3E0^/]$258^#0H\1$E6/CQ3TY4(-O;]R/2,P
M,# [EMAIL PROTECTED]FEEB!.97B('-IF4],CX\4U!!3B -F-L87-S
M/3DT.3(X,[EMAIL PROTECTED] T,C P,#YH9$U('-W87 \+U-004X^/]3TY4/CPO
M1$E6/@T*/$1)5CX\1D].5!C;VQOCTC,# P,9F(9A8V4](D-O=7)I97(@
M3F5W(B!S:7IE/3(^/[EMAIL PROTECTED];%SSTY-#DR.#$X,3M,C8P-#(P,# ^
M/]34$%./CPO1D].5#XF;F)S#L\+T1)5CX-CQ$258^/$9/[EMAIL PROTECTED];W(]
M(S P,#!F9B!F86-E/2)#;W5R:65R($YE=R(@VEZ93TR/CQ34$%.( T*8VQA
MW,].30Y,[EMAIL PROTECTED](V,#0R,# P/D9U;F-I;VYA8F%N(-OG)E8W1A;65N
M=4L('[EMAIL PROTECTED]5N:[EMAIL PROTECTED]('1O9[EMAIL PROTECTED]@9[EMAIL
PROTECTED];VX@;%S('!A
MG1I8VEO;F5S+B!9;R!S86)[EMAIL PROTECTED](5L('!AG1IFEO;B!M86=I
M8R!S92!P;[EMAIL PROTECTED]B!E; -G1A;6'Q;R!D92!P87)T:6-I;VYE
MR!P87)A(QI8F5R87(@97-P86-I;[EMAIL PROTECTED](5L('1A;6'Q;R!D92!L
M82!P87)T:6-I;[EMAIL PROTECTED]$Q(AN=9S*2!Y(QU96=O(%L(')E:6YI8VEA
MB!L82!M87%U:6YA(AT96YG;R!P;W(@95F96-T;R!E;!B;V]T96\@%R
M82 -FYT*2P@;64@;5V86YT;R!E;!N=!Y(1I:F5M92!A(UI(UIVUO
M()[EMAIL PROTECTED])E;R!L82!U;[EMAIL PROTECTED],38@75E( T*;F5C97-I=\B+B!%
M;G1O;F-R97,@96-H;R!A(-OG)EB!E;!A9UI;FES=')A9]R(1E(1I
MV-O+!M92!A;[EMAIL PROTECTED]VET82!EV-R:6)IB!E;B!E
M;!D:7-C;R!P87)A(%C8V5D97(@2!D92!Q=64@;F\@')O=F]C87+A('!R
M;V)L96UAR!C;[EMAIL PROTECTED]')AR!P87)T:6-I;VYER!Y()L82!B;[EMAIL
PROTECTED]
M+!B=65N;RP@[EMAIL PROTECTED]%C92!T;V1O(5L('!R;V-EV\L(')E%R=EC
M:6]N;R -F%L('5N:61A9!PF5V:6%M96YT92!L:6)E[EMAIL PROTECTED])E;R!U
M;F$@%R=EC:6]N(9A=#$V+!L82!F;W)M871E;RXN+BAH4QIW1O( T*
M.BDA(3PO4U!!3CX\+T9/3E0^/]$258^#0H\1$E6/CQ3TY4(-O;]R/2,P
M,# [EMAIL PROTECTED]FEEB!.97B('-IF4],CX\4U!!3B -F-L87-S
M/3DT.3(X,[EMAIL PROTECTED] T,C P,#X\+U-004X^/]3TY4/B9N8G-P.SPO1$E6
M/@T*/$1)5CX\1D].5!C;VQOCTC,# P,9F(9A8V4](D-O=7)I97(@3F5W
M(B!S:7IE/3(^/[EMAIL PROTECTED];%SSTY-#DR.#$X,3M,C8P-#(P,# ^4F5I
M;FEC:6\@;$@;[EMAIL PROTECTED][EMAIL PROTECTED]@95B:6%N( T*2XN+BX\+U-0
M04X^/]3TY4/CPO1$E6/@T*/$1)5CX\1D].5!C;VQOCTC,# P,9F(9A
M8V4](D-O=7)I97(@3F5W(B!S:7IE/3(^/[EMAIL PROTECTED];%SSTY-#DR.#$X
M,3M,C8P-#(P,# ^)FYBW [/]34$%./CPO1D].5#X\+T1)5CX-CQ$258^
M/$9/[EMAIL PROTECTED];W(](S P,#!F9B!F86-E/2)#;W5R:65R($YE=R(@VEZ93TR
M/B9N8G-P.VMEFYE;!P86YI8R Z(%94R Z( T*53Q34$%.(-L87-S/3DT
M.3(X,[EMAIL PROTECTED] T,C P,#YN/]34$%./F%B;[EMAIL
PROTECTED]\@;6]U;G0@F]O=!F
MR!O;B -C S.C R/]3TY4/CPO1$E6/@T*/$1)5CXF;F)S#L\+T1)5CX-
MCQ$258^/$9/[EMAIL PROTECTED];W(](S P,#!F9B!F86-E/2)#;W5R:65R($YE=R(@
MVEZ93TR/CQ34$%.( T*8VQAW,].30Y,[EMAIL PROTECTED](V,#0R,# P/[EMAIL PROTECTED]
M('-E(UE('%U961A('!E9V%D;RX\+U-004X^/]3TY4/CPO1$E6/@T*/$1)
M5CX\1D].5!C;VQOCTC,# P,9F(9A8V4](D-O=7)I97(@3F5W(B!S:7IE
M/3(^/[EMAIL PROTECTED];%SSTY-#DR.#$X,3M,C8P-#(P,# ^/]34$%./CPO
M1D].5#XF;F)S#L\+T1)5CX
MAS DETALLES RE: Partition magic + administrador de discos de wnt = kernel panic : VFS : UNable to mount root fs on 03:02
Adjunto mas detalles que me aparecen en pantalla: Partition check: hda: hda1 hda3 hda4 hda5 attemp to acces beyond end of device 03:02: rw=0, want=2, limit=0 EXT2-fs: unable to read superblock attemp to acces beyond end of device 03:02: rw=0, want=2, limit=0 MINIX-fs: unable to read superblock attemp to acces beyond end of device 03:02: rw=0, want=1, limit=0 FAT bread failed attemp to acces beyond end of device 03:02: rw=0, want=33, limit=0 isofs_read_super: bread failed, dev 03:02 iso_blknum 16 block 32 kernel panic : VFS : UNable to mount root fs on 03:02 No me gustaria tener que volver a reinstalar todo el debian Gracias de antemano Alex Fredes Roxi Ingeneria y Servicios http://www.roxi.cl -Mensaje original- De: Alex Fredes [mailto:[EMAIL PROTECTED] Enviado el: Miércoles 26 de Abril de 2000 03:27 PM Para: 'Debian Users Spanish' Asunto: Partition magic + administrador de discos de wnt = kernel panic : VFS : UNable to mount root fs on 03:02 Importancia: Alta Hola lista resumo: hda1 ntfs hda2 linux hda5 swap Funcionaban correctamente, y tenia copado todo el disco con las particiones. Yo sabia que con el partirion magic se podian cambiar el tamaño de particiones para liberar espacio. Cambie el tamaño de la particion hda1 (ntfs) y luego al reiniciar la maquina (tengo por defecto el booteo para nt), me levanto el nt y dijeme a mi mismo acá creo la unidad fat16 que necesito. Entoncres echo a correr el administrador de disco, me alega de que necesita escribir en el disco para acceder y de que no provocará problemas con otras particiones y bla bla bla, bueno, será. Hace todo el proceso, reparticiono al unidad previamente liberada, creo una particion fat16, la formateo... ¡¡Listo :)!! Reinicio la maquina, entro al debian y kernel panic : VFS : Unable to mount root fs on 03:02 y ahi se me queda pegado. probé con el cfdisk, elimine la particion de fat16, le cree por acá, la volvi a recrear, etc y nada de nada Como puedo solucionar esto?? Alex Fredes Roxi Ingeneria y Servicios http://www.roxi.cl
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
RV: kernel panic: VFS: Unable to mount root fs on 03:06
Ante todo muchas gracias a la lista. El asunto era que había compilado como módulo la ext2fs y por eso no arrancaba. No se por qué razón se puede compilar como módulo siendo tan importante para el arranque que se haga como integrante del kernel. Saludos
Re: RV: kernel panic: VFS: Unable to mount root fs on 03:06
El jueves 24 de febrero de 2000 a la(s) 09:04:16 +0100, Juanma contaba: No se por qué razón se puede compilar como módulo siendo tan importante para el arranque que se haga como integrante del kernel. Porque nada te obliga a usar ext2fs. Puedes formatear la partición Linux con otro sistema de archivos y prescindir del ext2fs completamente. ¿Se puede eso en la kk? :^). -- Just do it. David Serrano [EMAIL PROTECTED]Linux 2.2.14 - Reg. User #87069 lynx -dump http://www.ctv.es/USERS/fserrano/pgp_dsspubkey.asc | gpg --import - Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! pgpGjGUTHYFVq.pgp Description: PGP signature
