boot-repair

Questions about Grub, UEFI,the liveCD and the installer
Forum rules
Before you post please read how to get help
Lartizan
Level 1
Level 1
Posts: 16
Joined: Thu Jun 29, 2017 4:30 am

Re: boot-repair

Postby Lartizan » Thu Jun 29, 2017 9:23 am

Tried grub repair once it somewhat messed up the grub. It was ok because I could boot again but it did not boot directly after post instead I had to choose from several option (ubuntu EFI, and two different kernels of Linux mint). I reinstalled Linux.

Deep_Thought
Level 1
Level 1
Posts: 13
Joined: Sat Nov 07, 2015 2:56 am

Re: boot-repair

Postby Deep_Thought » Sat Jul 01, 2017 8:12 am

I just installed linux mint 18.2 beta on a test system, (32 Gb ssd + 160 Gb Hdd), but it didn't boot.
Looks like the boot manager didn't install.
The tip in the first post got it working for me.
So thank you.
My arcade cab running Linux Mint Xfce: https://goo.gl/photos/yE1KACHryQjCaaCj7
Based on a core 2 duo e8400 (@3.6 Ghz) with Mame, Daphne (the laserdisk emulator) and lots of others.

therealBatman
Level 1
Level 1
Posts: 3
Joined: Thu Aug 10, 2017 10:31 pm

Re: boot-repair

Postby therealBatman » Fri Aug 11, 2017 3:27 am

What you should do if for some freakish reason the grub menu didn<t install itself. Get a supergrubdisk iso, burn to a dvd-rw, so you will not waste a whole dvd for a tiny file you may want to delete later on. Select your Linux install, press enter. Install Boot-Repair, the ppa is called yannubuntu, it should be easy enough to find in a cursory Firefox search engine search and to install. For some reason it isn<t in the 14.04 repos, it was in the previous one by default (Boot-Repair that is), but that fixes it.

Regarding UEFI...I have refused to get myself acquainted with it, but my usb stick with mint 17.3 when I press F8 to get my motherboards boot menu, sees my usb key twice, normalely named, and UEFI then the name.

