Boot Issues

Questions about Grub, UEFI,the liveCD and the installer
Forum rules
Before you post please read how to get help
Post Reply
FixMyBootProblem
Level 1
Level 1
Posts: 9
Joined: Thu May 18, 2017 10:49 pm

Boot Issues

Post by FixMyBootProblem »

Hello all.

I've tried searching, reading stickies and trying stuff out in other posts and I've hit a wall.

When I try to run boot repair, I get this message:
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
linux-signed-generic : Depends: linux-headers-generic (= 4.4.0.78.84) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
How do I fix this propertly? I've attempted to burn knoppix and the other boot repair things to USBs but this laptop won't read it.

Before anyone asks me about UEFI or Legacy/CSM- I have no clue. I'll need a step by step.

Also, when I boot up the screen says /boot is missing? When I run this off the USB. Since if I try to boot off HDD I get that message saying something about boot device and enter key.

Thanks in advance. I'm kind of in dire straights. I've tried Zorin and Linux Mint and I have the same issue.

FixMyBootProblem
Level 1
Level 1
Posts: 9
Joined: Thu May 18, 2017 10:49 pm

Re: Boot Issues

Post by FixMyBootProblem »

Code: Select all

Boot Info Script cfd9efe + Boot-Repair extra info      [Boot-Info 26Apr2016]


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

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

sda1: __________________________________________________________________________

    File system:       vfat
    Boot sector type:  FAT32
    Boot sector info:  No errors found in the Boot Parameter Block.
    Operating System: 
    Boot files:        /Boot/bootx64.efi /ubuntu/grubx64.efi
                       /EFI/Boot/bootx64.efi /EFI/ubuntu/MokManager.efi
                       /EFI/ubuntu/grubx64.efi /EFI/ubuntu/shimx64.efi
                       /Microsoft/Boot/bootmgfw.efi
                       /Microsoft/Boot/bootx64.efi
                       /EFI/Microsoft/Boot/bootmgfw.efi
                       /EFI/Microsoft/Boot/bootx64.efi

sda2: __________________________________________________________________________

    File system:       ext2
    Boot sector type:  -
    Boot sector info:
    Operating System: 
    Boot files:        /grub/grub.cfg

sda3: __________________________________________________________________________

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

sdb1: __________________________________________________________________________

    File system:       iso9660
    Boot sector type:  Unknown
    Boot sector info:
    Mounting failed:   mount: /dev/sdb1 is already mounted or /mnt/BootInfo/sdb1 busy

sdb2: __________________________________________________________________________

    File system:       vfat
    Boot sector type:  FAT16
    Boot sector info:  According to the info in the boot sector, sdb2 starts
                       at sector 0. But according to the info from fdisk,
                       sdb2 starts at sector 3522820. According to the info
                       in the boot sector, sdb2 has 0 sectors.
    Mounting failed:   mount: /dev/sdb1 is already mounted or /mnt/BootInfo/sdb1 busy
mount: /dev/sdb2 is already mounted or /mnt/BootInfo/sdb2 busy

mint-vg-root: __________________________________________________________________

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

mint-vg-swap_1: ________________________________________________________________

    File system:       swap
    Boot sector type:  -
    Boot sector info: [/quote]

