You are not logged in.

#1 2022-09-15 23:22:18

milessummers
Member
Registered: 2014-03-07
Posts: 4

Grub upgrade issues

I have just done an system upgrade and see that ... To use the new features provided in this GRUB update, it is recommended to install it to the MBR or UEFI. Due to potential configuration incompatibilities, it is advised to run both, installation and generation of configuration:
     $ grub-install ...
     $ grub-mkconfig -o /boot/grub/grub.cfg

I have forgotten how I setup my machine for booting but assume it is UEFI as I have a 2G EFI System partition /dev/sda1 and there are modules in /boot/grub/x86_64-efi/
It seems that grubx64.efi is currently in /boot/EFI/arch_grub/

Should my commands be

grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id=arch_grub
grub-mkconfig -o /boot/grub/grub.cfg

Offline

#2 2022-09-16 01:23:55

kermit63
Member
Registered: 2018-07-04
Posts: 111

Re: Grub upgrade issues

Please post the output of lsblk and contents of /etc/fstab.

Offline

#3 2022-09-16 03:00:44

milessummers
Member
Registered: 2014-03-07
Posts: 4

Re: Grub upgrade issues

$lsblk
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda      8:0    0 465.8G  0 disk
├─sda1   8:1    0     2G  0 part /boot
├─sda2   8:2    0    16G  0 part [SWAP]
└─sda3   8:3    0 447.8G  0 part /
sr0     11:0    1  1024M  0 rom

#
# /etc/fstab: static file system information
#
# <file system> <dir>   <type>  <options>       <dump>  <pass>
# /dev/sda3
UUID=5e5b98ca-ef2b-4052-80c3-b25ee8d4713d       /               ext4            rw,relatime,data=ordered        0 1

# /dev/sda1
UUID=7356-13C4          /boot           vfat            rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro    0 2

# /dev/sda2
UUID=62a82645-ea8f-4665-99c7-e1d50581dd1d       none            swap            defaults        0 0

Offline

#4 2022-09-16 03:26:03

kermit63
Member
Registered: 2018-07-04
Posts: 111

Re: Grub upgrade issues

Your grub-install and grub-mkconfig commands look fine.

Is arch-grub your existing bootloader-id? If so, you may want to use a different name to preserve the old efi entry in case something goes wrong.

After executing the 2 commands, run efibootmgr to verify that a new efi entry is indeed created and the boot order is to your liking. You can then use efibootmgr to remove the old entry later.

Offline

#5 2022-09-21 08:32:48

funkaddict
Member
Registered: 2018-08-13
Posts: 99

Re: Grub upgrade issues

Hi there,

I have similar issue. Thus I gonna add my question to this thread. I am also not sure after years, how I initially configured my system. In order to make sure I don't update it and make it unbootable... I would like to ask you for advice in advance.

I am running a dualboot Arch/Win10. I according to pacman grub is not installed. So I guess, I am using another bootloader and just can proceed the update?

$ lsblk
NAME          MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINTS
nvme2n1       259:0    0 931.5G  0 disk  
|-nvme2n1p1   259:2    0   512M  0 part  /boot
|-nvme2n1p2   259:3    0   800G  0 part  
| `-cryptroot 254:0    0   800G  0 crypt /
|-nvme2n1p3   259:6    0    32G  0 part  [SWAP]
`-nvme2n1p4   259:7    0    99G  0 part  /home/user/...
nvme0n1       259:1    0   1.8T  0 disk  
|-nvme0n1p1   259:4    0   1.7T  0 part  /home/user/...
`-nvme0n1p2   259:5    0  93.1G  0 part  /home/user/...
nvme1n1       259:8    0 238.5G  0 disk  
|-nvme1n1p1   259:9    0    16M  0 part  
|-nvme1n1p2   259:10   0 208.6G  0 part  
|-nvme1n1p3   259:11   0   546M  0 part  
`-nvme1n1p4   259:12   0  29.3G  0 part  

fstab:

# <file system> <dir> <type> <options> <dump> <pass>
# /dev/mapper/cryptroot
UUID=4a65ee7e-4377-422d-8013-189d7e36d024	/         	ext4      	rw,relatime	0 1

# /dev/nvme0n1p1
UUID=55F8-39A1      	/boot     	vfat      	rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro	0 2

# /dev/nvme0n1p3
UUID=415c9f6b-b2df-4ea3-bce3-94c90546024b	none      	swap      	defaults  	0 0

# /dev/nvme0n1p4 (not encrypted)
UUID=dc5241fe-6c49-42fb-91fd-d1ebaf1b6bb7	/mountpath	ext4	rw,relatime	0 2

# /dev/nvme0n1p1 (not encrypted)
UUID=0e37062c-940c-41a9-9c5f-6660b23ec054	/mountpath	ext4	rw,relatime	0 2

# /dev/nvme0n1p2 (not encrypted)
UUID=532587C90D1525BF				/mountpath  ntfs-3g	uid=blabla,gid=users,umask=0022	0 0

Thank you!

Offline

#6 2022-09-21 09:07:46

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 17,032

Re: Grub upgrade issues

On an Arch system a plain update will not and never has rendered your system unbootable unless you actively run grub-mkconfig you won't have an issue.

As for the answer on how this is set up, based on that fstab, look at the contents of your /boot (... and the output of efibootmgr -uv if that contains grub directories/EFI binaries/NVRAM entries for GRUB). you'd have to rerun the two commands as suggested in the OP by milessummer

Last edited by V1del (2022-09-21 09:08:12)

Offline

#7 2022-09-21 09:51:23

funkaddict
Member
Registered: 2018-08-13
Posts: 99

Re: Grub upgrade issues

Thank you for the hint V1del. I remember about the principles of Arch that it wouldn't render a system unbootable without the user to cause it. However, I got a little bit unsure when I read that warning.

I just recognized that it looks like I am using systemd-boot rather than grub. There is the folder /boot/EFI which contains the following folders:
BOOT,Dell,Linux,Microsoft,systemd
Furthermore, /boot/loader contains the a loader.conf and an "entries" folder.

Sorry for confusion. It has been a pretty long time since I did setup this system. Didn't dig in the basement of the system for a while wink

Offline

Board footer

Powered by FluxBB