I have only seen people at their wits end bringing their computer to a repair shop from UEFI. All I can understand from it is that it is to install your OS on a usb 3.0/3.1 external drive, with an image of the system on it, so that any hiccup or issue should arise, can be quickly repaired with UEFI...I don<t know, thankfully my motherboard allows me to choose. I might be wrong. Once somebody I was at their home only one had their desktop connected to about 3-4 wifi ethernet and wifi hard drives and it was on windows 8.1 and was fully UEFI. One of the 2 people living there didn<t want to wake up their significant other....I managed to get into windows, but all data was gone, although windows 8.1 would install itself quickly from LAN. After seeing what I did to force myself in win 8.1 (I never used 8.1 before or after that), but I bruteforced myself in i dont remember how exactly by pressing the motherboard F8 key which brought me to a menu with a lot more stuff than a boot menu (it still wasn<t the BIOS, unless if I am to understand it well..there<s no more BIOS fiddling if using UEFI. But what do i know...all I know is that knowing about it isn<t crucial.

User avatar
Sgthawker
Level 3
Level 3
Posts: 145
Joined: Sun Apr 27, 2014 2:23 am

Re: boot-repair

Postby Sgthawker » Sat Aug 12, 2017 10:48 am

therealBatman wrote:I have only seen people at their wits end bringing their computer to a repair shop from UEFI.


I have multi-boot UEFI installs on 3 different computers with little hassle. It just takes learning what they do/how they work.

I did TV repair work for years, everybody said the OSD, on screen display, was never gonna make it. Well it did and went beyond that to controlling your TV from your smart phone. Technology, huh? Great stuff!
LM 18.2 KDE UEFI on Sabertooth Z170 S, i6700K, 2 x Echelon GTX950, Samsung 950 Pro M.2 NVMe
LM 18.2 KDE UEFI on Asus ROG STRIX laptop, i7700 HQ, GTX 1060, Samsung 960 Pro M.2 NVMe

User avatar
sdibaja
Level 4
Level 4
Posts: 201
Joined: Sun May 08, 2011 12:57 pm
Location: Baja California, Mexico

Re: boot-repair

Postby sdibaja » Sat Aug 12, 2017 11:17 am

Sgthawker wrote:
therealBatman wrote:I have only seen people at their wits end bringing their computer to a repair shop from UEFI.


I have multi-boot UEFI installs on 3 different computers with little hassle. It just takes learning what they do/how they work.

I did TV repair work for years, everybody said the OSD, on screen display, was never gonna make it. Well it did and went beyond that to controlling your TV from your smart phone. Technology, huh? Great stuff!


I am happy that you have mastered UEFI in your environment.

In my alternate universe I find "Unified Extensible Firmware Interface(UEFI)" a confusing mess. Every darn OEM has a different version for every Model of every machine they produce. The terms are odd, and the menus are weird.
I hope that some sort of standardization evolves soon. (maybe it has already, I only see recycled machines)
Some installers "automatically" reset things and make Grub work (for them). Some fail completely and I have to manually reset and get a boot loader working.

PS: I am among the group that have had the various "Boot Repair" tools do more damage than good.
Peter

feffer
Level 4
Level 4
Posts: 204
Joined: Mon Jul 07, 2008 7:49 pm

Re: boot-repair

Postby feffer » Mon Sep 04, 2017 7:38 pm

New computer with win-10 installed. In ignorance, Mint, LMDE and Ubuntu were installed in legacy mode. After some hassle, I ended with a grub menu that could boot any linux OS, but not see windows. I can boot windows via the F11 (boot key). I posted about this earlier and Austin.Texas pointed me to some pages explaining the issue. After digesting those and most of this thread, I might make the attempt at boot-repair, but have a few questions. I do not want to do a fresh install...I'd like to keep my already configured systems. That should be possible, Right?

Grub (grub-pc, I believe) is installed on the SSD containing my linux OSes -- /dev/nvme0n1. Gparted shows the esp (EFI system partition) is installed on a different SSD, and is on /dev/sda2. My repair process should be something like this: boot the Mint install disc in EFI mode; install boot-repair; go to advanced and install grub (grub-efi now) in the esp partition; then update-grub and reboot. Sound right?

fruitkiller
Level 4
Level 4
Posts: 272
Joined: Tue Aug 05, 2014 7:52 pm

Re: boot-repair

Postby fruitkiller » Fri Sep 22, 2017 12:04 am

Boot-repair is great and unfortunate it is not in the trusty distro. That's why I keep a saucy PPA for it. It's even better since it became a bootable program in itself, makes one skip the supergrubdisk part, after one installs, for some reason or another, Windows past Win7 x64 ultimate.

damir91ue
Level 1
Level 1
Posts: 1
Joined: Sun Oct 01, 2017 8:40 am

Re: boot-repair

Postby damir91ue » Sun Oct 01, 2017 8:48 am

Guys I have problems installing Linux Mint. I made bootable USB drive with installation. I start installation and it always freezes screen at "installing grub2". I tried boot repair, but when I start repair it doesn't finish process and again it freezes screen.

Code: Select all

Boot Info Script 8f991e4 + Boot-Repair extra info      [Boot-Info 30Sep2017]


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

 => No boot loader is installed in the MBR of /dev/sda.
 => No boot loader is installed in the MBR of /dev/sdb.

sda1: __________________________________________________________________________

    File system:       vfat
    Boot sector type:  Windows 8/2012: FAT32
    Boot sector info:  No errors found in the Boot Parameter Block.
    Operating System: 
    Boot files:        /boot/grub/grub.cfg /syslinux.cfg /EFI/BOOT/grubx64.efi

sdb1: __________________________________________________________________________

    File system:       vfat
    Boot sector type:  FAT32
    Boot sector info:  No errors found in the Boot Parameter Block.
    Operating System: 
    Boot files:        /EFI/ubuntu/grub.cfg /EFI/ubuntu/fwupx64.efi
                       /EFI/ubuntu/grubx64.efi

sdb2: __________________________________________________________________________

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

sdb3: __________________________________________________________________________

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

sdb4: __________________________________________________________________________

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

sdb5: __________________________________________________________________________

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

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

Drive: sda _____________________________________________________________________
Disk /dev/sda: 7.5 GiB, 8074035200 bytes, 15769600 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
Disklabel type: gpt

Partition  Boot  Start Sector    End Sector  # of Sectors  Id System

/dev/sda1                   1 4,294,967,295 4,294,967,295  ee GPT

/dev/sda1 ends after the last sector of /dev/sda

GUID Partition Table detected.

Partition  Attrs   Start Sector    End Sector  # of Sectors System
/dev/sda1                 2,048    15,769,566    15,767,519 Data partition (Windows/Linux)

Attributes: R=Required, N=No Block IO, B=Legacy BIOS Bootable, +=More bits set

Drive: sdb _____________________________________________________________________
Disk /dev/sdb: 465.8 GiB, 500107862016 bytes, 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
Disklabel type: gpt

Partition  Boot  Start Sector    End Sector  # of Sectors  Id System

/dev/sdb1                   1   976,773,167   976,773,167  ee GPT


GUID Partition Table detected.

Partition  Attrs   Start Sector    End Sector  # of Sectors System
/dev/sdb1                 2,048     1,050,623     1,048,576 EFI System partition
/dev/sdb2             1,050,624    16,642,047    15,591,424 Data partition (Linux)
/dev/sdb3           958,341,120   976,773,119    18,432,000 Swap partition (Linux)
/dev/sdb4            16,642,048   111,851,519    95,209,472 Data partition (Linux)
/dev/sdb5           111,851,520   958,341,119   846,489,600 Data partition (Linux)

Attributes: R=Required, N=No Block IO, B=Legacy BIOS Bootable, +=More bits set

"blkid" output: ________________________________________________________________

Device           UUID                                   TYPE       LABEL

/dev/loop0                                              squashfs   
/dev/sda1        3272-104C                              vfat       LINUX MINT
/dev/sdb1        C8ED-8AF3                              vfat       
/dev/sdb2        5d63d21b-446d-4db2-b977-83e71310f002   ext4       
/dev/sdb3        485b9804-0915-4f04-ab16-b689818612fb   swap       
/dev/sdb4        90680ceb-bc50-452f-8042-e5eb4978a693   ext4       
/dev/sdb5        4123b9ef-189c-439a-bda4-930e9c81a686   ext4       

========================= "ls -l /dev/disk/by-id" output: ======================

total 0
lrwxrwxrwx 1 root root  9 Sep 30 23:37 ata-TOSHIBA_MQ01ABF050_277XC0SUT -> ../../sdb
lrwxrwxrwx 1 root root 10 Sep 30 23:37 ata-TOSHIBA_MQ01ABF050_277XC0SUT-part1 -> ../../sdb1
lrwxrwxrwx 1 root root 10 Sep 30 23:37 ata-TOSHIBA_MQ01ABF050_277XC0SUT-part2 -> ../../sdb2
lrwxrwxrwx 1 root root 10 Sep 30 23:37 ata-TOSHIBA_MQ01ABF050_277XC0SUT-part3 -> ../../sdb3
lrwxrwxrwx 1 root root 10 Sep 30 23:37 ata-TOSHIBA_MQ01ABF050_277XC0SUT-part4 -> ../../sdb4
lrwxrwxrwx 1 root root 10 Sep 30 23:37 ata-TOSHIBA_MQ01ABF050_277XC0SUT-part5 -> ../../sdb5
lrwxrwxrwx 1 root root  9 Sep 30 23:37 usb-IS817_innostor_201404300326-0:0 -> ../../sda
lrwxrwxrwx 1 root root 10 Sep 30 23:37 usb-IS817_innostor_201404300326-0:0-part1 -> ../../sda1
lrwxrwxrwx 1 root root  9 Sep 30 23:37 wwn-0x50000397943030e1 -> ../../sdb
lrwxrwxrwx 1 root root 10 Sep 30 23:37 wwn-0x50000397943030e1-part1 -> ../../sdb1
lrwxrwxrwx 1 root root 10 Sep 30 23:37 wwn-0x50000397943030e1-part2 -> ../../sdb2
lrwxrwxrwx 1 root root 10 Sep 30 23:37 wwn-0x50000397943030e1-part3 -> ../../sdb3
lrwxrwxrwx 1 root root 10 Sep 30 23:37 wwn-0x50000397943030e1-part4 -> ../../sdb4
lrwxrwxrwx 1 root root 10 Sep 30 23:37 wwn-0x50000397943030e1-part5 -> ../../sdb5

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

Device           Mount_Point              Type       Options

/dev/loop0       /rofs                    squashfs   (ro,noatime)
/dev/sda1        /cdrom                   vfat       (ro,noatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)


=========================== sda1/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 18.2 Xfce 64-bit" {
   set gfxpayload=keep
   linux   /casper/vmlinuz  file=/cdrom/preseed/linuxmint.seed boot=casper iso-scan/filename=${iso_path} quiet splash --
   initrd   /casper/initrd.lz
}
menuentry "Start Linux Mint 18.2 Xfce 64-bit (compatibility mode)" {
   linux   /casper/vmlinuz  file=/cdrom/preseed/linuxmint.seed boot=casper xforcevesa iso-scan/filename=${iso_path} ramdisk_size=1048576 root=/dev/ram rw noapic noacpi nosplash irqpoll --
   initrd   /casper/initrd.lz
}
menuentry "OEM install (for manufacturers)" {
   set gfxpayload=keep
   linux   /casper/vmlinuz  file=/cdrom/preseed/linuxmint.seed oem-config/enable=true only-ubiquity boot=casper iso-scan/filename=${iso_path} quiet splash --
   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
}
--------------------------------------------------------------------------------

