Professional Web Applications Themes

New Kernel - VFS: Unable to mount root fs on 304 or unknown-block(3,4) - Linux Setup, Configuration & Administration

Hello, I'trying to install a new compiled kernel. I used exactly the same configurations (at least, I hope I have) as had the kernel that came with debian. Jet, when rebooting with the new kernel, I get the following error message: VFS: Unable to mount root fs on 304 or unknown-block(3,4) There are lots of mailing list logs out there on the web that deal with this problem, but none could help me. I have already tried the kernels 2.2.20, 2.4.17, 2.4.18, 2.4.22, and 2.6.0-test6 and I typed root=/dev/hda4, root=304, root=300, root=302 and any kombination you can think of at ...

  1. #1

    Default New Kernel - VFS: Unable to mount root fs on 304 or unknown-block(3,4)

    Hello,

    I'trying to install a new compiled kernel. I used exactly the same
    configurations (at least, I hope I have) as had the kernel that came with
    debian. Jet, when rebooting with the new kernel, I get the following error
    message:

    VFS: Unable to mount root fs on 304 or unknown-block(3,4)

    There are lots of mailing list logs out there on the web that deal with
    this problem, but none could help me. I have already tried the kernels
    2.2.20, 2.4.17, 2.4.18, 2.4.22, and 2.6.0-test6 and I typed root=/dev/hda4,
    root=304, root=300, root=302 and any kombination you can think of at the
    LILO boot prompt, but it still did not work (I don't have any root=... in
    my lilo.conf). The file system on /dev/hda4 is ext2 and it is compiled as
    "y" (not "m") into the kernel.

    Something that might be relevant: I have a multi boot System with WinXP on
    /dev/hda1, Win95 on /dev/hda2, and Debian GNU/Linux on /dev/hda4. LILO
    starts automatically when booting, however "fdisk -l" says:

    =======

    Disk /dev/hda: 40.0 GB, 40060403712 bytes
    255 heads, 63 sectors/track, 4870 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes

    Device Boot Start End Blocks Id System
    /dev/hda1 * 1 3442 27647833+ 7 HPFS/NTFS
    /dev/hda2 4488 4870 3076447+ c W95 FAT32 (LBA)
    /dev/hda3 3443 3504 498015 82 Linux swap
    /dev/hda4 3505 4487 7895947+ 83 Linux

    Partition table entries are not in disk order

    =======

    So the partitions seem to be in a somewhat unusual order and the boot
    partition is /dev/hda1 instead of /dev/hda4.

    It would be great if you could help me with this problem. Please tell me,
    if you need further information. I can also send the kernel .config file,
    if this is important.

    Robert
    Robert Guest

  2. #2

    Default Re: New Kernel - VFS: Unable to mount root fs on 304 or unknown-block(3,4)

    On Mon, 13 Oct 2003 22:20:10 +0200, Robert Bamler <de> wrote: 
    Did you move the new system.map to /boot and re-run lilo after compiling
    the new kernel?

    As far as I know you need the root=/dev/foo in the linux stanza, at least.
    And I'd use cfdisk (or whatever) to flag the right partition as boot.

    --
    Alan C
    PGP SIG: iErEARECAAXFAj+ItCoACghQhVcNCxZ4ID84NQCggQxmIDiB5Z v90lNee6jh7chm
    FSEBnA//aDq7YFfB6Y1pjHQz8xxtij+EG
    =j7+8 :END PGP SIG: Hash: SHA1
    Alan Guest

  3. #3

    Default Re: New Kernel - VFS: Unable to mount root fs on 304 or unknown-block(3,4)

    Robert Bamler wrote:
     

    Forgot to run "lilo", I suspect. Or you are encountering an old MBR
    stuffed at the beginning of the drive instead of the MBS you are
    expecting to install on the active partition. You might have to change
    your lilo.conf to put it on "/dev/hda" instead of "/dev/hda1", if you
    made that setting.

    I've also actually seen people get away with not updating lilo.conf for
    several updates, until installing the new kernel with "/boot/vmlinuz"
    linked to it actually put the kernel on a different block. It drove me
    *ape* tracking that one down on specialized, hand-built boot CD
    image....

    Nico Guest

  4. #4

    Default Re: New Kernel - VFS: Unable to mount root fs on 304 or unknown-block(3,4)

    Robert Bamler wrote:
     

    .... did you re-run lilo - if so, switch to grub and be done with it
    ..
    --
    /// Michael J. Tobler: motorcyclist, surfer, skydiver, \\\
    \\\ and author: "Inside Linux", "C++ HowTo", "C++ Unleashed" ///
    Heavy, adj.: Seduced by the chocolate side of the force.

    mjt Guest

  5. #5

    Default Re: New Kernel - VFS: Unable to mount root fs on 304 or unknown-block(3,4)

    Hello,

    thank you for your reply.
     

    No, I ran lilo every time after editing lilo.conf.

     

    Thank you for your hint. Unfortunately, I'm not so used to lilo
    configuration. May you help me where to put this? I send my lilo.conf
    (without comments) at the bottom of this message.

    Thanks,
    Robert

    PS: As Alan Connor wrote, I also copied the System.map both to
    /boot/System.map as well as to /boot/map and ran lilo after doing this.
    This made /boot/map to become much tinier (63KB, was 385.7KB). But this
    also did not help.


    My lilo.conf is:

    lba32

    boot=/dev/hda

    root=/dev/hda4

    install=/boot/boot-menu.b

    map=/boot/map

    delay=20

    prompt
    timeout=50
    vga=normal

    default="WinNT(hda1)"

    image=/vmlinuz.old
    label=LinuxOld
    read-only
    optional
    # restricted
    # alias=2


    # Test
    image=/boot/vmlinuz-2.6.0-test6
    label=kernel-2.6.0-t6
    read-only
    optional
    # root="/dev/hda4"
    # append="hdd=ide-scsi"

    other=/dev/hda1
    label="WinNT(hda1)"

    other=/dev/hda2
    label="Windows(hda2)"
    Robert Guest

  6. #6

    Default Re: New Kernel - VFS: Unable to mount root fs on 304 or unknown-block(3,4)

    >> Forgot to run "lilo", I suspect. 

    Use a few -v switches when your run it.
    LILO is not the problem though.
    Linux cannot mount your root FS.
    Could be that you forgot to include the correct filesystem.
    (I noticed you checked that already though)
    Perhaps the IDE driver?
     

    Duh.
    /boot/map is lilo's second stage loader.
    Do not overwrite it.
    You will not really need system.map
     

    There is nothing wrong with this lilo.conf as far as I can see.
    Check your configuration again. It sure sounds as if you forget
    to compile something in the kernel.

    Eric
    Eric Guest

  7. #7

    Default Re: New Kernel - VFS: Unable to mount root fs on 304 or unknown-block(3,4)


    "Robert Bamler" <de> wrote in message
    news:online.de... 
    root=/dev/hda4, 

    The message comes from the loaded kernel after it is initialised and it's
    trying to access the file system root, so please do not mess with LILO
    here - the original setup is probably right.

    Please check that the kernel has the IDE drivers and the root file system
    driver (probably ext2 or ext3) compiled in. The common blunder is to either
    forget the drivers totally or make them as modules.

    HTH

    Tauno Voipio
    tauno voipio iki fi



    Tauno Guest

  8. #8

    Default Re: New Kernel - VFS: Unable to mount root fs on 304 or unknown-block(3,4)

    Tauno Voipio wrote:
     
    >
    > root=/dev/hda4,

    >
    >
    > The message comes from the loaded kernel after it is initialised and it's
    > trying to access the file system root, so please do not mess with LILO
    > here - the original setup is probably right.
    >
    > Please check that the kernel has the IDE drivers and the root file system
    > driver (probably ext2 or ext3) compiled in. The common blunder is to either
    > forget the drivers totally or make them as modules.[/ref]

    Ah-hah! I'll bet, at this point, that he used ext3 file systems but has
    them as modules (which matches the default kernel configurations). In
    this case, he'd need to run "mkinitrd" with an approprite modules.conf,
    and make sure it gets loaded by his lilo.conf....

    Nico Guest

  9. #9

    Default Re: New Kernel - VFS: Unable to mount root fs on 304 or unknown-block(3,4)

    Hello,

    Thank you all for your help, but I still have problems with my kernel.
     

    No, I'm using ext2 (at least this is what /etc/fstab says) and I have
    compiled both ext2 and ext3 as "y" (but without the extended attributes).

     

    What is mkinitrd? I only found something about writing boot CDs with this
    programm.

    Tauno Voipio wrote that I had to make sure to compile the IDE-Drivers.
    Where can I find this in the configuration-tree? I aktivated (i.e. "y")
    "ATA/ATAPI/MFM/RLL support (IDE)" and "Enhanced IDE/MFM/RLL
    disk/cdrom/tape/floppy support (BLK_DEV_IDE)" but none of them helped me.

    Please help me.
    Robert
    Robert Guest

  10. #10

    Default Re: New Kernel - VFS: Unable to mount root fs on 304 or unknown-block(3,4)

    >> In this case, he'd need to run "mkinitrd" with an approprite 
    >
    > What is mkinitrd? I only found something about writing boot CDs with
    > this programm.[/ref]

    It creates an initial ramdisk. You can use it to load kernel
    modules needed during boot-up
     

    What IDE controller do you have? Anything fancy here?
    check out the "IDE/ATA/ATAPI block devices" tab

    Eric
    Eric Guest

  11. #11

    Default Re: New Kernel - VFS: Unable to mount root fs on 304 or unknown-block(3,4)

    Hello,
     

    Yes, this was the reason. I didn't have IDE harddisk support.

    Thank you very much for your help.

    Robert
    Robert Guest

Similar Threads

  1. mirrored root disk boot block
    By Bridge in forum Sun Solaris
    Replies: 9
    Last Post: July 29th, 02:41 AM
  2. root device name w/kernel-image
    By Drew Scott Daniels in forum Debian
    Replies: 3
    Last Post: July 24th, 09:10 PM
  3. KERNEL PANIC: VFS: Unable to mount root fs on 01:00
    By Paul A Morgan in forum Linux Setup, Configuration & Administration
    Replies: 0
    Last Post: July 18th, 07:19 PM
  4. kernel panic on root
    By David M Noriega in forum Linux Setup, Configuration & Administration
    Replies: 3
    Last Post: July 15th, 12:43 PM
  5. Repartitioned, now can't mount root
    By Ryan Heise in forum Debian
    Replies: 0
    Last Post: July 4th, 11:30 PM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139