Mint 17 deleted EFI boot folders?

[Resistor]

I have reinstalled Mint 17 a few times, here lately. The whole system was corrupted when I installed Wicd, due to the removal of some essential files, when I removed network manager.
http://forums.linuxmint.com/viewtopic.p ... 58#p904958

I was able to boot nicely in EFI mode, after reinstalling Mint 17 and grub-efi.

Last week, I moved some boot folders around with elevated privileges, and at this late date, I cannot recall exactly what I did, or why. It seemed like the thing to do at the time, and was likley due to an issue of some sort.

The next day, all of the efi folders were gone and I have been booting with SuperGrub2 from DVD, in BIOS mode, ever since.

This is pretty close in time, to when I updated Grub, like so:

Code: Select all

sudo apt-get update;sudo apt-get install grub-efi grub-efi-amd64 grub-efi-amd64-bin
sudo update-grub

I updated Grub the same way, another time or two, since then, to no avail.
Each update reported that the most current EFI version was already installed.
Could this have caused too many Grub entries?

I copied the EFI folders from /dev/sdb to /dev/sda, to get them back, and they are still there, after more than a week, so I'm at a loss as to what caused the deletion.

I suspect they are not in proper position, but I wonder if it is a 32-bit-depth issue on a 64-bit system.

Last night, I tried to install Boot Repair to the HDD and to USB. It does not work, today.

sda1 is flagged as 'boot', in GParted.


This is an excerpt from the result of 'bootinfoscript':

Code: Select all

============== sda2: Version of COM32(R) files used by Syslinux: ===============
 boot/extlinux/chain.c32            :  COM32R module (v4.xx)

============== sdb2: Version of COM32(R) files used by Syslinux: ===============
 boot/extlinux/chain.c32            :  COM32R module (v4.xx)

I have a line in the fstab file, that shows an empty line after the comment, with: $ grep ^# /etc/fstab:

Code: Select all

# To automatically mount EFI file system:
none            /sys/firmware/efi/efivars efivarfs        optional                0       0

Is that line correctly formatted, or does the syntax even work?

To top it all off, a few days ago, Cinnamon started running in Software Rendering mode, on boot up. Is there a fix for this?

I would like to get the file system straightened out, in the hopes that many problems will go away.

Any ideas to bring me back from my wits end?

Code: Select all

                  Boot Info Script 0.61      [1 April 2012]

Fri, August 22, 2014
============================= Boot Info Summary: ===============================

 => Grub2 (v1.99) is installed in the MBR of /dev/sda and looks at sector 
    51736368 of the same hard drive for core.img. core.img is at this location 
    and looks in partition 112 for .

 => Grub2 (v1.99) is installed in the MBR of /dev/sdb and looks at sector 1 of 
    the same hard drive for core.img, but core.img can not be found at this 
    location.

(sda is a 500 GB Hard Drive.)
sda1: __________________________________________________________________________

    File system:       vfat
    Boot sector type:  Grub2 (v1.99)
    Boot sector info:  Grub2 (v1.99) is installed in the boot sector of sda1 
                       and looks at sector 5621408 of the same hard drive for 
                       core.img. core.img is at this location and looks in 
                       partition 112 for . No errors found in the Boot 
                       Parameter Block.
    Operating System:  
    Boot files:        /efi/linuxmint/grubx64.efi /efi/ubuntu/grubx64.efi 
                       /efi/ubuntu/MokManager.efi /efi/ubuntu/shimx64.efi

sda2: __________________________________________________________________________

    File system:       ext4
    Boot sector type:  -
    Boot sector info: 
    Operating System:  Linux Mint 17 Qiana
    Boot files:        /boot/grub/grub.cfg /etc/fstab 
                       /boot/extlinux/extlinux.conf

sda3: __________________________________________________________________________

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

sda4: __________________________________________________________________________

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

sda5: __________________________________________________________________________

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


(sdb is a 32 GB SSD.)
sdb1: __________________________________________________________________________

    File system:       vfat
    Boot sector type:  SYSLINUX 4.05 20140113
    Boot sector info:  Syslinux looks at sector 30632 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:        /efi/BOOT/grubx64.efi /efi/linuxmint/grubx64.efi 
                       /efi/ubuntu/grubx64.efi /efi/ubuntu/MokManager.efi 
                       /ldlinux.sys

sdb2: __________________________________________________________________________

    File system:       ext4
    Boot sector type:  -
    Boot sector info: 
    Operating System:  Linux Mint 17 Qiana
    Boot files:        /boot/grub/grub.cfg /etc/fstab 
                       /boot/extlinux/extlinux.conf

sdb3: __________________________________________________________________________

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


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

Drive: sda _____________________________________________________________________

Disk /dev/sda: 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

Partition  Boot  Start Sector    End Sector  # of Sectors  Id System

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


GUID Partition Table detected.

Partition    Start Sector    End Sector  # of Sectors System
/dev/sda1           2,048     1,026,047     1,024,000 EFI System partition
/dev/sda2       1,026,048    43,958,271    42,932,224 Data partition (Linux)
/dev/sda3      43,958,272   353,796,095   309,837,824 Data partition (Linux)
/dev/sda4     353,796,096   384,944,127    31,148,032 Data partition (Linux)
/dev/sda5     384,944,128   397,965,611    13,021,484 Swap partition (Linux)

Drive: sdb _____________________________________________________________________

Disk /dev/sdb: 32.0 GB, 32017047552 bytes
255 heads, 63 sectors/track, 3892 cylinders, total 62533296 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                   1    62,533,295    62,533,295  ee GPT


GUID Partition Table detected.