============================== sda1/syslinux.cfg: ==============================

--------------------------------------------------------------------------------
DEFAULT loadconfig

LABEL loadconfig
  CONFIG /isolinux/isolinux.cfg
  APPEND /isolinux/
--------------------------------------------------------------------------------

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

           GiB - GB             File                                 Fragment(s)

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

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

           GiB - GB             File                                 Fragment(s)

            ?? = ??             syslinux.cfg                                   1

========================== sdb1/EFI/ubuntu/grub.cfg: ===========================

--------------------------------------------------------------------------------
search.fs_uuid 90680ceb-bc50-452f-8042-e5eb4978a693 root hd0,gpt4
set prefix=($root)'/boot/grub'
--------------------------------------------------------------------------------

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

           GiB - GB             File                                 Fragment(s)

   0.640411377 = 0.687636480    vmlinuz-4.8.0-53-generic                       1
   0.680660248 = 0.730853376    initrd.img-4.8.0-53-generic                    2

=============================== sdb4/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>
# / was on /dev/sda4 during installation
UUID=90680ceb-bc50-452f-8042-e5eb4978a693 /               ext4    errors=remount-ro 0       1
# /boot was on /dev/sda2 during installation
#UUID=5d63d21b-446d-4db2-b977-83e71310f002 /boot           ext4    defaults        0       2
# /boot/efi was on /dev/sda1 during installation
#UUID=C8ED-8AF3  /boot/efi       vfat    umask=0077      0       1
# swap was on /dev/sda3 during installation
UUID=485b9804-0915-4f04-ab16-b689818612fb none            swap    sw              0       0
UUID=5d63d21b-446d-4db2-b977-83e71310f002   /boot   ext4   defaults   0   2
UUID=C8ED-8AF3   /boot/efi   vfat   defaults   0   1
--------------------------------------------------------------------------------

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