[quote]chroot /mnt/boot-sav/mapper/mint--vg-root update-grub
Generating grub configuration file ...
File descriptor 9 (/proc/4468/mounts) leaked on vgs invocation. Parent PID 15498: /usr/sbin/grub-probe
File descriptor 63 (pipe:[59049]) leaked on vgs invocation. Parent PID 15498: /usr/sbin/grub-probe
File descriptor 9 (/proc/4468/mounts) leaked on vgs invocation. Parent PID 15498: /usr/sbin/grub-probe
File descriptor 63 (pipe:[59049]) leaked on vgs invocation. Parent PID 15498: /usr/sbin/grub-probe
File descriptor 9 (/proc/4468/mounts) leaked on vgs invocation. Parent PID 15514: /usr/sbin/grub-probe
File descriptor 63 (pipe:[59049]) leaked on vgs invocation. Parent PID 15514: /usr/sbin/grub-probe
File descriptor 9 (/proc/4468/mounts) leaked on vgs invocation. Parent PID 15514: /usr/sbin/grub-probe
File descriptor 63 (pipe:[59049]) leaked on vgs invocation. Parent PID 15514: /usr/sbin/grub-probe
File descriptor 9 (/proc/4468/mounts) leaked on vgs invocation. Parent PID 15529: /usr/sbin/grub-probe
File descriptor 63 (pipe:[59049]) leaked on vgs invocation. Parent PID 15529: /usr/sbin/grub-probe
File descriptor 9 (/proc/4468/mounts) leaked on vgs invocation. Parent PID 15529: /usr/sbin/grub-probe
File descriptor 63 (pipe:[59049]) leaked on vgs invocation. Parent PID 15529: /usr/sbin/grub-probe
File descriptor 9 (/proc/4468/mounts) leaked on vgs invocation. Parent PID 15545: /usr/sbin/grub-probe
File descriptor 63 (pipe:[59049]) leaked on vgs invocation. Parent PID 15545: /usr/sbin/grub-probe
File descriptor 9 (/proc/4468/mounts) leaked on vgs invocation. Parent PID 15545: /usr/sbin/grub-probe
File descriptor 63 (pipe:[59049]) leaked on vgs invocation. Parent PID 15545: /usr/sbin/grub-probe
File descriptor 9 (/proc/4468/mounts) leaked on vgs invocation. Parent PID 15615: /usr/sbin/grub-probe
File descriptor 63 (pipe:[59049]) leaked on vgs invocation. Parent PID 15615: /usr/sbin/grub-probe
File descriptor 9 (/proc/4468/mounts) leaked on vgs invocation. Parent PID 15615: /usr/sbin/grub-probe
File descriptor 63 (pipe:[59049]) leaked on vgs invocation. Parent PID 15615: /usr/sbin/grub-probe
Found linux image: /boot/vmlinuz-4.4.0-53-generic
Found initrd image: /boot/initrd.img-4.4.0-53-generic
File descriptor 9 (/proc/4468/mounts) leaked on vgs invocation. Parent PID 15913: /usr/sbin/grub-probe
File descriptor 63 (pipe:[59049]) leaked on vgs invocation. Parent PID 15913: /usr/sbin/grub-probe
File descriptor 9 (/proc/4468/mounts) leaked on vgs invocation. Parent PID 15913: /usr/sbin/grub-probe
File descriptor 63 (pipe:[59049]) leaked on vgs invocation. Parent PID 15913: /usr/sbin/grub-probe
File descriptor 9 (/proc/4468/mounts) leaked on lvs invocation. Parent PID 16025: /bin/sh
File descriptor 63 (pipe:[59049]) leaked on lvs invocation. Parent PID 16025: /bin/sh
grub-probe: error: cannot find a GRUB drive for /dev/sdb1.  Check your device.map.
Adding boot menu entry for EFI firmware configuration
mount: /dev/sdb2 is already mounted or /mnt/boot-sav/sdb2 busy
mount /dev/sdb2 : Error code 32
mount -r /dev/sdb2 /mnt/boot-sav/sdb2
mount: /dev/sdb2 is already mounted or /mnt/boot-sav/sdb2 busy
mount -r /dev/sdb2 : Error code 32

An error occurred during the repair.