Partition    Start Sector    End Sector  # of Sectors System
/dev/sdb1           2,048     1,048,575     1,046,528 EFI System partition
/dev/sdb2       1,048,576    47,654,911    46,606,336 Data partition (Linux)
/dev/sdb3      47,654,912    62,531,583    14,876,672 Swap partition (Linux)



"blkid" output: ________________________________________________________________

Device           UUID                                   TYPE       LABEL

/dev/sda1        12C9-D3F4                              vfat       
/dev/sda2        08f04b50-c81f-45ae-b7d8-6c9e932d7b3d   ext4       
/dev/sda3        4f61b644-bd64-43b1-8ddb-bf58114a786c   ext4       
/dev/sda4        d8cbee2f-6abd-4d7c-87bc-000c7a21ce37   ext4       New_OS
/dev/sda5        3138fc90-fc36-4a26-aaf2-a0f584fa75ab   swap       

/dev/sdb1        2DD4-C3AA                              vfat       
/dev/sdb2        12ccb75a-ea4d-4af3-901c-49dab9bbed11   ext4       
/dev/sdb3        2e239d9f-9673-4d20-903e-908a63b417b3   swap       


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

Device           Mount_Point              Type       Options

/dev/sda1        /boot/efi                vfat       (rw,utf8,umask=007,gid=46)
/dev/sda2        /                        ext4       (rw,errors=remount-ro)
/dev/sda3        /home/Data               ext4       (rw)
/dev/sda4        /home/New_OS             ext4       (rw)

/dev/sdb2        /media/gt/12ccb75a-ea4d-4af3-901c-49dab9bbed11 ext4       (rw,nosuid,nodev,uhelper=udisks2)

/dev/sdc1        /media/gt/3663-6234      vfat       (rw,nosuid,nodev,uid=1000,gid=1000,shortname=mixed,dmask=0077,utf8=1,showexec,flush,uhelper=udisks2)


=========================== sda2/boot/grub/grub.cfg: ===========================

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

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
  set have_grubenv=true
  load_env
fi
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
set root='hd0,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2  08f04b50-c81f-45ae-b7d8-6c9e932d7b3d
else
  search --no-floppy --fs-uuid --set=root 08f04b50-c81f-45ae-b7d8-6c9e932d7b3d
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=hidden
    set timeout=0
  # Fallback hidden-timeout code in case the timeout_style feature is
  # unavailable.
  elif sleep --interruptible 0 ; then
    set timeout=0
  fi
fi
play 480 440 1
### 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
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/06_mint_theme ###
set menu_color_normal=white/black
set menu_color_highlight=white/light-gray
### END /etc/grub.d/06_mint_theme ###

### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
	set gfxpayload="$1"
	if [ "$1" = "keep" ]; then
		set vt_handoff=vt.handoff=7
	else
		set vt_handoff=
	fi
}
if [ ${recordfail} != 1 ]; then
  if [ -e ${prefix}/gfxblacklist.txt ]; then
    if hwmatch ${prefix}/gfxblacklist.txt 3; then
      if [ ${match} = 0 ]; then
        set linux_gfx_mode=keep
      else
        set linux_gfx_mode=text
      fi
    else
      set linux_gfx_mode=text
    fi
  else
    set linux_gfx_mode=keep
  fi
else
  set linux_gfx_mode=text
fi
export linux_gfx_mode
if [ "$linux_gfx_mode" != "text" ]; then load_video; fi
menuentry 'Linux Mint 17 Cinnamon 64-bit, 3.13.0-24-generic (/dev/sda2)' --class ubuntu --class gnu-linux --class gnu --class os {
	recordfail
	gfxmode $linux_gfx_mode
	insmod gzio
	insmod part_gpt
	insmod ext2
	set root='hd0,gpt2'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2  08f04b50-c81f-45ae-b7d8-6c9e932d7b3d
	else
	  search --no-floppy --fs-uuid --set=root 08f04b50-c81f-45ae-b7d8-6c9e932d7b3d
	fi
	linux	/boot/vmlinuz-3.13.0-24-generic root=UUID=08f04b50-c81f-45ae-b7d8-6c9e932d7b3d ro   quiet splash nomodeset $vt_handoff
	initrd	/boot/initrd.img-3.13.0-24-generic
}
menuentry 'Linux Mint 17 Cinnamon 64-bit, 3.13.0-24-generic (/dev/sda2) -- recovery mode' --class ubuntu --class gnu-linux --class gnu --class os {
	recordfail
	insmod gzio
	insmod part_gpt
	insmod ext2
	set root='hd0,gpt2'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2  08f04b50-c81f-45ae-b7d8-6c9e932d7b3d
	else
	  search --no-floppy --fs-uuid --set=root 08f04b50-c81f-45ae-b7d8-6c9e932d7b3d
	fi
	echo	'Loading Linux 3.13.0-24-generic ...'
	linux	/boot/vmlinuz-3.13.0-24-generic root=UUID=08f04b50-c81f-45ae-b7d8-6c9e932d7b3d ro recovery nomodeset 
	echo	'Loading initial ramdisk ...'
	initrd	/boot/initrd.img-3.13.0-24-generic
}
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/10_lupin ###
### END /etc/grub.d/10_lupin ###

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

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

### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry 'Memory test (memtest86+)' {
	insmod part_gpt
	insmod ext2
	set root='hd0,gpt2'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2  08f04b50-c81f-45ae-b7d8-6c9e932d7b3d
	else
	  search --no-floppy --fs-uuid --set=root 08f04b50-c81f-45ae-b7d8-6c9e932d7b3d
	fi
	knetbsd	/boot/memtest86+.elf
}
menuentry 'Memory test (memtest86+, serial console 115200)' {
	insmod part_gpt
	insmod ext2
	set root='hd0,gpt2'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2  08f04b50-c81f-45ae-b7d8-6c9e932d7b3d
	else
	  search --no-floppy --fs-uuid --set=root 08f04b50-c81f-45ae-b7d8-6c9e932d7b3d
	fi
	linux16	/boot/memtest86+.bin console=ttyS0,115200n8
}
### END /etc/grub.d/20_memtest86+ ###