File descriptor 9 (/proc/3754/mounts) leaked on lvs invocation. Parent PID 14175: bash
File descriptor 63 (pipe:[36540]) leaked on lvs invocation. Parent PID 14175: bash

ADDITIONAL INFORMATION :
=================== log of boot-repair 20170930_2337 ===================
boot-repair version : 4ppa50
boot-sav version : 4ppa50
boot-sav-extra version :
glade2script version : 3.2.3~ppa2
boot-repair is executed in live-session (Linux Mint 18.2 Sonya, sonya, LinuxMint, x86_64)
CPU op-mode(s):        32-bit, 64-bit
BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/linuxmint.seed boot=casper iso-scan/filename= quiet splash --
ls: cannot access '/home/usr/.config': No such file or directory

=================== os-prober:
/dev/sdb4:Linux Mint 18.2 Sonya (18.2):LinuxMint:linux

=================== blkid:
/dev/sda1: LABEL="LINUX MINT" UUID="3272-104C" TYPE="vfat" PARTLABEL="Microsoft Basic Data" PARTUUID="e316b43f-1ab0-42db-a047-b5c8b9170d83"
/dev/loop0: TYPE="squashfs"
/dev/sdb1: UUID="C8ED-8AF3" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="c4855090-89d5-43c0-ae17-d40a86e0fc59"
/dev/sdb2: UUID="5d63d21b-446d-4db2-b977-83e71310f002" TYPE="ext4" PARTLABEL="Boot" PARTUUID="fd2d9aca-ad78-45d6-9661-e87b95b2863b"
/dev/sdb3: UUID="485b9804-0915-4f04-ab16-b689818612fb" TYPE="swap" PARTUUID="3f0fd9de-f2b1-4da6-9ec1-5d6414c1f4ae"
/dev/sdb4: UUID="90680ceb-bc50-452f-8042-e5eb4978a693" TYPE="ext4" PARTLABEL="Root" PARTUUID="6bc4ac66-0644-4493-8f61-1cfccc4027e1"
/dev/sdb5: UUID="4123b9ef-189c-439a-bda4-930e9c81a686" TYPE="ext4" PARTLABEL="Home" PARTUUID="0049d452-dce3-420c-9748-298d21735735"


1 disks with OS, 1 OS : 1 Linux, 0 MacOS, 0 Windows, 0 unknown type OS.


=================== sdb4/etc/grub.d/ :
drwxr-xr-x  2 root root    4096 Jun 28 13:07 grub.d
total 96
-rwxr-xr-x 1 root root  9791 May 11 10:32 00_header
-rwxr-xr-x 1 root root  6258 Mar 15  2016 05_debian_theme
-rwxr-xr-x 1 root root  1180 Oct 25  2014 06_mint_theme
-rwxr-xr-x 1 root root 12552 May 11 10:32 10_linux
-rwxr-xr-x 1 root root 10634 Oct  1  2012 10_lupin
-rwxr-xr-x 1 root root 11082 May 11 10:32 20_linux_xen
-rwxr-xr-x 1 root root  1992 Jan 28  2016 20_memtest86+
-rwxr-xr-x 1 root root 11692 May 11 10:32 30_os-prober
-rwxr-xr-x 1 root root  1418 May 11 10:32 30_uefi-firmware
-rwxr-xr-x 1 root root   214 May 11 10:32 40_custom
-rwxr-xr-x 1 root root   216 May 11 10:32 41_custom
-rw-r--r-- 1 root root   483 May 11 10:32 README




=================== sdb4/etc/default/grub :




=================== No kernel in /mnt/boot-sav/sdb4/boot:
efi
grub


/boot/efi detected in the fstab of sdb4: UUID=C8ED-8AF3    (sdb1)
/boot detected in the fstab of sdb4: UUID=5d63d21b-446d-4db2-b977-83e71310f002    (sdb2)

=================== efibootmgr -v
BootCurrent: 0001
Timeout: 0 seconds
BootOrder: 0001,2001,2002,2003
Boot0000* Unknown Device:    HD(1,GPT,c4855090-89d5-43c0-ae17-d40a86e0fc59,0x800,0x100000)/File(EFIubuntugrubx64.efi)RC
Boot0001* Linux   HD(1,GPT,e316b43f-1ab0-42db-a047-b5c8b9170d83,0x800,0xf097df)/File(EFIBootgrubx64.efi)RC
Boot0002* Unknown Device:    HD(1,GPT,c2e2d177-5258-4d6f-a9b0-564da6648ce4,0x800,0x32000)/File(EFIubuntugrubx64.efi)RC
Boot2001* EFI USB Device   RC
Boot2002* EFI DVD/CDROM   RC
Boot2003* EFI Network   RC

=================== UEFI/Legacy mode:
BIOS is EFI-compatible, and is setup in EFI-mode for this live-session.
SecureBoot disabled. (maybe sec-boot, Please report this message to boot.repair@gmail.com)


