Announcement

Collapse
No announcement yet.

Boot/Grub issue

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

    Boot/Grub issue

    Have a triple boot system. First is Kubuntu 7.04, Second is Ubuntu 7.10 and final is XP. All set on seperate drives. When I go to boot into Ubuntu I get error "11 unrecognized device string".

    Here is grub file:

    ## ## End Default Options ##

    title Ubuntu, kernel 2.6.20-16-generic
    root (hd0,0)
    kernel /boot/vmlinuz-2.6.20-16-generic root=UUID=28227cd0-9e12-4b0f-b89d-7700dc15a503 ro quiet splash
    initrd /boot/initrd.img-2.6.20-16-generic
    quiet
    savedefault

    title Ubuntu, kernel 2.6.20-16-generic (recovery mode)
    root (hd0,0)
    kernel /boot/vmlinuz-2.6.20-16-generic root=UUID=28227cd0-9e12-4b0f-b89d-7700dc15a503 ro single
    initrd /boot/initrd.img-2.6.20-16-generic

    title Ubuntu, kernel 2.6.20-15-generic
    root (hd0,0)
    kernel /boot/vmlinuz-2.6.20-15-generic root=UUID=28227cd0-9e12-4b0f-b89d-7700dc15a503 ro quiet splash
    initrd /boot/initrd.img-2.6.20-15-generic
    quiet
    savedefault

    title Ubuntu, kernel 2.6.20-15-generic (recovery mode)
    root (hd0,0)
    kernel /boot/vmlinuz-2.6.20-15-generic root=UUID=28227cd0-9e12-4b0f-b89d-7700dc15a503 ro single
    initrd /boot/initrd.img-2.6.20-15-generic

    title Ubuntu, memtest86+
    root (hd0,0)
    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 an existing
    # linux installation on /dev/sda1.

    title Ubuntu 7.10, kernel 2.6.22-14-generic
    root (hd1,0)
    kernel /boot/vmlinuz-2.6.22-14-generic root=UUID=e0f09388-71b3-42be-8b1c-4d8fe3c9fd19 ro quiet splash
    initrd /boot/initrd.img-2.6.22-14-generic
    quiet


    # This entry automatically added by the Debian installer for an existing
    # linux installation on /dev/sda1.

    title Ubuntu 7.10, kernel 2.6.22-14-generic (recovery mode)
    root (hd1,0)
    kernel /boot/vmlinuz-2.6.22-14-generic root=UUID=e0f09388-71b3-42be-8b1c-4d8fe3c9fd19 ro single
    initrd /boot/initrd.img-2.6.22-14-generic
    quiet

    # This entry automatically added by the Debian installer for an existing
    # linux installation on /dev/sda1.

    title Ubuntu 7.10, kernel 2.6.20-16-generic
    root (hd1,0)
    kernel /boot/vmlinuz-2.6.20-16-generic root=UUID=e0f09388-71b3-42be-8b1c-4d8fe3c9fd19 ro quiet splash
    initrd /boot/initrd.img-2.6.20-16-generic
    quiet

    # This entry automatically added by the Debian installer for an existing
    # linux installation on /dev/sda1.

    title Ubuntu 7.10, kernel 2.6.20-16-generic (recovery mode)
    root (hd1,0)
    kernel /boot/vmlinuz-2.6.20-16-generic root=UUID=e0f09388-71b3-42be-8b1c-4d8fe3c9fd19 ro single
    initrd /boot/initrd.img-2.6.20-16-generic

    # This entry automatically added by the Debian installer for an existing
    # linux installation on /dev/sda1.

    title Ubuntu, memtest86+
    root (hd1,0)
    kernel /boot/memtest86+.bin
    savedefault
    boot


    # This entry automatically added by the Debian installer for a non-linux OS
    # on /dev/sdb1.
    title Microsoft Windows XP Professional
    root (hd2,0)
    savedefault
    makeactive
    map (hd0) (hd2)
    map (hd2) (hd0)
    chainloader +1


    My device map is:

    (hd0) /dev/hda
    (hd1) /dev/sda
    (hd2) /dev/sdb

    If I move down to load Ubuntu with the backup older kernel it will boot fine. What do I need to fix so I can boot into new kernel. Am trying to get everything working in Ubuntu before I upgrade Kubuntu to 7.10

    #2
    Re: Boot/Grub issue

    Puzzling. A device string is anything that refers to a device—a hard drive, a partition, a path for such.
    Error 11 indicates that GRUB doesn’t like the syntax (using the filesystem you’ve used for Ubuntu).
    The only lines that could cause this are three: the root, the kernel, and the initrd lines of the Ubuntu boot stanza:

    title Ubuntu 7.10, kernel 2.6.22-14-generic
    root (hd1,0)
    kernel /boot/vmlinuz-2.6.22-14-generic root=UUID=e0f09388-71b3-42be-8b1c-4d8fe3c9fd19 ro quiet splash
    initrd /boot/initrd.img-2.6.22-14-generic
    quiet

    I’m assuming that you are able to boot Kubuntu and Windows.

    The UUID must be correct because the older kernel line has the same. Besides, if that were not correct in /etc/fstab, I think you’d get an error like the disk does not exist or something similar.

    I don’t see a syntax error or misspelling or a period that should be a comma or etc. in these parts:
    /boot/vmlinuz-2.6.22-14-generic
    /boot/initrd.img-2.6.22-14-generic
    or in
    root (hd1,0).

    I presume that /boot/vmlinuz-2.6.22-14-generic does actually exist, but even if it didn’t, I don’t think you get Error 11 (you’d get another “can’t find device/file” or “no such device/file.”).

    Maybe someone else can see it. I’ll think about it.

    In the meantime, I would copy that boot stanza (just those 5 lines for the new Ubuntu), save it somewhere safe (say in OOo Writer .odt), and then re-type it manually back into /boot/grub/menu.lst, same location, making sure you allow for spaces (eg after root, after each part of the kernel line), typing carefully, save (after you edit as root), exit, and re-boot to test it.

    Your Windows entry looks right, and it boots, and device.map looks consistent with everything else.

    I just don’t see anything wrong with your strings there; maybe I’m looking too hard. It looks the same as the lines of the old Ubuntu kernel, which, as you say, does boot.




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

    Comment


      #3
      Re: Boot/Grub issue

      Make sure you have spaces between everything.

      Check your Windows entry too, spaces between (hd2) and (hd0), etc.
      An intellectual says a simple thing in a hard way. An artist says a hard thing in a simple way. Charles Bukowski

      Comment


        #4
        Re: Boot/Grub issue

        The device lines do look correctly-formed, as far as I can see, but I'm curious about the location of that /boot directory that you are using, and the sequence that I observe in your file. Questions:

        1. Are both your Linux kernels in the same /boot directory? If not, why set them up with /boot directories separate from the rest of their root filesystems? If so, then the UUID is wrong for one of the versions, I would think -- if it's one "consolidated" boot directory, then only one UUID should appear.

        2. 7.10 being newer than 7.04, one would think it was the last Linux installed, which would put it "above the line". But you have the older one first, and 7.10 below the "Debian Automagic Kernels" line -- is that intentional? What was the sequence of installation?

        { scratching my head, like Qqmike! }

        Comment


          #5
          Re: Boot/Grub issue

          Seems to me, that some assumptions are/have been made regarding the problem at hand. As no one yet has asked, I will.

          technoidiot - you said you are triple-booting, with Kubuntu, Ubuntu, and XP "on separate drives." What type of setup Are you running a desktop PC or laptop? If a desktop, are all the drives internal, or are any of them external? If external, how are they connected - USB or If a laptop, are the other two (unless your laptop had two internal drives) connected via USB??
          Windows no longer obstructs my view.
          Using Kubuntu Linux since March 23, 2007.
          "It is a capital mistake to theorize before one has data." - Sherlock Holmes

          Comment


            #6
            Re: Boot/Grub issue

            Not sure about the location of the boot directory? It came from my grub file on the Kubuntu install.

            Here is my current configuration:

            IDE drive - Kubuntu install one partition full drive
            SATA drive #1 - Ubuntu 7.10 one partition full drive
            SATA drive #2 - XP

            Was only a SATA system then wanted to learn Linux. Tried different ones on second SATA drive. Ended up with Ubuntu 7.04 but couldn't get wireless working. Installed IDE drive put Kubuntu on it and got wireless up and going. Decided to upgrade Ubuntu to learn and work on wireless issue. Still no wireless on that system but want to get boot issue fixed first.

            Primary reason for setting up this way is I can unplug a drive and not worry about losing other systems or files, etc. As I said I can boot into the older kernel.

            BTW I did do a grub reconfiguration in the event I did mistype something and the listing is the result. This reconfiguration was done by the Kubuntu system.

            I was thinking maybe I have to issue a map line on the Ubuntu 7.10 section? Not sure if that would help or hinder?

            The reason the 7.10 is below the older 7.04 is they are separate drives. No matter how I have tried to change the BIOS it boots the first IDE drive which is the older system.

            My setup is a desktop with all internal drives. One IDE drive and two SATA drives. (still have room for one more IDE drive) They are connected by either IDE or SATA cables.

            Comment


              #7
              Re: Boot/Grub issue

              Well, Error 11 is a syntax error.
              So, how about the syntax?

              Other possibility is that GRUB is trying to read a Linux system when in fact there’s Windows there (or the other way).

              BIOS is set to boot from (hd0) – right?

              You might try to re-install GRUB to (hd0).
              You can also use the GRUB geometry command to verify exactly what OS is on what drive:
              How To GRUB Methods - Toolkit
              http://kubuntuforums.net/forums/inde...opic=3081671.0


              What gets me is the older Ubuntu kernel does boot, and it is on the same drive as the newer kernel.
              Suggests a syntax error – make sure the spaces are there, the periods are not commas, etc.
              Re-type it by hand.



              EDIT:
              BTW, it's bad news mixing IDE & SATA for the GRUB bootloader--things can get complicated or confusing. However, the geometry command along with re-installing GRUB usually takes care of all that stuff--knowing exactly where everything is, and manually ensuring that GRUB is installed where you want it to be installed.
              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: Boot/Grub issue

                I figured the syntax was incorrect also and rechecked then had the GRUB fix link so I followed the instructions to fix the GRUB menu. Still got the same error. BIOS is set to boot from (hd0). Going to get geometry and post is after I have run and (read) the How To.

                Will also retype by hand, then I'll be back with all the results.

                This has me stumped as the boot operation was fine prior to the upgrade of Ubuntu 7.04 to 7.10.

                Comment


                  #9
                  Re: Boot/Grub issue

                  I read of a case where such an update caused a syntax error like this.
                  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: Boot/Grub issue

                    Here,

                    get into Kubuntu or Ubuntu.
                    At Konsole, type
                    sudo grub
                    press Enter
                    get the grub> prompt
                    type geometry (hd<press the TAB key>
                    (no closed ) )that returns your drives
                    explore each one now as follows:
                    grub> geometry (hd0)
                    grub> geometry (hd1)
                    grub > geometry (hd2)
                    hopefully, you will be able to confirm what is on each drive, just to be sure here that Windows didn't get swapped with a Linux drive.
                    An intellectual says a simple thing in a hard way. An artist says a hard thing in a simple way. Charles Bukowski

                    Comment

                    Working...
                    X