Page 1 of 3 123 LastLast
Results 1 to 10 of 25

Thread: BOOTMGR is missing :(

  1. #1
    Join Date
    Aug 2006
    Location
    West Midlands, England
    Beans
    158

    BOOTMGR is missing :(

    I have three hard disks;

    200GB on which Vista is installed

    300GB on which Ubuntu is installed in one partition, and another is used for storing music

    500GB which is used for storing videos

    Originally I had hardy installed. I deleted the ext3 partition, and the swap space. I left the windows partition alone.

    I then installed Intrepid in a new partition in the place of the old one.

    Unfortunately, although Vista shows up in grub, if I select it I get:

    BOOTMGR is missing

    and it asks me to restart.

    I really, REALLY need vista working, as well as ubuntu (hence the dual boot), so any help would be greatly appreciated.

    It's funny; I upgraded in this exact same way from gutsy to hardy and it worked fine...
    Core i7 920 D0, 12GB RAM

  2. #2
    Join Date
    Mar 2008
    Location
    California, USA
    Beans
    8,111

    Re: BOOTMGR is missing :(

    How about opening a terminal (applications > accessories > terminal), and posting the output of:
    Code:
    sudo fdisk -lu
    cat /boot/grub/menu.lst
    Also, for each of the drives fdisk lists, like sda, sdb, etc, please post the output of:
    Code:
    sudo dd if=/dev/sda count=1 2>/dev/null | strings | grep -ie grub -ie "missing operating system"
    So replace "sda" above with each of your drives. And finally, for each command above that returns "GRUB", please post:
    Code:
    sudo dd if=/dev/sda bs=1 skip=1049 count=2 2>/dev/null | hexdump
    And replace sda with the drives that previously returned "GRUB". That will greatly clarify what your setup is like.

  3. #3
    Join Date
    Jan 2007
    Location
    ~/PA/USA
    Beans
    1,984
    Distro
    Ubuntu 11.04 Natty Narwhal

    Re: BOOTMGR is missing :(

    If you just want to repair the boot sector for Vista, just download the repair disc from here, burn the iso to disc and reboot with the disc. This will repair the Vista "BOOTMGR is missing" error easier.

    Hope this helps........

  4. #4
    Join Date
    Aug 2006
    Location
    West Midlands, England
    Beans
    158

    Re: BOOTMGR is missing :(

    Will using that disc mess up grub?
    Core i7 920 D0, 12GB RAM

  5. #5
    Join Date
    Aug 2008
    Location
    Jawja
    Beans
    2,486
    Distro
    Ubuntu 13.04 Raring Ringtail

    Re: BOOTMGR is missing :(

    Quote Originally Posted by Sirron View Post
    Will using that disc mess up grub?
    If you can go into grub via "gksudo gedit /boot/grub/menu.lst" look for 2 lines under the Vista section at the bottom.

    If the lines show (hd0) (hd1) then (hd1) (hd0), delete those lines then save the menu.lst

    I was having problems with loading XP through grub after Intrepid install. Once I deleted the 2 lines, XP loads just fine.

  6. #6
    Join Date
    Aug 2006
    Location
    West Midlands, England
    Beans
    158

    Re: BOOTMGR is missing :(

    Thanks, but all it says is:

    Code:
    # This entry automatically added by the Debian installer for a non-linux OS
    # on /dev/sda1
    title		Windows Vista/Longhorn (loader)
    root		(hd0,0)
    savedefault
    makeactive
    chainloader	+1
    Core i7 920 D0, 12GB RAM

  7. #7
    Join Date
    Aug 2006
    Location
    West Midlands, England
    Beans
    158

    Re: BOOTMGR is missing :(

    Quote Originally Posted by caljohnsmith View Post
    How about opening a terminal (applications > accessories > terminal), and posting the output of:
    Code:
    sudo fdisk -lu
    cat /boot/grub/menu.lst
    Also, for each of the drives fdisk lists, like sda, sdb, etc, please post the output of:
    Code:
    sudo dd if=/dev/sda count=1 2>/dev/null | strings | grep -ie grub -ie "missing operating system"
    So replace "sda" above with each of your drives. And finally, for each command above that returns "GRUB", please post:
    Code:
    sudo dd if=/dev/sda bs=1 skip=1049 count=2 2>/dev/null | hexdump
    And replace sda with the drives that previously returned "GRUB". That will greatly clarify what your setup is like.
    Ok, the fdisk one gives:

    Code:
    colin@UbuRevelation:~$ sudo fdisk -lu
    [sudo] password for colin: 
    
    Disk /dev/sda: 200.0 GB, 200049647616 bytes
    255 heads, 63 sectors/track, 24321 cylinders, total 390721968 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Disk identifier: 0xc9bec9be
    
       Device Boot      Start         End      Blocks   Id  System
    /dev/sda1   *        2048   390719487   195358720    7  HPFS/NTFS
    
    Disk /dev/sdb: 500.1 GB, 500107862016 bytes
    255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Disk identifier: 0x794c0630
    
       Device Boot      Start         End      Blocks   Id  System
    /dev/sdb1            2048   976769023   488383488    7  HPFS/NTFS
    
    Disk /dev/sdc: 300.0 GB, 300090728448 bytes
    255 heads, 63 sectors/track, 36483 cylinders, total 586114704 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Disk identifier: 0x00000001
    
       Device Boot      Start         End      Blocks   Id  System
    /dev/sdc1   *        2048   293177343   146587648    7  HPFS/NTFS
    /dev/sdc2       293186250   586099394   146456572+   5  Extended
    /dev/sdc5       293186313   574114904   140464296   83  Linux
    /dev/sdc6       574114968   586099394     5992213+  82  Linux swap / Solaris
    colin@UbuRevelation:~$ cat /boot/grub/menu.lst
    # 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=306e681d-f6a3-4c3c-84d2-7dab09894496 ro
    
    ## default grub root device
    ## e.g. groot=(hd0,0)
    # groot=306e681d-f6a3-4c3c-84d2-7dab09894496
    
    ## 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.10, kernel 2.6.27-7-generic
    uuid		306e681d-f6a3-4c3c-84d2-7dab09894496
    kernel		/boot/vmlinuz-2.6.27-7-generic root=UUID=306e681d-f6a3-4c3c-84d2-7dab09894496 ro quiet splash 
    initrd		/boot/initrd.img-2.6.27-7-generic
    quiet
    
    title		Ubuntu 8.10, kernel 2.6.27-7-generic (recovery mode)
    uuid		306e681d-f6a3-4c3c-84d2-7dab09894496
    kernel		/boot/vmlinuz-2.6.27-7-generic root=UUID=306e681d-f6a3-4c3c-84d2-7dab09894496 ro  single
    initrd		/boot/initrd.img-2.6.27-7-generic
    
    title		Ubuntu 8.10, memtest86+
    uuid		306e681d-f6a3-4c3c-84d2-7dab09894496
    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		Windows Vista/Longhorn (loader)
    root		(hd0,0)
    savedefault
    makeactive
    chainloader	+1
    and the other one gives:

    Code:
    colin@UbuRevelation:~$ sudo dd if=/dev/sda count=1 2>/dev/null | strings | grep -ie grub -ie "missing operating system"
    GRUB
    colin@UbuRevelation:~$ sudo dd if=/dev/sda bs=1 skip=1049 count=2 2>/dev/null | hexdump
    0000000 8204                                   
    0000002
    colin@UbuRevelation:~$ sudo dd if=/dev/sdb count=1 2>/dev/null | strings | grep -ie grub -ie "missing operating system"
    Missing operating system
    colin@UbuRevelation:~$ sudo dd if=/dev/sdc count=1 2>/dev/null | strings | grep -ie grub -ie "missing operating system"
    GRUB 
    colin@UbuRevelation:~$ sudo dd if=/dev/sdc bs=1 skip=1049 count=2 2>/dev/null | hexdump
    0000000 ff04                                   
    0000002
    I hope that's good ^^, thanks for the help so far, this is encouraging
    Core i7 920 D0, 12GB RAM

  8. #8
    Join Date
    Mar 2008
    Location
    California, USA
    Beans
    8,111

    Re: BOOTMGR is missing :(

    According to those commands, you have Grub installed into the MBR (Master Boot Record) of both your sda and sdc drives. It looks like you are booting from the sdc drive, which would be ideal. If you are booting from the sdc drive, then one of the following entries should work to boot Windows:
    Code:
    title	   Windows Vista (hd1)
    root       (hd1,0)
    map        (hd0) (hd1)
    map        (hd1) (hd0)
    chainloader +1
    
    title	   Windows Vista (hd2)
    root       (hd2,0)
    map        (hd0) (hd2)
    map        (hd2) (hd0)
    chainloader +1
    You can add the entries to the end of your menu.lst with:
    Code:
    gksudo gedit /boot/grub/menu.lst
    Give it a shot and let me know how it goes.

  9. #9
    Join Date
    Aug 2008
    Location
    Jawja
    Beans
    2,486
    Distro
    Ubuntu 13.04 Raring Ringtail

    Re: BOOTMGR is missing :(

    Quote Originally Posted by caljohnsmith View Post
    According to those commands, you have Grub installed into the MBR (Master Boot Record) of both your sda and sdc drives. It looks like you are booting from the sdc drive, which would be ideal. If you are booting from the sdc drive, then one of the following entries should work to boot Windows:
    Code:
    title       Windows Vista (hd1)
    root       (hd1,0)
    map        (hd0) (hd1)
    map        (hd1) (hd0)
    chainloader +1
    
    title       Windows Vista (hd2)
    root       (hd2,0)
    map        (hd0) (hd2)
    map        (hd2) (hd0)
    chainloader +1
    You can add the entries to the end of your menu.lst with:
    Code:
    gksudo gedit /boot/grub/menu.lst
    Give it a shot and let me know how it goes.
    I made the suggestion to delete the map drives. That fixed my problem but, then again, my system set up is different. I have partitioned the hd0 for XP and Ubuntu.

  10. #10
    Join Date
    Mar 2008
    Location
    California, USA
    Beans
    8,111

    Re: BOOTMGR is missing :(

    Quote Originally Posted by 73ckn797 View Post
    I made the suggestion to delete the map drives. That fixed my problem but, then again, my system set up is different. I have partitioned the hd0 for XP and Ubuntu.
    If Windows is on the same drive as Ubuntu, and that is the drive you are booting from on start up, then you are absolutely right about not needing the mapping lines. But it is usually necessary to include those mapping lines if Windows is on a different drive than the drive you are booting from.

Page 1 of 3 123 LastLast

Bookmarks

Posting Permissions

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