Results 1 to 10 of 10

Thread: 64 bit 12.04 /win 7 dual boot fail mbr/gpt/efi problems (bootinfoscript inside)

  1. #1
    Join Date
    Feb 2012
    Beans
    16

    64 bit 12.04 /win 7 dual boot fail mbr/gpt/efi problems (bootinfoscript inside)

    hey all,

    Just bought an asus n76 and managed to kill the windows 7 install the same day!

    there was a generous enough space on the 1st hdd (there are 2 x 1tb), but i forgot/failed to create a dedicated boot partition for linux and ended up writing linux boot partitition to windows boot partition.

    obviously, windows would not boot with grub, but through the bios was able to boot into the windows boot sequence. UNfortunately, i used easybcd to try to fix things and a bug in 2.1.2. ended up corrupting the mbr. Subsequent attempts to boot with the windows sequence required hard powerdowns in order to boot again.

    ive gone through recovery cds, win 7 dvds, bootsect,diskpart, etc to try to fix the windows mbr, even reinstall - nothing works. I get invalid gpt/efi related errors even attempting to install windows to the blank hdd. My optical drive is also bluray and has 2 booting possibilities (uefi and p2). I installed ubuntu studio via usb.

    as the system is new, there isnt any data to lose, but im getting frustrated about wasting my time. ive been using 11.10 and 12.04 on another laptop since the winter and would like to get windows working again.

    i cant mount the windows partition, it doesnt show up in grub any more (it used to), but diskpart sees it and it is listed as bootable in gparted.

    included are hte results from bootinfoscript.

    booting into the recovery partitions reults in an invalid efi path andunknown command "drivemap" error and retrn to grub menu. however, i can mount and navigate it. i would to see if i can edit grub to make it bootable or somehow load it on a usb stick and boot that to repair or reinstall.

    recovery section of grub
    ### BEGIN /etc/grub.d/30_os-prober ###
    menuentry "Windows Recovery Environment (loader) (on /dev/sda5)" --class windows --class os {
    insmod part_gpt
    insmod ntfs
    set root='(hd0,gpt5)'
    search --no-floppy --fs-uuid --set=root 8E7233AF72339AC3
    drivemap -s (hd0) ${root}
    chainloader +1

    bootscript results
    Boot Info Script 0.61 [1 April 2012]


    ============================= Boot Info Summary: ===============================

    => Syslinux MBR (4.04 and higher) is installed in the MBR of /dev/sda.
    => Windows is installed in the MBR of /dev/sdb.

    sda1: __________________________________________________ ________________________

    File system: vfat
    Boot sector type: Windows 7: FAT32
    Boot sector info: No errors found in the Boot Parameter Block.
    Operating System:
    Boot files:

    sda2: __________________________________________________ ________________________

    File system:
    Boot sector type: -
    Boot sector info:
    Mounting failed: mount: unknown filesystem type ''

    sda3: __________________________________________________ ________________________

    File system: ntfs
    Boot sector type: Windows Vista/7: NTFS
    Boot sector info: No errors found in the Boot Parameter Block.
    Operating System:
    Boot files:

    sda4: __________________________________________________ ________________________

    File system: ext4
    Boot sector type: -
    Boot sector info:
    Operating System:
    Boot files: /grub/grub.cfg /extlinux/extlinux.conf

    sda5: __________________________________________________ ________________________

    File system: ntfs
    Boot sector type: Windows Vista/7: NTFS
    Boot sector info: No errors found in the Boot Parameter Block.
    Operating System:
    Boot files: /bootmgr /boot/bcd

    sda6: __________________________________________________ ________________________

    File system: swap
    Boot sector type: -
    Boot sector info:

    sda7: __________________________________________________ ________________________

    File system: ext4
    Boot sector type: -
    Boot sector info:
    Operating System: Ubuntu 12.04 LTS
    Boot files: /etc/fstab

    sda8: __________________________________________________ ________________________

    File system: ext4
    Boot sector type: -
    Boot sector info:
    Operating System:
    Boot files:

    sdb1: __________________________________________________ ________________________

    File system: ntfs
    Boot sector type: Windows Vista/7: NTFS
    Boot sector info: No errors found in the Boot Parameter Block.
    Operating System:
    Boot files:

    sdb2: __________________________________________________ ________________________

    File system: ntfs
    Boot sector type: Windows Vista/7: NTFS
    Boot sector info: No errors found in the Boot Parameter Block.
    Operating System:
    Boot files: /boot.ini

    ============================ Drive/Partition Info: =============================

    Drive: sda __________________________________________________ ___________________

    Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
    255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 4096 bytes

    Partition Boot Start Sector End Sector # of Sectors Id System

    /dev/sda1 1 1,953,525,167 1,953,525,167 ee GPT


    GUID Partition Table detected.

    Partition Start Sector End Sector # of Sectors System
    /dev/sda1 2,048 411,647 409,600 EFI System partition
    /dev/sda2 411,648 673,791 262,144 Microsoft Reserved Partition (Windows)
    /dev/sda3 673,792 782,084,095 781,410,304 EFI System partition
    /dev/sda4 782,084,096 783,060,658 976,563 Data partition (Windows/Linux)
    /dev/sda5 1,902,325,760 1,953,524,129 51,198,370 Windows Recovery Environment (Windows)
    /dev/sda6 1,869,557,760 1,902,325,759 32,768,000 Swap partition (Linux)
    /dev/sda7 783,060,659 841,654,409 58,593,751 Data partition (Windows/Linux)
    /dev/sda8 841,654,410 1,869,556,753 1,027,902,344 Data partition (Windows/Linux)

    Drive: sdb __________________________________________________ ___________________

    Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
    255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 4096 bytes

    Partition Boot Start Sector End Sector # of Sectors Id System

    /dev/sdb1 1 1,953,525,167 1,953,525,167 ee GPT


    GUID Partition Table detected.

    Partition Start Sector End Sector # of Sectors System
    /dev/sdb1 2,048 1,024,002,047 1,024,000,000 Data partition (Windows/Linux)
    /dev/sdb2 1,024,002,048 1,953,523,711 929,521,664 Data partition (Windows/Linux)

    "blkid" output: __________________________________________________ ______________

    Device UUID TYPE LABEL

    /dev/sda1 149D-7F8C vfat SYSTEM
    /dev/sda3 0A58AC2A58AC168B ntfs OS
    /dev/sda4 cac44829-bd0b-4b2f-a14c-ccea15d1b901 ext4
    /dev/sda5 8E7233AF72339AC3 ntfs Recovery
    /dev/sda6 c7de32f4-64fa-4c05-95b1-a5f5653815a5 swap
    /dev/sda7 cceca161-a571-4129-a3a6-49900e4799d2 ext4
    /dev/sda8 61321b48-dcee-4a1a-b616-d84abab93b98 ext4
    /dev/sdb1 3C4C13CE0F97890B ntfs files1
    /dev/sdb2 34134C9B63770875 ntfs files2
    /dev/sr0 udf UDF Volume

    ================================ Mount points: =================================

    Device Mount_Point Type Options

    /dev/sda1 /boot/efi vfat (rw)
    /dev/sda4 /boot ext4 (rw)
    /dev/sda7 / ext4 (rw,errors=remount-ro)
    /dev/sda8 /home ext4 (rw)
    /dev/sdb2 /media/files2 fuseblk (rw,nosuid,nodev,allow_other,default_permissions,b lksize=4096)
    /dev/sr0 /media/UDF Volume udf (ro,nosuid,nodev,uid=1000,gid=1000,iocharset=utf8, umask=0077,uhelper=udisks)


    ============================= sda4/grub/grub.cfg: ==============================

    --------------------------------------------------------------------------------
    #
    # DO NOT EDIT THIS FILE
    #
    # It is automatically generated by grub-mkconfig using templates
    # from /etc/grub.d and settings from /etc/default/grub
    #

    ### BEGIN /etc/grub.d/00_header ###
    if [ -s $prefix/grubenv ]; then
    set have_grubenv=true
    load_env
    fi
    set default="0"
    if [ "${prev_saved_entry}" ]; then
    set saved_entry="${prev_saved_entry}"
    save_env saved_entry
    set prev_saved_entry=
    save_env prev_saved_entry
    set boot_once=true
    fi

    function savedefault {
    if [ -z "${boot_once}" ]; then
    saved_entry="${chosen}"
    save_env saved_entry
    fi
    }

    function recordfail {
    set recordfail=1
    if [ -n "${have_grubenv}" ]; then if [ -z "${boot_once}" ]; then save_env recordfail; fi; fi
    }

    function load_video {
    insmod efi_gop
    insmod efi_uga
    insmod video_bochs
    insmod video_cirrus
    }

    insmod part_gpt
    insmod ext2
    set root='(hd0,gpt7)'
    search --no-floppy --fs-uuid --set=root cceca161-a571-4129-a3a6-49900e4799d2
    if loadfont /usr/share/grub/unicode.pf2 ; then
    set gfxmode=auto
    load_video
    insmod gfxterm
    insmod part_gpt
    insmod ext2
    set root='(hd0,gpt4)'
    search --no-floppy --fs-uuid --set=root cac44829-bd0b-4b2f-a14c-ccea15d1b901
    set locale_dir=($root)/grub/locale
    set lang=en_US
    insmod gettext
    fi
    terminal_output gfxterm
    if [ "${recordfail}" = 1 ]; then
    set timeout=-1
    else
    set timeout=10
    fi
    ### END /etc/grub.d/00_header ###

    ### BEGIN /etc/grub.d/05_debian_theme ###
    insmod part_gpt
    insmod ext2
    set root='(hd0,gpt7)'
    search --no-floppy --fs-uuid --set=root cceca161-a571-4129-a3a6-49900e4799d2
    insmod png
    if background_image /usr/share/images/desktop-base/spacefun-grub.png; then
    set color_normal=light-gray/black
    set color_highlight=white/black
    else
    set menu_color_normal=white/black
    set menu_color_highlight=black/light-gray
    fi
    ### END /etc/grub.d/05_debian_theme ###

    ### BEGIN /etc/grub.d/10_linux ###
    function gfxmode {
    set gfxpayload="${1}"
    if [ "${1}" = "keep" ]; then
    set vt_handoff=vt.handoff=7
    else
    set vt_handoff=
    fi
    }
    if [ "${recordfail}" != 1 ]; then
    if [ -e ${prefix}/gfxblacklist.txt ]; then
    if hwmatch ${prefix}/gfxblacklist.txt 3; then
    if [ ${match} = 0 ]; then
    set linux_gfx_mode=keep
    else
    set linux_gfx_mode=text
    fi
    else
    set linux_gfx_mode=text
    fi
    else
    set linux_gfx_mode=keep
    fi
    else
    set linux_gfx_mode=text
    fi
    export linux_gfx_mode
    if [ "${linux_gfx_mode}" != "text" ]; then load_video; fi
    menuentry 'Ubuntu, with Linux 3.4.3-030403-generic' --class ubuntu --class gnu-linux --class gnu --class os {
    recordfail
    gfxmode $linux_gfx_mode
    insmod gzio
    insmod part_gpt
    insmod ext2
    set root='(hd0,gpt4)'
    search --no-floppy --fs-uuid --set=root cac44829-bd0b-4b2f-a14c-ccea15d1b901
    linux /vmlinuz-3.4.3-030403-generic root=UUID=cceca161-a571-4129-a3a6-49900e4799d2 ro quiet splash $vt_handoff
    initrd /initrd.img-3.4.3-030403-generic
    }
    menuentry 'Ubuntu, with Linux 3.4.3-030403-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
    recordfail
    insmod gzio
    insmod part_gpt
    insmod ext2
    set root='(hd0,gpt4)'
    search --no-floppy --fs-uuid --set=root cac44829-bd0b-4b2f-a14c-ccea15d1b901
    echo 'Loading Linux 3.4.3-030403-generic ...'
    linux /vmlinuz-3.4.3-030403-generic root=UUID=cceca161-a571-4129-a3a6-49900e4799d2 ro recovery nomodeset
    echo 'Loading initial ramdisk ...'
    initrd /initrd.img-3.4.3-030403-generic
    }
    submenu "Previous Linux versions" {
    menuentry 'Ubuntu, with Linux 3.2.0-23-lowlatency' --class ubuntu --class gnu-linux --class gnu --class os {
    recordfail
    gfxmode $linux_gfx_mode
    insmod gzio
    insmod part_gpt
    insmod ext2
    set root='(hd0,gpt4)'
    search --no-floppy --fs-uuid --set=root cac44829-bd0b-4b2f-a14c-ccea15d1b901
    linux /vmlinuz-3.2.0-23-lowlatency root=UUID=cceca161-a571-4129-a3a6-49900e4799d2 ro quiet splash $vt_handoff
    initrd /initrd.img-3.2.0-23-lowlatency
    }
    menuentry 'Ubuntu, with Linux 3.2.0-23-lowlatency (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
    recordfail
    insmod gzio
    insmod part_gpt
    insmod ext2
    set root='(hd0,gpt4)'
    search --no-floppy --fs-uuid --set=root cac44829-bd0b-4b2f-a14c-ccea15d1b901
    echo 'Loading Linux 3.2.0-23-lowlatency ...'
    linux /vmlinuz-3.2.0-23-lowlatency root=UUID=cceca161-a571-4129-a3a6-49900e4799d2 ro recovery nomodeset
    echo 'Loading initial ramdisk ...'
    initrd /initrd.img-3.2.0-23-lowlatency
    }
    }
    ### END /etc/grub.d/10_linux ###

    ### BEGIN /etc/grub.d/20_linux_xen ###
    ### END /etc/grub.d/20_linux_xen ###

    ### BEGIN /etc/grub.d/20_memtest86+ ###
    menuentry "Memory test (memtest86+)" {
    insmod part_gpt
    insmod ext2
    set root='(hd0,gpt4)'
    search --no-floppy --fs-uuid --set=root cac44829-bd0b-4b2f-a14c-ccea15d1b901
    linux16 /memtest86+.bin
    }
    menuentry "Memory test (memtest86+, serial console 115200)" {
    insmod part_gpt
    insmod ext2
    set root='(hd0,gpt4)'
    search --no-floppy --fs-uuid --set=root cac44829-bd0b-4b2f-a14c-ccea15d1b901
    linux16 /memtest86+.bin console=ttyS0,115200n8
    }
    ### END /etc/grub.d/20_memtest86+ ###

    ### BEGIN /etc/grub.d/30_os-prober ###
    menuentry "Windows Recovery Environment (loader) (on /dev/sda5)" --class windows --class os {
    insmod part_gpt
    insmod ntfs
    set root='(hd0,gpt5)'
    search --no-floppy --fs-uuid --set=root 8E7233AF72339AC3
    drivemap -s (hd0) ${root}
    chainloader +1
    }
    ### END /etc/grub.d/30_os-prober ###

    ### BEGIN /etc/grub.d/40_custom ###
    # This file provides an easy way to add custom menu entries. Simply type the
    # menu entries you want to add after this comment. Be careful not to change
    # the 'exec tail' line above.
    ### END /etc/grub.d/40_custom ###

    ### BEGIN /etc/grub.d/41_custom ###
    if [ -f $prefix/custom.cfg ]; then
    source $prefix/custom.cfg;
    fi
    ### END /etc/grub.d/41_custom ###
    --------------------------------------------------------------------------------

    ========================= sda4/extlinux/extlinux.conf: =========================

    --------------------------------------------------------------------------------
    ## /boot/extlinux/extlinux.conf
    ##
    ## IMPORTANT WARNING
    ##
    ## The configuration of this file is generated automatically.
    ## Do not edit this file manually, use: extlinux-update


    default l0
    prompt 1
    timeout 50

    include themes/debian/theme.cfg
    --------------------------------------------------------------------------------

    =================== sda4: Location of files loaded by Grub: ====================

    GiB - GB File Fragment(s)

    373.187994957 = 400.707558400 grub/grub.cfg 1
    372.965309143 = 400.468451328 initrd.img-3.2.0-23-lowlatency 3
    373.006628990 = 400.512818176 initrd.img-3.4.3-030403-generic 2
    372.944727898 = 400.446352384 vmlinuz-3.2.0-23-lowlatency 2
    372.974475861 = 400.478294016 vmlinuz-3.4.3-030403-generic 2

    ================= sda4: Location of files loaded by Syslinux: ==================

    GiB - GB File Fragment(s)

    373.067431450 = 400.578104320 extlinux/chain.c32 1
    373.068098068 = 400.578820096 extlinux/extlinux.conf 1

    ============== sda4: Version of COM32(R) files used by Syslinux: ===============

    extlinux/chain.c32 : COM32R module (v4.xx)

    =============================== sda7/etc/fstab: ================================

    --------------------------------------------------------------------------------
    # /etc/fstab: static file system information.
    #
    # Use 'blkid' to print the universally unique identifier for a
    # device; this may be used with UUID= as a more robust way to name devices
    # that works even if disks are added and removed. See fstab(5).
    #
    # <file system> <mount point> <type> <options> <dump> <pass>
    proc /proc proc nodev,noexec,nosuid 0 0
    # / was on /dev/sda7 during installation
    UUID=cceca161-a571-4129-a3a6-49900e4799d2 / ext4 errors=remount-ro 0 1
    # /boot was on /dev/sda4 during installation
    UUID=cac44829-bd0b-4b2f-a14c-ccea15d1b901 /boot ext4 defaults 0 2
    # /boot/efi was on /dev/sda1 during installation
    UUID=149D-7F8C /boot/efi vfat defaults 0 1
    # /home was on /dev/sda8 during installation
    UUID=61321b48-dcee-4a1a-b616-d84abab93b98 /home ext4 defaults 0 2
    # swap was on /dev/sda6 during installation
    UUID=c7de32f4-64fa-4c05-95b1-a5f5653815a5 none swap sw 0 0
    --------------------------------------------------------------------------------

    =================== sda7: Location of files loaded by Grub: ====================

    GiB - GB File Fragment(s)

    373.472290516 = 401.012818432 initrd.img 2
    373.472290516 = 401.012818432 initrd.img.old 2
    373.440137386 = 400.978294272 vmlinuz 2
    373.440137386 = 400.978294272 vmlinuz.old 2

    ============== sda7: Version of COM32(R) files used by Syslinux: ===============

    boot/extlinux/chain.c32 : COM32R module (v4.xx)

    ================================ sdb2/boot.ini: ================================

    --------------------------------------------------------------------------------
    [boot loader]
    timeout=30
    default=multi(0)disk(0)rdisk(0)partition(2)\WINDOW S
    [operating systems]
    multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windo ws XP Media Center Edition" /noexecute=optin /fastdetect
    --------------------------------------------------------------------------------



    thx for any ideas

  2. #2
    Join Date
    Nov 2009
    Location
    Segur De Calafell, Spain
    Beans
    11,745
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: 64 bit 12.04 /win 7 dual boot fail mbr/gpt/efi problems (bootinfoscript inside)

    I don't use UEFI but here is what I see and my ideas from reading UEFI threads here:
    1. There are two EFI System partitions (sda1 and sd3) and there should be only one. Did you create sda3 or changed its type? The EFI System partition should always be the first one (sda1). I guess you need to delete sda3.
    You might choose to delete all partitions except sda1 in fact.

    2. With UEFI it's very important how you boot the media to install/repair. You have to also boot it in UEFI mode. The win7 dvd and ubuntu cd can be booted in both UEFI and the standard bios mode. Make sure you boot them in UEFI.
    Try using F12 to get the boot menu of your board, and select the UEFI DVD-ROM.
    If there is no boot menu and you have to go through BIOS, make sure the UEFI DVD is above standard DVD so that it boots in UEFI.

    3. There was a bug in grub2 (I think it's not repaired) that was deleting the win7 boot files from sda1 during the ubuntu installation. So, just in case, after you install win7 again in UEFI, copy the files from sda1 to a usb stick or hdd, and then install ubuntu. In case it deletes the win7 files, copy them back to sda1.
    Darko.
    -----------------------------------------------------------------------
    Ubuntu 12.04 LTS 64bit & Windows 7 Ultimate 64bit

  3. #3
    Join Date
    Feb 2012
    Beans
    16

    Re: 64 bit 12.04 /win 7 dual boot fail mbr/gpt/efi problems (bootinfoscript inside)

    1. partitions 1-3 are from the factory. I discovered there is an asus folder in partition 1, so I am guessing that the linux install did not totally write over that. sda3 is the original windows os partition.

    2. Could booting and installing linux using non uefi mode have caused the error? Admittedly, even this live 12.04 usb boot I am currently using is non-uefi, so its possible I made a similar mistake initially. Pressing escape key upon asus flash screen is what I use to enter bios or select booting type. sometimes it goes to bios, sometimes to boot option, but i havent figured out why. Using gparted, i copied the recovery partition to a partition on the second hdd, but i am cautious to fully format the first hdd just yet, while i do have a win 7 dvd and some sort of disk from asus for drivers.

    3. as ive now looked into sda1, it has asus, microsoft, boot, and ubuntu folders, all containing files. is there anything i can do to copy somethign from recovery partition?

    is sda2 just something that windows makes?

  4. #4
    Join Date
    Nov 2009
    Location
    Segur De Calafell, Spain
    Beans
    11,745
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: 64 bit 12.04 /win 7 dual boot fail mbr/gpt/efi problems (bootinfoscript inside)

    Yeah, sda2 seems like the small partition win7 makes with a few boot files on it.

    If I understand gpt and uefi correctly, sda3 should be Data Partition, like all of the others (except the swap and recovery partitions). Compare how all the others say Data Partition.

    There is only one single EFI System partition, I am sure of that.

    I guess trying to install ubuntu non-uefi could make issues, but I can't really say what exactly. Or maybe the failed EasyBCD attempt caused this.

    What you could do is delete only the ubuntu partitions, and try to install again making sure you use uefi now. But before that it's probably best to try and change sda3 into different type (code). I am not sure if there are windows tools to do that. In ubuntu, you could try with gdisk or cgdisk or similar.
    Note that I'm not sure if they exist on the live cd by default, maybe you will need to add the into the live environment with apt-get install.

    Once sda3 is again recognized as the correct type, if you delete the ubuntu partition you are back to the factory default layout.
    Darko.
    -----------------------------------------------------------------------
    Ubuntu 12.04 LTS 64bit & Windows 7 Ultimate 64bit

  5. #5
    Join Date
    Jun 2009
    Location
    Chicago Suburbs
    Beans
    Hidden!
    Distro
    Ubuntu 14.04 Trusty Tahr

    Re: 64 bit 12.04 /win 7 dual boot fail mbr/gpt/efi problems (bootinfoscript inside)

    You can also use gparted to change sda3 from efi to data. In parted or gparted it is the boot flag, but that is not really the same thing in gpt as in MBR. In gpt a boot flag is setting the efi partition which should only be sda1 or first partition.

    Since Windows is in UEFI mode you should install Ubuntu in UEFI mode. Almost everyone that has had success with UEFI had posted they partitioned in advance and used the manual install to choose partitions. Grub is then installed to the efi partition (not the MBR as in BIOS).

    Older Windows info on gpt - 2008 updated 2011
    http://msdn.microsoft.com/en-us/wind.../gg463525.aspx
    Microsoft suggested partitions including reserved partition for gpt & UEFI:
    http://technet.microsoft.com/en-us/l...8WS.10%29.aspx

    In GPT fdisk, ESPs have a type code of EF00. In libparted-based tools, you mark the ESP as such by setting its "boot flag." Note that the libparted "boot flag" means something entirely different under MBR, and you should not set the "boot flag" on any OS partition under GPT!

    Grub2 efi info ArchLinux - Arch but grub2 is grub2 with maybe minor differences by distribution
    https://wiki.archlinux.org/index.php...r_UEFI_systems

    https://help.ubuntu.com/community/UE...g#UEFI%20Shell
    Recompiling GRUB not required with newest versions of grub.
    Creating efi partition & folders in advance works.

    https://wiki.archlinux.org/index.php/UEFI
    https://wiki.archlinux.org/index.php/GPT
    https://wiki.archlinux.org/index.php/Grub2

    UEFI dual boot trouble: Win7x64 - Ubuntu 12.04 LTS amd64
    http://ubuntuforums.org/showthread.php?t=2003442
    GUIDE: (U)EFI installation Also full install post *52 superfreak pg.6
    http://ubuntuforums.org/showthread.php?t=1958383
    UEFI screen shots with choice to boot
    http://ubuntuforums.org/showthread.p...7#post12030957
    Asus UEFI instructions (except efi should be first partition, but must not have to be)
    http://ubuntuforums.org/showthread.php?p=11842855

    https://help.ubuntu.com/community/UE..._64%20UEFI-GPT
    For info on UEFI boot install & repair - Updated Mar 2015:
    http://ubuntuforums.org/showthread.php?t=2147295
    Please use Thread Tools above first post to close thread when/if answered completely.







  6. #6
    Join Date
    Feb 2012
    Beans
    16

    Re: 64 bit 12.04 /win 7 dual boot fail mbr/gpt/efi problems (bootinfoscript inside)

    in a fit i attempted to reinstall windows at sda3 using install dvd, which of course failed, but in the process formatted sda3. at this point, i have sda5 (recovery) backed up on the second hdd and on a usb stick and have downloaded the program from asus to make recovery dvds. my attempt to install that with wine was unsuccessful.

    also tried to remove grub and upstate with grub-efi using bootrepair in order to boot from the recovery partition itself. no dice, same invalid efi file path error.

    i give up and have backed up and downloaded everything i think might be useful and am heading over to a friend who will help me wipe hdd 1 clean and start fresh. he has over 10 years experience programming for microsoft, so hopefully this works!

    thx for the help, i learned alot, and i bet something would have worked if i wrote earlier!

    i'll still be dualbooting, somehow!

  7. #7
    Join Date
    Jun 2009
    Location
    Chicago Suburbs
    Beans
    Hidden!
    Distro
    Ubuntu 14.04 Trusty Tahr

    Re: 64 bit 12.04 /win 7 dual boot fail mbr/gpt/efi problems (bootinfoscript inside)

    The main choice is do you want the old standard BIOS(MBR) or the new UEFI with gpt. And then be consistent on how you install.

    If you elect the old MBR you do have to remove the gpt and the backup gpt partition table. Windows MBR installs to gpt drives only erase the primary table and then all Linux tools see the backup table and get confused on whether drive is MBR(msdos0 or gpt(GUID).

    I prefer gpt but once set up do not really notice any difference. But if you do want to use BIOS mode use this to erase all gpt info.
    Fixparts - Repair broken partition tables (not overlapping issues) & delete Stray gpt data from MBR drives
    http://ubuntuforums.org/showthread.php?t=1705325
    http://www.rodsbooks.com/fixparts/
    For info on UEFI boot install & repair - Updated Mar 2015:
    http://ubuntuforums.org/showthread.php?t=2147295
    Please use Thread Tools above first post to close thread when/if answered completely.







  8. #8
    Join Date
    Feb 2012
    Beans
    16

    Re: 64 bit 12.04 /win 7 dual boot fail mbr/gpt/efi problems (bootinfoscript inside)

    i kept gpt and efi for clean windows install. building my ubuntu studio stick again and will read a bit more before hitting go this time

  9. #9
    Join Date
    Jun 2009
    Location
    Chicago Suburbs
    Beans
    Hidden!
    Distro
    Ubuntu 14.04 Trusty Tahr

    Re: 64 bit 12.04 /win 7 dual boot fail mbr/gpt/efi problems (bootinfoscript inside)

    Is studio 23bit or 64 bit? I have not use studio.

    I was just reviewing desktop ISOs and could not find any efi in the 32bit Desktop install where the 64 bit has the extra files/folder for efi boot.
    For info on UEFI boot install & repair - Updated Mar 2015:
    http://ubuntuforums.org/showthread.php?t=2147295
    Please use Thread Tools above first post to close thread when/if answered completely.







  10. #10
    Join Date
    Feb 2013
    Beans
    1

    Re: 64 bit 12.04 /win 7 dual boot fail mbr/gpt/efi problems (bootinfoscript inside)

    Hello,

    Now-a-days losing data due to MBR corruption is a quite common issue among the regular users of computer. No need to worry, since it is possible to recover data when MBR fails to boot the operating system by using some powerful file recovery tool.One such effective tool is partition recovery tool which will help you to recover all of your lost data. In case you want to use the software to recover your lost data you can click here.

    Best of luck,
    Christin

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
  •