=================== PARTITIONS & DISKS:
sdb1   : sdb,   not-sepboot,   no-grubenv   nogrub,   no-docgrub,   no-update-grub,   32,   no-boot,   no-os,   is-correct-EFI,   part-has-no-fstab,   part-has-no-fstab,   no-nt,   no-winload,   no-recov-nor-hid,   no-bmgr,   notwinboot,   nopakmgr,   nogrubinstall,   no---usr,   part-has-no-fstab,   not-sep-usr,   standard,   not-far,   /mnt/boot-sav/sdb1.
sdb2   : sdb,   is-sepboot,   grubenv-ok   nogrub,   no-docgrub,   no-update-grub,   32,   no-boot,   no-os,   is-maybe-EFI,   part-has-no-fstab,   part-has-no-fstab,   no-nt,   no-winload,   no-recov-nor-hid,   no-bmgr,   notwinboot,   nopakmgr,   nogrubinstall,   no---usr,   part-has-no-fstab,   not-sep-usr,   standard,   not-far,   /mnt/boot-sav/sdb2.
sdb4   : sdb,   not-sepboot,   grubenv-ok   grub2,   signed grub-efi ,   update-grub,   64,   no-kernel,   is-os,   not--efi--part,   fstab-has-goodBOOT,   fstab-has-goodEFI,   no-nt,   no-winload,   no-recov-nor-hid,   no-bmgr,   notwinboot,   apt-get,   grub-install,   with--usr,   fstab-without-usr,   not-sep-usr,   standard,   not-far,   /mnt/boot-sav/sdb4.
sdb5   : sdb,   maybesepboot,   no-grubenv   nogrub,   no-docgrub,   no-update-grub,   32,   no-boot,   no-os,   not--efi--part,   part-has-no-fstab,   part-has-no-fstab,   no-nt,   no-winload,   no-recov-nor-hid,   no-bmgr,   notwinboot,   nopakmgr,   nogrubinstall,   no---usr,   part-has-no-fstab,   not-sep-usr,   standard,   farbios,   /mnt/boot-sav/sdb5.

sdb   : GPT,   no-BIOS_boot,   has-correctEFI,    not-usb,   not-mmc, has-os,   2048 sectors * 512 bytes


=================== parted -lm:

BYT;
/dev/sda:8074MB:scsi:512:512:gpt:IS817 innostor:;
1:1049kB:8074MB:8073MB:fat32:Microsoft Basic Data:msftdata;

BYT;
/dev/sdb:500GB:scsi:512:4096:gpt:ATA TOSHIBA MQ01ABF0:;
1:1049kB:538MB:537MB:fat32:EFI System Partition:boot, esp;
2:538MB:8521MB:7983MB:ext4:Boot:;
4:8521MB:57.3GB:48.7GB:ext4:Root:;
5:57.3GB:491GB:433GB:ext4:Home:;
3:491GB:500GB:9437MB:linux-swap(v1)::;

=================== lsblk:
KNAME TYPE FSTYPE     SIZE LABEL
sdb   disk          465.8G
sdb4  part ext4      45.4G
sdb2  part ext4       7.4G
sdb5  part ext4     403.7G
sdb3  part swap       8.8G
sdb1  part vfat       512M
loop0 loop squashfs   1.5G
sda   disk            7.5G
sda1  part vfat       7.5G LINUX MINT

KNAME ROTA RO RM STATE   MOUNTPOINT
sdb      1  0  0 running
sdb4     1  0  0         /mnt/boot-sav/sdb4
sdb2     1  0  0         /mnt/boot-sav/sdb2
sdb5     1  0  0         /mnt/boot-sav/sdb5
sdb3     1  0  0         [SWAP]
sdb1     1  0  0         /mnt/boot-sav/sdb1
loop0    1  1  0         /rofs
sda      1  0  1 running
sda1     1  0  1         /cdrom


=================== mount:
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,nosuid,relatime,size=1917720k,nr_inodes=479430,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=386640k,mode=755)
/dev/sda1 on /cdrom type vfat (ro,noatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
/dev/loop0 on /rofs type squashfs (ro,noatime)
aufs on / type aufs (rw,noatime,si=2b62a7f34eeadd4d)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /sys/fs/cgroup type tmpfs (rw,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset,clone_children)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids,release_agent=/run/cgmanager/agents/cgm-release-agent.pids)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb,release_agent=/run/cgmanager/agents/cgm-release-agent.hugetlb)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event,release_agent=/run/cgmanager/agents/cgm-release-agent.perf_event)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=30,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=9943)
mqueue on /dev/mqueue type mqueue (rw,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
tracefs on /sys/kernel/debug/tracing type tracefs (rw,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,relatime)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime)
cgmfs on /run/cgmanager/fs type tmpfs (rw,relatime,size=100k,mode=755)
tmpfs on /run/user/999 type tmpfs (rw,nosuid,nodev,relatime,size=386640k,mode=700,uid=999,gid=999)
gvfsd-fuse on /run/user/999/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=999,group_id=999)
/dev/sdb1 on /mnt/boot-sav/sdb1 type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
/dev/sdb2 on /mnt/boot-sav/sdb2 type ext4 (rw,relatime,data=ordered)
/dev/sdb4 on /mnt/boot-sav/sdb4 type ext4 (rw,relatime,data=ordered)
/dev/sdb5 on /mnt/boot-sav/sdb5 type ext4 (rw,relatime,data=ordered)


