Grub update: no more EOS entry

General system Newbie
1

I dual boot EOS with Windows 7 on a BIOS system on my laptop. After today’s system update, including grub update, I experienced the issue that I could not boot EOS anymore and tried to follow the instructions in the forum: I created a bootable EOS DVD and used arch-chroot to reinstall grub.

When booting my laptop now, grub displays only the Windows 7 entry (on the partition /dev/sda3). The EOS entry is missing and I can not boot EOS (on /dev/sda1). Apparently, EOS is not found anymore. This is the output when doing arch-chroot into my system:

[root@EndeavourOS /]# grub-install --target=i386-pc /dev/sda
Installing for i386-pc platform.
Installation finished. No error reported.
[root@EndeavourOS /]# grub-mkconfig -o /boot/grub/grub.cfg
Generating grub configuration file ...
Found theme: /boot/grub/themes/EndeavourOS/theme.txt
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
Found Windows 7 on /dev/sda3
done

I don’t know what other information could be helpful for troubleshooting. Of course, I will provide any requested information needed.

2

Can we see the output of sudo parted -l

3

Here you go:

[root@EndeavourOS /]# parted -l
Model: ATA SanDisk SDSSDH35 (scsi)
Disk /dev/sda: 512GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size    Type     File system  Flags
 1      1049kB  50.0GB  50.0GB  primary  ext4         boot
 2      50.0GB  170GB   120GB   primary  ntfs
 3      170GB   512GB   342GB   primary  ntfs


Warning: Unable to open /dev/sr0 read-write (Read-only file system).  /dev/sr0
has been opened read-only.
Error: Can't have a partition outside the disk!
Ignore/Cancel?                                                            
Ignore/Cancel? Cancel                                                     
Model: TSSTcorp CDDVDW SN-208BB (scsi)
Disk /dev/sr0: 1944MB
Sector size (logical/physical): 2048B/2048B
Partition Table: unknown
Disk Flags:

Edit: FYI: I am still using arch-chroot from the live DVD. That may be the reason for the warning and error about the /dev/sr0 partition in the bottom lines

4

Looks it’s not seeing your kernel(s).

it should show also something like:

Found linux image: /boot/vmlinuz-linux-zen
Found initrd image: /boot/amd-ucode.img /boot/initramfs-linux-zen.img
Found fallback initrd image(s) in /boot:  amd-ucode.img initramfs-linux-zen-fallback.img

In the chroot check the content of the boot directory.

5

ls this sufficient?

[root@EndeavourOS /]# ls -a /boot
.  ..  amd-ucode.img  grub
6

You have no kernel image in there.

In chroot run:

mkinitcpio -P

and see if they get generated.

Post any and all error message.

7

No, they are not generated:

[root@EndeavourOS /]# mkinitcpio -P
==> ERROR: No presets found in /etc/mkinitcpio.d

EDIT: I have installed the linux kernel and the linux-lts kernel, and I usually boot the linux-lts kernel.

8

First run a full update:

pacman -Syu

Then try (re-) installing some kernels of your choice plus its headers.

For example:

pacman -S linux-lts linux-lts-headers

If all goes well, run the grub-mkconfig command at the end:

grub-mkconfig -o /boot/grub/grub.cfg

9

Thanks a lot for the suggestions. I will do this now and post what happens here afterwards.

1 Like
10

Post from chroot

grep . /etc/fstab
lsblk -f

Do you have /boot on a separate partition?

11

It doesn’t look so.
See parted -l above.

1 Like
12

I updated the system and reinstalled linux-lts and linux-lts-headers. The output is still the following (EOS on /dev/sda1 still missing):

[root@EndeavourOS /]# grub-mkconfig -o /boot/grub/grub.cfg
Generating grub configuration file ...
Found theme: /boot/grub/themes/EndeavourOS/theme.txt
Found linux image: /boot/vmlinuz-linux-lts
Found initrd image: /boot/amd-ucode.img /boot/initramfs-linux-lts.img
Found fallback initrd image(s) in /boot:  amd-ucode.img initramfs-linux-lts-fallback.img
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
Found Windows 7 on /dev/sda3
Adding boot menu entry for UEFI Firmware Settings ...
done

@petsam

[root@EndeavourOS /]# grep . /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>
UUID=7a619db9-b680-41ae-ae48-8f59da7b04da /              ext4    defaults,noatime 0 1
tmpfs                                     /tmp           tmpfs   defaults,noatime,mode=1777 0 0
					 /swapfile none swap	 defaults 0 0
[root@EndeavourOS /]# lsblk -f
NAME   FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
loop0                                         
sda                                           
├─sda1                           21.2G    48% /
├─sda2                                        
└─sda3                                        
sr0

I have no separate boot partition, but boot from the partition that has EOS installed:

[root@EndeavourOS /]# fdisk -l
Disk /dev/sda: 476.94 GiB, 512110190592 bytes, 1000215216 sectors
Disk model: SanDisk SDSSDH35
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x7e5183e4

Device     Boot     Start        End   Sectors   Size Id Type
/dev/sda1  *         2048   97656831  97654784  46.6G 83 Linux
/dev/sda2        97656832  332029951 234373120 111.8G  7 HPFS/NTFS/exFAT
/dev/sda3       332032000 1000214527 668182528 318.6G  7 HPFS/NTFS/exFAT


Disk /dev/loop0: 1.61 GiB, 1724010496 bytes, 3367208 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
13

This looks correct now.
Type exit to quit chroot and reboot your system.

1 Like
14

It is there. Just not labeled :laughing: . Kernel images are from the local system, so it should boot fine now.

1 Like
15

OK, thanks a lot for your replies. I am going to reboot now and check whether I can boot EOS again.

1 Like
16

It has worked. The kernels have been found again, the linux-lts entries are in the grub-menu again and can be booted. Thank you very much, @pebcak and @petsam, for your replies and fast help! You have relieved me from a big worry :slight_smile:

2 Likes
17

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.