### BEGIN /etc/grub.d/30_os-prober ###
menuentry 'Linux Mint 17 Qiana (17) (on /dev/sdb2)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-simple-12ccb75a-ea4d-4af3-901c-49dab9bbed11' {
	insmod part_gpt
	insmod ext2
	set root='hd1,gpt2'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt2 --hint-efi=hd1,gpt2 --hint-baremetal=ahci1,gpt2  12ccb75a-ea4d-4af3-901c-49dab9bbed11
	else
	  search --no-floppy --fs-uuid --set=root 12ccb75a-ea4d-4af3-901c-49dab9bbed11
	fi
	linux /boot/vmlinuz-3.13.0-24-generic root=UUID=12ccb75a-ea4d-4af3-901c-49dab9bbed11 ro quiet splash $vt_handoff
	initrd /boot/initrd.img-3.13.0-24-generic
}
submenu 'Advanced options for Linux Mint 17 Qiana (17) (on /dev/sdb2)' $menuentry_id_option 'osprober-gnulinux-advanced-12ccb75a-ea4d-4af3-901c-49dab9bbed11' {
	menuentry 'Linux Mint 17 Cinnamon 64-bit, 3.13.0-24-generic (/dev/sdb2) (on /dev/sdb2)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-3.13.0-24-generic--12ccb75a-ea4d-4af3-901c-49dab9bbed11' {
		insmod part_gpt
		insmod ext2
		set root='hd1,gpt2'
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt2 --hint-efi=hd1,gpt2 --hint-baremetal=ahci1,gpt2  12ccb75a-ea4d-4af3-901c-49dab9bbed11
		else
		  search --no-floppy --fs-uuid --set=root 12ccb75a-ea4d-4af3-901c-49dab9bbed11
		fi
		linux /boot/vmlinuz-3.13.0-24-generic root=UUID=12ccb75a-ea4d-4af3-901c-49dab9bbed11 ro quiet splash $vt_handoff
		initrd /boot/initrd.img-3.13.0-24-generic
	}
	menuentry 'Linux Mint 17 Cinnamon 64-bit, 3.13.0-24-generic (/dev/sdb2) -- recovery mode (on /dev/sdb2)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-3.13.0-24-generic-root=UUID=12ccb75a-ea4d-4af3-901c-49dab9bbed11 ro recovery nomodeset-12ccb75a-ea4d-4af3-901c-49dab9bbed11' {
		insmod part_gpt
		insmod ext2
		set root='hd1,gpt2'
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt2 --hint-efi=hd1,gpt2 --hint-baremetal=ahci1,gpt2  12ccb75a-ea4d-4af3-901c-49dab9bbed11
		else
		  search --no-floppy --fs-uuid --set=root 12ccb75a-ea4d-4af3-901c-49dab9bbed11
		fi
		linux /boot/vmlinuz-3.13.0-24-generic root=UUID=12ccb75a-ea4d-4af3-901c-49dab9bbed11 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/30_os-prober ###

### BEGIN /etc/grub.d/30_uefi-firmware ###
### END /etc/grub.d/30_uefi-firmware ###

### 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 ###
--------------------------------------------------------------------------------

=============================== sda2/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/sda2 during installation
UUID=08f04b50-c81f-45ae-b7d8-6c9e932d7b3d /               ext4    errors=remount-ro 0       1
#
# /boot/efi was on /dev/sda1 during installation
UUID=12C9-D3F4  /boot/efi       vfat    utf8,umask=007,gid=46 0       1
#
# /home/Data was on /dev/sda3 during installation
UUID=4f61b644-bd64-43b1-8ddb-bf58114a786c /home/Data      ext4    defaults        0       2
#
# /home/New_OS was on /dev/sda4 during installation
UUID=d8cbee2f-6abd-4d7c-87bc-000c7a21ce37 /home/New_OS    ext4    defaults        0       2
#
# swap was on /dev/sda5 during installation
UUID=3138fc90-fc36-4a26-aaf2-a0f584fa75ab none            swap    sw              0       0
#
# swap was on /dev/sdb3 during installation
UUID=2e239d9f-9673-4d20-903e-908a63b417b3 none            swap    sw              0       0
#
# To automatically mount EFI file system:
none            /sys/firmware/efi/efivars efivarfs        optional                0       0
#
# Mount DATA partition under /mnt/DATA. I've commented it out, for later consideration.
# This caused a boot-time error message to (I) Ignore, (S) Skip or # (M) Manual Configuration. 
#
# UUID=4f61b644-bd64-43b1-8ddb-bf58114a786c  /mnt/DATA     ext4     defaults     0     2
--------------------------------------------------------------------------------

====================== sda2/boot/extlinux/extlinux.conf: =======================

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


default l0
prompt 1
timeout 50

display boot.txt
include linux.cfg
include memdisk.cfg
include os-prober.cfg
--------------------------------------------------------------------------------

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

           GiB - GB             File                                 Fragment(s)


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

           GiB - GB             File                                 Fragment(s)

##  Note: I noticed those fragments on sdb2, before, so I reformated the sdb2 partions and reinstalled.



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

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

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

           GiB - GB             File                                 Fragment(s)


=========================== sdb2/boot/grub/grub.cfg: ===========================

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

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
  set have_grubenv=true
  load_env
fi
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
set root='hd1,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt2 --hint-efi=hd1,gpt2 --hint-baremetal=ahci1,gpt2  12ccb75a-ea4d-4af3-901c-49dab9bbed11
else
  search --no-floppy --fs-uuid --set=root 12ccb75a-ea4d-4af3-901c-49dab9bbed11
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
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/06_mint_theme ###
set menu_color_normal=white/black
set menu_color_highlight=white/light-gray
### END /etc/grub.d/06_mint_theme ###

### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
	set gfxpayload="$1"
	if [ "$1" = "keep" ]; then
		set vt_handoff=vt.handoff=7
	else
		set vt_handoff=
	fi
}
if [ ${recordfail} != 1 ]; then
  if [ -e ${prefix}/gfxblacklist.txt ]; then
    if hwmatch ${prefix}/gfxblacklist.txt 3; then
      if [ ${match} = 0 ]; then
        set linux_gfx_mode=keep
      else
        set linux_gfx_mode=text
      fi
    else
      set linux_gfx_mode=text
    fi
  else
    set linux_gfx_mode=keep
  fi
else
  set linux_gfx_mode=text
fi
export linux_gfx_mode
if [ "$linux_gfx_mode" != "text" ]; then load_video; fi
menuentry 'Linux Mint 17 Cinnamon 64-bit, 3.13.0-24-generic (/dev/sdb2)' --class ubuntu --class gnu-linux --class gnu --class os {
	recordfail
	gfxmode $linux_gfx_mode
	insmod gzio
	insmod part_gpt
	insmod ext2
	set root='hd1,gpt2'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt2 --hint-efi=hd1,gpt2 --hint-baremetal=ahci1,gpt2  12ccb75a-ea4d-4af3-901c-49dab9bbed11
	else
	  search --no-floppy --fs-uuid --set=root 12ccb75a-ea4d-4af3-901c-49dab9bbed11
	fi
	linux	/boot/vmlinuz-3.13.0-24-generic root=UUID=12ccb75a-ea4d-4af3-901c-49dab9bbed11 ro   quiet splash $vt_handoff
	initrd	/boot/initrd.img-3.13.0-24-generic
}
menuentry 'Linux Mint 17 Cinnamon 64-bit, 3.13.0-24-generic (/dev/sdb2) -- recovery mode' --class ubuntu --class gnu-linux --class gnu --class os {
	recordfail
	insmod gzio
	insmod part_gpt
	insmod ext2
	set root='hd1,gpt2'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt2 --hint-efi=hd1,gpt2 --hint-baremetal=ahci1,gpt2  12ccb75a-ea4d-4af3-901c-49dab9bbed11
	else
	  search --no-floppy --fs-uuid --set=root 12ccb75a-ea4d-4af3-901c-49dab9bbed11
	fi
	echo	'Loading Linux 3.13.0-24-generic ...'
	linux	/boot/vmlinuz-3.13.0-24-generic root=UUID=12ccb75a-ea4d-4af3-901c-49dab9bbed11 ro recovery nomodeset 
	echo	'Loading initial ramdisk ...'
	initrd	/boot/initrd.img-3.13.0-24-generic
}
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/10_lupin ###
### END /etc/grub.d/10_lupin ###

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

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

### BEGIN /etc/grub.d/30_os-prober ###
menuentry 'Linux Mint 17 Qiana (17) (on /dev/sda2)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-simple-08f04b50-c81f-45ae-b7d8-6c9e932d7b3d' {
	insmod part_gpt
	insmod ext2
	set root='hd0,gpt2'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2  08f04b50-c81f-45ae-b7d8-6c9e932d7b3d
	else
	  search --no-floppy --fs-uuid --set=root 08f04b50-c81f-45ae-b7d8-6c9e932d7b3d
	fi
	linux /boot/vmlinuz-3.13.0-24-generic root=UUID=08f04b50-c81f-45ae-b7d8-6c9e932d7b3d ro quiet splash $vt_handoff
	initrd /boot/initrd.img-3.13.0-24-generic
}
submenu 'Advanced options for Linux Mint 17 Qiana (17) (on /dev/sda2)' $menuentry_id_option 'osprober-gnulinux-advanced-08f04b50-c81f-45ae-b7d8-6c9e932d7b3d' {
	menuentry 'Linux Mint 17 Cinnamon 64-bit, 3.13.0-24-generic (/dev/sda2) (on /dev/sda2)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-3.13.0-24-generic--08f04b50-c81f-45ae-b7d8-6c9e932d7b3d' {
		insmod part_gpt
		insmod ext2
		set root='hd0,gpt2'
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2  08f04b50-c81f-45ae-b7d8-6c9e932d7b3d
		else
		  search --no-floppy --fs-uuid --set=root 08f04b50-c81f-45ae-b7d8-6c9e932d7b3d
		fi
		linux /boot/vmlinuz-3.13.0-24-generic root=UUID=08f04b50-c81f-45ae-b7d8-6c9e932d7b3d ro quiet splash $vt_handoff
		initrd /boot/initrd.img-3.13.0-24-generic
	}
	menuentry 'Linux Mint 17 Cinnamon 64-bit, 3.13.0-24-generic (/dev/sda2) -- recovery mode (on /dev/sda2)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-3.13.0-24-generic-root=UUID=08f04b50-c81f-45ae-b7d8-6c9e932d7b3d ro recovery nomodeset-08f04b50-c81f-45ae-b7d8-6c9e932d7b3d' {
		insmod part_gpt
		insmod ext2
		set root='hd0,gpt2'
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2  08f04b50-c81f-45ae-b7d8-6c9e932d7b3d
		else
		  search --no-floppy --fs-uuid --set=root 08f04b50-c81f-45ae-b7d8-6c9e932d7b3d
		fi
		linux /boot/vmlinuz-3.13.0-24-generic root=UUID=08f04b50-c81f-45ae-b7d8-6c9e932d7b3d 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/30_os-prober ###

### BEGIN /etc/grub.d/30_uefi-firmware ###
### END /etc/grub.d/30_uefi-firmware ###

### 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 ###
--------------------------------------------------------------------------------

=============================== sdb2/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/sdb2 during installation
UUID=12ccb75a-ea4d-4af3-901c-49dab9bbed11 /               ext4    errors=remount-ro 0       1
#
# /boot/efi was on /dev/sdb1 during installation
UUID=2DD4-C3AA  /boot/efi       vfat    utf8,umask=007,gid=46 0       1
#
# swap was on /dev/sdb3 during installation
UUID=2e239d9f-9673-4d20-903e-908a63b417b3 none            swap    sw              0       0
#
# To automatically mount EFI file system:
none            /sys/firmware/efi/efivars efivarfs        optional                0       0
--------------------------------------------------------------------------------

====================== sdb2/boot/extlinux/extlinux.conf: =======================

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


default l0
prompt 1
timeout 50

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

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

           GiB - GB             File                                 Fragment(s)


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

           GiB - GB             File                                 Fragment(s)


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

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


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

cat: /tmp/BootInfo-ej2Um41g/Tmp_Log: No such file or directory
cat: /tmp/BootInfo-ej2Um41g/Tmp_Log: No such file or directory
cat: /tmp/BootInfo-ej2Um41g/Tmp_Log: No such file or directory
cat: /tmp/BootInfo-ej2Um41g/Tmp_Log: No such file or directory
cat: /tmp/BootInfo-ej2Um41g/Tmp_Log: No such file or directory
  No volume groups found

[Derek_S]

Hello Resistor - I had a look at all the info you've provided, and have to ask a few questions before trying to figure out how to fix things. In particular, just how many Linux OSs are installed on your system. It appears there are two (or more?), but I want to be sure about this.

dev/sda - The 500GB WD hard drive
dev/sda1 - An EFI boot partition, the one you tried to restore and want to use to boot the system?
dev/sda2 - A root partition for one version of Linux Mint 17
dev/sda3 - A home partition for the OS on sda2? (Please confirm!)
dev/sda4 - A data partition shared by both OSs? Or a home partition for the OS on dev/sdb2? (Or something else? Please clarify!)
dev/sda5 - A swap partition for the OS on sda2

dev/sdb - The 32GB SSD drive
dev/sdb1 - A second EFI boot partition (Realize this: You only need one to boot both systems.)
dev/sdb2 - A root partition for a second version of LM17
dev/sdb3 - A second swap partition for the OS on sdb2 (Again, you only need one for both systems.)

This can be fixed, but if it were me, I would consider reinstalling both OSs and revamping your partition setup entirely.

On the SSD - A small EFI boot partition (200MB) and two root partitions at 14GB each
On the WD drive - Two home partitions and a single swap partition (Optional - add a shared data partition that is mounted when booting either OS)

[Resistor]

Hi, Derek_S.

There are 2 Linux Mint 17 installations:
sda and sdb.

dev/sda1 - Is the EFI System boot partition to restore and use to boot the system.

dev/sda2 - This is the Root partition for version 2 of Linux Mint 17.

dev/sda3 - This is the Data partition for the OS on sda2. I did not intend to have a seperate /home partition, due to the settings issue. The data partitions are for Documents, Pictures, Audio, etc, and are to evenutually be shared by both sda and sdb. PatH57 had suggested using sdb to run the OS and use sda purely for storage. I still need to figure out how to do that...

dev/sda4 - Is an empty partition to provide a playground for other OSs, or simply as a reserve.
I have no idea how it was assigned a mount point, much less how it was designated a /home mount point.

dev/sda5 - Is the swap partition for the OS on sda. I don't know how to point the sdb OS to the sda5 swap partition.
_______

dev/sdb - The 32GB SSD drive

dev/sdb1 - A second EFI boot partition (Realize this: You only need one to boot both systems.)
This is the EFI System boot partition, formatted to vfat32, 500 MB.

I did not realize that you only need one System boot partition, and it is contrary to advice I've seen on these forums, that each drive is complete unto itself, including having its own EFI system partition as well as its own swap partition...

Should I reformat sdb1 to 100% ext4, and point sdb toward dev/sda1 EFI System partition and to the sda5 swap partition?

dev/sdb2 - Is the root partition for a second version of LM17 v2.
Yes.

dev/sdb3 - A second swap partition for the OS on sdb2 (Again, you only need one for both systems.)
Ok. Another issue on which I was confused.
It sounds as if I should use the entire SSD for LM17 v2, as Root.
How do I tell it to find the system, Data and swap partitions, on sda?
_______

I saw something the other day, that indicated there was some partition overlap on sdb.
I do not recall the application that I used, but this suggests a dirty installation.

I had re-formatted sdb1 to the same vfat32 and sdb2 to the same ext4 file systems, prior to the latest install. The only other way I know to get a clean install, would be to wipe the drive and start over.

I was running from sdb, in EFI mode, when things got squirrly.

This is a link to a shot of sda, as partitioned in GParted:
http://i60.tinypic.com/1twor9.jpg
I can't get the image size right and losing patience... Sorry for that.

Currently, on sdb:
sdb1 = EFI System Partition (500 MB).
sdb2 = Root (22 GB).
sdb3 = swap (7 GB).
_______

I was already contemplating reinstalling sdb and if you recommend reinstalling on sda, I will.

However, sda seems to be running well, after getting in with SuperGrub2, except it is running in BIOS mode instead of EFI mode. This version of SuperGrub2 is more than a year old.

The only issues I have with its current /sda configuration - aside from the boot issues - is how to mount the /sda3 stand-alone /Data partion, and the need to remove the mount point from /sda4, since sda4 has no present purpose other than as a back up, a playground or as a reserve.

Would it make much difference if we avoided reinstalling to sda? Though, I understand it would be necessary, if there is a need to restructure the HDD.
_______

You suggested: On the SSD - A small EFI boot partition (200MB) and two root partitions at 14GB each

WhY have two root partitions on the same drive - SSD?

I know that products and technology have come a long way, but it seems risky not having an operating system on both drives, when they are available. I don't know, but I'm with you, what ever you suggest.
_______

I can't tell you how encouraged I am, already, now that you have restored my sanity...


Thank you, Derek!

[Derek_S]

Hello Resistor - Reinstalling both systems requires two things on your part. 1.) Are you confident using Gparted to partition both drives prior to installation? 2.) Have you ever run the Linux Mint installer using the "Something Else" option? Both are necessary to do what I have described. If you're not sure about doing this, then it's probably better to install each OS separately on each hard drive.

[Resistor]

Hi, Derek.

Yes, on both counts, with maybe a little confusion regarding the installer vs the Live OS.

I just read that someone had to reboot to select the EFI installer from Firmware options.
I've never done that, though I have booted into the Live version from Firmware options.

I'll need to know what to look for in running the installer, if it is different from simply choosing the 'Install LM17' from the desktop of the Live version.

Legacy BIOS mode usually works, as I may not be able to boot to the Live version in EFI mode. When I get into EFI mode, everything usually works well in EFI mode.

So, consider I'm a little slow, but I will follow your instructions.

[Derek_S]

Hello Resistor - Just to let you know I haven't lost interest here. I've begun typing out some detailed instructions for you to follow regarding re-partitioning your drives and doing the installation. It's getting late so I saved them as a draft and will finish them tomorrow.

[Resistor]

Hi, Derek.

I'm looking forward to it, particularly since I lack the confidence in sda, that I had earlier.

You might consider making it a tutorial, to overcome some well-intentioned misinformation that appears from time to time.

Thank you,

[Derek_S]

Hello Resistor - I'll take you through this step by step. If there's something you don't understand or have a question about, refer to the step number in your reply.

Step 1.) Create the installation media for the two Linux Mint OSs you wish to install. Enter your BIOS settings and enable EFI boot. DO NOT enable Secure Boot. If you have to, set your boot order to boot from either the DVD drive or USB, whichever applies to the installation media you're using.

