Mint 14: 'grub-efi' package failed to install

Questions about Grub, UEFI,the liveCD and the installer
Forum rules
Before you post please read this

Mint 14: 'grub-efi' package failed to install

Postby cbrace on Wed Nov 21, 2012 2:43 pm

Hello,

I have an Asus Eee PC on which i have succesfully installed various earlier versions of Linux Mint. Just now I downloaded the Mint 14 ISO and burned it to a USB stick. I booted from this USB stick and verified the media.

Booting from the USB stick, I have tried installing Mint 14 on this netbook. I have selected the custom install, installing the OS on /dev/sda1 (reformatted), and keeping /dev/sda6 intact, which is my /home directory.

I have repeated the installation three times and every time I get the same error message:
Code: Select all
The 'grub-efi' package failed to install into /target/. Without the GRUB boot loader, the installed system will not boot

Indeed, my netbook is now unbootable.

Suggestions anyone?

TIA
Last edited by cbrace on Wed Nov 21, 2012 7:13 pm, edited 1 time in total.
cbrace
Level 1
Level 1
 
Posts: 40
Joined: Sun Jan 22, 2012 7:23 am
Location: Amsterdam

Linux Mint is funded by ads and donations.
 

Re: Miint 14: 'grub-efi' package failed to install

Postby wylton on Wed Nov 21, 2012 7:09 pm

the same error....
wylton
Level 1
Level 1
 
Posts: 8
Joined: Sun Feb 21, 2010 6:46 pm

Re: Mint 14: 'grub-efi' package failed to install

Postby los7 on Wed Nov 21, 2012 9:22 pm

Me to, but I'm at the opposite end of the spectrum instead of an eee pc I have a built amd/ati gaming desktop and instead of a dvd I'm installing off a thumb drive, same error and problem though.
los7
Level 1
Level 1
 
Posts: 3
Joined: Mon Dec 28, 2009 10:15 am

Re: Mint 14: 'grub-efi' package failed to install

Postby poincare on Wed Nov 21, 2012 11:46 pm

I have this error too. One other forum I found said to run "grub-install" to fix the problem. But, that did not work for me. I still cannot boot into Linux Mint 14 and experience the same problem that you mention with an (u)efi system.

I hope we find a solution soon.
poincare
Level 1
Level 1
 
Posts: 5
Joined: Wed Nov 21, 2012 11:24 pm

Re: Mint 14: 'grub-efi' package failed to install

Postby srs5694 on Wed Nov 21, 2012 11:53 pm

Could somebody with this problem please post the RESULTS.txt file obtained from running Boot Info Script? (Please post it in code tags or as a link to the original file.) That will provide critical diagnostic information on partition table type (MBR vs. GPT), partitions (particularly the presence or absence of an ESP), and boot loader configuration.
srs5694
Level 6
Level 6
 
Posts: 1020
Joined: Mon Feb 27, 2012 1:42 pm

Re: Mint 14: 'grub-efi' package failed to install

Postby los7 on Thu Nov 22, 2012 12:07 am

OK I'm back with a solution that at least worked for me and I hope at least a few of you. If you are using UEFI graphical bios disable it. If you are installing from a usb device go into the bios and select it to boot notice it should appear twice in the list of boot options, once as it's normal name and again prefixed with "UEFI" choose the non UEFI one and it should boot and install as before but sans error at the end. That worked for me. If that dosen't apply to your set up some of my research suggested "enabling legacy OS suppport" in the bios. Not sure what that entails but it's a start to a google search. take care all
los7
Level 1
Level 1
 
Posts: 3
Joined: Mon Dec 28, 2009 10:15 am

Re: Mint 14: 'grub-efi' package failed to install

Postby Mulder2012 on Thu Nov 22, 2012 1:47 am

me too, I got this error on my desktop which supports UEFI, whenI tried to install LinuxMint 14 from my usb HD, however LinuxMint 13 can be successfully installed.

Shall we waiting for a new iso or ... ?
fight for future
Mulder2012
Level 1
Level 1
 
Posts: 3
Joined: Wed Nov 21, 2012 8:58 pm

Re: Mint 14: 'grub-efi' package failed to install

Postby wylton on Thu Nov 22, 2012 4:08 am

how can we to do?

waiting for a new iso?????

who can slove this??
wylton
Level 1
Level 1
 
Posts: 8
Joined: Sun Feb 21, 2010 6:46 pm

Re: Mint 14: 'grub-efi' package failed to install

Postby cbrace on Thu Nov 22, 2012 5:50 am

Output of Boot Info script: http://slexy.org/view/s20SXGtazK

Thanks for your assistance.
cbrace
Level 1
Level 1
 
Posts: 40
Joined: Sun Jan 22, 2012 7:23 am
Location: Amsterdam

Re: Mint 14: 'grub-efi' package failed to install

Postby louisgv on Thu Nov 22, 2012 9:06 am