You can now reboot your computer.
Please do not forget to make your BIOS boot on sda (500GB) disk!
pastebinit  packages needed
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
W: The repository 'cdrom://Linux Mint 18.1 _Serena_ - Release amd64 20161213 xenial Release' does not have a Release file.
W: Symlinking final file /var/lib/apt/lists/Linux%20Mint%2018.1%20%5fSerena%5f%20-%20Release%20amd64%2020161213_dists_xenial_contrib_binary-amd64_Packages back to /var/lib/apt/lists/partial/Linux%20Mint%2018.1%20%5fSerena%5f%20-%20Release%20amd64%2020161213_dists_xenial_contrib_binary-amd64_Packages.xz failed - pkgAcqIndex::StageDownloadDone (17: File exists)
W: Symlinking final file /var/lib/apt/lists/Linux%20Mint%2018.1%20%5fSerena%5f%20-%20Release%20amd64%2020161213_dists_xenial_main_binary-amd64_Packages back to /var/lib/apt/lists/partial/Linux%20Mint%2018.1%20%5fSerena%5f%20-%20Release%20amd64%2020161213_dists_xenial_main_binary-amd64_Packages.xz failed - pkgAcqIndex::StageDownloadDone (17: File exists)
W: Symlinking final file /var/lib/apt/lists/Linux%20Mint%2018.1%20%5fSerena%5f%20-%20Release%20amd64%2020161213_dists_xenial_non-free_binary-amd64_Packages back to /var/lib/apt/lists/partial/Linux%20Mint%2018.1%20%5fSerena%5f%20-%20Release%20amd64%2020161213_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.1%20%5fSerena%5f%20-%20Release%20amd64%2020161213_dists_xenial_contrib_binary-amd64_Packages back to /var/lib/apt/lists/partial/Linux%20Mint%2018.1%20%5fSerena%5f%20-%20Release%20amd64%2020161213_dists_xenial_contrib_binary-amd64_Packages.bz2 failed - pkgAcqIndex::StageDownloadDone (17: File exists)
W: Symlinking final file /var/lib/apt/lists/Linux%20Mint%2018.1%20%5fSerena%5f%20-%20Release%20amd64%2020161213_dists_xenial_main_binary-amd64_Packages back to /var/lib/apt/lists/partial/Linux%20Mint%2018.1%20%5fSerena%5f%20-%20Release%20amd64%2020161213_dists_xenial_main_binary-amd64_Packages.bz2 failed - pkgAcqIndex::StageDownloadDone (17: File exists)
W: Symlinking final file /var/lib/apt/lists/Linux%20Mint%2018.1%20%5fSerena%5f%20-%20Release%20amd64%2020161213_dists_xenial_non-free_binary-amd64_Packages back to /var/lib/apt/lists/partial/Linux%20Mint%2018.1%20%5fSerena%5f%20-%20Release%20amd64%2020161213_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.1%20%5fSerena%5f%20-%20Release%20amd64%2020161213_dists_xenial_contrib_binary-amd64_Packages back to /var/lib/apt/lists/partial/Linux%20Mint%2018.1%20%5fSerena%5f%20-%20Release%20amd64%2020161213_dists_xenial_contrib_binary-amd64_Packages.lzma failed - pkgAcqIndex::StageDownloadDone (17: File exists)
W: Symlinking final file /var/lib/apt/lists/Linux%20Mint%2018.1%20%5fSerena%5f%20-%20Release%20amd64%2020161213_dists_xenial_main_binary-amd64_Packages back to /var/lib/apt/lists/partial/Linux%20Mint%2018.1%20%5fSerena%5f%20-%20Release%20amd64%2020161213_dists_xenial_main_binary-amd64_Packages.lzma failed - pkgAcqIndex::StageDownloadDone (17: File exists)
W: Symlinking final file /var/lib/apt/lists/Linux%20Mint%2018.1%20%5fSerena%5f%20-%20Release%20amd64%2020161213_dists_xenial_non-free_binary-amd64_Packages back to /var/lib/apt/lists/partial/Linux%20Mint%2018.1%20%5fSerena%5f%20-%20Release%20amd64%2020161213_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.1%20%5fSerena%5f%20-%20Release%20amd64%2020161213_dists_xenial_contrib_binary-amd64_Packages back to /var/lib/apt/lists/partial/Linux%20Mint%2018.1%20%5fSerena%5f%20-%20Release%20amd64%2020161213_dists_xenial_contrib_binary-amd64_Packages.gz failed - pkgAcqIndex::StageDownloadDone (17: File exists)
W: Symlinking final file /var/lib/apt/lists/Linux%20Mint%2018.1%20%5fSerena%5f%20-%20Release%20amd64%2020161213_dists_xenial_main_binary-amd64_Packages back to /var/lib/apt/lists/partial/Linux%20Mint%2018.1%20%5fSerena%5f%20-%20Release%20amd64%2020161213_dists_xenial_main_binary-amd64_Packages.gz failed - pkgAcqIndex::StageDownloadDone (17: File exists)
W: Symlinking final file /var/lib/apt/lists/Linux%20Mint%2018.1%20%5fSerena%5f%20-%20Release%20amd64%2020161213_dists_xenial_non-free_binary-amd64_Packages back to /var/lib/apt/lists/partial/Linux%20Mint%2018.1%20%5fSerena%5f%20-%20Release%20amd64%2020161213_dists_xenial_non-free_binary-amd64_Packages.gz failed - pkgAcqIndex::StageDownloadDone (17: File exists)
E: Failed to fetch cdrom://Linux Mint 18.1 _Serena_ - Release amd64 20161213/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.
W: --force-yes is deprecated, use one of the options starting with --allow instead.
Last edited by FixMyBootProblem on Sat May 20, 2017 7:48 pm, edited 1 time in total.