Step 2.) Boot into a live session using the OS you want to install first, then make your internet connection.

Step 3.) Open Gparted and use the tab in the upper right side to select the SSD drive first. Go to "Device", then select "Create New Partition Table". Click where it says "msdos" to show all the other choices and choose "GPT", then click "Apply". In a few seconds, a single line marked "Unallocated" will appear in the partiton table below. It should be about 29.8GB in size.

Step 4.) Right click the line marked "unallocated" and select "New". In the new panel that appears, you must do five things: a.) Create as: select "Primary". b.) Filesystem: select "FAT32" c.) Label: enter "EFI Boot". d.) New size: enter 400MB(I changed my mind on this). e.) Check that "Align to" is displayed as "MiB". If it shows "Cylinder", then change it to "MiB". When you are done, click "Add", and your new EFI boot partition will appear in the table. ***Please take note of the device assigned to the EFI partition (sda1, sdb1, or sdc1) and write it down. You will need this later on during installation.***

Step 5.) Now right click "Unallocated", and select "New". a.) Create as: select "Primary". b.) Filesystem: select "ext4" c.) Label: enter "Root #1"(or whatever makes sense to you). d.) New size: enter 12288MB(12GB). e.) Check that "Align to" is displayed as "MiB". When you are done, click "Add", and your first root partition will appear in the table.

