Ayuda con kernel panic en 2.6.5


  • 0

    Hola, el caso es que he compilado el 2.6.5 y al cargarlo me da un kernel panic, me dice:
    VFS: Unable to mount root fs on hda2
    El sistema de archivos es reiserfs, pero creo que está bien configurado en el kernel, no lo he puesto como módulo, lo he puesto como built-in, así que no creo que sea porque no soporte reiserfs y también he probado a cambiar cosas en el lilo pero nada, os dejo el lilo.conf, a ver si me podéis echar una mano:

    # /etc/lilo.conf - See: `lilo(8)' and `lilo.conf(5)',
    # ---------------       `install-mbr(8)', `/usr/share/doc/lilo/',
    #                       and `/usr/share/doc/mbr/'.
    # +---------------------------------------------------------------+
    # |                        !! Reminder !!                         |
    # |                                                               |
    # | Don't forget to run `lilo' after you make changes to this     |
    # | conffile, `/boot/bootmess.txt', or install a new kernel.  The |
    # | computer will most likely fail to boot if a kernel-image      |
    # | post-install script or you don't remember to run `lilo'.      |
    # |                                                               |
    # +---------------------------------------------------------------+
    # Support LBA for large hard disks.
    #
    lba32
    # Overrides the default mapping between harddisk names and the BIOS'
    # harddisk order. Use with caution.
    #disk=/dev/hde
    #    bios=0x81
    #disk=/dev/sda
    #    bios=0x80
    # Specifies the boot device.  This is where Lilo installs its boot
    # block.  It can be either a partition, or the raw device, in which
    # case it installs in the MBR, and will overwrite the current MBR.
    #
    boot=/dev/hda
    # Specifies the device that should be mounted as root. (`/')
    #
    root=/dev/hda2
    # Enable 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.  It is disabled here by default
    # because it doesn't always work.
    #
    # compact
    # Installs the specified file as the new boot sector
    # You have the choice between: bmp, compat, menu and text
    # Look in /boot/ and in lilo.conf(5) manpage for details
    #
    #install=/boot/boot-menu.b
    install=/boot/boot.b
    # Specifies the location of the map file
    #
    map=/boot/System.map
    # You can set a password here, and uncomment the `restricted' lines
    # in the image definitions below to make it so that a password must
    # be typed to boot anything but a default configuration.  If a
    # command line is given, other than one specified by an `append'
    # statement in `lilo.conf', the password will be required, but a
    # standard default boot will not require one.
    #
    # This will, for instance, prevent anyone with access to the
    # console from booting with something like `Linux init=/bin/sh',
    # and thus becoming `root' without proper authorization.
    #
    # Note that if you really need this type of security, you will
    # likely also want to use `install-mbr' to reconfigure the MBR
    # program, as well as set up your BIOS to disallow booting from
    # removable disk or CD-ROM, then put a password on getting into the
    # BIOS configuration as well.  Please RTFM `install-mbr(8)'.
    #
    # password=tatercounter2000
    # Specifies the number of deciseconds (0.1 seconds) LILO should
    # wait before booting the first image.
    #
    
    delay=20
    # You can put a customized boot message up if you like.  If you use
    # `prompt', and this computer may need to reboot unattended, you
    # must specify a `timeout', or it will sit there forever waiting
    # for a keypress.  `single-key' goes with the `alias' lines in the
    # `image' configurations below.  eg: You can press `1' to boot
    # `Linux', `2' to boot `LinuxOLD', if you uncomment the `alias'.
    #
    # message=/boot/bootmess.txt
    #	prompt
    #	single-key
    #	delay=100
    #	timeout=100
    # Specifies the VGA text mode at boot time. (normal, extended, ask, <mode>)
    #
    vga=771
    # vga=9
    #
    #vga=normal
    # Kernel command line options that apply to all installed images go
    # here.  See: The `boot-prompt-HOWO' and `kernel-parameters.txt' in
    # the Linux kernel `Documentation' directory.
    #
    # append="root=/dev/hda2"
    # Boot up Linux by default.
    #
    default=Linux
    
    image=/vmlinuz
    	label="Linux"
    	read-only
    #	restricted
    	#alias=1
    
    image=/vmlinuz.old
    	label="LinuxOLD"
    	read-only
    	optional
    #	restricted
    	#alias=2
    
    image=/boot/kernel2.6.5
    	label="Linux2.6.5new"
    	append="root=/dev/hda2 hdc=ide-cd"
    	read-only
    	#alias=3
    # If you have another OS on this machine to boot, you can uncomment the
    # following lines, changing the device name on the `other' line to
    # where your other OS' partition is.
    #
    # other=/dev/hda4
    #	label=HURD
    #	restricted
    #	alias=3</mode>
    


  • 1

    lo raro es que cuando ejecuto el kernel antiguo que trae debian puedo ver como antes de hacer lo del VFS carga el reiserfs, pero con el kernel nuevo no carga ningun fs, pero yo los he activado en el kernel, así que no sé que hacer para arreglarlo:(



  • 2

    vale, ya sé que el problema no es del lilo, el problema es del kernel que no le da la gana cargar los sistemas de archivos, habré recompilado el kernel decenas de veces y nada:rabieta:



  • 3

    Asegurate de que la siguiente opcon esta compilada en el kernel:

    File systems –-> Partition Types --->* Advanced partition selection –>* PC BIOS (MSDOS partition tables) support

    Un saludo.


  • 4

    Pues exactamente;), era que no tenía esa opción activada, pues muchas gracias porque tenía una comida de tarro impresionante:D



  • 5

    No entiendo pq tiene que estar activado esto? las particiones mediante Linux dependen del tipo soportado por MS-DOS??





Has perdido la conexión. Reconectando a Hardlimit.