LM 19 install fails at grub installation

[bushyiii]

Trying to do an install on a brand new HP laptop. I chose to leave WIN10s alone and share the HDD with LM19. Everything went along fine until the part of the installation where grub was being added. Then I got the message that grub failed and install stopped
What can I do?
.
.

Code: Select all

Model: ATA SAMSUNG MZNLN128 (scsi)
Disk /dev/sda: 128GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name                          Flags
 1      1049kB  274MB   273MB   fat32        EFI system partition          boot, esp
 2      274MB   290MB   16.8MB               Microsoft reserved partition  msftres
 3      290MB   75.3GB  75.0GB  ntfs         Basic data partition          msftdata
 5      75.3GB  127GB   51.7GB  ext4
 4      127GB   128GB   1028MB  ntfs         Basic data partition          hidden, diag

Code: Select all

mint@mint:~$ inxi -Fx
System:    Host: mint Kernel: 4.15.0-20-generic x86_64 bits: 64 gcc: 7.3.0
           Desktop: Cinnamon 3.8.6 (Gtk 3.22.30-1ubuntu1) Distro: Linux Mint 19 Tara
Machine:   Device: laptop System: HP product: HP Laptop 14-df0xxx v: Type1ProductConfigId serial: N/A
           Mobo: HP model: 8544 v: KBC Version 74.22 serial: N/A UEFI: Insyde v: F.14 date: 07/27/2018
Battery    BAT0: charge: 42.1 Wh 100.0% condition: 42.1/42.1 Wh (100%) model: HP Primary status: Full
CPU:       Dual core Intel Core i3-8130U (-MT-MCP-) arch: Kaby Lake rev.10 cache: 4096 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 8832
           clock speeds: max: 3400 MHz 1: 800 MHz 2: 800 MHz 3: 800 MHz 4: 800 MHz
Graphics:  Card: Intel UHD Graphics 620 bus-ID: 00:02.0
           Display Server: x11 (X.Org 1.19.6 ) drivers: modesetting (unloaded: fbdev,vesa)
           Resolution: 1920x1080@60.02hz
           OpenGL: renderer: Mesa DRI Intel UHD Graphics 620 (Kabylake GT2)
           version: 4.5 Mesa 18.0.0-rc5 Direct Render: Yes
Audio:     Card Intel Sunrise Point-LP HD Audio driver: snd_hda_intel bus-ID: 00:1f.3
           Sound: Advanced Linux Sound Architecture v: k4.15.0-20-generic
Network:   Card-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
           driver: r8169 v: 2.3LK-NAPI port: 4000 bus-ID: 01:00.0
           IF: enp1s0 state: up speed: 1000 Mbps duplex: full mac: 84:a9:3e:ad:b7:e0
           Card-2: Realtek Device b822 port: 3000 bus-ID: 02:00.0
           IF: N/A state: N/A speed: N/A duplex: N/A mac: N/A
Drives:    HDD Total Size: NA (-)
           ID-1: /dev/sda model: SAMSUNG_MZNLN128 size: 128.0GB temp: 30C
           ID-2: USB /dev/sdb model: Cruzer_Edge size: 64.0GB temp: 0C
Partition: ID-1: / size: 1.9G used: 198M (11%) fs: overlay dev: N/A
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   System Temperatures: cpu: 31.0C mobo: 0.0C
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 213 Uptime: 34 min Memory: 1260.0/3828.6MB Init: systemd runlevel: 5 Gcc sys: 7.3.0
           Client: Shell (bash 4.4.191) inxi: 2.3.56 

[redlined]

hi bushyiii!

I'm new to linux, however this made me curious. Please do not consider this as advice (I have little to no experience shared here) but it may help resolve the issue for you. If not a solution then others in forum with experience will likely be along shortly to troubleshoot and fix this issue.

Have you disabled "secure boot" in UEFI (Bios settings)