Step 6.) Again, right click "Unallocated", and select "New". a.) Create as: select "Primary". b.) Filesystem: select "ext4" c.) Label: enter "Root #2"(or whatever makes sense to you). d.) New size: enter 12288MB(12GB). e.) Check that "Align to" is displayed as "MiB". When you are done, click "Add", and your second root partition will appear in the table.

Step 7.) Closely examine your three new partitions in the partition table . Double-check that everything is correct. If something is wrong, you can click "Edit" and select "Undo Last Operation" and redo any partition. Once you are satisfied everything is good, go up and click "Edit", then click "Apply". This step is that actually creates the new partitions on the disk. Your 32GB SSD is now prepared for installation.

Step 8.) Now select the 500GB WD drive. Do exactly what you did in step 3 and create a new GPT partition table on the disk. You should see an unallocated space of about 465.66GB appear in the partition table below.

Step 9.) Now you'll have to do a little math here. You want to create a swap partition that is equal in size to your system's memory. This will allow you to hibernate the system (suspend to disk). Keep in mind 1GB = 1024MB. Right click "Unallocated". a.) Create as: select "Primary". b.) Filesystem: select "Linux Swap" c.) Label: enter "Swap". d.) New size: enter the amount you just calculated. e.) Check that "Align to" is displayed as "MiB". When you are done, click "Add", and your new swap partition will appear in the table.