User avatar
gold_finger
Level 9
Level 9
Posts: 2886
Joined: Mon Mar 11, 2013 11:39 pm

Re: Boot Issues

Post by gold_finger »

Looks like you've installed a dual-boot with Windows -- is that correct? (What version of Windows is on the machine?)

What was the boot issue you were trying to solve with Boot-Repair?

Is that boot issue something that happened immediately after installing Mint, or is it something that happened later, after a period of time (days/weeks) had passed?

Before attempting anymore boot repairs, boot computer with your live Mint install DVD/USB, open a terminal and post back with the output of these commands so we can see exactly what we're dealing with:

Code: Select all

ls /sys/firmware
sudo parted --list
inxi -b
Follow directions in this post to paste back the output of those commands here to the forum.
Please add [SOLVED] to your thread if a solution is found. Go to your first post in the thread, hit "Edit" button and add [SOLVED] to the title of the post.

How To Format Your Forum Posts.

Try Linux Beginner Search Engine for Linux questions.

FixMyBootProblem
Level 1
Level 1
Posts: 9
Joined: Thu May 18, 2017 10:49 pm

Re: Boot Issues

Post by FixMyBootProblem »

This machine USED to have Windows 10. I foolishly attempted to install Zorin OS 12 as a fresh overwrite of Windows. I didn't like Zorin so much but Mint looks better.

Code: Select all

mint@mint ~ $ ls /sys/firmware
acpi  dmi  efi  memmap

Code: Select all

mint@mint ~ $ sudo parted --list
Model: ATA TOSHIBA MQ01ABF0 (scsi)
Disk /dev/sda: 500GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size   File system  Name                  Flags
 1      1049kB  538MB   537MB  fat32        EFI System Partition  boot, esp
 2      538MB   1050MB  512MB  ext2
 3      1050MB  500GB   499GB                                     lvm


Warning: The driver descriptor says the physical block size is 2048 bytes, but
Linux says it is 512 bytes.
Ignore/Cancel? ignore                                                     
Model: Generic Flash Disk (scsi)
Disk /dev/sdb: 16.4GB
Sector size (logical/physical): 2048B/512B
Partition Table: mac
Disk Flags: 

Number  Start   End     Size    File system  Name   Flags
 1      2048B   6143B   4096B                Apple
 2      1804MB  1806MB  2425kB               EFI


Model: Linux device-mapper (linear) (dm)
Disk /dev/mapper/mint--vg-root: 495GB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Disk Flags: 