srs5694 wrote:Could somebody with this problem please post the RESULTS.txt file obtained from running Boot Info Script? (Please post it in code tags or as a link to the original file.) That will provide critical diagnostic information on partition table type (MBR vs. GPT), partitions (particularly the presence or absence of an ESP), and boot loader configuration.


My RESULTS.txt:

Code: Select all
           
       Boot Info Script 0.61      [1 April 2012]


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

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

sda1: __________________________________________________________________________

    File system:       vfat
    Boot sector type:  Unknown
    Boot sector info:  No errors found in the Boot Parameter Block.
    Operating System: 
    Boot files:        /efi/Boot/bootx64.efi

sda2: __________________________________________________________________________

    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

sda3: __________________________________________________________________________

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

sda4: __________________________________________________________________________

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

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 /Windows/System32/winload.exe

sda6: __________________________________________________________________________

    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:       

sda7: __________________________________________________________________________

    File system:       ext4
    Boot sector type:  -
    Boot sector info:
    Operating System:  Linux Mint 14 Nadia
    Boot files:        /etc/fstab

sda8: __________________________________________________________________________

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

sda9: __________________________________________________________________________

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

sdb1: __________________________________________________________________________

    File system:       vfat
    Boot sector type:  SYSLINUX 4.06 2012-10-23
    Boot sector info:  Syslinux looks at sector 60832 of /dev/sdb1 for its
                       second stage. SYSLINUX is installed in the  directory.
                       No errors found in the Boot Parameter Block.
    Operating System: 
    Boot files:        /boot/grub/grub.cfg /syslinux/syslinux.cfg
                       /efi/BOOT/grubx64.efi /ldlinux.sys

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

Drive: sda _____________________________________________________________________

Disk /dev/sda: 750.2 GB, 750156374016 bytes
255 heads, 63 sectors/track, 91201 cylinders, total 1465149168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes

Partition  Boot  Start Sector    End Sector  # of Sectors  Id System

/dev/sda1                   1 1,465,149,167 1,465,149,167  ee GPT


GUID Partition Table detected.

Partition    Start Sector    End Sector  # of Sectors System
/dev/sda1           2,048       534,527       532,480 -
/dev/sda2         534,528     3,553,279     3,018,752 Windows Recovery Environment (Windows)
/dev/sda3       3,553,280     4,085,759       532,480 EFI System partition
/dev/sda4       4,085,760     4,347,903       262,144 Microsoft Reserved Partition (Windows)
/dev/sda5       4,347,904   996,396,585   992,048,682 Data partition (Windows/Linux)
/dev/sda6   1,416,722,432 1,465,147,391    48,424,960 Windows Recovery Environment (Windows)
/dev/sda7     996,396,586 1,399,521,585   403,125,000 Data partition (Windows/Linux)
/dev/sda8   1,400,191,508 1,416,722,431    16,530,924 Swap partition (Linux)
/dev/sda9   1,399,521,586 1,400,191,507       669,922 Data partition (Windows/Linux)

Drive: sdb _____________________________________________________________________

Disk /dev/sdb: 7999 MB, 7999586304 bytes
170 heads, 32 sectors/track, 2872 cylinders, total 15624192 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes

Partition  Boot  Start Sector    End Sector  # of Sectors  Id System

/dev/sdb1    *             32    15,624,190    15,624,159   c W95 FAT32 (LBA)


"blkid" output: ________________________________________________________________

Device           UUID                                   TYPE       LABEL

/dev/dm-0        fb646657-06ce-4ddf-9890-bd96f6557ab3   swap       
/dev/loop0                                              squashfs   
/dev/sda1        4660-A8D3                              vfat       SONYSYS
/dev/sda2        7A1471A814716851                       ntfs       Windows RE tools
/dev/sda3        BA47-4BDA                              vfat       
/dev/sda5        B64CC8414CC7FA5F                       ntfs       Window8
/dev/sda6        F0A257E1A257AABC                       ntfs       Recovery
/dev/sda7        48230909-deed-4ef2-b670-73ccde997983   ext4       
/dev/sda9        070233b0-e0e7-4f93-9035-20097860b4c5   ext4       
/dev/sdb1        150A-4224                              vfat       PENDRIVE

========================= "ls -R /dev/mapper/" output: =========================

/dev/mapper:
control
cryptswap1

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

Device           Mount_Point              Type       Options

/dev/loop0       /rofs                    squashfs   (ro,noatime)
/dev             /target/dev              none       (rw,bind)
/dev/sda3        /target/boot/efi         vfat       (rw)
/dev/sda7        /target                  ext4       (rw,errors=remount-ro)
/dev/sda9        /target/boot             ext4       (rw)
/dev/sdb1        /cdrom                   vfat       (ro,noatime,fmask=0022,dmask=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)