Step 10.) Now you can take the rest of the unallocated space and divide it between the two home partitions you need to create. Or if you wish, you can make one larger than the other for the OS you use the most. This is up to you. Make both of them primary. Use ext4 for the filesystem for both. Just be sure to apply two different labels (like Home #1/Home #2) so you can tell them apart. Again, examine the partition table to be sure everything is correct, then click "Edit" and "Apply". One thing left to do. Go to the line for Swap, right click it, then select "swap on". This mounts the swap partition and makes it active so the installer will automatically detect it as swap. Now you can exit Gparted.

Step 11.) Click the "Install" icon on the desktop to start the installation. Go through the initial steps until you get to "Installation Type", then check the "Something Else" option. On the next screen, "Installation", you will see a small partition table displaying the partitions on both disks (you may have to scroll up and down to see them all). Start by finding the line for your EFI boot partition on the SSD. Click on it to highlight it, then go down and hit the "Change" button. There is only one thing to do here, and that is to click "Use as" and select "EFI boot partition". DO NOT resize it or check the "Format" box! (You have already done this using Gparted). Now click the "OK" button, your EFI boot partition is set.

Step 12.) Find the line for the first root partition on the SSD. Click on it to highlight it, then go down and hit the "Change" button. On the small pop-up screen that appears, click the "Use As" button, and select ext4 as the file system. Then click "Mount Point" and select " / " - the root symbol. You are done with root at this point and can click the "OK" button.