Number  Start  End    Size   File system  Flags
 1      0.00B  495GB  495GB  ext4


Model: Linux device-mapper (linear) (dm)
Disk /dev/mapper/mint--vg-swap_1: 3691MB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Disk Flags: 

Number  Start  End     Size    File system     Flags
 1      0.00B  3691MB  3691MB  linux-swap(v1)

Code: Select all

mint@mint ~ $ inxi -b
System:    Host: mint Kernel: 4.4.0-53-generic x86_64 (64 bit)
           Desktop: Cinnamon 3.2.6  Distro: Linux Mint 18.1 Serena
Machine:   System: TOSHIBA product: Satellite C55D-B v: PSCN4U-00T019
           Mobo: TOSHIBA model: ZBWAE v: 1.00
           Bios: TOSHIBA v: 1.30 date: 06/06/2014
CPU:       Quad core AMD A8-6410 APU with AMD Radeon R5 Graphics (-MCP-)
           speed/max: 1000/2000 MHz
Graphics:  Card: Advanced Micro Devices [AMD/ATI] Mullins [Radeon R4/R5 Graphics]
           Display Server: X.Org 1.18.4 drivers: ati,radeon (unloaded: fbdev,vesa)
           Resolution: 1366x768@60.02hz
           GLX Renderer: Gallium 0.4 on AMD MULLINS (DRM 2.43.0, LLVM 3.8.0)
           GLX Version: 3.0 Mesa 11.2.0
Network:   Card-1: Realtek RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller
           driver: r8169
           Card-2: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter
           driver: ath9k
Drives:    HDD Total Size: NA (-)
Info:      Processes: 193 Uptime: 11 min Memory: 925.2/3382.8MB
           Client: Shell (bash) inxi: 2.2.35 

User avatar
gold_finger
Level 9
Level 9
Posts: 2886
Joined: Mon Mar 11, 2013 11:39 pm

Re: Boot Issues

Post by gold_finger »

gold_finger wrote:What was the boot issue you were trying to solve with Boot-Repair?

Is that boot issue something that happened immediately after installing Mint, or is it something that happened later, after a period of time (days/weeks) had passed?
Please answer above questions.

Also answer the following:

Do you have data on computer that needs to be saved in the event you need to do a re-install of Mint?

Is there a specific reason you chose to install using LVM vs. just regular partitioning?
Please add [SOLVED] to your thread if a solution is found. Go to your first post in the thread, hit "Edit" button and add [SOLVED] to the title of the post.

How To Format Your Forum Posts.

Try Linux Beginner Search Engine for Linux questions.

FixMyBootProblem
Level 1
Level 1
Posts: 9
Joined: Thu May 18, 2017 10:49 pm

Re: Boot Issues

Post by FixMyBootProblem »