There are work-arounds to keeping secure boot enabled but complicated and secure boot is little protection for anything except booting from other OS that originally shipped with system. Basically secure boot is designed to interfere or prevent Grub installing as the bootloader because it is not a signed fingerprint stored in firmware.. Win10 may further complicate things if it gets one of them big spring/fall updates as it overwrites your bootloader instructions. For this reason disable secure boot and often advice to use legacy mode (Bios) instead of UEFI is often suggested but both may not be doable or even applicable in your case.

edit to add: fyi, your both code boxes you paste info into can be combined using a -d flag, as well it is common to filter IP/MAC address from results (although risk of showing MAC is low/no threat) so -z flag is usually used to remove that info. Your combined command would look like this: inxi -Fxzd

[kukamuumuka]

At first tell the result for the next command

Code: Select all

inxi -po | grep sd ; sudo efibootmgr

See also: viewtopic.php?f=60&t=97221

[bushyiii]

mint@mint:~$ inxi -po | grep sd ; sudo efibootmgr
Unmounted: ID-1: /dev/sda1 size: 0.27G fs: FAT (32 bit) label: N/A uuid: 009F-511D
ID-2: /dev/sda2 size: 0.02G label: N/A uuid: N/A
ID-3: /dev/sda3 size: 75.00G fs: NTFS label: Windows uuid: 8662302C623022FB
ID-4: /dev/sda4 size: 1.03G fs: NTFS label: Windows RE tools uuid: 6AE05455E0542999
ID-5: /dev/sda5 size: 51.71G fs: ext4 label: N/A uuid: db0a5eb7-ceba-4daa-a5c7-ad1ee88f2a38
ID-6: /dev/sdb1 size: 1.94G
ID-7: /dev/sdb2 size: 0.00G fs: FAT (12 bit) label: N/A uuid: 044E-AC17
BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 2001,0001,3001,0002,2002,2004
Boot0000* USB Hard Drive (UEFI) - SanDisk Cruzer Edge (SanDisk Cruzer Edge)
Boot0001* Windows Boot Manager
Boot0002* ubuntu
Boot2001* EFI USB Device
Boot2002* EFI DVD/CDROM
Boot3001* Internal Hard Disk or Solid State Disk

[kukamuumuka]

Run installer without installing Grub and install rEFInd.

Code: Select all

ubiquity -b

viewtopic.php?f=46&t=256244&p=1383522&h ... d#p1383522

[bushyiii]

Two questions, it seems like most everything is already on the LM 19 partition, if I rerun the installer does it pick up where the failure occurred or do I tell the installer to re-install using the LM 19 partition.

When do I enter the command "ubiquity -b"?

[bushyiii]

I am reading the link you provided I think it answers my questions.

[kukamuumuka]

Two questions, it seems like most everything is already on the LM 19 partition, if I rerun the installer does it pick up where the failure occurred or do I tell the installer to re-install using the LM 19 partition.

When do I enter the command "ubiquity -b"?

At first via Terminal. ubiquity -b runs installer without bootloader option, so an installation should go well. Use the same partition, but format it before installing.

[bushyiii]

I get an error ubi-partman failed with exit code 10.
I tried looking in syslog but it is extremely long and beyond my ability to comprehend.

I will format the partition again and give it another try and see what happens.

[JeremyB]

Just boot the Live ISO, open terminal and do

Code: Select all

sudo mkdir -p /mnt/boot/efi
sudo mount /dev/sda5 /mnt
sudo mount /dev/sda1 /mnt/boot/efi
for i in /dev /dev/pts /proc /sys /run; do sudo mount -B $i /mnt$i; done
sudo chroot /mnt
sudo apt-get update
sudo apt-get install ubuntu-system-adjustments
apt install --reinstall grub-efi-amd64-signed 
sudo os-prober
sudo update-grub
exit

See if you can use it when rebooting

[bushyiii]

Tried this several times and it keeps failing at this line 'for i in /dev /dev/pts /proc /sys /run; do sudo mount -B $i /mnt$i; done'
The message is mount: /dev: mount(2) system call failed: No such file or directory
mount: /dev/pts: mount(2) system call failed: No such file or directory
mount: /proc: mount(2) system call failed: No such file or directory
mount: /sys: mount(2) system call failed: No such file or directory
mount: /run: mount(2) system call failed: No such file or directory