=============================== 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=48230909-deed-4ef2-b670-73ccde997983 /               ext4    errors=remount-ro 0       1
# /boot was on /dev/sda9 during installation
UUID=070233b0-e0e7-4f93-9035-20097860b4c5 /boot           ext4    defaults        0       2
# /boot/efi was on /dev/sda3 during installation
UUID=BA47-4BDA  /boot/efi       vfat    defaults        0       1
# swap was on /dev/sda8 during installation
#UUID=5d8fbb40-ee9a-4cbd-886a-26624eb12a11 none            swap    sw              0       0
/dev/mapper/cryptswap1 none swap sw 0 0
--------------------------------------------------------------------------------

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

           GiB - GB             File                                 Fragment(s)

 475.185306549 = 510.226337792  initrd.img                                     3
            ?? = ??             initrd.img.old                                 1
 475.163003922 = 510.202390528  vmlinuz                                        1

=========================== sdb1/boot/grub/grub.cfg: ===========================

--------------------------------------------------------------------------------

if loadfont /boot/grub/font.pf2 ; then
   set gfxmode=auto
   insmod efi_gop
   insmod efi_uga
   insmod gfxterm
   terminal_output gfxterm
fi

set menu_color_normal=white/black
set menu_color_highlight=black/light-gray

menuentry "Start Linux Mint" {
   set gfxpayload=keep
   linux   /casper/vmlinuz  file=/cdrom/preseed/mint.seed boot=casper iso-scan/filename=${iso_path} quiet splash --
   initrd   /casper/initrd.lz
}
menuentry "Start Linux Mint (compatibility mode)" {
   linux   /casper/vmlinuz  file=/cdrom/preseed/mint.seed boot=casper xforcevesa iso-scan/filename=${iso_path} ramdisk_size=1048576 root=/dev/ram rw noapic noapci nosplash irqpoll --
   initrd   /casper/initrd.lz
}
menuentry "Check the integrity of the medium" {
   linux   /casper/vmlinuz  boot=casper integrity-check iso-scan/filename=${iso_path} quiet splash --
   initrd   /casper/initrd.lz
}
menuentry "Test memory" {
   linux16   /install/mt86plus
}
--------------------------------------------------------------------------------

========================= sdb1/syslinux/syslinux.cfg: ==========================

--------------------------------------------------------------------------------
default vesamenu.c32
timeout 100

menu background splash.jpg
menu title Welcome to Linux Mint 13

menu color screen   37;40      #80ffffff #00000000 std
MENU COLOR border       30;44   #40ffffff #a0000000 std
MENU COLOR title        1;36;44 #ffffffff #a0000000 std
MENU COLOR sel          7;37;40 #e0ffffff #20ffffff all
MENU COLOR unsel        37;44   #50ffffff #a0000000 std
MENU COLOR help         37;40   #c0ffffff #a0000000 std
MENU COLOR timeout_msg  37;40   #80ffffff #00000000 std
MENU COLOR timeout      1;37;40 #c0ffffff #00000000 std
MENU COLOR msg07        37;40   #90ffffff #a0000000 std
MENU COLOR tabmsg       31;40   #ffDEDEDE #00000000 std
MENU WIDTH 78
MENU MARGIN 15
MENU ROWS 5
MENU VSHIFT 7
MENU TABMSGROW 11
MENU CMDLINEROW 11
MENU HELPMSGROW 16
MENU HELPMSGENDROW 29

label live
  menu label Start Linux Mint
  kernel /casper/vmlinuz
  append noprompt cdrom-detect/try-usb=true persistent file=/cdrom/preseed/mint.seed boot=casper initrd=/casper/initrd.lz quiet splash --
menu default
label xforcevesa
  menu label Start in compatibility mode
  kernel /casper/vmlinuz
  append noprompt cdrom-detect/try-usb=true persistent file=/cdrom/preseed/mint.seed boot=casper xforcevesa initrd=/casper/initrd.lz ramdisk_size=1048576 root=/dev/ram rw noapic noapci nosplash irqpoll --
label memtest
  menu label Memory test
  kernel memtest
label local
  menu label Boot from local drive
  localboot 0x80
--------------------------------------------------------------------------------

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

           GiB - GB             File                                 Fragment(s)

            ?? = ??             boot/grub/grub.cfg                             1

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

           GiB - GB             File                                 Fragment(s)

            ?? = ??             ldlinux.sys                                    1
            ?? = ??             syslinux/menu.c32                              1
            ?? = ??             syslinux/syslinux.cfg                          1
            ?? = ??             syslinux/vesamenu.c32                          1

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

 syslinux/menu.c32                  :  COM32R module (v4.xx)
 syslinux/vesamenu.c32              :  COM32R module (v4.xx)

======================== Unknown MBRs/Boot Sectors/etc: ========================

Unknown GPT Partiton Type
329701f46e06124e8273346c5641494f
Unknown BootLoader on sda1