gold_finger wrote:
gold_finger wrote:What was the boot issue you were trying to solve with Boot-Repair?
When I tried to boot up after installs of Zorin/Linux Mint, it wouldn't boot, only saying "no bootable device, insert boot device and press any key". Tried boot repair. Tried other boot repair iso USB's, no good.
Is that boot issue something that happened immediately after installing Mint, or is it something that happened later, after a period of time (days/weeks) had passed?
immediately after Zorin (wiped Windows with Zorin install- that's what I get for trusting a buddy saying his USB was good), and immediately after Mint attempts 1 through 3- currently on 3 just running off of USB
Do you have data on computer that needs to be saved in the event you need to do a re-install of Mint?
nope. but could i format the disc and then try again?
Is there a specific reason you chose to install using LVM vs. just regular partitioning?
no. just seeing if it would do anything different. didn't do anything differently, obviously.

User avatar
gold_finger
Level 9
Level 9
Posts: 2886
Joined: Mon Mar 11, 2013 11:39 pm

Re: Boot Issues

Post by gold_finger »

Not sure what the problem is. Possibly the machine has buggy implementation of UEFI firmware and it's trying to boot Windows (which is no longer there). Let's take a look at current boot order setup and try to manually change it if possible.

Boot with Mint DVD/USB, open a terminal and enter this command to confirm that you booted it in UEFI/EFI mode before continuing:

Code: Select all

ls /sys/firmware
If "efi" is shown in output, you're booted properly in that mode and can continue with next command to display current boot order info. (If not, reboot and try to select boot option for USB/DVD that pertains to UEFI.)

Code: Select all

efibootmgr -v
Post back with output of that second command for us to look at.

Also, let us know if you'd like to put Windows 10 back on that computer and have a dual-boot system instead of just a Linux system? If so, do you have access to any other Windows-based computer? (That will make creating an install USB for Windows a bit easier.)

If you do want Windows back on computer, you can do that now and tell it to erase everything on drive. Then you can follow this tutorial to install Mint as a dual-boot with it.

Here is tutorial for creating Windows 10 install USB. (I recommend using option #2 shown there.)
Please add [SOLVED] to your thread if a solution is found. Go to your first post in the thread, hit "Edit" button and add [SOLVED] to the title of the post.

How To Format Your Forum Posts.

Try Linux Beginner Search Engine for Linux questions.

FixMyBootProblem
Level 1
Level 1
Posts: 9
Joined: Thu May 18, 2017 10:49 pm

Re: Boot Issues

Post by FixMyBootProblem »

Code: Select all

$ ls /sys/firmware
acpi  dmi  efi  memmap

Code: Select all

BootCurrent: 0009
Timeout: 0 seconds
BootOrder: 0000,0001,0002,0007,0008,0009
Boot0000* ubuntu	VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
Boot0001* UEFI: IP4 Realtek PCIe FE Family Controller	PciRoot(0x0)/Pci(0x2,0x3)/Pci(0x0,0x0)/MAC(f8a963f10f1e,0)/IPv4(0.0.0.0:0<->0.0.0.0:0,0,0)..BO
Boot0002* UEFI: IP6 Realtek PCIe FE Family Controller	PciRoot(0x0)/Pci(0x2,0x3)/Pci(0x0,0x0)/MAC(f8a963f10f1e,0)/IPv6([::]:<->[::]:,0,0)..BO
Boot0007* UEFI: IP4 Realtek PCIe FE Family Controller	PciRoot(0x0)/Pci(0x2,0x3)/Pci(0x0,0x0)/MAC(f8a963f10f1e,0)/IPv4(0.0.0.0:0<->0.0.0.0:0,0,0)..BO
Boot0008* UEFI: IP6 Realtek PCIe FE Family Controller	PciRoot(0x0)/Pci(0x2,0x3)/Pci(0x0,0x0)/MAC(f8a963f10f1e,0)/IPv6([::]:<->[::]:,0,0)..BO
Boot0009* UEFI: Corsair Voyager 1100	PciRoot(0x0)/Pci(0x12,0x0)/USB(1,0)/USB(2,0)/HD(1,MBR,0x106,0x5d8,0x1300)..BO
PS- I'd much prefer to be windows free. Thanks.

User avatar
gold_finger
Level 9
Level 9
Posts: 2886
Joined: Mon Mar 11, 2013 11:39 pm

Re: Boot Issues

Post by gold_finger »

Well I must admit I was expecting to see that the computer was trying to boot Windows, but that is not the case. "0000" is first in the boot order and that is Ubuntu (Mint). Your second post with output from Boot Repair showed that there were Microsoft files in the EFI System Partition, but they don't appear in the output you just posted for some reason. (Not a problem, just making a note of it.)

At this point, I don't know why it's not booting. Maybe best thing to do is wipe everything out on that drive and start all over. Boot with Mint install USB/DVD and do the following.

First, open a terminal and run command to make sure USB/DVD got booted in UEFI-mode.

Code: Select all

ls /sys/firmware
If you see "efi" in output, you're booted correctly and can continue on below. If not, reboot and try again.

Next, open the GParted program (Menu -> Administration, or System -> GParted).

Use GParted to delete all partitions on the disk. (Select each partition, mark for deletion, then hit "Apply" button to apply the operation.)

Close GParted and run installer.

When you get to "Installation Type" screen, choose the option to use the whole disk. (That's probably the first option.) Choosing that the installer will then do eveything automatically for you as a standard install without LVM -- will make a new ESP (EFI System Partition), a Root partition, and a Swap partition.

Hopefully everything goes alright and system will boot properly.
Please add [SOLVED] to your thread if a solution is found. Go to your first post in the thread, hit "Edit" button and add [SOLVED] to the title of the post.

How To Format Your Forum Posts.

Try Linux Beginner Search Engine for Linux questions.

FixMyBootProblem
Level 1
Level 1
Posts: 9
Joined: Thu May 18, 2017 10:49 pm

Re: Boot Issues

Post by FixMyBootProblem »

Gparted wouldn't allow me to delete sda3?
This machine's firmware has started the installer in UEFI mode but it looks like there may be existing operating systems already installed using "BIOS compatibility mode". If you continue to install Debian in UEFI mode, it might be difficult to reboot the machine into any BIOS-mode operating systems later.

If you wish to install in UEFI mode and don't care about keeping the ability to boot one of the existing systems, you have the option to force that here. If you wish to keep the option to boot an existing operating system, you should choose NOT to force UEFI installation here.
If you continue, the changes listed below will be written to the disks. Otherwise, you will be able to make further changes manually.

The partition tables of the following devices are changed:
SCSI1 (0,0,0) (sda)

The following partitions are going to be formatted:
partition #1 of SCSI1 (0,0,0) (sda) as ESP
partition #2 of SCSI1 (0,0,0) (sda) as ext4
partition #3 of SCSI1 (0,0,0) (sda) as swap
Still not working. Still no /boot and still have insert boot device and press any key if I don't have the USB in place.

With that said. I attempted to format the hard drive and it only shows 466 of 500gb available?

User avatar
gold_finger
Level 9
Level 9
Posts: 2886
Joined: Mon Mar 11, 2013 11:39 pm

Re: Boot Issues

Post by gold_finger »

Not sure what's going on.

Go into UEFI/Bios Settings of computer and make sure it is set to boot in UEFI/EFI mode -- maybe it's booting in Legacy/CSM mode which would cause the problem you're having. You should see some type of message flash on screen immediately after powering on computer telling you what key to hit to get into UEFI settings. Don't know what key will be for yours, but I have an old non-UEFI Toshiba and the key on that is <F2>. Once in Settings Menu, look for a setting dealing with boot mode and set it to UEFI (or UEFI only) if it's not already set that way. Reboot and see if Mint now works (assuming you went ahead and force installed it in UEFI mode, ignoring the warning message you showed in your last post).
Please add [SOLVED] to your thread if a solution is found. Go to your first post in the thread, hit "Edit" button and add [SOLVED] to the title of the post.

How To Format Your Forum Posts.

Try Linux Beginner Search Engine for Linux questions.

FixMyBootProblem
Level 1
Level 1
Posts: 9
Joined: Thu May 18, 2017 10:49 pm

Re: Boot Issues

Post by FixMyBootProblem »

verified UEFI.

still says /boot/ is missing.

should I consider replacing hard drive, or?

User avatar
austin.texas
Level 20
Level 20
Posts: 12054
Joined: Tue Nov 17, 2009 3:57 pm
Location: at /home

Re: Boot Issues

Post by austin.texas »

FixMyBootProblem wrote:Gparted wouldn't allow me to delete sda3?
To delete a swap partition, you have to turn swap off
Right-click on it in Gparted > Swap Off

Anyway, I hate to see someone saddle themselves with a UEFI installation, with it's complications and limitations.
I recommend switching your boot configuration to Legacy/CSM and install that way.
I think that would be far easier than trying to fix a UEFI boot that is not working, and you would have a better (non-UEFI) system as a result.
Use this tutorial.
You already have GPT partitioning, but it would not hurt anything to create a new GPT partition table, anyway, just to have a clean slate to work with.
Mint 18.2 Cinnamon, Quad core AMD A8-3870 with Radeon HD Graphics 6550D, 8GB DDR3, Ralink RT2561/RT61 802.11g PCI
Linux Linx 2018

User avatar
gold_finger
Level 9
Level 9
Posts: 2886
Joined: Mon Mar 11, 2013 11:39 pm

Re: Boot Issues

Post by gold_finger »

FixMyBootProblem wrote:should I consider replacing hard drive, or?
It's most likely not a problem with the hard drive.

Go ahead and try switching boot modes to Legacy/CSM and install that way following tutorial posted by austin.texas.

You'll need to use whatever special keystrokes are necessary to do two things before you install:
  1. Change main boot mode of computer from UEFI to Legacy/Bios/CSM (not sure what exact wording will be).
  2. Change boot mode of Mint USB to Legacy/Bios/CSM -- (make sure the USB is plugged into computer when doing this).
Again, you're machine may have different key combinations for doing that than my old non-UEFI Toshiba, but as an example on mine I hit <F2> to get into main Bios Settings and <F12> brings up the per session Boot Menu for boot devices attached to computer. Use equivalent of my <F2> to change overall computer boot mode and use equivalent of my <F12> to see boot mode choices for the USB install stick (pick which ever choice is shown as non-UEFI for the stick).

After booted with USB, run command again to check boot mode. If "efi" not shown in output, you're correctly booted in Legacy mode and can then follow install steps in tutorial.

Code: Select all

ls /sys/firmware
Please add [SOLVED] to your thread if a solution is found. Go to your first post in the thread, hit "Edit" button and add [SOLVED] to the title of the post.

How To Format Your Forum Posts.

Try Linux Beginner Search Engine for Linux questions.

FixMyBootProblem
Level 1
Level 1
Posts: 9
Joined: Thu May 18, 2017 10:49 pm

Re: Boot Issues

Post by FixMyBootProblem »

austin.texas wrote: Use this tutorial.
.
I got to the "something else" part of the install
I'm getting an error message saying no root file system is defined?

User avatar
austin.texas
Level 20
Level 20
Posts: 12054
Joined: Tue Nov 17, 2009 3:57 pm
Location: at /home

Re: Boot Issues

Post by austin.texas »

FixMyBootProblem wrote:
austin.texas wrote: Use this tutorial.
.
I'm getting an error message saying no root file system is defined?
When you chose the partition you want to be the root partition (the operating system), double-click on it (or click the CHANGE button) then select Mount Point: /
installScreenshot.png
Mint 18.2 Cinnamon, Quad core AMD A8-3870 with Radeon HD Graphics 6550D, 8GB DDR3, Ralink RT2561/RT61 802.11g PCI
Linux Linx 2018

FixMyBootProblem
Level 1
Level 1
Posts: 9
Joined: Thu May 18, 2017 10:49 pm

Re: Boot Issues

Post by FixMyBootProblem »

Well I owe the both of you a beverage of choice.

Thank you

Thank you

Thank you.

I am windows free.

User avatar
austin.texas
Level 20
Level 20
Posts: 12054
Joined: Tue Nov 17, 2009 3:57 pm
Location: at /home

Re: Boot Issues

Post by austin.texas »

FixMyBootProblem wrote:Well I owe the both of you a beverage of choice.
So there is a Cerveza Bohemía Obscura in my future. :D

I am glad you got it worked out !
Please go to your first post, click the EDIT (pencil) icon, and add [SOLVED] to the title, so that others can find solutions.
Mint 18.2 Cinnamon, Quad core AMD A8-3870 with Radeon HD Graphics 6550D, 8GB DDR3, Ralink RT2561/RT61 802.11g PCI
Linux Linx 2018

Post Reply

Return to “Installation & Boot”