/how-do-i-fix-a-grub-problem-associated-with-a-clean-install?noredirect=1#comment624506_352532

Sean Lake

16:24

I won't have access to the machine for about 5 or 6 hours.

Bahamut

hi

Sean Lake

Hello.

Any suggestions for when I have access to the machine again?

Bahamut

Boot Live-session and show gdisk -l /dev/sda and sudo dmidecode -t0 -t1 first. And the /etc/fstab from broken system.

Sean Lake

Thanks. I'll be back as soon as I can get at the machine in question. :)

Bahamut

take your time.

Sean Lake

21:24

mint@mint ~ $ sudo gdisk -l /dev/sda
GPT fdisk (gdisk) version 1.0.1

Partition table scan:
MBR: MBR only
BSD: not present
APM: not present
GPT: not present

***************************************************************
Found invalid GPT and valid MBR; converting MBR to GPT format
in memory.
***************************************************************

Disk /dev/sda: 2930277168 sectors, 1.4 TiB
Logical sector size: 512 bytes
Disk identifier (GUID): 2B88F17C-1345-4532-BEAC-A2AB7B72CBB7
Partition table holds up to 128 entries

mint@mint ~ $ sudo dmidecode -t0 -t1
# dmidecode 3.0
Getting SMBIOS data from sysfs.
SMBIOS 2.7 present.

Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
Vendor: American Megatrends Inc.
Version: 4608
Release Date: 12/24/2013
Address: 0xF0000
Runtime Size: 64 kB
ROM Size: 8192 kB
Characteristics:
PCI is supported
APM is supported
BIOS is upgradeable
BIOS shadowing is allowed
Boot from CD is supported
Selectable boot is supported
BIOS ROM is socketed
EDD is supported
5.25"/1.2 MB floppy services are supported (int 13h)

mint@mint ~ $ cat /etc/fstab
overlay / overlay rw 0 0
tmpfs /tmp tmpfs nosuid,nodev 0 0

Wait, wrong fstab - that's from the LiveDVD

mint@mint ~/temp $ cat 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=e73704c9-a919-48dd-8509-32552514d0c9 / ext4 errors=remount-ro 0 1
# swap was on /dev/sda1 during installation

Bahamut

21:53

Hi, can you also show sudo lsblk -f

And sudo parted -l In your /etc/fstab is no EFI Boot Partition

Sean Lake

mint@mint ~/temp $ sudo lsblk -f
NAME FSTYPE LABEL UUID MOUNTPOINT
sda
├─sda1 swap 878ce59e-cabf-4755-8298-8608cd33d529 [SWAP]
└─sda2 ext4 e73704c9-a919-48dd-8509-32552514d0c9 /home/mint
sdb
├─sdb1 vfat D4C7-060D
├─sdb2
├─sdb3 ntfs 7290DB6A90DB3379
└─sdb4 ntfs C8F8A9AEF8A99AE8
sdc
├─sdc1 ntfs Windows Backup 607B345D41B08C2C
├─sdc2 ntfs Windows Backup 7A86DF1386DECF2F

mint@mint ~/temp $ sudo parted -l
Model: ATA WDC WD1502FAEX-0 (scsi)
Disk /dev/sda: 1500GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:

Number Start End Size Type File system Flags
2 1049kB 1467GB 1467GB primary ext4 boot
1 1468GB 1500GB 32.8GB primary linux-swap(v1)

Model: ATA WDC WD1502FAEX-0 (scsi)
Disk /dev/sdb: 1500GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number Start End Size File system Name Flags

Interesting. The rest of my disks have gpt partition tables. Would that be enough to get it to boot on an EFI system?

Bahamut

22:09

1 1049kB 106MB 105MB fat32 EFI system partition boot, esp

Is Efi partition.

Sean Lake

Ah, I see. And that should be able to boot to the Linux disk in question, right?

Bahamut

chroot sudo mount /dev/sda2 /mnt

sudo mount /dev/sdb1 /mnt/boot/efi

Sean Lake