Am I doing something wrong?

[bushyiii]

I found a typo in my terminal command. I corrected it but there is still a problem:
Here's what I get after I enter 'for i in /dev /dev/pts /proc /sys /run; do sudo mount -B $i /mnt$i; done'
mount: mnt/dev: mount point does not exist
mount: mnt/dev/pts: mount point does not exist
mount: mnt/proc: mount point does not exist
mount: mnt/sys: mount point does not exist
mount: mnt/run: mount point does not exist

[kukamuumuka]

How about if you simply install rEFInd or boot computer using Super Grub 2 CD or USB and then install grub-efi?
viewtopic.php?f=46&t=256244&p=1383522&h ... d#p1383522

[bushyiii]

I have installed rEFInd several times, it does nothing on the reboot. After I install it I enter, sudo mount /dev/sda1 /boot and reboot. The laptop goes directly into WIN10.

[bushyiii]

Still no luck, after following the suggestions on reboot the laptop continues to go directly into WIN10

Here's what I did this time:
booted from a thumb drive using Super Grub 2, within the Super Grub 2 menu I chose to then boot LM19. once LM19 was running I entered the following into the termina w/o any reported errorsl:
sudo mkdir -p /mnt/boot/efi
sudo mount /dev/sda5 /mnt
sudo mount /dev/sda1 /mnt/boot/efi
for i in /dev /dev/pts /proc /sys /run; do sudo mount -B $i /mnt$i; done
sudo chroot /mnt
sudo apt-get update
sudo apt-get install ubuntu-system-adjustments
apt install --reinstall grub-efi-amd64-signed
sudo os-prober
sudo update-grub
exit

[bushyiii]

I tried using a slightly different set of instructions again without success.
I booted LM19 using Super Grub2 USB drive and then entered the following:
sudo -i
mkdir -p /boot/efi/EFI/ubuntu
apt-get install grub-efi grub-efi-amd64
update-grub
sync
reboot

Did several reboots, laptop goes directly into WIN10, grub menu is never displayed.

[JeremyB]

Can you change Boot order in BIOS?

[redlined]

hi bushyiii!

Have you adjusted boot order in bios?

This is last I noticed this thread:

BootOrder: 2001,0001,3001,0002,2002,2004
Boot0000* USB Hard Drive (UEFI) - SanDisk Cruzer Edge (SanDisk Cruzer Edge)
Boot0001* Windows Boot Manager
Boot0002* ubuntu
Boot2001* EFI USB Device
Boot2002* EFI DVD/CDROM
Boot3001* Internal Hard Disk or Solid State Disk

perhaps rearrange the order (something like +/- keys to move up/down, booting to UEFI options via esc, or some fkey to get there). I think it may help get 0002 (ubuntu) considered and more involved before it looks to windows boot manager

edit to add:
if I was a bit more experienced i'd say gmta perhaps better to leave it at:
+1 JeremyB post

Can you change Boot order in BIOS?

[bushyiii]

I will change the boot order and report back

[bushyiii]

In the bios Setup Utility I was able to move every boot device below the OS Boot Manager. Opening this OS Boot Manager show two entries in this order Windows Boot Manager followed by Ubuntu. The order of these entries cannot be changed. So nothing is gained by change the order of the other boot devices.

I found a cumbersome work around. In the OS Boot Manager I set a boot delay of 5 seconds. During a this boot delay I can press ESC to bring up a Startup Menu. F9 allows me to choose UBUNTU. Choosing UBUNTU and then continuing with the boot brings up Grub. Then I can choose LM19 or WIN10.

As an aside Grub show two entries for MAC OS, 32 and 64 bit. This is bogus as MAC is not on this Laptop, it was bought new and the owner isn't technically competent to do anything to his computer other than use a browser of simple office tasks. Grub says the two MAC Os's are pn SDSDB3 which does not exist

Very confusing.