=================== ls:
/sys/block/sda (filtered):  alignment_offset badblocks bdi capability dev device discard_alignment events events_async events_poll_msecs ext_range holders inflight integrity power queue range removable ro sda1 size slaves stat subsystem trace uevent
/sys/block/sdb (filtered):  alignment_offset badblocks bdi capability dev device discard_alignment events events_async events_poll_msecs ext_range holders inflight integrity power queue range removable ro sdb1 sdb2 sdb3 sdb4 sdb5 size slaves stat subsystem trace uevent
/dev (filtered):  autofs block bsg btrfs-control bus char console core cpu cpu_dma_latency cuse disk dri drm_dp_aux0 drm_dp_aux1 ecryptfs fb0 fd full fuse gpiochip0 hidraw0 hpet hugepages hwrng i2c-0 i2c-1 i2c-10 i2c-11 i2c-12 i2c-2 i2c-3 i2c-4 i2c-5 i2c-6 i2c-7 i2c-8 i2c-9 initctl input kmsg kvm lightnvm log mapper mcelog media0 mei0 mem memory_bandwidth mqueue net network_latency network_throughput null port ppp psaux ptmx pts random rfkill rtc rtc0 sda sda1 sdb sdb1 sdb2 sdb3 sdb4 sdb5 sg0 sg1 shm snapshot snd stderr stdin stdout tpm0 uhid uinput urandom userio v4l vfio vga_arbiter vhci vhost-net video0 zero
ls /dev/mapper:  control

=================== hexdump -n512 -C /dev/sdb1
00000000  eb 58 90 6d 6b 66 73 2e  66 61 74 00 02 08 20 00  |.X.mkfs.fat... .|
00000010  02 00 00 00 00 f8 00 00  3f 00 ff 00 00 08 00 00  |........?.......|
00000020  00 00 10 00 fe 03 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 01 29 f3 8a ed c8 20  20 20 20 20 20 20 20 20  |..)....         |
00000050  20 20 46 41 54 33 32 20  20 20 0e 1f be 77 7c ac  |  FAT32   ...w|.|
00000060  22 c0 74 0b 56 b4 0e bb  07 00 cd 10 5e eb f0 32  |".t.V.......^..2|
00000070  e4 cd 16 cd 19 eb fe 54  68 69 73 20 69 73 20 6e  |.......This is n|
00000080  6f 74 20 61 20 62 6f 6f  74 61 62 6c 65 20 64 69  |ot a bootable di|
00000090  73 6b 2e 20 20 50 6c 65  61 73 65 20 69 6e 73 65  |sk.  Please inse|
000000a0  72 74 20 61 20 62 6f 6f  74 61 62 6c 65 20 66 6c  |rt a bootable fl|
000000b0  6f 70 70 79 20 61 6e 64  0d 0a 70 72 65 73 73 20  |oppy and..press |
000000c0  61 6e 79 20 6b 65 79 20  74 6f 20 74 72 79 20 61  |any key to try a|
000000d0  67 61 69 6e 20 2e 2e 2e  20 0d 0a 00 00 00 00 00  |gain ... .......|
000000e0  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  00 00 00 00 00 00 55 aa  |..............U.|
00000200

=================== df -Th:

Filesystem     Type      Size  Used Avail Use% Mounted on
udev           devtmpfs  1.9G     0  1.9G   0% /dev
tmpfs          tmpfs     378M  6.1M  372M   2% /run
/dev/sda1      vfat      7.6G  1.6G  6.0G  21% /cdrom
/dev/loop0     squashfs  1.5G  1.5G     0 100% /rofs
aufs           aufs      1.9G  149M  1.7G   8% /
tmpfs          tmpfs     1.9G  164K  1.9G   1% /dev/shm
tmpfs          tmpfs     5.0M  4.0K  5.0M   1% /run/lock
tmpfs          tmpfs     1.9G     0  1.9G   0% /sys/fs/cgroup
tmpfs          tmpfs     1.9G   12K  1.9G   1% /tmp
cgmfs          tmpfs     100K     0  100K   0% /run/cgmanager/fs
tmpfs          tmpfs     378M   44K  378M   1% /run/user/999
/dev/sdb1      vfat      511M  1.2M  510M   1% /mnt/boot-sav/sdb1
/dev/sdb2      ext4      7.2G   82M  6.8G   2% /mnt/boot-sav/sdb2
/dev/sdb4      ext4       45G  4.6G   38G  11% /mnt/boot-sav/sdb4
/dev/sdb5      ext4      398G   71M  377G   1% /mnt/boot-sav/sdb5

=================== fdisk -l:
Disk /dev/loop0: 1.5 GiB, 1591537664 bytes, 3108472 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 /dev/sda: 7.5 GiB, 8074035200 bytes, 15769600 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
Disklabel type: gpt
Disk identifier: DCFA6CE7-070A-47FF-9EDD-BDB9082882B0

Device     Start      End  Sectors  Size Type
/dev/sda1   2048 15769566 15767519  7.5G Microsoft basic data


Disk /dev/sdb: 465.8 GiB, 500107862016 bytes, 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
Disklabel type: gpt
Disk identifier: BBC0D4BB-875F-4971-B16D-D33C014441AB