Step 13.) Now find the line for your first home partition on the WD drive, click and highlight it, then hit the "Change" button. On the small pop-up screen that appears, click the "Use As" button, and select ext4 as the file system. Then click "Mount Point" and select " /home ". You are done with home at this point and can click the "OK" button.

Step 14.) One thing remains here, go to the bottom of this screen and make sure that the appropriate device is selected as the "Device for boot loader installation". Enter the partition that you are using for EFI boot (remember what you wrote down in step #4? - or go back up to the partition table to find it). Once you have done this, click the "Install Now" button at the bottom of the page. ***Note - you will probably get a message that root or home is not set to be formatted, ignore it and proceed. Then it's a matter of filling in a few more things and letting the installer run to completion.

Step 15.) When you restart the system, you may find that it doesn't boot. If this happens, you will have to enter your BIOS settings and set your SSD drive as the first device in the boot order.

Step 16.) To install your second OS, follow these instructions starting at step #11. Just be sure to select the second root partition on the SSD and the second home partition on the WD drive.

[Resistor]

Hello, Derek.

Thank you for a very clear procedure.
I understand almost everything you have written and anticipate a smooth installation.

One thing I am not sure about, which may be due to my own failure to be clear.

I inadvertently wiped out Windows 8, 14 months ago. I do not expect to replace it.
So, Linux Mint 17 Qiana v2 is the only OS on this computer, at the moment.

Should I install to only /sdb "Root_1" and leave "Root_2" empty?
Or, should "Root_2" be the same as "Root_1"?

Or, should I use the entire SSD for one instance of LM17?


Since I'm in BIOS mode right now, I expect to get a blank screen with slight backlighting, and an inablity to boot up into EFI mode, when I boot to the USB.

So, I will have to boot the USB in Legacy BIOS mode.

I want to stay with booting to EFI mode, since the BIOS is a fading system.
I was thinking that I would need to remove grub, then reinstall grub-efi.

That is secondary to getting this re-installation done, though.


I'm about to boot into the USB Live version and will report back with results.

[Derek_S]

Hello Resistor - I went back and re-reard the first part of this thread, and now I understand what you did. You did not have two separate versions of Linux Mint installed - you installed the same version multiple times and ended up with way too many partitions on the two drives. If all you want is a single Linux Mint OS on this machine, then modify my instructions by doing this when formatting the two drives:

1.) You only need one EFI boot, one root, one home, and one swap partition.

2.) On the 32GB SSD drive, start by making a 400MB primary partion for EFI boot, formatted FAT32. Make sure it is aligned to MiB, not cylinder. Then create one primary partition 20480MB(20GB) for your root partition, formatted ext4. Again, check to see it is aligned to MiB, not cylinder.

3.) On the 500GB WD drive, start by making a primary partition for swap, equal in size to your system memory, formatted Linux Swap. Then you can use the rest of the drive to create a large primary partition for home, formatted ext4.

By putting the EFI boot partition and root on the SSD, your system will boot faster and run applications faster. By putting home and swap on the WD drive, you will be keeping the browser cache files, which are stored in the home directory, off the SSD drive. The idea here is to speed up your system and reduce unnecessary writes to the SSD. After you finish the installation, check out how to optimize Linux Mint when installed on a SSD: https://sites.google.com/site/easylinuxtipsproject/ssd

[Resistor]

Hello, Derek.

I really appreciate your patience.

I am also amazed at the flexibility of the installer.
I had no idea that it would operate on two seperate drives, at the same time.

I am now into the new installation, running in Legacy BIOS mode.

Edit to add:
Several attempts to boot in the normal way and with all EFI option, resulted in a black screen with some back lighting.

Even booting from Legacy options resulted in the grub resucue> prompt.

As I set things up, I am discovering some new quirks with Firefox and Febe (Firefox configuration backup).

As usual, during the installation process, I started with the VFAT32 boot partition and the pointer converted to a busy ball that never seems to finish. I quit a couple of times, then started with the other partitions, as I have done before. I don't know why, but it works this way, for this laptop.

There was no option to select "Use as", select "EFI boot partition".
This may be due to having booted into Legacy BIOS mode.

I had to select "Use as" vFAT32 file system, Size: 436 MB
I had to manually set the mount point to: /boot/efi

So, that leaves me much more capable with the installer, than before.

There are two issues that I am a little confused on, though I may now have a better capacity for thinking it through.

I wanted to move the data files to a separate, vFAT32 partition, to remove any potential conflict with the settings stored in the home folder. These would be Documents, Music, Pictures, etc.

