Announcement

Collapse
No announcement yet.

Remnants from a previous installation

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

    Remnants from a previous installation

    Hello,
    A week ago I tried to install Kubuntu on my USB HDD. Because this was not working properly (I could not get in), it requires some tuning I removed it. I also used the LiveCD a lot.
    Recently I re-installed Kubuntu on my normal HDD (I altered an existing partition) an it's running ! So my machine is dual-boot now. However, when I start my PC I get the regular menu from which I can choose the OS I want. If I choose XP I get another menu which is the same menu when using the LiveCD (btw the CD is not in my player). I want to get rid of that menu. How can I do that ??

    Thanks again,

    Remmelt

    #2
    Re: Remnants from a previous installation

    So, basically you can't log into XP? Are you running Kubuntu 8.10? You may want to start with the System Settings "control panel", go to Advanced -> Grub Editor. If that doesn't get you going, you'll probably need to output more info, we'll let you know what we need :-)

    Cheers!

    Comment


      #3
      Re: Remnants from a previous installation

      Hi,

      I can get into XP, no problem. However after I choose for XP in the boot menu I need to make another choice (that's the same menu as form the LiveBoot CD. I want that menu out of my way !!

      I use Hardy Heron (8.04).

      Eagerly awaiting the rescue

      Remmelt

      Comment


        #4
        Re: Remnants from a previous installation

        Ha, can you load Konsole? And then type "df -h" and send us that output (pls use the "code" tag from the forum message editor if you can). Also, we need the output of "sudo cat /boot/grub/menu.lst"

        Comment


          #5
          Re: Remnants from a previous installation

          Hi,

          Here's the result of df -h

          =================
          remmelt@remmelt:~$ df -h
          Bestandssysteem Grtte Gebr Besch Geb% Aangekoppeld op
          /dev/sda6 19G 2,7G 15G 16% /
          varrun 506M 156K 506M 1% /var/run
          varlock 506M 0 506M 0% /var/lock
          udev 506M 96K 506M 1% /dev
          devshm 506M 0 506M 0% /dev/shm
          lrm 506M 38M 468M 8% /lib/modules/2.6.24-19-generic/volatile
          /dev/sda1 38G 35G 2,9G 93% /C-schijf
          /dev/sdb1 6,0G 1,2G 4,9G 20% /Werk - oude C-schijf
          /dev/sda5 38G 22G 16G 58% /D-schijf
          remmelt@remmelt:~$
          ==================

          and here's the file menu.lst:

          ==============
          remmelt@remmelt:~$ sudo cat /boot/grub/menu.lst
          [sudo] password for remmelt:
          # 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 4

          ## timeout sec
          # Set a timeout, in SEC seconds, before automatically booting the default entry
          # (normally the first entry defined).
          timeout 15

          ## 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=50a1e89a-9823-4e87-aed5-05ca01458ce3 ro

          ## Setup crashdump menu entries
          ## e.g. crashdump=1
          # crashdump=0

          ## default grub root device
          ## e.g. groot=(hd0,0)
          # groot=(hd0,5)

          ## 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 8.04.1, kernel 2.6.24-19-generic
          root (hd0,5)
          kernel /boot/vmlinuz-2.6.24-19-generic root=UUID=50a1e89a-9823-4e87-aed5-05ca01458ce3 ro quiet splash
          initrd /boot/initrd.img-2.6.24-19-generic
          quiet

          title Ubuntu 8.04.1, kernel 2.6.24-19-generic (recovery mode)
          root (hd0,5)
          kernel /boot/vmlinuz-2.6.24-19-generic root=UUID=50a1e89a-9823-4e87-aed5-05ca01458ce3 ro single
          initrd /boot/initrd.img-2.6.24-19-generic

          title Ubuntu 8.04.1, memtest86+
          root (hd0,5)
          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/sda1
          title Microsoft Windows XP Home Edition
          root (hd0,0)
          savedefault
          makeactive
          chainloader +1

          remmelt@remmelt:~$
          ===============

          Again eagerly awaiting the light 8)

          Remmelt

          Comment


            #6
            Re: Remnants from a previous installation

            I'll look at this later. If anyone else reading this thread has a dual boot system (I don't), can you pls check whether the Windows entry is correct in the menu.lst?

            Comment


              #7
              Re: Remnants from a previous installation

              So, your Windows partition is the one at /dev/sda1, right? What's in that small partition /deb/sdb1? Is that a USB or flashdirive? Can you disconnect any other device? Are you sure the BIOS is setup to boot from the harddrive and not a removable device?

              For what you describe, it looks like grub is loading another bootloader in a different partition, and that one was allowing you to log into XP. But the menu.lst seems ok! Unless there is another grub installed in the partition where you have Windows, in which case I think there is little to do and I would just live with this issue (a lot better than reinstalling Windows if you screw something up).

              Something you can try is pushing the letter "e" (edit) in grub at boot time, and edit the windows entry on the fly, and see if it helps. These changes are not permanent, grub always restores the entries in menu.lst. I would try the following:

              * change (hd0,0) into (hd0,1), or other similar combinations, maybe the device map is wrong.
              * change "root" into "rootnoverify"
              * remove "makeactive"

              If any of these options work, you can put them in the menu.lst first, carefully (backup first, etc):
              http://boff.wordpress.com/2007/01/17...rub-boot-menu/

              Best!



              Comment


                #8
                Re: Remnants from a previous installation

                Hi,

                The changes you suggested are not working. The problem remains.

                I do not believe that I need to live with this (it's not a major problem but it is a plain stupid problem). Suggestions welcome !!

                Remmelt

                Comment


                  #9
                  Re: Remnants from a previous installation

                  I'm not certain of this, but the description of what you observe sounds like you have managed to install Grub on two different drives or partitions, such that the first Grub that boots is pointing to the second one, which actually boots your Kubuntu installation. I didn't even know that was possible -- Qqmike is the Grub expert around here. His excellent guidance is here.

                  I'd like to see these three outputs from your system:

                  Code:
                  sudo fdisk -lu
                  Code:
                  sudo blkid
                  Code:
                  cat /etc/fstab

                  Comment


                    #10
                    Re: Remnants from a previous installation

                    Originally posted by dibl
                    I'm not certain of this, but the description of what you observe sounds like you have managed to install Grub on two different drives or partitions, such that the first Grub that boots is pointing to the second one, which actually boots your Kubuntu installation.
                    Yes, that's what I was saying above, and it's why I asked all these questions (which went unanswered, so I am probably giving up on this thread):

                    So, your Windows partition is the one at /dev/sda1, right? What's in that small partition /deb/sdb1? Is that a USB or flashdirive? Can you disconnect any other device? Are you sure the BIOS is setup to boot from the harddrive and not a removable device?

                    Comment


                      #11
                      Re: Remnants from a previous installation

                      Imilano,

                      Sorry for not exactly answering your questions.

                      Answers are:
                      Yes it is on sda1 as you can see in the menu.lst file.
                      The small partition is just a small partition and not an external drive of any kind.
                      I could disconnect all other devices ? (only printer, external USB HDD, external memory card reader).
                      BIOS is setup to boot from CD-rom, and then from HDD (internal one).

                      Next time, do no be afraid to ask again !!

                      Dible: I will post the output later on. Gotta go now. Thanks for jumping in !

                      Remmelt

                      Comment


                        #12
                        Re: Remnants from a previous installation

                        No worries

                        Where is the small partition then? Apparently in the external drive, because the name is /dev/sdb1 (note the "b", it denotes the second drive).

                        Please disconnect the external usb HDD and try rebooting again, make sure there is nothing on the CDrom. I have a hunch you are loading a GRUB instance from sdb (the USB HDD).

                        Good luck!

                        Comment


                          #13
                          Re: Remnants from a previous installation

                          Hi,

                          Disconnecting the external drive (USB-HDD) did not help. Oh, BTW the small partition is on my internal HDD.

                          Here are the outputs you are interested in:

                          Code:
                          sudo fdisk -lu
                          [sudo] password for remmelt:

                          Schijf /dev/sda: 122.9 GB, 122942324736 bytes
                          255 koppen, 63 sectoren/spoor, 14946 cilinders, totaal 240121728 sectoren
                          Eenheid = sectoren van 1 * 512 = 512 bytes
                          Schijf-ID: 0x0e9c0e9b

                          Apparaat Opstart Begin Einde Blokken ID Systeem
                          /dev/sda1 * 63 78124094 39062016 c W95 FAT32 (LBA)
                          /dev/sda2 78124095 240107489 80991697+ f W95 Uitgeb. (LBA)
                          /dev/sda5 78124158 156248189 39062016 7 HPFS/NTFS
                          /dev/sda6 156248253 195318269 19535008+ 83 Linux
                          /dev/sda7 195318333 240107489 22394578+ 82 Linux wisselgeheugen

                          Schijf /dev/sdb: 6448 MB, 6448619520 bytes
                          255 koppen, 63 sectoren/spoor, 784 cilinders, totaal 12594960 sectoren
                          Eenheid = sectoren van 1 * 512 = 512 bytes
                          Schijf-ID: 0x0eaf0eae

                          Apparaat Opstart Begin Einde Blokken ID Systeem
                          /dev/sdb1 * 63 12594959 6297448+ b W95 FAT32

                          Schijf /dev/sdh: 500.1 GB, 500107862016 bytes
                          255 koppen, 63 sectoren/spoor, 60801 cilinders, totaal 976773168 sectoren
                          Eenheid = sectoren van 1 * 512 = 512 bytes
                          Schijf-ID: 0x83575884

                          Apparaat Opstart Begin Einde Blokken ID Systeem
                          /dev/sdh1 63 976768064 488384001 7 HPFS/NTFS
                          remmelt@remmelt:~$


                          Code:
                          sudo blkid
                          remmelt@remmelt:~$ sudo blkid
                          /dev/sda1: LABEL="40 GB" UUID="0000-0D7D" TYPE="vfat"
                          /dev/sda5: UUID="EA94F9BF94F98E77" LABEL="Video en film" TYPE="ntfs"
                          /dev/sda6: UUID="50a1e89a-9823-4e87-aed5-05ca01458ce3" TYPE="ext3"
                          /dev/sda7: TYPE="swap" UUID="bdb3e6b7-320a-482a-a45a-55f00bf507d7"
                          /dev/sdb1: LABEL="WERK OUDE C" UUID="0000-0F03" TYPE="vfat"
                          /dev/sdh1: UUID="F4CCC205CCC1C25A" LABEL="PHILIPS External Hard Disk" TYPE="ntfs"
                          remmelt@remmelt:~$


                          Code:
                          cat /etc/fstab
                          remmelt@remmelt:~$ cat /etc/fstab
                          # /etc/fstab: static file system information.
                          #
                          # <file system> <mount point> <type> <options> <dump> <pass>
                          proc /proc proc defaults 0 0
                          # /dev/sda6
                          UUID=50a1e89a-9823-4e87-aed5-05ca01458ce3 / ext3 nouser,relatime,errors=remount-ro,atime,auto,rw,dev,exec,suid 0 1
                          # /dev/sda7
                          UUID=bdb3e6b7-320a-482a-a45a-55f00bf507d7 none swap sw 0 0
                          /dev/scd0 /media/cdrom0 auto user,utf8,atime,auto,rw,dev,exec,suid 0 0
                          /dev/scd1 /media/cdrom1 auto user,utf8,atime,auto,rw,dev,exec,suid 0 0
                          /dev/sda1 /C-schijf vfat uid=0,gid=0,auto,rw,nouser 0 0
                          /dev/sdb1 /Werk\040-\040oude\040C-schijf vfat uid=0,gid=0,auto,rw,nouser 0 0
                          /dev/sda5 /D-schijf auto nouser,atime,auto,rw,nodev,noexec,nosuid 0 0
                          remmelt@remmelt:~$



                          Hopefully this will shed light on this apparent mistery.

                          Remmelt

                          Comment


                            #14
                            Re: Remnants from a previous installation

                            I am really astonished about /dev/sdb ... according to the earlier output of df, and the output of fdisk, /dev/sdb1 is not on the same internal hdd, but on another disk. It seems to be a 6 Gb device, typical of SDHC cards. Are you sure you don't have an SD slot and a card in there? That small parition seems bootable (I think that's what the * in fdisk denotes). Both dsf and fdisk treat them as different devices (the HDD and the sdb drive). Maybe you are booting from there without knowing it!

                            If that's the case, I would try removing that SDHC card. If not, there is something really weird, probably confusing Grub, and clearly confusing fdisk (which would be a shocker, but hey, anything can happen)

                            When you insert/remove removable and external drives, sometimes the internal mapping of devices changes and that confuses GRUB (what used to be the first drive now is the second, etc).

                            Comment


                              #15
                              Re: Remnants from a previous installation

                              Hi,

                              The sdb is for sure a partition on my internal HDD. The fact that it is seen as sdb is probably caused by the fact that it is formatted in a different way ??

                              I would like Qqmike to jump in !!

                              Thanks a lot sofar, Imilano

                              Remmelt.

                              Comment

                              Working...
                              X