00000000  eb 58 90 4d 53 44 4f 53  35 2e 30 00 02 08 fe 1b  |.X.MSDOS5.0.....|
00000010  02 00 00 00 00 f8 00 00  3f 00 ff 00 00 08 00 00  |........?.......|
00000020  00 20 08 00 01 02 00 00  00 00 00 00 02 00 00 00  |. ..............|
00000030  01 00 06 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
00000040  80 00 29 d3 a8 60 46 4e  4f 20 4e 41 4d 45 20 20  |..)..`FNO NAME  |
00000050  20 20 46 41 54 33 32 20  20 20 33 c9 8e d1 bc f4  |  FAT32   3.....|
00000060  7b 8e c1 8e d9 bd 00 7c  88 56 40 88 4e 02 8a 56  |{......|.V@.N..V|
00000070  40 b4 41 bb aa 55 cd 13  72 10 81 fb 55 aa 75 0a  |@.A..U..r...U.u.|
00000080  f6 c1 01 74 05 fe 46 02  eb 2d 8a 56 40 b4 08 cd  |...t..F..-.V@...|
00000090  13 73 05 b9 ff ff 8a f1  66 0f b6 c6 40 66 0f b6  |.s......f...@f..|
000000a0  d1 80 e2 3f f7 e2 86 cd  c0 ed 06 41 66 0f b7 c9  |...?.......Af...|
000000b0  66 f7 e1 66 89 46 f8 83  7e 16 00 75 39 83 7e 2a  |f..f.F..~..u9.~*|
000000c0  00 77 33 66 8b 46 1c 66  83 c0 0c bb 00 80 b9 01  |.w3f.F.f........|
000000d0  00 e8 2c 00 e9 a8 03 a1  f8 7d 80 c4 7c 8b f0 ac  |..,......}..|...|
000000e0  84 c0 74 17 3c ff 74 09  b4 0e bb 07 00 cd 10 eb  |..t.<.t.........|
000000f0  ee a1 fa 7d eb e4 a1 7d  80 eb df 98 cd 16 cd 19  |...}...}........|
00000100  66 60 80 7e 02 00 0f 84  20 00 66 6a 00 66 50 06  |f`.~.... .fj.fP.|
00000110  53 66 68 10 00 01 00 b4  42 8a 56 40 8b f4 cd 13  |Sfh.....B.V@....|
00000120  66 58 66 58 66 58 66 58  eb 33 66 3b 46 f8 72 03  |fXfXfXfX.3f;F.r.|
00000130  f9 eb 2a 66 33 d2 66 0f  b7 4e 18 66 f7 f1 fe c2  |..*f3.f..N.f....|
00000140  8a ca 66 8b d0 66 c1 ea  10 f7 76 1a 86 d6 8a 56  |..f..f....v....V|
00000150  40 8a e8 c0 e4 06 0a cc  b8 01 02 cd 13 66 61 0f  |@............fa.|
00000160  82 74 ff 81 c3 00 02 66  40 49 75 94 c3 42 4f 4f  |.t.....f@Iu..BOO|
00000170  54 4d 47 52 20 20 20 20  00 00 00 00 00 00 00 00  |TMGR    ........|
00000180  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
000001a0  00 00 00 00 00 00 00 00  00 00 00 00 0d 0a 44 69  |..............Di|
000001b0  73 6b 20 65 72 72 6f 72  ff 0d 0a 50 72 65 73 73  |sk error...Press|
000001c0  20 61 6e 79 20 6b 65 79  20 74 6f 20 72 65 73 74  | any key to rest|
000001d0  61 72 74 0d 0a 00 00 00  00 00 00 00 00 00 00 00  |art.............|
000001e0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
000001f0  00 00 00 00 00 00 00 00  ac 01 b9 01 00 00 55 aa  |..............U.|
00000200

Unknown BootLoader on sda3

