Page 209 of 227 FirstFirst ... 109159199207208209210211219 ... LastLast
Results 2,081 to 2,090 of 2264

Thread: [Boot-Repair] Graphical tool to repair the PC boot in one click

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

    Re: [Boot-Repair] Graphical tool to repair the PC boot in one click

    @Marcio_Moraes

    You originally installed in BIOS boot mode, but it looks like Boot-Repair tried to convert to UEFI boot. But not boot files were installed into efi partition. You should have an ubuntu folder and do not.

    what computer & model is this & what video chip?

    It looks like an UltraBook with Intel SRT which looks like RAID to grub. You can try turning off the Intel SRT to see if grub will then correctly install. Or a few systems have had corrupted efi partitions where nothing could be written and the only solution was to backup the boot files, and with gparted erase partition and recreate a FAT32 partition of the same size with the boot flag to make it an efi partition and copy Windows files back in.

    Intel Smart Response Technology
    http://www.intel.com/p/en_US/support...ts/chpsts/imsm
    http://software.intel.com/en-us/arti...art-technology
    http://download.intel.com/support/mo...user_guide.pdf
    Some general info in post #3
    http://ubuntuforums.org/showthread.php?t=2071242
    Install 13.10 - just change UEFI to AHCI mode
    http://ubuntuforums.org/showthread.php?t=2199382

    More info in link in my signature.
    For info on UEFI boot install & repair:
    http://ubuntuforums.org/showthread.php?t=2147295
    Please use Thread Tools above first post to close thread when/if answered completely.







  2. #2082
    Join Date
    Aug 2013
    Beans
    10

    Re: [Boot-Repair] Graphical tool to repair the PC boot in one click

    have raid 0 set up I have windows 8.1 with Ubuntu 14.04 I can boot to both just fine but I have to do it in the uefi bios . I would like to have in a boot menu in grub is that possible? I have tried a few workaround with no luck.
    In grub customizer it dose not show the uefi windows path at all. I tried some windows based editors but it just corrupts the boot loader.
    After I installed ubunte It would not load I had to run Boot-Repair

    I have added my grub config file Im not a expert thanks


    Code:
    #
    # 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
    if [ "${next_entry}" ] ; then
       set default="${next_entry}"
       set next_entry=
       save_env next_entry
       set boot_once=true
    else
       set default="0"
    fi
    
    
    if [ x"${feature_menuentry_id}" = xy ]; then
      menuentry_id_option="--id"
    else
      menuentry_id_option=""
    fi
    
    
    export menuentry_id_option
    
    
    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 {
      if [ x$feature_all_video_module = xy ]; then
        insmod all_video
      else
        insmod efi_gop
        insmod efi_uga
        insmod ieee1275_fb
        insmod vbe
        insmod vga
        insmod video_bochs
        insmod video_cirrus
      fi
    }
    
    
    if [ x$feature_default_font_path = xy ] ; then
       font=unicode
    else
    insmod part_gpt
    insmod ext2
    if [ x$feature_platform_search_hint = xy ]; then
      search --no-floppy --fs-uuid --set=root  944e1cb8-1584-4e54-8a27-455fe241fc21
    else
      search --no-floppy --fs-uuid --set=root 944e1cb8-1584-4e54-8a27-455fe241fc21
    fi
        font="/usr/share/grub/unicode.pf2"
    fi
    
    
    if loadfont $font ; then
      set gfxmode=auto
      load_video
      insmod gfxterm
      set locale_dir=$prefix/locale
      set lang=en_US
      insmod gettext
    fi
    terminal_output gfxterm
    if [ "${recordfail}" = 1 ] ; then
      set timeout=-1
    else
      if [ x$feature_timeout_style = xy ] ; then
        set timeout_style=menu
        set timeout=10
      # Fallback normal timeout code in case the timeout_style feature is
      # unavailable.
      else
        set timeout=10
      fi
    fi
    ### END /etc/grub.d/00_header ###
    
    
    ### BEGIN /etc/grub.d/05_debian_theme ###
    set menu_color_normal=white/black
    set menu_color_highlight=black/light-gray
    if background_color 44,0,30; then
      clear
    fi
    ### END /etc/grub.d/05_debian_theme ###
    
    
    ### BEGIN /etc/grub.d/10_linux_proxy ###
    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
    
    
    ### END /etc/grub.d/10_linux_proxy ###
    
    
    ### BEGIN /etc/grub.d/30_uefi-firmware ###
    menuentry 'System setup' $menuentry_id_option 'uefi-firmware' {
        fwsetup
    }
    ### END /etc/grub.d/30_uefi-firmware ###
    
    
    ### BEGIN /etc/grub.d/33_linux_proxy ###
    menuentry "Ubuntu" --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-944e1cb8-1584-4e54-8a27-455fe241fc21' {
        recordfail
        load_video
        gfxmode $linux_gfx_mode
        insmod gzio
        insmod part_gpt
        insmod ext2
        if [ x$feature_platform_search_hint = xy ]; then
          search --no-floppy --fs-uuid --set=root  944e1cb8-1584-4e54-8a27-455fe241fc21
        else
          search --no-floppy --fs-uuid --set=root 944e1cb8-1584-4e54-8a27-455fe241fc21
        fi
        linux   /boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=944e1cb8-1584-4e54-8a27-455fe241fc21 ro  quiet splash $vt_handoff
        initrd  /boot/initrd.img-3.13.0-24-generic
    }
    submenu "Advanced options for Ubuntu"{
    menuentry "Ubuntu, with Linux 3.13.0-24-generic" --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.13.0-24-generic-advanced-944e1cb8-1584-4e54-8a27-455fe241fc21' {
            recordfail
            load_video
            gfxmode $linux_gfx_mode
            insmod gzio
            insmod part_gpt
            insmod ext2
            if [ x$feature_platform_search_hint = xy ]; then
              search --no-floppy --fs-uuid --set=root  944e1cb8-1584-4e54-8a27-455fe241fc21
            else
              search --no-floppy --fs-uuid --set=root 944e1cb8-1584-4e54-8a27-455fe241fc21
            fi
            echo    'Loading Linux 3.13.0-24-generic ...'
            linux   /boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=944e1cb8-1584-4e54-8a27-455fe241fc21 ro  quiet splash $vt_handoff
            echo    'Loading initial ramdisk ...'
            initrd  /boot/initrd.img-3.13.0-24-generic
    }
    menuentry "Ubuntu, with Linux 3.13.0-24-generic (recovery mode)" --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.13.0-24-generic-recovery-944e1cb8-1584-4e54-8a27-455fe241fc21' {
            recordfail
            load_video
            insmod gzio
            insmod part_gpt
            insmod ext2
            if [ x$feature_platform_search_hint = xy ]; then
              search --no-floppy --fs-uuid --set=root  944e1cb8-1584-4e54-8a27-455fe241fc21
            else
              search --no-floppy --fs-uuid --set=root 944e1cb8-1584-4e54-8a27-455fe241fc21
            fi
            echo    'Loading Linux 3.13.0-24-generic ...'
            linux   /boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=944e1cb8-1584-4e54-8a27-455fe241fc21 ro recovery nomodeset 
            echo    'Loading initial ramdisk ...'
            initrd  /boot/initrd.img-3.13.0-24-generic
    }
    }
    ### END /etc/grub.d/33_linux_proxy ###
    
    
    ### BEGIN /etc/grub.d/34_linux_xen ###
    
    
    ### END /etc/grub.d/34_linux_xen ###
    
    
    ### BEGIN /etc/grub.d/35_os-prober ###
    menuentry 'Ubuntu 14.04 LTS (14.04) (on /dev/mapper/pdc_ejjdbjffd5)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-simple-944e1cb8-1584-4e54-8a27-455fe241fc21' {
        insmod part_gpt
        insmod ext2
        if [ x$feature_platform_search_hint = xy ]; then
          search --no-floppy --fs-uuid --set=root  944e1cb8-1584-4e54-8a27-455fe241fc21
        else
          search --no-floppy --fs-uuid --set=root 944e1cb8-1584-4e54-8a27-455fe241fc21
        fi
        linux /boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=944e1cb8-1584-4e54-8a27-455fe241fc21 ro quiet splash $vt_handoff
        initrd /boot/initrd.img-3.13.0-24-generic
    }
    submenu 'Advanced options for Ubuntu 14.04 LTS (14.04) (on /dev/mapper/pdc_ejjdbjffd5)' $menuentry_id_option 'osprober-gnulinux-advanced-944e1cb8-1584-4e54-8a27-455fe241fc21' {
        menuentry 'Ubuntu (on /dev/mapper/pdc_ejjdbjffd5)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-3.13.0-24-generic.efi.signed--944e1cb8-1584-4e54-8a27-455fe241fc21' {
            insmod part_gpt
            insmod ext2
            if [ x$feature_platform_search_hint = xy ]; then
              search --no-floppy --fs-uuid --set=root  944e1cb8-1584-4e54-8a27-455fe241fc21
            else
              search --no-floppy --fs-uuid --set=root 944e1cb8-1584-4e54-8a27-455fe241fc21
            fi
            linux /boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=944e1cb8-1584-4e54-8a27-455fe241fc21 ro quiet splash $vt_handoff
            initrd /boot/initrd.img-3.13.0-24-generic
        }
        menuentry 'Ubuntu, with Linux 3.13.0-24-generic (on /dev/mapper/pdc_ejjdbjffd5)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-3.13.0-24-generic.efi.signed--944e1cb8-1584-4e54-8a27-455fe241fc21' {
            insmod part_gpt
            insmod ext2
            if [ x$feature_platform_search_hint = xy ]; then
              search --no-floppy --fs-uuid --set=root  944e1cb8-1584-4e54-8a27-455fe241fc21
            else
              search --no-floppy --fs-uuid --set=root 944e1cb8-1584-4e54-8a27-455fe241fc21
            fi
            linux /boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=944e1cb8-1584-4e54-8a27-455fe241fc21 ro quiet splash $vt_handoff
            initrd /boot/initrd.img-3.13.0-24-generic
        }
        menuentry 'Ubuntu, with Linux 3.13.0-24-generic (recovery mode) (on /dev/mapper/pdc_ejjdbjffd5)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-3.13.0-24-generic.efi.signed-root=UUID=944e1cb8-1584-4e54-8a27-455fe241fc21 ro recovery nomodeset-944e1cb8-1584-4e54-8a27-455fe241fc21' {
            insmod part_gpt
            insmod ext2
            if [ x$feature_platform_search_hint = xy ]; then
              search --no-floppy --fs-uuid --set=root  944e1cb8-1584-4e54-8a27-455fe241fc21
            else
              search --no-floppy --fs-uuid --set=root 944e1cb8-1584-4e54-8a27-455fe241fc21
            fi
            linux /boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=944e1cb8-1584-4e54-8a27-455fe241fc21 ro recovery nomodeset
            initrd /boot/initrd.img-3.13.0-24-generic
        }
    }
    
    
    set timeout_style=menu
    if [ "${timeout}" = 0 ]; then
      set timeout=10
    fi
    ### END /etc/grub.d/35_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  ${config_directory}/custom.cfg ]; then
      source ${config_directory}/custom.cfg
    elif [ -z "${config_directory}" -a -f  $prefix/custom.cfg ]; then
      source $prefix/custom.cfg;
    fi
    ### END /etc/grub.d/41_custom ###

    not sure if this helps at all or not Found linux image: /boot/vmlinuz-3.13.0-24-generic Found initrd image: /boot/initrd.img-3.13.0-24-generic No volume groups found Found Ubuntu 14.04 LTS (14.04) on /dev/mapper/pdc_ejjdbjffd5 Adding boot menu entry for EFI firmware configuration done – raven.warsong yesterday
    Last edited by oldfred; May 14th, 2014 at 02:59 PM. Reason: Please use code tags, # in advanced editor

  3. #2083
    Join Date
    Aug 2013
    Beans
    10

    Re: [Boot-Repair] Graphical tool to repair the PC boot in one click

    I have tried to re-install Ubuntu about 15 times with different settings at first boot repair told me I needed to make a boot partition so I did that. but still get a random error and gparted will not even load. but both os work fine and boot in uefi mode. just have to select in the uefi bois what I'm booting to,


    http://www.asus.com/Motherboards/M5A97_R20/ board
    hd 7800 gpu
    cpu fm 8350

    its a amd chip set nothing intel



    An error occurred during the repair.


    Please write on a paper the following URL:
    http://paste.ubuntu.com/7461268/



    In case you still experience boot problem, indicate this URL to:
    boot.repair@gmail.com


    You can now reboot your computer.
    Please do not forget to make your BIOS boot on mapper/pdc_ejjdbjffd (238GB) disk!


    The boot files of [The OS now in use - Ubuntu 14.04 LTS] are far from the start of the disk. Your BIOS may not detect them. You may want to retry after creating a /boot partition (EXT4, >200MB, start of the disk). This can be performed via tools such as gParted. Then select this partition via the [Separate /boot partition:] option of [Boot Repair]. (https://help.ubuntu.com/community/BootPartition
    )




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

    Re: [Boot-Repair] Graphical tool to repair the PC boot in one click

    With RAID you cannot use gparted, that is for standard partitions, you have to use your RAID tools for RAID partitioning.
    The boot files far from start of drive is primarily older BIOS, BIOS in ide mode not AHCI (or RAID in your case) or USB drives with older BIOS. You should not need a separate /boot partition as your boot issues are not related.

    I do not know RAID.
    But those with RAID usually have an efi partition for UEFI boot outside of the RAID. Windows only boots in UEFI mode from gpt partitioned drives.
    If booting in BIOS mode you must use MBR(msdos) partitioning not gpt.
    You are showing an extended partition which is only with MBR that RAID is contained in and gpt with an efi partition inside the RAID. Not sure if tha works or not?
    So system seems very confused. And with the RAID that adds another level of complexity.

    The standard desktop installer does not include RAID drivers. With 12.04 you had to use the alternative installer for RAID or LVM. They said when 12.10 came out that they planned on adding RAID & LVM to desktop but not yet. I see with 14.04 that full drive LVM is now an option, but RAID is not yet.
    You may have to use server install and then add the desktop of your choice. Not sure if just installing RAID driver to live system then lets installer use it or not?

    Was this a system with preconfigured RAID. Do you really want RAID, if you do not fully understand how it works. I am not a fan of RAID for most standard desktops, but often it is required for servers.

    Do not use gparted on RAID.
    http://www.howtoforge.com/how-to-res...-software-raid
    Don't bother with RAID 0 unless you have a specific need for speed without data redundancy, since if one drive goes out, you lose the whole array.
    http://en.wikipedia.org/wiki/RAID
    http://www.smallnetbuilder.com/nas/n...-is-not-backup
    For info on UEFI boot install & repair:
    http://ubuntuforums.org/showthread.php?t=2147295
    Please use Thread Tools above first post to close thread when/if answered completely.







  5. #2085
    Join Date
    Aug 2013
    Beans
    10

    Re: [Boot-Repair] Graphical tool to repair the PC boot in one click

    [QUOTE=oldfred;13023434]With RAID you cannot use gparted, that is for standard , you have to use your RAID tools for RAID partitioning.
    The boot files far from start of drive is primarily older BIOS, BIOS in ide mode not AHCI (or RAID in your case) or USB drives with older BIOS. You should not need a separate /boot partition as your boot issues are not related.

    Thats good to know about gparted. 14.04 was able to read and edit my raid just fine.


    I do not know RAID.
    But those with RAID usually have an efi partition for UEFI boot outside of the RAID. Windows only boots in UEFI mode from gpt partitioned drives.
    If booting in BIOS mode you must use MBR(msdos) partitioning not gpt.
    You are showing an extended partition which is only with MBR that RAID is contained in and gpt with an efi partition inside the RAID. Not sure if tha works or not?
    So system seems very confused. And with the RAID that adds another level of complexity.

    my uefi bois shows both partitions are uefi



    The standard desktop installer does not include RAID drivers. With 12.04 you had to use the alternative installer for RAID or LVM. They said when 12.10 came out that they planned on adding RAID & LVM to desktop but not yet. I see with 14.04 that full drive LVM is now an option, but RAID is not yet.
    You may have to use server install and then add the desktop of your choice. Not sure if just installing RAID driver to live system then lets installer use it or not?

    14.04 did see my raid 0

    Was this a system with preconfigured RAID. Do you really want RAID, if you do not fully understand how it works. I am not a fan of RAID for most standard desktops, but often it is required for servers.

    I set up the raid
    It works well I dont have any problems with it. I do a weekly image back up. The Ubuntu and windows 8.1 work great I just have to select a different partitions if I want to use the 2 os. so its not a deal breaker just some thing minor i wanted to fix.

    Do not use gparted on RAID.
    http://www.howtoforge.com/how-to-res...-software-raid
    Don't bother with RAID 0 unless you have a specific need for speed without data redundancy, since if one drive goes out, you lose the whole array.
    http://en.wikipedia.org/wiki/RAID
    http://www.smallnetbuilder.com/nas/n...-is-not-backup

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

    Re: [Boot-Repair] Graphical tool to repair the PC boot in one click

    Good to know 14.04 will see RAID with desktop installer.

    Often the main reason for having to directly boot from UEFI/BIOS is that one system is UEFI and the other BIOS? Is Ubuntu installed in BIOS boot and is Windows in UEFI boot?

    Do not know how to check Windows once booted, but this works in Linux.
    Query to see if UEFI or BIOS
    [ -d /sys/firmware/efi ] && echo "EFI boot on HDD" || echo "Legacy boot on HDD"

    We usually can tell by looking at partitions but with the RAID, I do not fully understand details. The efi partition is normally used by both installs if both are UEFI.
    You do show both ubuntu & Windows folders in efi partition for UEFI boot.

    What error do you get on this:
    sudo update-grub

    Boot-Repair showed a variety of issues, and sometimes they are not critical. With RAID I do not know which are important or not.
    Last edited by oldfred; May 14th, 2014 at 07:46 PM.
    For info on UEFI boot install & repair:
    http://ubuntuforums.org/showthread.php?t=2147295
    Please use Thread Tools above first post to close thread when/if answered completely.







  7. #2087
    Join Date
    Aug 2013
    Beans
    10

    Re: [Boot-Repair] Graphical tool to repair the PC boot in one click

    Generating grub configuration file ...
    Found linux image: /boot/vmlinuz-3.13.0-24-generic
    Found initrd image: /boot/initrd.img-3.13.0-24-generic
    No volume groups found
    Found Ubuntu 14.04 LTS (14.04) on /dev/mapper/pdc_ejjdbjffd5
    Adding boot menu entry for EFI firmware configuration
    done


    WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.


    Disk /dev/sda: 120.0 GB, 120034123776 bytes
    256 heads, 63 sectors/track, 14536 cylinders, total 234441648 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0xc93112b4

    Device Boot Start End Blocks Id System
    /dev/sda1 1 4294967295 2147483647+ ee GPT

    Disk /dev/sdb: 120.0 GB, 120034123776 bytes
    255 heads, 63 sectors/track, 14593 cylinders, total 234441648 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0x41413535

    Disk /dev/sdb doesn't contain a valid partition table
    Warning: ignoring extra data in partition table 5
    Warning: ignoring extra data in partition table 5
    Warning: ignoring extra data in partition table 5
    Warning: invalid flag 0xffff of partition table 5 will be corrected by w(rite)

    Disk /dev/sdc: 500.1 GB, 500107862016 bytes
    255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0xde004917

    Device Boot Start End Blocks Id System
    /dev/sdc1 1985 1953118207 976558111+ f W95 Ext'd (LBA)
    /dev/sdc5 ? 4294969280 8589936574 2147483647+ ff BBT
    Warning: ignoring extra data in partition table 5
    Warning: ignoring extra data in partition table 5
    Warning: ignoring extra data in partition table 5
    Warning: invalid flag 0xffff of partition table 5 will be corrected by w(rite)

    Disk /dev/sdd: 500.1 GB, 500107862016 bytes
    255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 4096 bytes
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes
    Disk identifier: 0xe3fa8347

    Device Boot Start End Blocks Id System
    /dev/sdd1 1985 976766975 488382495+ f W95 Ext'd (LBA)
    Partition 1 does not start on physical sector boundary.
    /dev/sdd5 ? 4294969280 8589936574 2147483647+ ff BBT

    Disk /dev/sde: 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 / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0x90909090

    Device Boot Start End Blocks Id System
    /dev/sde1 * 1985 1953519615 976758815+ f W95 Ext'd (LBA)
    /dev/sde5 2048 1953519615 976758784 7 HPFS/NTFS/exFAT

    WARNING: GPT (GUID Partition Table) detected on '/dev/mapper/pdc_ejjdbjffd'! The util fdisk doesn't support GPT. Use GNU Parted.


    Disk /dev/mapper/pdc_ejjdbjffd: 238.0 GB, 237999882240 bytes
    256 heads, 63 sectors/track, 28822 cylinders, total 464843520 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 65536 bytes / 131072 bytes
    Disk identifier: 0xc93112b4

    Device Boot Start End Blocks Id System
    /dev/mapper/pdc_ejjdbjffd1 1 4294967295 2147483647+ ee GPT
    Partition 1 does not start on physical sector boundary.

    Disk /dev/mapper/pdc_cafjbfdji: 1000.0 GB, 999999930368 bytes
    255 heads, 63 sectors/track, 121576 cylinders, total 1953124864 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 4096 bytes
    I/O size (minimum/optimal): 65536 bytes / 131072 bytes
    Disk identifier: 0xde004917

    Device Boot Start End Blocks Id System
    /dev/mapper/pdc_cafjbfdji1 1985 1953118207 976558111+ f W95 Ext'd (LBA)
    Partition 1 does not start on physical sector boundary.
    /dev/mapper/pdc_cafjbfdji5 2048 976758783 488378368 7 HPFS/NTFS/exFAT
    /dev/mapper/pdc_cafjbfdji6 976760832 1953118207 488178688 7 HPFS/NTFS/exFAT

    Disk /dev/mapper/pdc_ejjdbjffd1: 314 MB, 314572800 bytes
    255 heads, 63 sectors/track, 38 cylinders, total 614400 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 65536 bytes / 131072 bytes
    Disk identifier: 0x73736572

    This doesn't look like a partition table
    Probably you selected the wrong device.

    Device Boot Start End Blocks Id System
    /dev/mapper/pdc_ejjdbjffd1p1 1920221984 3736432267 908105142 72 Unknown
    Partition 1 does not start on physical sector boundary.
    /dev/mapper/pdc_ejjdbjffd1p2 ? 1936028192 3889681299 976826554 6c Unknown
    Partition 2 does not start on physical sector boundary.
    /dev/mapper/pdc_ejjdbjffd1p3 ? 0 0 0 0 Empty
    /dev/mapper/pdc_ejjdbjffd1p4 27722122 27722568 223+ 0 Empty
    Partition 4 does not start on physical sector boundary.

    Disk /dev/mapper/pdc_ejjdbjffd2: 104 MB, 104857600 bytes
    255 heads, 63 sectors/track, 12 cylinders, total 204800 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 65536 bytes / 131072 bytes
    Disk identifier: 0x500a0dff

    This doesn't look like a partition table
    Probably you selected the wrong device.

    Device Boot Start End Blocks Id System
    /dev/mapper/pdc_ejjdbjffd2p1 ? 1948285285 3650263507 850989111+ 6e Unknown
    Partition 1 does not start on physical sector boundary.
    /dev/mapper/pdc_ejjdbjffd2p2 ? 0 0 0 74 Unknown
    /dev/mapper/pdc_ejjdbjffd2p4 28049408 28049848 220+ 0 Empty

    Partition table entries are not in disk order

    Disk /dev/mapper/pdc_ejjdbjffd3: 134 MB, 134217728 bytes
    255 heads, 63 sectors/track, 16 cylinders, total 262144 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 65536 bytes / 131072 bytes
    Disk identifier: 0x00000000

    Disk /dev/mapper/pdc_ejjdbjffd3 doesn't contain a valid partition table
    fdisk: unable to read /dev/mapper/pdc_cafjbfdji1: Inappropriate ioctl for device

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

    Re: [Boot-Repair] Graphical tool to repair the PC boot in one click

    Because of the RAID, fdisk and most Linux standard partition tools will not see partitions correctly.
    I cannot tell if any of that is a real issue or not, as I do not know RAID.
    For info on UEFI boot install & repair:
    http://ubuntuforums.org/showthread.php?t=2147295
    Please use Thread Tools above first post to close thread when/if answered completely.







  9. #2089
    Join Date
    Aug 2013
    Beans
    10

    Re: [Boot-Repair] Graphical tool to repair the PC boot in one click

    Sorry that's all I know. I'm my BIOS its shows uefi by the windows and Linux
    Partitions. If I try to burn a iso and boot from it and it dose not have uefi drivers it dose let me boot from it unless I change it to legacy boot.

    So I'm 100% uefi boot is working on both partitions. But my knowledge ends there. My be its as you say the boot repair tools dose not support raid. Thanks
    Last edited by chris_wiley; May 14th, 2014 at 08:29 PM.

  10. #2090
    Join Date
    Dec 2008
    Location
    Haïti
    Beans
    21
    Distro
    Ubuntu 14.04 Trusty Tahr

    Re: [Boot-Repair] Graphical tool to repair the PC boot in one click

    Hi all, I've been trying to install Ubuntu 14.04 on an brand new Acer Aspire V3 772 9460. W8 came preinstalled, Installed Ubuntu from USB, but after installation is complete only Windows 8 starts up, no sign of Ubuntu. This is exactly the same machine and problem as Ed Martins post higher in this thread. The difference is I'm trying to install Ubuntu 14.04

    After trial & error & a lot of searching on the forums I followed the steps described in this suggested thread that include the Boot-Repair solution.

    I am stuck at the Boot-Repair "Recommended Repair" since it keeps complaining that I should close my package managers. I have none running, the only program I have running is Boot-Repair from a Live USB Session (as I can't get ubuntu started any other way). Searched around and others seem to have the same problem but could not find a solution to that particular problem.

    The output from the "Create BootInfo Summary" is here: http://paste.ubuntu.com/7470378

    I don't care if I have to reinstall, no data is on the machine yet, but I would like to know how to get it straight this time...

    Thanks for your advise

Page 209 of 227 FirstFirst ... 109159199207208209210211219 ... 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
  •