Device         Start       End   Sectors   Size Type
/dev/sdb1       2048   1050623   1048576   512M EFI System
/dev/sdb2    1050624  16642047  15591424   7.4G Linux filesystem
/dev/sdb3  958341120 976773119  18432000   8.8G Linux swap
/dev/sdb4   16642048 111851519  95209472  45.4G Linux filesystem
/dev/sdb5  111851520 958341119 846489600 403.7G Linux filesystem

Partition table entries are not in disk order.


Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
/boot detected. Please check the options.


=================== Suggested repair
The default repair of the Boot-Repair utility would reinstall the grub-efi-amd64-signed of sdb4, using the following options:        sdb2/boot, sdb1/boot/efi,
Additional repair would be performed: unhide-bootmenu-10s    use-standard-efi-file rename-ms-efi


=================== User settings
The settings chosen by the user will not act on the boot.




pastebinit  packages needed
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
W: The repository 'cdrom://Linux Mint 18.2 _Sonya_ - Release amd64 20170628 xenial Release' does not have a Release file.
W: Symlinking final file /var/lib/apt/lists/Linux%20Mint%2018.2%20%5fSonya%5f%20-%20Release%20amd64%2020170628_dists_xenial_contrib_binary-amd64_Packages back to /var/lib/apt/lists/partial/Linux%20Mint%2018.2%20%5fSonya%5f%20-%20Release%20amd64%2020170628_dists_xenial_contrib_binary-amd64_Packages.xz failed - pkgAcqIndex::StageDownloadDone (17: File exists)
W: Symlinking final file /var/lib/apt/lists/Linux%20Mint%2018.2%20%5fSonya%5f%20-%20Release%20amd64%2020170628_dists_xenial_main_binary-amd64_Packages back to /var/lib/apt/lists/partial/Linux%20Mint%2018.2%20%5fSonya%5f%20-%20Release%20amd64%2020170628_dists_xenial_main_binary-amd64_Packages.xz failed - pkgAcqIndex::StageDownloadDone (17: File exists)
W: Symlinking final file /var/lib/apt/lists/Linux%20Mint%2018.2%20%5fSonya%5f%20-%20Release%20amd64%2020170628_dists_xenial_non-free_binary-amd64_Packages back to /var/lib/apt/lists/partial/Linux%20Mint%2018.2%20%5fSonya%5f%20-%20Release%20amd64%2020170628_dists_xenial_non-free_binary-amd64_Packages.xz failed - pkgAcqIndex::StageDownloadDone (17: File exists)
W: Symlinking final file /var/lib/apt/lists/Linux%20Mint%2018.2%20%5fSonya%5f%20-%20Release%20amd64%2020170628_dists_xenial_contrib_binary-amd64_Packages back to /var/lib/apt/lists/partial/Linux%20Mint%2018.2%20%5fSonya%5f%20-%20Release%20amd64%2020170628_dists_xenial_contrib_binary-amd64_Packages.bz2 failed - pkgAcqIndex::StageDownloadDone (17: File exists)
W: Symlinking final file /var/lib/apt/lists/Linux%20Mint%2018.2%20%5fSonya%5f%20-%20Release%20amd64%2020170628_dists_xenial_main_binary-amd64_Packages back to /var/lib/apt/lists/partial/Linux%20Mint%2018.2%20%5fSonya%5f%20-%20Release%20amd64%2020170628_dists_xenial_main_binary-amd64_Packages.bz2 failed - pkgAcqIndex::StageDownloadDone (17: File exists)
W: Symlinking final file /var/lib/apt/lists/Linux%20Mint%2018.2%20%5fSonya%5f%20-%20Release%20amd64%2020170628_dists_xenial_non-free_binary-amd64_Packages back to /var/lib/apt/lists/partial/Linux%20Mint%2018.2%20%5fSonya%5f%20-%20Release%20amd64%2020170628_dists_xenial_non-free_binary-amd64_Packages.bz2 failed - pkgAcqIndex::StageDownloadDone (17: File exists)
W: Symlinking final file /var/lib/apt/lists/Linux%20Mint%2018.2%20%5fSonya%5f%20-%20Release%20amd64%2020170628_dists_xenial_contrib_binary-amd64_Packages back to /var/lib/apt/lists/partial/Linux%20Mint%2018.2%20%5fSonya%5f%20-%20Release%20amd64%2020170628_dists_xenial_contrib_binary-amd64_Packages.lzma failed - pkgAcqIndex::StageDownloadDone (17: File exists)
W: Symlinking final file /var/lib/apt/lists/Linux%20Mint%2018.2%20%5fSonya%5f%20-%20Release%20amd64%2020170628_dists_xenial_main_binary-amd64_Packages back to /var/lib/apt/lists/partial/Linux%20Mint%2018.2%20%5fSonya%5f%20-%20Release%20amd64%2020170628_dists_xenial_main_binary-amd64_Packages.lzma failed - pkgAcqIndex::StageDownloadDone (17: File exists)
W: Symlinking final file /var/lib/apt/lists/Linux%20Mint%2018.2%20%5fSonya%5f%20-%20Release%20amd64%2020170628_dists_xenial_non-free_binary-amd64_Packages back to /var/lib/apt/lists/partial/Linux%20Mint%2018.2%20%5fSonya%5f%20-%20Release%20amd64%2020170628_dists_xenial_non-free_binary-amd64_Packages.lzma failed - pkgAcqIndex::StageDownloadDone (17: File exists)
W: Symlinking final file /var/lib/apt/lists/Linux%20Mint%2018.2%20%5fSonya%5f%20-%20Release%20amd64%2020170628_dists_xenial_contrib_binary-amd64_Packages back to /var/lib/apt/lists/partial/Linux%20Mint%2018.2%20%5fSonya%5f%20-%20Release%20amd64%2020170628_dists_xenial_contrib_binary-amd64_Packages.gz failed - pkgAcqIndex::StageDownloadDone (17: File exists)
W: Symlinking final file /var/lib/apt/lists/Linux%20Mint%2018.2%20%5fSonya%5f%20-%20Release%20amd64%2020170628_dists_xenial_main_binary-amd64_Packages back to /var/lib/apt/lists/partial/Linux%20Mint%2018.2%20%5fSonya%5f%20-%20Release%20amd64%2020170628_dists_xenial_main_binary-amd64_Packages.gz failed - pkgAcqIndex::StageDownloadDone (17: File exists)
W: Symlinking final file /var/lib/apt/lists/Linux%20Mint%2018.2%20%5fSonya%5f%20-%20Release%20amd64%2020170628_dists_xenial_non-free_binary-amd64_Packages back to /var/lib/apt/lists/partial/Linux%20Mint%2018.2%20%5fSonya%5f%20-%20Release%20amd64%2020170628_dists_xenial_non-free_binary-amd64_Packages.gz failed - pkgAcqIndex::StageDownloadDone (17: File exists)
E: Failed to fetch cdrom://Linux Mint 18.2 _Sonya_ - Release amd64 20170628/dists/xenial/contrib/binary-i386/Packages  Please use apt-cdrom to make this CD-ROM recognized by APT. apt-get update cannot be used to add new CD-ROMs
E: Some index files failed to download. They have been ignored, or old ones used instead.
dpkg-preconfigure: unable to re-open stdin: No such file or directory
paste2.org ko (http://paste2.org/)

Perry Grin
Level 1
Level 1
Posts: 4
Joined: Fri Sep 29, 2017 3:02 am

Re: boot-repair

Postby Perry Grin » Tue Oct 03, 2017 1:50 am

I have the same problem.

Using a mid 2012 Macbook Pro with an SSD.

Made a installation USB using unebootin.

All goes well till it gets to the installing 'grub2'.

Then it stops and the message is: The 'grub-efi-amd64-signed' package failed to install into/target/.

Without the GRUB boot loader, the installed system will not boot.

fruitkiller
Level 4
Level 4
Posts: 272
Joined: Tue Aug 05, 2014 7:52 pm

Re: boot-repair

Postby fruitkiller » Sun Oct 15, 2017 6:25 am

You should make a boot-repair usb or if that fails, use a good old CD or DVD (DVD-RW preferably, that'd be a waste of space of epic proportion to install boot-repair on a DVD.

Have you solved the problem, you've never given a follow-up? In the worst case scenario, boot with a live DVD of whatever linux distro you have on a CD or DVD or burn a set of open sources programs called Hiren's Boot Disk, it has tons of diagnostic, repair, and more, including xfburn or some other disk burning program. Download supergrubdisk, burn that, to a CD, unfortunately never had much luck when I tried supergrubdisk on a USB key, although it is supposed to work.

Once you have the supergrubdisk CD/DVD, you boot with it, you'll get a menu, the first option is Detect all OS's on this computer, and you will then see your Linux install, press Enter and it will boot your Linux Mint install. Once in there, install Boot-Repair, as a program that's always there. It is not available in a PPA past Saucy, but it works with Trusty and the one after that I forgot the name of, Xenial? Anyway, don't be intimidated by the large amount of options there, just click the large Repair Boot button and it will repair your MBR, it takes a while, and you might see a ton of tabs in your lower panel open, that's normal, they then happen to close just before Boot-Repair will declare your repair a success with a Reboot button,although you can click the "X" button on it and do as you please in your Mint or other linux distro you're in and then, when ready, don't do a reset button reboot, shut down your computer, turn it back on a grub will be back. It's saved my ass a lot of times while I was learning how to Linux all by myself from 2010 to 2012, by then not much of the regular kind of issues faze me, although some definitely does still.

I hope you managed to fix it without formatting and reinstalling, if you had a lot of files you wanted to keep and didn't have the space to move elsewhere, that's ouch, although you canget some back, you won't get much back if you enter any data on the hard drive where you want to find back your lost data, through say my favourite program for such purposes, TestDisk.

Brian h65
Level 1
Level 1
Posts: 13
Joined: Fri Dec 23, 2016 4:52 pm

Re: boot-repair

Postby Brian h65 » Sun Nov 05, 2017 11:37 pm

Could boot repair work for me? Linux Mint 18.1 Cinnamon I recently fixed update issues, I don't know if that caused this, but the 2nd start up afterwards, I got this error message" : Failed to connect to socket /com/ubuntu/upstart: connection refused
Syndaemon: no process found|
mdm[1428]: GLib_CRITICAL: g_key_file_free: assertion 'key_file ! = NULL' failed

recovery mode did not help, I can't run my computer. I tried also in command line, but I can't find a command which will work. :(


Return to “Installation & Boot”