Announcement

Collapse
No announcement yet.

Kernel says "File not found" at boot

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Kernel says "File not found" at boot

    All recent kernel updates, 2.6.24-17, 2.6.24-18 and 2.6.24-19 result in an error at boot. The latest kernel is selected in GRUB but then states "File not found".
    2.6.24-16 starts normally.

    When I look into the /boot directory, I can see all kernel files in place, with the same owner and permissions.
    Once your problem is solved please edit the first post of your topic and add [SOLVED] in front of the subject. In that way, others can benefit from your experience!

    #2
    Re: Kernel says "File not found" at boot

    In your file /boot/grub/menu.lst, what does the "groot=" value say? That should be the same as the "hd(n,n)" value on the kernel line of the menu down below where it shows the kernel number.

    Comment


      #3
      Re: Kernel says "File not found" at boot

      Thank you for answering, everything seems allright. The grub entries are exactly the same (apart from the "-16" changed in "-17", "-18" or "-19")

      # groot=(hd1,0)

      title Ubuntu 8.04, kernel 2.6.24-17-generic
      root (hd1,0)
      kernel /boot/vmlinuz-2.6.24-17-generic root=UUID=dc1ae9fe-b142-43ca-9f3d-0f8fa684c7c7 ro quiet splash
      initrd /boot/initrd.img-2.6.24-17-generic
      quiet


      title Ubuntu 8.04, kernel 2.6.24-16-generic
      root (hd1,0)
      kernel /boot/vmlinuz-2.6.24-16-generic root=UUID=dc1ae9fe-b142-43ca-9f3d-0f8fa684c7c7 ro quiet splash
      initrd /boot/initrd.img-2.6.24-16-generic
      Once your problem is solved please edit the first post of your topic and add [SOLVED] in front of the subject. In that way, others can benefit from your experience!

      Comment


        #4
        Re: Kernel says "File not found" at boot

        Has there been any recent change in the hard drive partitions on that computer (partitions added or deleted)?

        Comment


          #5
          Re: Kernel says "File not found" at boot

          The file that is “not found” can also be the initrd file, as well as the vmlinuz file.
          For example, see Reply #23, Error 15 of this:
          How To GRUB Methods - Toolkit
          http://kubuntuforums.net/forums/inde...opic=3081671.0
          --- GRUB Errors -- common errors and what causes them and how to fix them, Reply #23

          Problem is that fixing it isn't always easy or permanent (it may break upon the next kernel update). I'm batting just 75% at this, and so I don't profess to profess anything.
          At least one other member here has also seen this "chroot & update-initramfs" stuff, and maybe he will read your post, too. Somehow, after the update, you may have a backup initrd file (.bak), but not an original. And/or possibly other mishaps along those lines. (You already checked that the kernels were there, the vmlinuz's, right?)
          An intellectual says a simple thing in a hard way. An artist says a hard thing in a simple way. Charles Bukowski

          Comment


            #6
            Re: Kernel says "File not found" at boot

            @dibl:
            No there were no changes in partitions. I have two Kubuntu systems installed (one for use and one for testing purposes). The test system (8.04 KDE4) gives Error 17, the installation for normal use (8.04 KDE3.5) only boots with kernel 2.6.24-16 (or earlier).

            @Qqmike:
            Is this then what I should do? Sounds rather scary... can't I just re-install the kernel in adept or so?

            Code:
            From the Live CD, chroot into the sda2 partition (see how-to note below).
            Issue the following command:
            sudo update-initramfs -u -v
            and let it run and put things together & right for your initrd.
            
            Chroot -- How-to
            To chroot into sda2 from the Live Kubuntu CD at Konsole:
            sudo mkdir /media/fixthings
            sudo mount /dev/sda2 /media/fixthings
            sudo chroot  /media/fixthings
            (Now you are “in” sda2 as root and can work from there as if you were actually booted into it.)
            Once your problem is solved please edit the first post of your topic and add [SOLVED] in front of the subject. In that way, others can benefit from your experience!

            Comment


              #7
              Re: Kernel says "File not found" at boot

              JohanLingen -- yes, that's what I did. It has never messed anything up, but sometimes it doesn't fix it or fixes it only until the next kernel update.

              And yes, I would think you could instead " ...just re-install the kernel in adept or so?" At least, you could try it.

              Did you check to see if initrd's were missing (corresponding to new kernels)? Because we need to be sure of our Error 15 diagnosis (=> is a file missing? if so, which one?).


              In the past, when the initrd was missing, I have at times seen that the correct backup was there (.bak). So, in root mode I deleted the .bak extension (from the right initrd file) and that fixed the boot problem! THAT is, however, rather quick & dirty, perhaps even sloppy.


              An intellectual says a simple thing in a hard way. An artist says a hard thing in a simple way. Charles Bukowski

              Comment


                #8
                Re: Kernel says "File not found" at boot

                re-installation of -19 kernel files did not resolve the issue

                I quadruple-checked that the initrd.img... files are in place. Both the normal and the .bak files exist.

                Is there no way to prevent this from happening in the feature and is there any chance that the issue will resolve itself on the next kernel update? I cannot imagine that the kernel files are dependent upon each other. But then it would be very coincident that I have had 3 kernel entries in grub that don't start...
                Once your problem is solved please edit the first post of your topic and add [SOLVED] in front of the subject. In that way, others can benefit from your experience!

                Comment


                  #9
                  Re: Kernel says "File not found" at boot

                  Hmmm. Puzzling.
                  I mean “File Not Found” is that simple.
                  And the only two files that can be “not found” are the kernel & initrd's.
                  Both directly under /boot
                  both in the second hard drive, the first partition (i.e., in (hd1,0)).
                  ==>> ((hd1,0) is correct, right? And that's IS where the new files should be and are?)
                  ==>> And the UUID for (hd1,0) is correct?
                  UUIDs, listing:
                  From Live CD and HD: ls /dev/disk/by-uuid/ -alh
                  From HD: blkid

                  And, finally, you read the GRUB “error post” under my how-to, so you know the usual and standard stuff (e.g., misspellings in menu.lst, etc.).
                  Maybe someone else will look in here and help out. I'll keep looking at it, too.
                  An intellectual says a simple thing in a hard way. An artist says a hard thing in a simple way. Charles Bukowski

                  Comment


                    #10
                    Re: Kernel says "File not found" at boot

                    It wouldn't hurt to run at Konsole, Live CD:
                    sudo fdisk -lu
                    An intellectual says a simple thing in a hard way. An artist says a hard thing in a simple way. Charles Bukowski

                    Comment


                      #11
                      Re: Kernel says "File not found" at boot

                      The files are in place and menu.lst seems correct (in post #2 I pasted t he -16 entry and the -17 entry, which seem quite identical to me. Furthermore I copy-pasted the -16 entry in kwrite and changed all "-16" to "-17", but with no effect; during boot I edited the -16 grub entry to start as -19, but also without effect other then error 15).

                      I wil try complete removal of the -17 kernel files and re-install them.

                      ---edit---

                      Here are some things I tried:

                      I completely removed all -17, -18 and -19 files and installed the -19 kernel files.

                      I copied the working -16 files in /boot and named them -19.

                      I copied intitrd...-19.bak to initrd...-19

                      All result in error 15 File not found.
                      Once your problem is solved please edit the first post of your topic and add [SOLVED] in front of the subject. In that way, others can benefit from your experience!

                      Comment


                        #12
                        Re: Kernel says "File not found" at boot

                        Well, you are persistent with this and working hard!
                        And, just to double check, the output of
                        sudo fdisk -lu
                        makes sense, right?
                        And the UUID in menu.lst lines is right, right?
                        An intellectual says a simple thing in a hard way. An artist says a hard thing in a simple way. Charles Bukowski

                        Comment


                          #13
                          Re: Kernel says "File not found" at boot

                          blkid is the same as in menu.lst; the UUID-entries in menu.lst are also equal for -16 and others, while -16 works and the rest doesn't.

                          I ran fdisk -lu from the system (not from live-cd):

                          Code:
                          Schijf /dev/sda: 40.0 GB, 40027029504 bytes
                          255 koppen, 63 sectoren/spoor, 4866 cilinders, totaal 78177792 sectoren
                          Eenheid = sectoren van 1 * 512 = 512 bytes
                          Schijf-ID: 0x0001668e
                          
                           Apparaat Opstart  Begin    Einde   Blokken  ID Systeem
                          /dev/sda1  *     63  74878964  37439451  83 Linux
                          /dev/sda2    74878965  78172289   1646662+  5 Uitgebreid
                          /dev/sda5    74879028  78172289   1646631  82 Linux wisselgeheugen
                          
                          Schijf /dev/sdb: 122.9 GB, 122942324736 bytes
                          255 koppen, 63 sectoren/spoor, 14946 cilinders, totaal 240121728 sectoren
                          Eenheid = sectoren van 1 * 512 = 512 bytes
                          Schijf-ID: 0x0005f6a2
                          
                           Apparaat Opstart  Begin    Einde   Blokken  ID Systeem
                          /dev/sdb1       63  23438834  11719386  83 Linux
                          /dev/sdb2    233263800  240107489   3421845  83 Linux
                          /dev/sdb3    225456210  233263799   3903795  82 Linux wisselgeheugen
                          /dev/sdb4    23438835  225456209  101008687+ 83 Linux
                          
                          Partitietabel-items liggen niet in schijfvolgorde.
                          Once your problem is solved please edit the first post of your topic and add [SOLVED] in front of the subject. In that way, others can benefit from your experience!

                          Comment


                            #14
                            Re: Kernel says "File not found" at boot

                            That looks normal.

                            I'm assuming that
                            sda1 = (hd0,0)
                            and that
                            (sdb1) = (hd1,0)
                            and that it is the (hd1,0) where your problems are, right?
                            Your BIOS is set to boot first from the sda drive (=hd0).
                            GRUB is installed to the Master Boot record of sda.
                            And GRUB points to the Linux system on sdb1 (=(hd1,0)),
                            and that's how your sdb1 Linux boots.
                            That looks like your setup.

                            We just want to be sure that the (hd1,0) is correct in menu.lst (i.e., that it is NOT supposed to be (hd0,0)).


                            (GRUB counts drives and partition starting from zero. So the first hard drive (set to boot from BIOS) is hd0; and the first partition on a drive is partition 0; e.g., (hd1,0) = the first partition (partition 0) on the second hard drive (hd1).)


                            EDIT added:
                            Just a comment: 82 is swap and 5 is an Extended partition.
                            "Partitietabel-items liggen niet in schijfvolgorde."
                            That means partitions are not in disk order (I think that's what it says!) , which as you can see, they are not. But that is OK--no problem there. (in disk order, it would be sdb1, sdb4, sdb3, then sdb2 -- but, as I say, this is not a problem here).


                            An intellectual says a simple thing in a hard way. An artist says a hard thing in a simple way. Charles Bukowski

                            Comment


                              #15
                              Re: Kernel says "File not found" at boot

                              all correct, except that I thought that I had grub installed at /dev/hdb. But I can be mistaken in that matter, it is how I want it to be, but I am not sure I made it work that way.

                              hd0,1 is causing problems. Or the kernel files are the problem, I don't know. At first I thought it was a kernel bug that would be solved soon as many people would be suffering from it, but that turned out to be untrue.

                              BIOS should be set to boot from hdb, but I'll check that.

                              ---edit---
                              BIOS is set to start from slave HD
                              Once your problem is solved please edit the first post of your topic and add [SOLVED] in front of the subject. In that way, others can benefit from your experience!

                              Comment

                              Working...
                              X