The other is to get this current installation booting into EFI mode.
Would it make sense to uninstall grub, then re-install grub-efi?

I used the following command once before, and it worked well. But not since that time, as I have been unable to boot in EFI mode.
sudo apt-get update;sudo apt-get install grub-efi grub-efi-amd64 grub-efi-amd64-bin
sudo update-grub

The /boot/efi folder is empty, but I have saved the files.
I need to know the structure that Mint looks for.
I think it is: boot/efi/EFI/grub/grub.cfg -- but I am not sure.
Once I copy the files to the proper folder, would that be enough to boot into EFI mode?

I have some other things to do and will check back probably tomorrow, unless I get a chance late, late tonight.

Thanks again, Dereck.
You have really helped me along with the learning curve.

[rbmorse]

Several attempts to boot in the normal way and with all EFI option, resulted in a black screen with some back lighting

Do you recall if there might have been disk activity even though the screen was blank? If so, and if you have occasion to try the fresh installation again, you might let it run (it could take quite awhile). On my system, an ASUS motherboard-based PC with an nVidia video card, the installer uses an inappropriate video mode for my display and the screen will be blank until the kernel loads and set the proper video mode. As I said, it takes a couple of minutes.

If that is the problem, you can avoid this by using the option "nomodeset" with the installer...but I'm embarrassed to admit that I can't remember how to do it. (maybe: Press and hold the left shift key after POST completes and as soon as the installer starts from optical/flash media?)

[Resistor]

Hi, rbmorse.

This has been a problem off and on, for quite a while.

There is disk activity in the beginning, but it goes quiet, after a time.
Today, I took a smoke break and came back to find the disk quiet and the black screen with a little back lighting. There is no response to anything from the keyboard, other than ctrl-alt-del.

There is one of the grub files where that can be changed.
I was poking around the grub files, but decided to wait for help.
I've demonstrated a capacity to corrupt things, so I want to get it right, this time.

Thanks for your input.

[Derek_S]

I am now into the new installation, running in Legacy BIOS mode.

There was no option to select "Use as", select "EFI boot partition".
This may be due to having booted into Legacy BIOS mode.

Hello Resistor - This is the cause of your problems. In order to install the OS to use EFI boot, you must boot your installation media with EFI boot enabled in the system BIOS. This is exactly why you cannot set the mount point of the FAT32 partition correctly, to "EFI boot partition". It also means that the wrong files will be used when grub is installed. The files needed for MBR boot will be installed in grub, not the files needed for EFI boot. And on top of all that, your etc/fstab file will either be lacking an entry for mounting the EFI boot partition, or it will be incorrect.

I know that you feel that using EFI boot is the way to go. But it's causing you a world of grief. Sometimes simpler is better. Why don't you consider trying MBR boot? Just because your BIOS has the option to use EFI boot doesn't mean you must use it. In order to do this, you'll have to make a few changes.

1.) Set your BIOS to use Legacy boot (which you've already been doing).

2.) Boot into a live session from your installation media. Open Gparted, and create a ms-dos partition table on both drives. This will enabled you to use MBR boot. (You cannot use GPT.)

3.) You only need three partitions. On the 32GB SSD, create one primary partition for root. Make it 20480MB(20GB) in size. Format it ext4, and check to see that it's aligned to MiB, not cylinder. On the 500GB WD drive, do as you did before. Make a primary partition for swap. Make it equal in size to your system memory and format it Linux Swap. Then use the rest of the drive for home. Make it a primary partition and format it ext4.

4.) When you do the installation, there is one very important difference. When you get to "Device for Bootloader Installation", select the SSD drive, which should be either sda, sdb, or sdc. Information from using Gparted and the installer's partition table will tell you this. DO NOT include any numbers, or it will install grub to a partition and not the MBR area of the SSD disk. Understand? Just use sda, sdb, or sdc, whatever one is assigned to the SSD.

[Resistor]

Hi, Derek.

Sorry to be such a pain in the derriere. Usually, I do not have the time, but I do, at the moment. So, I'm learning all I can, while I can. It is a matter of suffering the grief now, or later, when time may be more limited.

I was able to set and mount the FAT32 partition.
It had to be done manually and after the other mount points were set.

I understand your explanation for the need to boot into EFI mode.
I just have no options and no control over forcing the mode.

The fstab file seems to look good:
# /boot/efi was on /dev/sdb1 during installation
UUID=B368-FF99 /boot/efi vfat utf8,umask=007,gid=46 0 1

I also have another line to automatically mount the EFI file system:
I just don't know if the entry is in correct form, etc.
# To automatically mount EFI file system:
none /sys/firmware/efi/efivars efivarfs optional 0 0

I know the computer works well, in EFI mode. I've somehow managed to alternate between EFI, BIOS and back, again.
It has to be a matter of having the right boot files in the right location and having grub recognize those files.

I did it once before, running from BIOS mode:
# grub-efi_2.02~beta2-9ubuntu1_amd64.deb
sudo apt-get update;sudo apt-get install grub-efi grub-efi-amd64 grub-efi-amd64-bin
sudo update-grub

The computer booted into EFI mode and worked well.
My mistake was an attempt to install Wicd and remove Network Manager.

I'll experiment with manually placing the efi boot files and updating grub to grub-efi.

I'm sure there is a way to do it, because I did it before.
I'm beginning to suspect that the efi folders were all removed, because the cursor grabbed the main folder and all its contents, and sent to no man's land.

I've really learned a lot from you, not only in this thread, but others as well, and I do appreciate the time you took, to try to help and coach me through this. I have a new power with the installer, of which I was previously unaware.

Thank you, again.