Announcement

Collapse
No announcement yet.

[SOLVED] Kernel 2.6.24-14 and -15 won't boot

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

    [SOLVED] Kernel 2.6.24-14 and -15 won't boot

    Hey all,

    I run Kubuntu 8.04 with KDE3.. I got some updatesrecently, first kernel -14 then kernel -15, but neither of them will boot.. I get the Kubuntu logo with the blue loading bar.. nothing happens.. Alt+F2 shows me this

    Starting up
    Loading please wait
    <few minutes go by>
    Check root= bootarg cat /proc/cmdline
    or missing modules, devices: cat /proc/modules ls /dev
    ALERT! /dev/disk/by-uuid/9c60e178-a4eb-48d0-936e-26962c7f48e3 does not exist.
    Dropping to a shell!

    Busybox 1.1.3 (Debian 1:1.1.3-5ubuntu12) Built-in shell (ash)
    Enter 'help' for a list of built-in commands

    (initramfs)_

    No clue what all this is, I'm fairly new to linux...
    Rebooting (Ctrl Alt Del) and delecting the -12 kernel in the grub menu works fine.. Kubuntu loads and works right away..

    Can anyone explain what's going on here? Error in the updates? Or is it something with my computer?

    Cheers
    Linda

    #2
    Re: Kernel 2.6.24-14 and -15 won't boot

    I have been seeing that problem around this forum lately so I just boot from the .14 kernel for now (mine works )

    Hardy is still beta so I am sure this issue will be resolved shortly.

    I see you have posted the issue with launchpad so you should be getting a few responses within due time
    HP Pavilion dv6 core i7 (Main)
    4 GB Ram
    Kubuntu 18.10

    Comment


      #3
      Re: Kernel 2.6.24-14 and -15 won't boot

      I shall wait patiently then.
      the -12 kernel works fine as far as I can tell (whatever that means )

      Thanks for your reply

      Comment


        #4
        Re: Kernel 2.6.24-14 and -15 won't boot

        When I accepted the upgrade for the -15 kernel, and when it offered me the new Grub boot menu, I "accepted the package maintainer's version". That was a mistake. For reasons unknown, it wrote a "rootflags=data=writeback" option into the menu.lst, and also on the kernel boot line. That caused mine to "mis-boot" to the busybox. Removing the rootflags option, and fixing the kernel boot line, restored the correct boot into the -15 kernel.

        I'm tossing this out in case it is a problem for others.

        Comment


          #5
          Re: Kernel 2.6.24-14 and -15 won't boot

          Where would I find those options? How do you fix the kernel bootline?

          This is my menu.lst

          Code:
          # menu.lst - See: grub(8), info grub, update-grub(8)
          #      grub-install(8), grub-floppy(8),
          #      grub-md5-crypt, /usr/share/doc/grub
          #      and /usr/share/doc/grub-doc/.
          
          ## default num
          # Set the default entry to the entry number NUM. Numbering starts from 0, and
          # the entry number 0 is the default if the command is not used.
          #
          # You can specify 'saved' instead of a number. In this case, the default entry
          # is the entry saved with the command 'savedefault'.
          # WARNING: If you are using dmraid do not use 'savedefault' or your
          # array will desync and will not let you boot your system.
          default		0
          
          ## timeout sec
          # Set a timeout, in SEC seconds, before automatically booting the default entry
          # (normally the first entry defined).
          timeout		10
          
          ## hiddenmenu
          # Hides the menu by default (press ESC to see the menu)
          #hiddenmenu
          
          # Pretty colours
          #color cyan/blue white/blue
          
          ## password ['--md5'] passwd
          # If used in the first section of a menu file, disable all interactive editing
          # control (menu entry editor and command-line) and entries protected by the
          # command 'lock'
          # e.g. password topsecret
          #   password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
          # password topsecret
          
          #
          # examples
          #
          # title		Windows 95/98/NT/2000
          # root		(hd0,0)
          # makeactive
          # chainloader	+1
          #
          # title		Linux
          # root		(hd0,1)
          # kernel	/vmlinuz root=/dev/hda2 ro
          #
          
          #
          # Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST
          
          ### BEGIN AUTOMAGIC KERNELS LIST
          ## lines between the AUTOMAGIC KERNELS LIST markers will be modified
          ## by the debian update-grub script except for the default options below
          
          ## DO NOT UNCOMMENT THEM, Just edit them to your needs
          
          ## ## Start Default Options ##
          ## default kernel options
          ## default kernel options for automagic boot options
          ## If you want special options for specific kernels use kopt_x_y_z
          ## where x.y.z is kernel version. Minor versions can be omitted.
          ## e.g. kopt=root=/dev/hda1 ro
          ##   kopt_2_6_8=root=/dev/hdc1 ro
          ##   kopt_2_6_8_2_686=root=/dev/hdc2 ro
          # kopt=root=UUID=9c60e178-a4eb-48d0-936e-2b962c7f48e3 ro
          
          ## Setup crashdump menu entries
          ## e.g. crashdump=1
          # crashdump=0
          
          ## default grub root device
          ## e.g. groot=(hd0,0)
          # groot=(hd0,7)
          
          ## should update-grub create alternative automagic boot options
          ## e.g. alternative=true
          ##   alternative=false
          # alternative=true
          
          ## should update-grub lock alternative automagic boot options
          ## e.g. lockalternative=true
          ##   lockalternative=false
          # lockalternative=false
          
          ## additional options to use with the default boot option, but not with the
          ## alternatives
          ## e.g. defoptions=vga=791 resume=/dev/hda5
          # defoptions=quiet splash
          
          ## should update-grub lock old automagic boot options
          ## e.g. lockold=false
          ##   lockold=true
          # lockold=false
          
          ## Xen hypervisor options to use with the default Xen boot option
          # xenhopt=
          
          ## Xen Linux kernel options to use with the default Xen boot option
          # xenkopt=console=tty0
          
          ## altoption boot targets option
          ## multiple altoptions lines are allowed
          ## e.g. altoptions=(extra menu suffix) extra boot options
          ##   altoptions=(recovery) single
          # altoptions=(recovery mode) single
          
          ## controls how many kernels should be put into the menu.lst
          ## only counts the first occurence of a kernel, not the
          ## alternative kernel options
          ## e.g. howmany=all
          ##   howmany=7
          # howmany=all
          
          ## should update-grub create memtest86 boot option
          ## e.g. memtest86=true
          ##   memtest86=false
          # memtest86=true
          
          ## should update-grub adjust the value of the default booted system
          ## can be true or false
          # updatedefaultentry=false
          
          ## should update-grub add savedefault to the default options
          ## can be true or false
          # savedefault=false
          
          ## ## End Default Options ##
          
          title		Ubuntu hardy (development branch), kernel 2.6.24-15-generic
          root		(hd0,7)
          kernel		/boot/vmlinuz-2.6.24-15-generic root=UUID=9c60e178-a4eb-48d0-936e-2b962c7f48e3 ro quiet splash
          initrd		/boot/initrd.img-2.6.24-15-generic
          quiet
          
          title		Ubuntu hardy (development branch), kernel 2.6.24-15-generic (recovery mode)
          root		(hd0,7)
          kernel		/boot/vmlinuz-2.6.24-15-generic root=UUID=9c60e178-a4eb-48d0-936e-2b962c7f48e3 ro single
          initrd		/boot/initrd.img-2.6.24-15-generic
          
          title		Ubuntu hardy (development branch), kernel 2.6.24-14-generic
          root		(hd0,7)
          kernel		/boot/vmlinuz-2.6.24-14-generic root=UUID=9c60e178-a4eb-48d0-936e-2b962c7f48e3 ro quiet splash
          initrd		/boot/initrd.img-2.6.24-14-generic
          quiet
          
          title		Ubuntu hardy (development branch), kernel 2.6.24-14-generic (recovery mode)
          root		(hd0,7)
          kernel		/boot/vmlinuz-2.6.24-14-generic root=UUID=9c60e178-a4eb-48d0-936e-2b962c7f48e3 ro single
          initrd		/boot/initrd.img-2.6.24-14-generic
          
          title		Ubuntu hardy (development branch), kernel 2.6.24-12-generic
          root		(hd0,7)
          kernel		/boot/vmlinuz-2.6.24-12-generic root=UUID=9c60e178-a4eb-48d0-936e-2b962c7f48e3 ro quiet splash
          initrd		/boot/initrd.img-2.6.24-12-generic
          quiet
          
          title		Ubuntu hardy (development branch), kernel 2.6.24-12-generic (recovery mode)
          root		(hd0,7)
          kernel		/boot/vmlinuz-2.6.24-12-generic root=UUID=9c60e178-a4eb-48d0-936e-2b962c7f48e3 ro single
          initrd		/boot/initrd.img-2.6.24-12-generic
          
          title		Ubuntu hardy (development branch), memtest86+
          root		(hd0,7)
          kernel		/boot/memtest86+.bin
          quiet
          
          ### END DEBIAN AUTOMAGIC KERNELS LIST
          
          # This is a divider, added to separate the menu items below from the Debian
          # ones.
          title		Other operating systems:
          root
          
          
          # This entry automatically added by the Debian installer for a non-linux OS
          # on /dev/hda1
          title		Microsoft Windows XP Professional
          root		(hd0,0)
          savedefault
          makeactive
          chainloader	+1
          Can you tell me if your problem appears here too?
          I'm not very experienced with all this ^_^

          Thanks!

          Comment


            #6
            Re: Kernel 2.6.24-14 and -15 won't boot

            You did not get bitten by the same critter. If you had the problem, it would appear here:

            # defoptions=quiet splash rootflags=data=writeback
            and again here:


            kernel /boot/vmlinuz-2.6.24-15-generic root=UUID=9c60e178-a4eb-48d0-936e-2b962c7f48e3 ro quiet splash rootflags=data=writeback

            Comment


              #7
              Re: Kernel 2.6.24-14 and -15 won't boot

              Ok thanks

              guess it's waiting for someone else here or at
              launchpad to have an idea which critter it was here

              Comment


                #8
                Re: Kernel 2.6.24-14 and -15 won't boot


                @BlueRose -- check your /etc/fstab file, and see whether there has been a change to your UUID numbers. The UUID number for /dev/hd07 must be a match to the UUID shown on the kernel boot line above. If they don't match, change the one it /boot/grub/menu.lst to match /etc/fstab.

                Comment


                  #9
                  Re: Kernel 2.6.24-14 and -15 won't boot

                  Aha! The problem has been found by Rog131, here:

                  http://kubuntuforums.net/forums/inde...seen#msg125145


                  In etc/fstab, you must use "UUID=UUID=9c60e178-a4eb-48d0-936e-2b962c7f48e3" to mount, or else "/dev/sd07"

                  Comment


                    #10
                    Re: Kernel 2.6.24-14 and -15 won't boot

                    Ok before I screw things up

                    this is currently my /etc/fstab (running the -12 kernel)
                    Code:
                    # /etc/fstab: static file system information.
                    #
                    # <file system> <mount point>  <type> <options>    <dump> <pass>
                    proc      /proc      proc  defaults    0    0
                    # /dev/hda8
                    UUID=9c60e178-a4eb-48d0-936e-2b962c7f48e3 /        ext3  relatime,errors=remount-ro 0    1
                    # /dev/hda9
                    UUID=aff8435e-5214-4eff-99f9-62a7edcccabb /home      ext3  relatime    0    2
                    # /dev/hda7
                    UUID=8C10DEE010DECFF6 /media/archive ntfs  defaults,umask=007,gid=46 0    1
                    # /dev/sda5
                    UUID=3ACC439ACC434EF7 /media/documents ntfs  defaults,umask=007,gid=46 0    1
                    # /dev/sda9
                    UUID=9EE06C66E06C471D /media/ebooks  ntfs  defaults,umask=007,gid=46 0    1
                    # /dev/sda8
                    UUID=661C5E0C1C5DD79F /media/installs ntfs  defaults,umask=007,gid=46 0    1
                    # /dev/sda7
                    UUID=760854700854317B /media/movies  ntfs  defaults,umask=007,gid=46 0    1
                    # /dev/sda6
                    UUID=243849E33849B518 /media/music  ntfs  defaults,umask=007,gid=46 0    1
                    # /dev/hda5
                    UUID=3698D75198D70DED /media/programs ntfs  defaults,umask=007,gid=46 0    1
                    # /dev/hda1
                    UUID=E690354E90352689 /media/windows ntfs  defaults,umask=007,gid=46 0    1
                    # /dev/hda6
                    UUID=440d8410-a1e7-4cfe-8ffd-892c191cfdba none      swap  sw       0    0
                    /dev/hdd    /media/cdrom0  udf,iso9660 user,noauto,exec,utf8 0    0
                    /dev/hdc    /media/cdrom1  udf,iso9660 user,noauto,exec,utf8 0    0
                    The #comments are a bit weird.. The partitions mounted to windows, programs and archive should be hdaX (all on my 160GB IDE disk.. and the ones mounted to documents, music, movies, installs, ebooks should be sdaX.. which is my 500GB SATA disk.


                    The UUID's in mune.lst are the same for all 3 kernel versions, so I don't think there's the problem. it boots one fine.. however my fstab is weird? Not sure, I have no experience with that, and before I can't enter my system anymore I rather spam here again and let you look over it and tell me if there's something wrong and how to fix it (if you would be so kind , you have been so far)

                    Comment


                      #11
                      Re: Kernel 2.6.24-14 and -15 won't boot

                      Meh -- it's not jumping out at me what's wrong.

                      The distinction between "h" and "s" for hard drives is history -- you might as well forget what you once knew about IDE drives and SCSI drives and SATA drive designations. They're all "s" now, for /etc/fstab purposes. Grub still thinks they're all "h", however.

                      But, since you are mounting by UUID, that's irrelevant, and your UUIDs match, so that's not the problem.

                      I think the "1" at the end of the root mount line in /etc/fstab should be a "2" but again that's irrelevant to booting.

                      Have you to tried to boot -15 in "recovery" mode?

                      Comment


                        #12
                        Re: Kernel 2.6.24-14 and -15 won't boot

                        I haven't yet, but I could do that now of course
                        I'll update shortly how that worked out

                        EDIT: I just rebooted the recovery version of the -15 kernel..
                        It got to
                        [163.253046] /build/buildd/linux-2.6.24/driver/hid/usbhid/hid-core.c: v2.6:USB HID core driver
                        <took a minute>
                        Done

                        and then came the error again:
                        Check root= bootarg cat /proc/cmdline
                        or missing modules, devices: cat /proc/modules ls /dev
                        ALERT! /dev/disk/by-uuid/9c60e178-a4eb-48d0-936e-26962c7f48e3 does not exist.
                        Dropping to a shell!

                        Busybox 1.1.3 (Debian 1:1.1.3-5ubuntu12) Built-in shell (ash)
                        Enter 'help' for a list of built-in commands

                        (initramfs)_

                        So same as the normal boot method I guess..
                        I'm back in 2.6.24-12 now

                        Comment


                          #13
                          Re: Kernel 2.6.24-14 and -15 won't boot

                          dibl: Why do you think it should be a 2 in fstab? what does the 2 mean?
                          (just curious, wanna learn where I can

                          Comment


                            #14
                            Re: Kernel 2.6.24-14 and -15 won't boot

                            The last digit in the mount line for each hard drive partition is the "Files System Check" order value, or "Fsck order".

                            Fsck: Fsck order is to tell fsck what order to check the file systems, if set to "0" file system is ignored.
                            However, upon looking this up, and then looking your /etc/fstab file again, I was wrong -- the oddball is not the root filesystem, which should be a "1" just like you have it. The oddball is the other hard drive partitions, which would normally be "2" like your /home partition is. I don't know why those NTFS partitions are all set at "1".

                            But it's no big deal the way you have it, and I don't believe it is relevant to the booting problem, which must related to a change in the kernel that affects your hardware somehow.

                            Comment


                              #15
                              Re: Kernel 2.6.24-14 and -15 won't boot

                              Ok, I think it's been fixed.. the guys at launchpad told me to try to tka ethe jumper off of the hard disk. Set my pata drive in single driver mode (the disk on which my root partition is). Something weird with Western Digital drives.. anyways. IT WORKED I'm in kernel -15 now.

                              And even better: loading grub doesn't take so long anymore!
                              I had 30sec between post and grub loading stage1.5, then 30sec nothig again, then loading grublease wait (another 20sec or so) before I finally hit the boot menu.. with the jumper gone.. it only took 10 seconds tops from post to menu now that's what I call happy waking up

                              I think this might have been the reason that the openSUSE installer didn't see my pata disk either, just my sata disk.. oh well

                              Thanks again for your help guys

                              Comment

                              Working...
                              X