Find the answer to your Linux question:
Page 1 of 2 1 2 LastLast
Results 1 to 10 of 17
Hello, My grub got corrupted so that when I tried to boot into my computer I got grub loading stage 1.5 grub loading, please wait error 21 or 17 I ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Nov 2008
    Posts
    72

    Unable to restore most-recent Grub


    Hello,

    My grub got corrupted so that when I tried to boot into my computer I got

    grub loading stage 1.5
    grub loading, please wait
    error 21 or 17

    I restored grub using my super grub disk, but it only saw one grub to restore (hd0,4) which evidently was an older one. It is the older blue menu and not the nice green menu that Mint Gloria produced. I cannot get into Linux Mint all all now. It was the last distro I installed and it was triple booting with XP, Vista, and Ubuntu. I can still access XP and Ubuntu from this menu but not the Linux Mint. I can use BIOS to get into Vista which is on the IDE drive along with Mint, but Vista is no longer listed on the menu. Mint is listed but does not work. I think the Mint entry is for an older drive location where Mint is no longer located. Can anyone help me get back that recent Mint menu or correctly edit the present one so that I can load Mint and/or Vista directly?

  2. #2
    Administrator MikeTbob's Avatar
    Join Date
    Apr 2006
    Location
    Texas
    Posts
    7,864
    Post the output of these commands please, from Ubuntu.
    Code:
    sudo fdisk -l
    *note,,that is a lowercase L in the above code.
    Code:
    sudo cat /boot/grub/menu.lst
    Code:
    sudo ls /boot
    You can always change the boot splash screen after you get your GRUB problems sorted out.
    I do not respond to private messages asking for Linux help, Please keep it on the forums only.
    All new users please read this.** Forum FAQS. ** Adopt an unanswered post.

    I'd rather be lost at the lake than found at home.

  3. #3
    Just Joined!
    Join Date
    Nov 2008
    Posts
    72
    Thanks for the reply. Here are the results:

    arch@arch-desktop:~$ sudo fdisk -l
    [sudo] password for arch:

    Disk /dev/sda: 80.0 GB, 80026361856 bytes
    255 heads, 63 sectors/track, 9729 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk identifier: 0xba1a5abd

    Device Boot Start End Blocks Id System
    /dev/sda1 * 1 7817 62788156 7 HPFS/NTFS
    /dev/sda2 7818 9154 10739452+ 83 Linux
    /dev/sda3 9155 9729 4618687+ 5 Extended
    /dev/sda5 9155 9729 4618656 82 Linux swap / Solaris

    Disk /dev/sdb: 320.0 GB, 320072933376 bytes
    255 heads, 63 sectors/track, 38913 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk identifier: 0x07510751

    Device Boot Start End Blocks Id System
    /dev/sdb1 * 1 35120 282101368+ 7 HPFS/NTFS
    /dev/sdb2 35121 35125 40162+ 7 HPFS/NTFS
    /dev/sdb3 35126 35368 1951897+ 82 Linux swap / Solaris
    /dev/sdb4 35369 38913 28475212+ 5 Extended
    /dev/sdb5 35369 35639 2176776 83 Linux
    /dev/sdb6 35640 38913 26298372+ 83 Linux

    Disk /dev/sdc: 1000.2 GB, 1000204886016 bytes
    255 heads, 63 sectors/track, 121601 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk identifier: 0x09490dc5

    Device Boot Start End Blocks Id System
    /dev/sdc1 * 1 2550 20480000 7 HPFS/NTFS
    Partition 1 does not end on cylinder boundary.
    /dev/sdc2 2550 66291 512000000 7 HPFS/NTFS
    Partition 2 does not end on cylinder boundary.
    /dev/sdc3 66291 82864 133120000 7 HPFS/NTFS
    Partition 3 does not end on cylinder boundary.

    Disk /dev/sdd: 640.1 GB, 640135028736 bytes
    243 heads, 49 sectors/track, 105002 cylinders
    Units = cylinders of 11907 * 512 = 6096384 bytes
    Disk identifier: 0x500b9b3f

    Device Boot Start End Blocks Id System
    /dev/sdd1 * 1 1410 8393938 7 HPFS/NTFS
    /dev/sdd2 1410 22631 126335160 5 Extended
    /dev/sdd3 22631 105002 490400253 7 HPFS/NTFS
    /dev/sdd5 1410 22631 126335128+ 7 HPFS/NTFS

    Disk /dev/sde: 1000.2 GB, 1000204886016 bytes
    255 heads, 63 sectors/track, 121601 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk identifier: 0x5d7d47e1

    Device Boot Start End Blocks Id System
    /dev/sde1 1 3942 31662080 7 HPFS/NTFS
    /dev/sde2 * 3943 6667 21888562+ 7 HPFS/NTFS
    /dev/sde3 6668 48441 335548631 7 HPFS/NTFS
    /dev/sde4 48442 121601 587657700 7 HPFS/NTFS
    arch@arch-desktop:~$ sudo cat /boot/grub/menu.lst
    # menu.lst - See: grub(, info grub, update-grub(
    # grub-install(, grub-floppy(,
    # grub-md5-crypt, /usr/share/doc/grub
    # and /usr/share/doc/grub-doc/.


    # title mint boot on sdd2
    # root (hd3,1)
    # configfile /boot/grub/menu.lst
    # boot


    # title Linux Mint on sdc2
    # root (hd2,1)
    # configfile /boot/grub/menu.lst
    # boot


    ## 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 4

    ## 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=d23f4423-71f5-4588-a9d3-2845cacce7d2 ro

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

    ## 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

    ## specify if running in Xen domU or have grub detect automatically
    ## update-grub will ignore non-xen kernels when running in domU and vice versa
    ## e.g. indomU=detect
    ## indomU=true
    ## indomU=false
    # indomU=detect

    ## 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.10, kernel 2.6.27-7-generic
    # root (hd0,4)
    # kernel /vmlinuz-2.6.27-7-generic root=UUID=d23f4423-71f5-4588-a9d3-2845cacce7d2 ro quiet splash
    # initrd /initrd.img-2.6.27-7-generic
    # quiet

    # title Ubuntu 8.10, kernel 2.6.27-7-generic (recovery mode)
    # root (hd0,4)
    # kernel /vmlinuz-2.6.27-7-generic root=UUID=d23f4423-71f5-4588-a9d3-2845cacce7d2 ro single
    # initrd /initrd.img-2.6.27-7-generic

    # title Ubuntu 8.10, kernel 2.6.24-16-generic
    # root (hd0,4)
    # kernel /vmlinuz-2.6.24-16-generic root=UUID=d23f4423-71f5-4588-a9d3-2845cacce7d2 ro quiet splash
    # initrd /initrd.img-2.6.24-16-generic
    # quiet

    # title Ubuntu 8.10, kernel 2.6.24-16-generic (recovery mode)
    # root (hd0,4)
    # kernel /vmlinuz-2.6.24-16-generic root=UUID=d23f4423-71f5-4588-a9d3-2845cacce7d2 ro single
    # initrd /initrd.img-2.6.24-16-generic

    # title Ubuntu 8.10, kernel 2.6.22-14-generic
    # root (hd0,4)
    # kernel /vmlinuz-2.6.22-14-generic root=UUID=d23f4423-71f5-4588-a9d3-2845cacce7d2 ro quiet splash
    # initrd /initrd.img-2.6.22-14-generic
    # quiet

    # title Ubuntu 8.10, kernel 2.6.22-14-generic (recovery mode)
    # root (hd0,4)
    # kernel /vmlinuz-2.6.22-14-generic root=UUID=d23f4423-71f5-4588-a9d3-2845cacce7d2 ro single
    # initrd /initrd.img-2.6.22-14-generic

    # title Ubuntu 8.10, memtest86+
    # root (hd0,4)
    # kernel /memtest86+.bin
    # quiet

    ### END DEBIAN AUTOMAGIC KERNELS LIST

    # This is a divider, added to separate the menu items below from the Debian
    # ones.
    # title Windows Vista (64-bit)
    # root (hd1,0)
    # savedefault
    # makeactive
    # chainloader +1

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

    title Linux Mint 5
    root (hd2,1)
    configfile /boot/grub/menu.lst
    boot

    title Linux Ubuntu
    root (hd0,4)
    kernel /vmlinuz-2.6.27-9-generic root=UUID=d23f4423-71f5-4588-a9d3-2845cacce7d2 ro quiet splash
    initrd /initrd.img-2.6.27-9-generic
    quiet

    title Linux Ubuntu (recovery mode)
    root (hd0,4)
    kernel /vmlinuz-2.6.27-9-generic root=UUID=d23f4423-71f5-4588-a9d3-2845cacce7d2 ro single
    initrd /initrd.img-2.6.27-9-generic
    arch@arch-desktop:~$ sudo ls /boot
    abi-2.6.22-14-generic lost+found
    abi-2.6.24-16-generic memtest86+.bin
    abi-2.6.27-9-generic Recycled
    abi-2.6.28-11-generic System.map-2.6.22-14-generic
    abi-2.6.28-13-generic System.map-2.6.24-16-generic
    config-2.6.22-14-generic System.map-2.6.27-9-generic
    config-2.6.24-16-generic System.map-2.6.28-11-generic
    config-2.6.27-9-generic System.map-2.6.28-13-generic
    config-2.6.28-11-generic vmcoreinfo-2.6.27-9-generic
    config-2.6.28-13-generic vmcoreinfo-2.6.28-11-generic
    grub vmcoreinfo-2.6.28-13-generic
    initrd.img-2.6.22-14-generic vmlinuz-2.6.22-14-generic
    initrd.img-2.6.24-16-generic vmlinuz-2.6.24-16-generic
    initrd.img-2.6.27-9-generic vmlinuz-2.6.27-9-generic
    initrd.img-2.6.28-11-generic vmlinuz-2.6.28-11-generic
    initrd.img-2.6.28-13-generic vmlinuz-2.6.28-13-generic
    arch@arch-desktop:~$

  4. $spacer_open
    $spacer_close
  5. #4
    Administrator MikeTbob's Avatar
    Join Date
    Apr 2006
    Location
    Texas
    Posts
    7,864
    Ok, I'm having a bit of a hard time identifying which partition is Ubuntu or Mint, Which partition is XP and Vista? Do you know for sure?
    We need to mount the Mint /boot partition to see what's in it.
    I do not respond to private messages asking for Linux help, Please keep it on the forums only.
    All new users please read this.** Forum FAQS. ** Adopt an unanswered post.

    I'd rather be lost at the lake than found at home.

  6. #5
    Just Joined!
    Join Date
    Nov 2008
    Posts
    72
    With 5 drives, I'm not surprised that you would be confused. unfortunately, I am still a Windows user who only occasionally has a look at Linux. I still think in Windows. I've spent very little time looking at Linux file folders. I can tell you in terms of disk type and size where the stuff is. The Ubuntu is on the 320 gb drive along with the WinXP32. The Vista64 is with the the Mint is on the 80gb IDE drive. I also have WinVista32 and Win7RC on one of the two TB disks. The other TB disk which I only got a couple of days ago has WinXP64 and I just put SUSE on it. I have not had success in getting all those OS's to be recognized correctly by Linux, probably because of SATA driver issues, but Mint did recognize the Vista64 on the IDE drive as well as the WinXP32 on the 320GB drive. Most of the disk space is occupied by a ton of movies that I stream through a kind of media extender to a large screen tv. I could attach a screen shot of XP disk management if possible. I clicked on Manage Attachments but nothing happened.

  7. #6
    Just Joined!
    Join Date
    Nov 2008
    Posts
    72
    I am sorry I made a mistake. The WinXP 64 bit version is by itself on one of the TB drives. The SUSE is by itself on the 640GB drive. I was confused because, somehow, SUSE included Windows in its menu even though no Windows drive was even connected at the time it was installed! Does that make sense? It would be nice if I could attach the screen capture.

  8. #7
    Just Joined!
    Join Date
    Nov 2008
    Posts
    72
    Seems like I have been at this too much today. I took a break and realized that what i said originally was correct. I did in fact install the SUSE on the same 1TB drive as the XP64 was on. What confused me when looking at the Disk Management was that I had a blank partition on the 640 gb drive labeled as OPENSUSE. That's because I had intended to put it there but found I needed more space. Despite this confusion I have only one problem really, and that is not being able to access my Mint installation which is on the 80gb IDE drive along with Vista64. There is no bootloader on this disk, though. If I switch to it via BIOS the Vista64 loads. I had been accustomed to accessing it from the main bootloader on the 320GB drive but can no longer do so.

  9. #8
    Just Joined!
    Join Date
    Nov 2008
    Posts
    72
    Any further comments on this please?

  10. #9
    Administrator MikeTbob's Avatar
    Join Date
    Apr 2006
    Location
    Texas
    Posts
    7,864
    MAke a backup of your menu.lst file right now with this command please.
    Code:
    cp /boot/grub/menu.lst /boot/grub/menu.lst.old
    Make sure it was created with this command please.
    ls /boot/grub/ it will be named menu.lst.old
    Now copy and paste the code below to your /boot/grub/menu.lst, reboot and see what happens.....try them all out. I'm sure they wont all work at first but we'll get there.


    Code:
    default 0
    timeout 4
    color cyan/blue white/blue
    
    title Windows Vista (64-bit)
    root (hd1,0)
    savedefault
    makeactive
    chainloader +1
    
    title Windows XP
    root (hd3,1)
    savedefault
    makeactive
    chainloader +1
    
    title Linux Mint 5
    root (hd1,5)
    configfile /boot/grub/menu.lst
    boot
    
    title Linux Ubuntu
    root (hd0,4)
    kernel /vmlinuz-2.6.27-9-generic root=UUID=d23f4423-71f5-4588-a9d3-2845cacce7d2 ro quiet splash
    initrd /initrd.img-2.6.27-9-generic
    quiet
    
    title Linux Ubuntu (recovery mode)
    root (hd0,4)
    kernel /vmlinuz-2.6.27-9-generic root=UUID=d23f4423-71f5-4588-a9d3-2845cacce7d2 ro single
    initrd /initrd.img-2.6.27-9-generic
    Ok I'm still a little confused on a couple of points, we will fine tune them as we go,, if this fails to work at anytime then you will still have the backup menu.lst file just in case something goes really wrong then you can copy the backup to the /boot/grub/ directory and you'll be right back where you started.

    You said Ubuntu works, so I made no changes to it.
    I do not respond to private messages asking for Linux help, Please keep it on the forums only.
    All new users please read this.** Forum FAQS. ** Adopt an unanswered post.

    I'd rather be lost at the lake than found at home.

  11. #10
    Just Joined!
    Join Date
    Nov 2008
    Posts
    72
    Thank you very much for this. Sorry for my impatience, but I just this moment reinstalled Mint to the same location, but this time with only the IDE drive connected. It successfully produced a dual boot menu, but this time only for that drive which I can access now through choosing the hard drive via BIOS. Meanwhile, I presume there is no reason why I can't follow with your instructions here to produce a second menu for the 320GB SATA drive which is the one I use every day. The more I learn about this the better.

Page 1 of 2 1 2 LastLast

Posting Permissions

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