00000000  eb 58 90 4d 53 44 4f 53  35 2e 30 00 02 01 7e 20  |.X.MSDOS5.0...~ |
00000010  02 00 00 00 00 f8 00 00  3f 00 ff 00 00 38 36 00  |........?....86.|
00000020  00 20 08 00 c1 0f 00 00  00 00 00 00 02 00 00 00  |. ..............|
00000030  01 00 06 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
00000040  80 00 29 da 4b 47 ba 4e  4f 20 4e 41 4d 45 20 20  |..).KG.NO NAME  |
00000050  20 20 46 41 54 33 32 20  20 20 33 c9 8e d1 bc f4  |  FAT32   3.....|
00000060  7b 8e c1 8e d9 bd 00 7c  88 56 40 88 4e 02 8a 56  |{......|.V@.N..V|
00000070  40 b4 41 bb aa 55 cd 13  72 10 81 fb 55 aa 75 0a  |@.A..U..r...U.u.|
00000080  f6 c1 01 74 05 fe 46 02  eb 2d 8a 56 40 b4 08 cd  |...t..F..-.V@...|
00000090  13 73 05 b9 ff ff 8a f1  66 0f b6 c6 40 66 0f b6  |.s......f...@f..|
000000a0  d1 80 e2 3f f7 e2 86 cd  c0 ed 06 41 66 0f b7 c9  |...?.......Af...|
000000b0  66 f7 e1 66 89 46 f8 83  7e 16 00 75 39 83 7e 2a  |f..f.F..~..u9.~*|
000000c0  00 77 33 66 8b 46 1c 66  83 c0 0c bb 00 80 b9 01  |.w3f.F.f........|
000000d0  00 e8 2c 00 e9 a8 03 a1  f8 7d 80 c4 7c 8b f0 ac  |..,......}..|...|
000000e0  84 c0 74 17 3c ff 74 09  b4 0e bb 07 00 cd 10 eb  |..t.<.t.........|
000000f0  ee a1 fa 7d eb e4 a1 7d  80 eb df 98 cd 16 cd 19  |...}...}........|
00000100  66 60 80 7e 02 00 0f 84  20 00 66 6a 00 66 50 06  |f`.~.... .fj.fP.|
00000110  53 66 68 10 00 01 00 b4  42 8a 56 40 8b f4 cd 13  |Sfh.....B.V@....|
00000120  66 58 66 58 66 58 66 58  eb 33 66 3b 46 f8 72 03  |fXfXfXfX.3f;F.r.|
00000130  f9 eb 2a 66 33 d2 66 0f  b7 4e 18 66 f7 f1 fe c2  |..*f3.f..N.f....|
00000140  8a ca 66 8b d0 66 c1 ea  10 f7 76 1a 86 d6 8a 56  |..f..f....v....V|
00000150  40 8a e8 c0 e4 06 0a cc  b8 01 02 cd 13 66 61 0f  |@............fa.|
00000160  82 74 ff 81 c3 00 02 66  40 49 75 94 c3 42 4f 4f  |.t.....f@Iu..BOO|
00000170  54 4d 47 52 20 20 20 20  00 00 00 00 00 00 00 00  |TMGR    ........|
00000180  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
000001a0  00 00 00 00 00 00 00 00  00 00 00 00 0d 0a 44 69  |..............Di|
000001b0  73 6b 20 65 72 72 6f 72  ff 0d 0a 50 72 65 73 73  |sk error...Press|
000001c0  20 61 6e 79 20 6b 65 79  20 74 6f 20 72 65 73 74  | any key to rest|
000001d0  61 72 74 0d 0a 00 00 00  00 00 00 00 00 00 00 00  |art.............|
000001e0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
000001f0  00 00 00 00 00 00 00 00  ac 01 b9 01 00 00 55 aa  |..............U.|
00000200


========= Devices which don't seem to have a corresponding hard drive: =========

sdc

=============================== StdErr Messages: ===============================

FIBMAP: Invalid argument
FIBMAP: Invalid argument
FIBMAP: Invalid argument
FIBMAP: Invalid argument
  No volume groups found


I deleted about 20000 line, which have this same string:

Code: Select all
FIBMAP: Invalid argument


Hope this help, please solve this problem.

If you need anymore data, please request it here!

Best regard!

Louis GV.
louisgv
Level 1
Level 1
 
Posts: 13
Joined: Thu Nov 22, 2012 7:28 am

Re: Mint 14: 'grub-efi' package failed to install

Postby Mulder2012 on Thu Nov 22, 2012 9:09 am

Done! :)
I managed to fix this boot issue via Boot-Repair tool.
Following instruction in below page, it works for me.
https://help.ubuntu.com/community/Boot-Repair#A2nd_option_%3a_install_Boot-Repair_in_Ubunt

Good luck!
fight for future
Mulder2012
Level 1
Level 1
 
Posts: 3
Joined: Wed Nov 21, 2012 8:58 pm

Re: Mint 14: 'grub-efi' package failed to install

Postby srs5694 on Thu Nov 22, 2012 11:15 am

Trying Mulder2012's suggestion of running the Boot Repair tool is worthwhile. That said, I've examined both cbrace's and louisgv's Boot Info Script outputs, and they've got two very different problems. Thus, the Boot Repair tool might not work for everybody.

In the case of cbrace, the disk is partitioned with the Master Boot Record (MBR) partitioning system, which is usually associated with a BIOS-mode boot; but it looks as if the Mint installer tried to install in EFI mode -- there's a file called /efi/BOOT/grubx64.efi, which is an EFI boot loader file. Of course, the message reported by cbrace (referring to the grub-efi package) also denotes an EFI-mode install. My hunch is that the installer booted in EFI mode by default, where previous ones didn't, and the installer didn't do any basic sanity checks to verify that it really should do an EFI-mode installation. You didn't say precisely what happens when you reboot, cbrace, so I'm not sure precisely what's happening. It looks like there's leftover BIOS GRUB code, so I'd expect you'd get something -- perhaps a "grub>" prompt or even a menu with inoperative options.

In any event, the Boot Repair tool may well work on this system. If not, the simplest solution is likely to be to re-install a BIOS-mode GRUB. You might try removing all the files that end in .efi from the installation medium and rebooting it into its "try before installing" mode, then use that to re-install GRUB. (There are lots of online guides about doing this, but I don't happen to have any bookmarked.)

The Boot Info Script output that louisgv posted shows an entirely different problem: The disk is partitioned using the GUID Partition Table (GPT) and appears to be set up for an EFI-mode boot, but with problems. /dev/sda1, which is usually the EFI System Partition (ESP) on EFI-based systems, has a FAT filesystem and an /efi/Boot/bootx64.efi boot loader file; but the Boot Info Script didn't recognize its partition type code. The /dev/sda3 partition, OTOH, is marked as an ESP, and has a FAT filesystem, but the script didn't identify any .efi boot loader files on it. The disk also has two Windows Recovery Environment partitions, which is odd. It looks almost as if Windows was installed twice and then one installation was incompletely erased to make room for Linux. The Linux installation then failed for reasons that aren't entirely clear but probably relate to the unusual set of pre-existing partitions at that point.

I'm less optimistic that the Boot Repair script will work on your system, louisgv, but it's worth a try. If it doesn't work, I'd do this:

  1. Download Parted Magic or System Rescue CD for use as an emergency system.
  2. Boot your emergency system.
  3. Open a Terminal window.
  4. Type "gdisk /dev/sda". This should launch gdisk on your main hard disk.
  5. Type "p" in gdisk. This will show you your partition table. Be sure it's the right one (with nine partitions; #3 should have a type code of "EF00"). If you see something else, type "q" to quit and try /dev/sdb instead.
  6. Out of curiosity, I'd be interested in knowing the type code for partition #1 -- what's reported under the "Code" column; and if that's "FFFF", the "Partition unique GUID" line when you type "i" followed by "1". Feel free to not report this to me if it's inconvenient, though.
  7. Type "t" to change a type code. In response to the prompts, enter "1" for the partition number and "EF00" for the type code.
  8. Type "t" to change another type code. Change the code for partition #3 to "8300". (This may not be strictly necessary, but I'm having you change it just in case.)
  9. Use "t" to change two more type codes: Change both 7 and 9 to "8300". This will keep them from showing up as unpartitioned disks in Windows.
  10. Type "w" to save your changes. Verify this operation when asked.
  11. Reboot. The computer should boot to something, probably Windows, but it might boot GRUB. If the latter, GRUB will probably be non-functional.

At this point, your task becomes one of getting both your OSes to boot. If you booted to Windows, you'll need to install a Linux EFI boot loader. Given your partition layout, I'd recommend booting an emergency Linux system, backing up /dev/sda9, creating a fresh FAT filesystem on it, restoring its files, and installing rEFInd on your ESP (/dev/sda1). (Installing rEFInd is best done from Windows, given your situation.) Once you create a refind_linux.conf file on /dev/sda9 (as described in the rEFInd documentation), you'll be able to boot Linux or Windows from the rEFInd menu, without dealing with GRUB. There are other options, though, including the EFI-enabled version of GRUB that ships with Mint.

Good luck to you all! It looks like Mint 14's EFI installer support is seriously messed up!
srs5694
Level 6
Level 6
 
Posts: 1020
Joined: Mon Feb 27, 2012 1:42 pm

Re: Mint 14: 'grub-efi' package failed to install

Postby poincare on Thu Nov 22, 2012 12:12 pm

srs5694 wrote:... There are other options, though, including the EFI-enabled version of GRUB that ships with Mint.


OK. If Mint 14 ships with (u)efi enabled version of Grub, how to we enable it during, beofre, or after the install so that when rebooting after install the user can either select Mint 14 from a list or boot straight into Mint 14? I don't see an easy way for new Mint users who don't understand even half of what is going on.
poincare
Level 1
Level 1
 
Posts: 5
Joined: Wed Nov 21, 2012 11:24 pm

Re: Mint 14: 'grub-efi' package failed to install

Postby louisgv on Thu Nov 22, 2012 1:36 pm

@srs5694:

Here are outputs for
gdisk -p:

Code: Select all
Command (? for help): p
Disk /dev/sda: 1465149168 sectors, 698.6 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 2481355D-E2A1-4FDE-AB5B-34FB8114C4E0
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 1465149134
Partitions will be aligned on 8-sector boundaries
Total free space is 3757 sectors (1.8 MiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1            2048          534527   260.0 MiB   FFFF  EFI system partition
   2          534528         3553279   1.4 GiB     2700  Basic data partition
   3         3553280         4085759   260.0 MiB   EF00  EFI system partition
   4         4085760         4347903   128.0 MiB   0C01  Microsoft reserved part
   5         4347904       996396585   473.0 GiB   0700  Basic data partition
   6      1416722432      1465147391   23.1 GiB    2700  Basic data partition
   7       996396586      1399521585   192.2 GiB   0700 
   8      1400191508      1416722431   7.9 GiB     8200 
   9      1399521586      1400191507   327.1 MiB   0700 


And -i:

Code: Select all
Partition number (1-9): 1
Partition GUID code: F4019732-066E-4E12-8273-346C5641494F (Unknown)
Partition unique GUID: 2359AC7F-2A70-48AF-83D6-20D4CF416976
First sector: 2048 (at 1024.0 KiB)
Last sector: 534527 (at 261.0 MiB)
Partition size: 532480 sectors (260.0 MiB)
Attribute flags: 0000000000000001
Partition name: 'EFI system partition'


Really appreciate your asisstance!

If you need anymore data, don't mind and ask, I will give it right away!

Best regard,

LGV
louisgv
Level 1
Level 1
 
Posts: 13
Joined: Thu Nov 22, 2012 7:28 am

Re: Mint 14: 'grub-efi' package failed to install

Postby srs5694 on Thu Nov 22, 2012 6:40 pm

poincare wrote:OK. If Mint 14 ships with (u)efi enabled version of Grub, how to we enable it during, beofre, or after the install so that when rebooting after install the user can either select Mint 14 from a list or boot straight into Mint 14? I don't see an easy way for new Mint users who don't understand even half of what is going on.


In theory, it should just work. In practice, it's clearly buggy. You have basically three choices:

  • Learn enough about EFI booting to fix it yourself. My Web page on the topic is one place to start, although there may be some Mint-specific documentation that could get you started more quickly. You might get some pointers here, too, but EFI problems (and their solutions) are often very system-specific.
  • Fumble around randomly and hope for the best.
  • Switch to a distribution that handles EFI better, such as Fedora 17.

Sorry to not have better news on this score, but EFI is still relatively new and it's changing very rapidly. Linux distributions in general have been slow to add good EFI support. In the long run, reporting EFI-related bugs may help get them fixed.

louisgv wrote:And -i:
Code: Select all
    Partition GUID code: F4019732-066E-4E12-8273-346C5641494F (Unknown)


Thanks for this. It's a new GPT type code. I Googled it and got just three hits, one of them being this thread! It looks like Sony is using its own unique type code for its ESP or some sort of Sony-specific partition. FWIW, I've added it to my GPT fdisk program, although I've not yet released the update.
srs5694
Level 6
Level 6
 
Posts: 1020
Joined: Mon Feb 27, 2012 1:42 pm

Re: Mint 14: 'grub-efi' package failed to install

Postby louisgv on Fri Nov 23, 2012 1:12 am

After doing exaclty what srs5694 instruct, now I'm only able to boot into a rescue Drive (not Window), which I don't know is my 1st or 2nd partition :-?..

And It seem no boot was installed, or I may have to reinstall GRUB into the 1st drive :-?..

Should I do that?

This is what I think:

The first partition was actually Sony's rescue Partition, which is actually a Norton backup, used to re-install Window8 to it's manufacture state, escape for the partition part done while installing LM14 :-?..

Then the second partition should be Win8 boot device, which hold Window's bootloader?

This one is my new lap for the next project though, so feel free to use it (through me) to have as much information as you like, since my old IBM with Fed and LM still out and about :)

New Ouput after done the instruction:

-i -1:

Code: Select all

Partition GUID code: C12A7328-F81F-11D2-BA4B-00A0C93EC93B (EFI System)
Partition unique GUID: 2359AC7F-2A70-48AF-83D6-20D4CF416976
First sector: 2048 (at 1024.0 KiB)
Last sector: 534527 (at 261.0 MiB)
Partition size: 532480 sectors (260.0 MiB)
Attribute flags: 0000000000000001
Partition name: 'EFI system partition'



-p

Code: Select all
Disk /dev/sda: 1465149168 sectors, 698.6 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 2481355D-E2A1-4FDE-AB5B-34FB8114C4E0
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 1465149134
Partitions will be aligned on 8-sector boundaries
Total free space is 3757 sectors (1.8 MiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1            2048          534527   260.0 MiB   EF00  EFI system partition
   2          534528         3553279   1.4 GiB     2700  Basic data partition
   3         3553280         4085759   260.0 MiB   8300  EFI system partition
   4         4085760         4347903   128.0 MiB   0C01  Microsoft reserved part
   5         4347904       996396585   473.0 GiB   0700  Basic data partition
   6      1416722432      1465147391   23.1 GiB    2700  Basic data partition
   7       996396586      1399521585   192.2 GiB   8300 
   8      1400191508      1416722431   7.9 GiB     8200 
   9      1399521586      1400191507   327.1 MiB   8300 
louisgv
Level 1
Level 1
 
Posts: 13
Joined: Thu Nov 22, 2012 7:28 am

Re: Mint 14: 'grub-efi' package failed to install

Postby wylton on Fri Nov 23, 2012 4:29 am

I get boot from grub-efi...


I do this: 3 Partition, one for Efi, one for Boot, other one for system.
and must do format Efi Partition before install.
i can boot from here.
if don't, you can use live-cd bootup, use boot-repair to repair.
wylton
Level 1
Level 1
 
Posts: 8
Joined: Sun Feb 21, 2010 6:46 pm

Re: Mint 14: 'grub-efi' package failed to install

Postby cbrace on Fri Nov 23, 2012 6:29 am

The boot-repair program fixed things here. Just booted Mint 14 from my laptop.

Thanks very much for your help, srs5694.
cbrace
Level 1
Level 1
 
Posts: 40
Joined: Sun Jan 22, 2012 7:23 am
Location: Amsterdam

Re: Mint 14: 'grub-efi' package failed to install

Postby srs5694 on Fri Nov 23, 2012 11:22 am

louisgv wrote:This is what I think:

The first partition was actually Sony's rescue Partition, which is actually a Norton backup, used to re-install Window8 to it's manufacture state


This is plausible, at least in part. /dev/sda1 is only 260MiB in size, which is far too small to hold a complete Windows recovery image; however, it may hold nothing but a specialized boot loader to launch the recovery system, which probably resides on /dev/sda2 and/or /dev/sda6.

Then the second partition should be Win8 boot device, which hold Window's bootloader?


If by "second partition" you mean /dev/sda2, then no. EFI boot loaders are found only on ESPs (FAT partitions with a particular type code), and /dev/sda2 is NTFS and has a type code for a Windows recovery environment. I'm guessing that Sony has configured its computers to boot from partitions with its own unique type code, too (/dev/sda1 as it was originally configured on your system).

If by "second partition" you mean the second ESP (/dev/sda3), then that's plausible; however, the Boot Info Script shows no sign of boot loaders on it now. Previous versions of Ubuntu and Mint had a bug that would erase the ESP prior to installing GRUB. This was supposedly fixed with Ubuntu 12.04 (and therefore Mint 13), but it's conceivable that it was just "plastered over" and it's still lurking in the code in a way that's been uncovered in Mint 14 and/or by something peculiar about your installation, such as the fact that the ESP is on /dev/sda3 rather than /dev/sda1. If so, then the Mint 14 installation attempt ended up wiping out the Windows boot loader, and some (presumably unrelated) bug caused it to fail to install GRUB.

Here's what I suggest you do at this point:

  1. Optionally, restore the type code for /dev/sda1 (this might break the computer booting into its current recovery system, though):
    1. Launch gdisk on /dev/sda
    2. Type "t" to change a type code.
    3. When prompted, type "1" to identify the first partition.
    4. Type (or cut-and-paste, if possible) "F4019732-066E-4E12-8273-346C5641494F" as the type code.
    5. Type "i" followed by "1" to view the partition details; "F4019732-066E-4E12-8273-346C5641494F" should be listed as the "partition GUID code."
  2. Run the Windows repair tool. With any luck this will restore a Windows boot loader to /dev/sda3 and enable you to boot Windows.

At this point you have a number of options for how to proceed. I won't describe them in detail, though:

  • Re-install Linux. This may well fail and re-create an unbootable computer.
  • Attempt to do a clean install of GRUB, either manually or using a boot repair utility.
  • Do a manual install of another boot loader. (Personally, I'd convert /dev/sda9 to FAT and install rEFInd, which should enable booting Linux without using GRUB; but as I maintain rEFInd, I'm not exactly unbiased.)

One more point: If this is a brand-new computer, chances are it's got Secure Boot enabled. Ubuntu 12.10 seems to ship with Secure Boot support, but I don't know offhand if Mint 14 also includes this support. Even if it does, something unexpected may have gone wrong with it -- after all, Secure Boot support is brand-new in Linux. Thus, you may want to disable it. You'll also need to do this if you install another boot loader (at least for now; Secure Boot support is starting to appear in more Linux tools).
srs5694
Level 6
Level 6
 
Posts: 1020
Joined: Mon Feb 27, 2012 1:42 pm

Re: Mint 14: 'grub-efi' package failed to install

Postby zerozero on Fri Nov 23, 2012 2:59 pm

to everyone in this topic: there's one issue with the 64bit isos (see this comment in the blog http://blog.linuxmint.com/?p=2216#comment-81935)
Srikanth K Says:
November 23rd, 2012 at 12:21 am

@jordi:

There is no UEFI installation support in Linux Mint 14.

Edit by Clem: UPDATE, we found the issue, it’s specific to Ubiquity in Mint 14 (i.e. it doesn’t affect Ubuntu). We’ll respin the 64-ISOs and make an announcement. For a rough ETA, this should take approximately a week.
zerozero
Level 16
Level 16
 
Posts: 6469
Joined: Tue Jul 07, 2009 2:29 pm

Linux Mint is funded by ads and donations.
 
Next

Return to Installation & Boot

Who is online

Users browsing this forum: BenBRockN, PatH57 and 21 guests