Wait, that first command was meant to mount /dev/sda2 to /mnt, and then chroot to /mnt?

Bahamut

No, wait 1 sec have your current backup?

Sean Lake

No.

There wasn't any important data on the disk, so I nuked it.

Bahamut

22:14

unsafed data are always unimportant.

Sean Lake

Well, I mounted /dev/sdb1 to /mnt/boot/efi

Bahamut

for dir in /dev /dev/pts /proc /sys /run; do sudo mount --bind $dir /mnt/$dir; done

This mount virtual-filesystem

Sean Lake

Ok.

Bahamut

sudo cp /etc/resolve.conf /mnt/etc/resolve.conf this is for Network-acces

Sean Lake

cp: cannot stat '/etc/resolve.conf': No such file or directory

Bahamut

22:19

Okay, how are you in chat?

Sean Lake

I have it open on my LiveCD (how I'm typing now), and on my laptop.

Odd - I just used less to look at /etc/resolve.conf

Bahamut

With WLAN or Ether?

Sean Lake

sudo cp /etc/resolv.conf /mnt/etc/resolv.conf
cp: '/etc/resolv.conf' and '/mnt/etc/resolv.conf' are the same file

Ethernet.

Is it resolv.conf?

Bahamut

I mußt think

Sean Lake

Take your time. :)

Bahamut

22:30

I often chroot, but I have only WLAN und connect over gnome-network-manager, but you have LAN. Btw. Is secure-boot enabled?

nmcli d and nmcli c

Sean Lake

Secure boot should not be enabled.

mint@mint /mnt $ nmcli d
DEVICE TYPE STATE CONNECTION
eno1 ethernet connected Wired connection 1
lo loopback unmanaged --
mint@mint /mnt $ nmcli c
NAME UUID TYPE DEVICE
Wired connection 1 4d533bdb-ec15-3a64-be8f-23044c1da9d2 802-3-ethernet eno1

Bahamut

sudo chroot /mnt/ /bin/bash

Sean Lake

done

Bahamut

In chroot dpkg -l | egrep 'grub|efi|signed'

Sean Lake

root@mint / # dpkg -l | egrep 'grub|efi|signed'
ii automake 1:1.15-4ubuntu1 all Tool for generating GNU Standards-compliant Makefiles
ii consolekit 0.4.6-5 amd64 framework for defining and tracking users, sessions and seats
ii efibootmgr 0.12-4 amd64 Interact with the EFI Boot Manager

Bahamut

22:47

Your grub is for Bios installation. Not for EFi.

Sean Lake

Sounds like a bug in the installer, to me. How do I fix this?

Bahamut

Gut question. In Live-Session [ -d /sys/firmware/efi ]

Sean Lake

mint@mint ~ $ [ -d /sys/firmware/efi ]
mint@mint ~ $

Bahamut

In chroot ls -al /mnt/boot/efi

Sean Lake

root@mint / # ls -al /mnt/boot/efi
ls: cannot access '/mnt/boot/efi': No such file or directory

Bahamut

23:02

It is a bios-installation. sudo efibootmgr

Sean Lake

in chroot or Live?

Bahamut

Both please.

Sean Lake

mint@mint ~ $ sudo efibootmgr
efibootmgr: EFI variables are not supported on this system.

root@mint / # sudo efibootmgr
sudo: unable to resolve host mint
efibootmgr: EFI variables are not supported on this system.

Bahamut

Can you check your efi if you have legacy-bios-mode enabled. And in which mode is Windows installt?

Sean Lake

Do I do that from the EFI after rebooting?

Nevermind - just googled it.

Bahamut

23:10

For mi its time to go sleeping. it is midnight in my timezone. Good night for now. Untill tomorrow.

Sean Lake

Thanks for all of your help. :)

Bahamut

Or so

so far I coud not help.

Sean Lake

Of course you did - finding out what it is not is a valuable part of the process.

The Windows 10 disk is labeled "UEFI" in the EFI firmware. I'm not sure how else to check.

Transcript for

/how-do-i-fix-a-grub-problem-associat…