You are not logged in.

Pages: 1 2

#1 2023-02-07 17:15:09

Epp
Member
Registered: 2022-07-11
Posts: 101

Arch not in my bootloader(s)

Hello,

Sadly, I messed up my grub.

In a flash I thought grub customizer would be handy for customizing.
After a simple change (making ibt=off as GRUB_CMDLINE_LINUX_DEFAULT), I only had to update grub.

So not needing this grub customizer I removed it by sudo pacman -R grub-customizer

Right after this I updated: sudo pacman -Syu
Not because of the grub action, but just because I knew there were updates for which I always reboot (linux kernel and NVIDIA driver).

There was no grub menu after this.
Booting didn't go further than my bios menu.

After all actions I have at this moment a grub menu that is booting and a systemd menu that is booting.
It's most likely those bootloaders don't have access to the right config files.
The menu's are both almost empty. Only showing Windows (which I have on an other device). My computer was not really dual boot.
Windows was never in my grub menu before on arch. I started Windows by use of my bios settings.

There is no need for Windows in my grub, or systemd boot menu.
But I would love to start Arch again.

Last actions done:

mount /dev/nvme0n1p2 /mnt
mount /dev/nvme0n1p1 /mnt/boot
arch-chroot /mnt
grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id=GRUB
grub-mkconfig -o /boot/grub/grub.cfg

Result:

ubuntu@ubuntu:/boot$ ls -l
total 6895
-rw-r--r-- 1 root root  260489 Mar 11  2022 config-5.15.0-23-generic
drwxr-xr-x 2 root root      58 Mar 26  2022 grub
lrwxrwxrwx 1 root root      28 Mar 26  2022 initrd.img -> initrd.img-5.15.0-23-generic
lrwxrwxrwx 1 root root      28 Mar 26  2022 initrd.img.old -> initrd.img-5.15.0-23-generic
-rw-r--r-- 1 root root  182800 Feb  6  2022 memtest86+.bin
-rw-r--r-- 1 root root  184476 Feb  6  2022 memtest86+.elf
-rw-r--r-- 1 root root  184980 Feb  6  2022 memtest86+_multiboot.bin
-rw------- 1 root root 6246081 Mar 11  2022 System.map-5.15.0-23-generic
lrwxrwxrwx 1 root root      25 Mar 26  2022 vmlinuz -> vmlinuz-5.15.0-23-generic
lrwxrwxrwx 1 root root      25 Mar 26  2022 vmlinuz.old -> vmlinuz-5.15.0-23-generic
ubuntu@ubuntu:/boot/grub$ ls -l
total 2338
-rw-r--r-- 1 root root     712 Mar 26  2022 gfxblacklist.txt
-rw-r--r-- 1 root root 2392289 Mar 26  2022 unicode.pf2

Last edited by Epp (2023-02-07 17:16:18)

Offline

#2 2023-02-07 17:32:12

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 25,257

Re: Arch not in my bootloader(s)

That /boot does not contain an Arch kernel and there's no GRUB config around. Are you sure that's the partition you used to use Arch for? What's your output of lsblk -f ?

Offline

#3 2023-02-07 17:51:55

Epp
Member
Registered: 2022-07-11
Posts: 101

Re: Arch not in my bootloader(s)

Oooww... oops sorry.
Moving too fast and fixing too little.

Those are the Ubuntu folders on the flash drive.
And yes I am ashamed.

ubuntu@ubuntu:/media/ubuntu/.../boot/grub$ lsblk -f
NAME        FSTYPE      FSVER            LABEL                  UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
loop0       squashfs    4.0                                                                                0   100% /rofs
loop1       squashfs    4.0                                                                                0   100% /snap/bare/5
loop2       squashfs    4.0                                                                                0   100% /snap/core20/1376
loop3       squashfs    4.0                                                                                0   100% /snap/firefox/1154
loop4       squashfs    4.0                                                                                0   100% /snap/gnome-3-38-2004/99
loop5       squashfs    4.0                                                                                0   100% /snap/gtk-common-themes/1526
loop6       squashfs    4.0                                                                                0   100% /snap/snap-store/575
loop7       squashfs    4.0                                                                                0   100% /snap/snapd/15177
loop8       squashfs    4.0                                                                                0   100% /snap/snapd-desktop-integration/7               
sdb         iso9660     Joliet Extension Ubuntu 22.04 LTS amd64 2022-03-26-08-25-44-00                              
├─sdb1      iso9660     Joliet Extension Ubuntu 22.04 LTS amd64 2022-03-26-08-25-44-00                     0   100% /cdrom
├─sdb2      vfat        FAT12            ESP                    7C2C-6960                                           
├─sdb3                                                                                                              
└─sdb4      ext4        1.0              writable               d944989c-f848-457e-894c-cb93954c7d17   10.8G     0% /var/crash
                                                                                                                    /var/log
sr0                                                                                                                 
nvme0n1                                                                                                             
├─nvme0n1p1 vfat        FAT32                                   C507-3BE8                                           
└─nvme0n1p2 ext4        1.0                                     7463609a-7666-42cb-a464-a3bf15622874  152.6G    78% /media/ubuntu/7463609a-7666-42cb-a464-a3bf15622874
nvme1n1                                                                                                             
├─nvme1n1p1 ntfs                                                33BE2E260E31512C                                    
└─nvme1n1p2 ntfs                                                9C54025954023714  
ubuntu@ubuntu:/media/ubuntu/.../boot$ ls -l
total 177512
drwxr-xr-x 2 root root     4096 Jul  9  2022 efi
drwxr-xr-x 6 root root     4096 Feb  6 18:14 grub
-rw------- 1 root root 68553085 Feb  6 16:22 initramfs-linux-fallback.img
-rw------- 1 root root 15377078 Feb  6 16:22 initramfs-linux.img
-rw------- 1 root root 61838481 Feb  6 16:22 initramfs-linux-lts-fallback.img
-rw------- 1 root root 14094043 Feb  6 16:22 initramfs-linux-lts.img
-rw-r--r-- 1 root root 11205568 Feb  6 16:22 vmlinuz-linux
-rw-r--r-- 1 root root 10683136 Feb  6 16:22 vmlinuz-linux-lts
ubuntu@ubuntu:/media/ubuntu/.../boot/grub$ ls -l
total 36
drwxr-xr-x 2 root root  4096 Jul  9  2022 fonts
-rw------- 1 root root  5628 Feb  6 18:14 grub.cfg
-rw-r--r-- 1 root root  1024 Jul  9  2022 grubenv
drwxr-xr-x 2 root root  4096 Jul  9  2022 locale
drwxr-xr-x 3 root root  4096 Jul  9  2022 themes
drwxr-xr-x 2 root root 12288 Jul  9  2022 x86_64-efi

The efi folder is empty.

Offline

#4 2023-02-07 18:14:42

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 25,257

Re: Arch not in my bootloader(s)

Content of the grub.cfg and 

file vmlinux-linux
efibootmgr -uv

Offline

#5 2023-02-07 18:31:54

Epp
Member
Registered: 2022-07-11
Posts: 101

Re: Arch not in my bootloader(s)

2 days ago I went over to the LTS kernel.

grub.cfg

#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
insmod part_gpt
insmod part_msdos
if [ -s $prefix/grubenv ]; then
  load_env
fi
if [ "${next_entry}" ] ; then
   set default="${next_entry}"
   set next_entry=
   save_env next_entry
   set boot_once=true
else
   set default="0"
fi

if [ x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
else
  menuentry_id_option=""
fi

export menuentry_id_option

if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z "${boot_once}" ]; then
    saved_entry="${chosen}"
    save_env saved_entry
  fi
}

function load_video {
  if [ x$feature_all_video_module = xy ]; then
    insmod all_video
  else
    insmod efi_gop
    insmod efi_uga
    insmod ieee1275_fb
    insmod vbe
    insmod vga
    insmod video_bochs
    insmod video_cirrus
  fi
}

if [ x$feature_default_font_path = xy ] ; then
   font=unicode
else
insmod part_gpt
insmod ext2
search --no-floppy --fs-uuid --set=root 7463609a-7666-42cb-a464-a3bf15622874
    font="/usr/share/grub/unicode.pf2"
fi

if loadfont $font ; then
  set gfxmode=auto
  load_video
  insmod gfxterm
fi
terminal_input console
terminal_output gfxterm
if [ x$feature_timeout_style = xy ] ; then
  set timeout_style=menu
  set timeout=5
# Fallback normal timeout code in case the timeout_style feature is
# unavailable.
else
  set timeout=5
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/10_linux ###
menuentry 'Arch Linux' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-7463609a-7666-42cb-a464-a3bf15622874' {
	load_video
	set gfxpayload=keep
	insmod gzio
	insmod part_gpt
	insmod ext2
	search --no-floppy --fs-uuid --set=root 7463609a-7666-42cb-a464-a3bf15622874
	echo	'Loading Linux linux-lts ...'
	linux	/boot/vmlinuz-linux-lts root=UUID=7463609a-7666-42cb-a464-a3bf15622874 rw  loglevel=3 ibt=off quiet
	echo	'Loading initial ramdisk ...'
	initrd	/boot/initramfs-linux-lts.img
}
submenu 'Advanced options for Arch Linux' $menuentry_id_option 'gnulinux-advanced-7463609a-7666-42cb-a464-a3bf15622874' {
	menuentry 'Arch Linux, with Linux linux-lts' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-lts-advanced-7463609a-7666-42cb-a464-a3bf15622874' {
		load_video
		set gfxpayload=keep
		insmod gzio
		insmod part_gpt
		insmod ext2
		search --no-floppy --fs-uuid --set=root 7463609a-7666-42cb-a464-a3bf15622874
		echo	'Loading Linux linux-lts ...'
		linux	/boot/vmlinuz-linux-lts root=UUID=7463609a-7666-42cb-a464-a3bf15622874 rw  loglevel=3 ibt=off quiet
		echo	'Loading initial ramdisk ...'
		initrd	/boot/initramfs-linux-lts.img
	}
	menuentry 'Arch Linux, with Linux linux-lts (fallback initramfs)' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-lts-fallback-7463609a-7666-42cb-a464-a3bf15622874' {
		load_video
		set gfxpayload=keep
		insmod gzio
		insmod part_gpt
		insmod ext2
		search --no-floppy --fs-uuid --set=root 7463609a-7666-42cb-a464-a3bf15622874
		echo	'Loading Linux linux-lts ...'
		linux	/boot/vmlinuz-linux-lts root=UUID=7463609a-7666-42cb-a464-a3bf15622874 rw  loglevel=3 ibt=off quiet
		echo	'Loading initial ramdisk ...'
		initrd	/boot/initramfs-linux-lts-fallback.img
	}
	menuentry 'Arch Linux, with Linux linux' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-advanced-7463609a-7666-42cb-a464-a3bf15622874' {
		load_video
		set gfxpayload=keep
		insmod gzio
		insmod part_gpt
		insmod ext2
		search --no-floppy --fs-uuid --set=root 7463609a-7666-42cb-a464-a3bf15622874
		echo	'Loading Linux linux ...'
		linux	/boot/vmlinuz-linux root=UUID=7463609a-7666-42cb-a464-a3bf15622874 rw  loglevel=3 ibt=off quiet
		echo	'Loading initial ramdisk ...'
		initrd	/boot/initramfs-linux.img
	}
	menuentry 'Arch Linux, with Linux linux (fallback initramfs)' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-fallback-7463609a-7666-42cb-a464-a3bf15622874' {
		load_video
		set gfxpayload=keep
		insmod gzio
		insmod part_gpt
		insmod ext2
		search --no-floppy --fs-uuid --set=root 7463609a-7666-42cb-a464-a3bf15622874
		echo	'Loading Linux linux ...'
		linux	/boot/vmlinuz-linux root=UUID=7463609a-7666-42cb-a464-a3bf15622874 rw  loglevel=3 ibt=off quiet
		echo	'Loading initial ramdisk ...'
		initrd	/boot/initramfs-linux-fallback.img
	}
}

### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###

### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/30_uefi-firmware ###
if [ "$grub_platform" = "efi" ]; then
	fwsetup --is-supported
	if [ "$?" = 0 ]; then
		menuentry 'UEFI Firmware Settings' $menuentry_id_option 'uefi-firmware' {
			fwsetup
		}
	fi
fi
### END /etc/grub.d/30_uefi-firmware ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries.  Simply type the
# menu entries you want to add after this comment.  Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###

### BEGIN /etc/grub.d/41_custom ###
if [ -f  ${config_directory}/custom.cfg ]; then
  source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f  $prefix/custom.cfg ]; then
  source $prefix/custom.cfg
fi
### END /etc/grub.d/41_custom ###

efibootmgr -uv

ubuntu@ubuntu:/media/ubuntu/7463609a-7666-42cb-a464-a3bf15622874/boot$ efibootmgr -uv
BootCurrent: 0005
Timeout: 0 seconds
BootOrder: 0005,0001,0000,0002,0004
Boot0000* Windows Boot Manager	HD(1,GPT,e77f2523-0007-4fcf-9c56-c231adc9f6e4,0x800,0x100000)/File(\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI)䥗䑎坏S
Boot0001* GRUB	HD(1,GPT,e77f2523-0007-4fcf-9c56-c231adc9f6e4,0x800,0x100000)/File(\EFI\GRUB\GRUBX64.EFI)
Boot0002* ubuntu	HD(1,GPT,e77f2523-0007-4fcf-9c56-c231adc9f6e4,0x800,0x100000)/File(\EFI\UBUNTU\SHIMX64.EFI)
Boot0004  Linux Boot Manager	HD(1,GPT,e77f2523-0007-4fcf-9c56-c231adc9f6e4,0x800,0x100000)/File(\EFI\SYSTEMD\SYSTEMD-BOOTX64.EFI)
Boot0005* UEFI: SanDisk, Partition 2	PciRoot(0x0)/Pci(0x14,0x0)/USB(7,0)/HD(2,GPT,256c84f8-5a00-480b-bc7d-7c091df019e9,0x660ea4,0x2138)

vmlinuz-linux

ubuntu@ubuntu:/media/ubuntu/7463609a-7666-42cb-a464-a3bf15622874/boot$ file vmlinuz-linux
vmlinuz-linux: Linux kernel x86 boot executable bzImage, version 6.1.9-arch1-2 (linux@archlinux) #1 SMP PREEMPT_DYNAMIC Fri, 03 Feb 2023 18:49:53 +0000, RO-rootFS, swap_dev 0XA, Normal VGA
ubuntu@ubuntu:/media/ubuntu/7463609a-7666-42cb-a464-a3bf15622874/boot$ file vmlinuz-linux-lts
vmlinuz-linux-lts: Linux kernel x86 boot executable bzImage, version 5.15.91-4-lts (linux-lts@archlinux) #1 SMP Fri, 03 Feb 2023 20:22:45 +0000, RO-rootFS, swap_dev 0XA, Normal VGA
ubuntu@ubuntu:/media/ubuntu/7463609a-7666-42cb-a464-a3bf15622874/boot$

Offline

#6 2023-02-07 18:48:37

Head_on_a_Stick
Member
From: The Wirral
Registered: 2014-02-20
Posts: 9,003
Website

Re: Arch not in my bootloader(s)

Please also post the output of

lsblk -no name,partuuid

The output of the `set` command from the GRUB command line would also be useful, take a picture of the screen then upload it to a hosting site and share the URL. Thanks.

Jin, Jîyan, Azadî

Offline

#7 2023-02-07 18:51:05

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 25,257

Re: Arch not in my bootloader(s)

This looks ok, the only thing that's weird is the apparent absence of EFI from the esp (assuming it is mounted...) if you did run these outputs immediately after each other you never mounted your ESP your grub-install command likely failed and what you'd actually want to do is mount nvme0n1p1 to /boot/efi and reinstall your GRUB payload there. If you boot into the GRUB entry it is empty right?

Offline

#8 2023-02-07 18:58:17

Epp
Member
Registered: 2022-07-11
Posts: 101

Re: Arch not in my bootloader(s)

Excuses, Head on, did you notice that I've added the output of lsblk -f already?

I think you mean with 'set', 'setparams'? There is nothing there in 'setparams'. No single param.

Last edited by Epp (2023-02-07 18:59:08)

Offline

#9 2023-02-07 19:01:59

Epp
Member
Registered: 2022-07-11
Posts: 101

Re: Arch not in my bootloader(s)

Hi V1del, no indeed, there is nothing in the setparams.

Offline

#10 2023-02-07 19:12:53

Epp
Member
Registered: 2022-07-11
Posts: 101

Re: Arch not in my bootloader(s)

@Head_on_a_Stick and V1del, it's not exactly true what I've typed above.
The only thing is "fwsetup"

This is all there is:

setparams 'UEFI firmware settings'
                                           fwsetup

Last edited by Epp (2023-02-07 19:16:11)

Offline

#11 2023-02-07 19:18:12

Head_on_a_Stick
Member
From: The Wirral
Registered: 2014-02-20
Posts: 9,003
Website

Re: Arch not in my bootloader(s)

Epp wrote:

Excuses, Head on, did you notice that I've added the output of lsblk -f already?

Yes but my requested command supplies different information. You seem to have two EFI system partitions and the PARTUUIDs will show which one is being loaded by the NVRAM boot entries.

Epp wrote:

I think you mean with 'set', 'setparams'?

No. I mean `set`. Press 'c' at the GRUB menu to bring up the command line from which to run `set`.

Having said that I do agree with V1del's suggestion to mount /dev/nvme0n1p1 under /boot/efi/ instead of /boot/. Having /boot/ on a FAT filesystem is sub-optimal IMO.

Jin, Jîyan, Azadî

Offline

#12 2023-02-07 19:50:07

Epp
Member
Registered: 2022-07-11
Posts: 101

Re: Arch not in my bootloader(s)

aha, ok
https://postimg.cc/BLQcvHkj

trying to mount /boot/efi/ gives "mount point does not exists". Tried all sorts of combinations.

ubuntu@ubuntu:~$ lsblk -f
NAME FSTYPE FSVER LABEL UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
loop0
     squash 4.0                                                    0   100% /rofs
loop1
     squash 4.0                                                    0   100% /snap/core20/1376
loop2
     squash 4.0                                                    0   100% /snap/bare/5
loop3
     squash 4.0                                                    0   100% /snap/firefox/1154
loop4
     squash 4.0                                                    0   100% /snap/gnome-3-38-2004/99
loop5
     squash 4.0                                                    0   100% /snap/gtk-common-themes/1526
loop6
     squash 4.0                                                    0   100% /snap/snap-store/575
loop7
     squash 4.0                                                    0   100% /snap/snapd/15177
loop8
     squash 4.0                                                    0   100% /snap/snapd-desktop-integration/7
sdb  iso966 Jolie Ubuntu 22.04 LTS amd64
│                       2022-03-26-08-25-44-00                              
├─sdb1
│    iso966 Jolie Ubuntu 22.04 LTS amd64
│                       2022-03-26-08-25-44-00                     0   100% /cdrom
├─sdb2
│    vfat   FAT12 ESP   7C2C-6960                                           
├─sdb3
│                                                                           
└─sdb4
     ext4   1.0   writable
                        d944989c-f848-457e-894c-cb93954c7d17   10.8G     0% /var/crash
                                                                            /var/log
sr0                                                                         
nvme0n1
│                                                                           
├─nvme0n1p1
│    vfat   FAT32       C507-3BE8                                           
└─nvme0n1p2
     ext4   1.0         7463609a-7666-42cb-a464-a3bf15622874  152.6G    78% /media/ubuntu/7463609a-7666-42cb-a464-a3bf15622874
nvme1n1
│                                                                           
├─nvme1n1p1
│    ntfs               33BE2E260E31512C                                    
└─nvme1n1p2
     ntfs               9C54025954023714

Offline

#13 2023-02-07 20:02:26

Head_on_a_Stick
Member
From: The Wirral
Registered: 2014-02-20
Posts: 9,003
Website

Re: Arch not in my bootloader(s)

Epp wrote:

I think GRUB's loading /grub/grub.cfg on /dev/nvme0n1p1. Not that it matters because /boot/efi/ is a better mountpoint for the ESP and we'll be reinstalling core.img again anyway.

Epp wrote:

trying to mount /boot/efi/ gives "mount point does not exists". Tried all sorts of combinations

You should post those combinations then. Did you create /boot/efi/ and mount the ESP under it? We need to see the exact, full commands.

And why do you keep posting 'lsblk -f' instead of the requested output? hmm

Jin, Jîyan, Azadî

Offline

#14 2023-02-07 20:21:29

Epp
Member
Registered: 2022-07-11
Posts: 101

Re: Arch not in my bootloader(s)

Doesn't this (from earlier post) show the folder efi is there (looks like since July)?

ubuntu@ubuntu:/media/ubuntu/.../boot$ ls -l
total 177512
drwxr-xr-x 2 root root     4096 Jul  9  2022 efi
drwxr-xr-x 6 root root     4096 Feb  6 18:14 grub

I am trying the mounting with the Arch iso. From there I can not copy and paste.

From typing on this webpage:

mount /dev/nvme0n1p1 /boot/efi
mount /dev/nvme0n1p1 /boot/efi/
mount /dev/nvme0n1p1 /mnt/boot/efi
mount /dev/nvme0n1p1 /boot/efi

As you can see. I don't understand much of it.
Meaning the syntax.

ubuntu@ubuntu:~$ lsblk -no name,partuuid
loop0       
loop1       
loop2       
loop3       
loop4       
loop5       
loop6       
loop7       
loop8       
sdb         
├─sdb1      256c84f8-5a00-480b-bc7e-7c091df019e9
├─sdb2      256c84f8-5a00-480b-bc7d-7c091df019e9
├─sdb3      256c84f8-5a00-480b-bc7c-7c091df019e9
└─sdb4      85d07d67-ad88-ca4a-8469-5df292f5e8ad
sr0         
nvme0n1     
├─nvme0n1p1 e77f2523-0007-4fcf-9c56-c231adc9f6e4
└─nvme0n1p2 969b3a8b-ff3b-11ec-9b60-d8bbc19aa82b
nvme1n1     
├─nvme1n1p1 90652871-af79-4810-89fa-a1b6619ca989
└─nvme1n1p2 42f07058-cf12-4f0f-bba7-68275bf3b4b0

Last edited by Epp (2023-02-07 20:30:46)

Offline

#15 2023-02-07 20:35:09

Head_on_a_Stick
Member
From: The Wirral
Registered: 2014-02-20
Posts: 9,003
Website

Re: Arch not in my bootloader(s)

Epp wrote:

Doesn't this (from earlier post) show the folder efi is there (looks like since July)?

ubuntu@ubuntu:/media/ubuntu/.../boot$ ls -l
total 177512
drwxr-xr-x 2 root root     4096 Jul  9  2022 efi
drwxr-xr-x 6 root root     4096 Feb  6 18:14 grub

Yes but it would be "hidden" if you subsequently mounted /dev/nvme0n1p1 under /mnt/boot/.

Epp wrote:

I am trying the mounting with the Arch iso. From there I can not copy and paste.

Yes you can: https://wiki.archlinux.org/title/List_o … ted_client

Epp wrote:

From typing on this webpage:

mount /dev/nvme0n1p1 /boot/efi
mount /dev/nvme0n1p1 /boot/efi/
mount /dev/nvme0n1p1 /mnt/boot/efi
mount /dev/nvme0n1p1 /boot/efi

Sorry but I don't understand this bit at all.

I would use

# mount /dev/nvme0n1p2 /mnt
# mkdir -p /mnt/boot/efi
# mount /dev/nvme0n1p1 /mnt/boot/efi
# arch-chroot /mnt

Then run the grub-install & grub-mkconfig commands from the chroot environment.

EDIT: and remember to update /etc/fstab after changing the ESP mountpoint.

Last edited by Head_on_a_Stick (2023-02-07 20:37:32)

Jin, Jîyan, Azadî

Offline

#16 2023-02-07 21:50:34

Epp
Member
Registered: 2022-07-11
Posts: 101

Re: Arch not in my bootloader(s)

For a moment I thought it was working. The good news is that Arch is back in grub.
But after the grub bootloader arch keeps hanging at "Starting systemd-udevd version 252.5-1-arch.

I tried to regenerate the fstab file.
genfstab -U -p /  >> /etc/fstab

Perhaps I have to go in the fstab file to manually edit it. For now excuses, have to go to bed.

Offline

#17 2023-02-08 06:54:34

Head_on_a_Stick
Member
From: The Wirral
Registered: 2014-02-20
Posts: 9,003
Website

Re: Arch not in my bootloader(s)

Epp wrote:

But after the grub bootloader arch keeps hanging at "Starting systemd-udevd version 252.5-1-arch.

Sounds more like a graphical failure. Do you have an NVIDIA card perchance? Can the "hung" system be accessed via ssh? What does the journal say about the situation? (https://wiki.archlinux.org/title/System … al_to_view)

Epp wrote:

I tried to regenerate the fstab file.
genfstab -U -p /  >> /etc/fstab

From where did you run that command? The installation guide says to run genfstab before using arch-chroot. Note that ">>" will append the output to the file so you will then end up with multiple entries for each partition.

Epp wrote:

Perhaps I have to go in the fstab file to manually edit it.

I think that would be best. It would only require a small change.

Jin, Jîyan, Azadî

Offline

#18 2023-02-08 18:23:30

Epp
Member
Registered: 2022-07-11
Posts: 101

Re: Arch not in my bootloader(s)

Yes, GPU is from NVIDIA.

The journalctl command gives this error:
https://askubuntu.com/questions/1208184 … or/1208467
Perhaps my Ubuntu flash contains an Ubuntu version not fit for journalctl this way.

The generate command is from here:
https://gist.github.com/Brainiarc7/c2dfc75ce931491fe510
Found this looking for the correct syntax. Most likely not the correct syntax though.
I ran this after grub-install and grub-mkconfig.

Most likely it's just my dumbness with this but

# mount /dev/nvme0n1p2 /mnt
# mkdir -p /mnt/boot/efi
# mount /dev/nvme0n1p1 /mnt/boot/efi
# arch-chroot /mnt

For me it looks like making a boot/efi directory on p2 (the data partition).
And than mount boot/efi on p1 (the original boot partition).
Shouldn't the intend be here mounting a total new efi directory on p2?

---
Edit:
Made a foto from the screen. It looks like an unrecoverable failure in required component org.gnome.Shell.desktop.
https://postimg.cc/GBmG0dn1

Six rows above this, there is text about running gnome shell as a wayland display driver.
Could this be where it's going wrong (with my DWM desktop not on Wayland)?

Last edited by Epp (2023-02-08 19:00:02)

Offline

#19 2023-02-08 18:59:14

Head_on_a_Stick
Member
From: The Wirral
Registered: 2014-02-20
Posts: 9,003
Website

Re: Arch not in my bootloader(s)

Epp wrote:

The journalctl command gives this error:
https://askubuntu.com/questions/1208184 … or/1208467
Perhaps my Ubuntu flash contains an Ubuntu version not fit for journalctl this way.

Looks like it, yes. Use the Arch live ISO instead and pipe the journal contents to a pastebin, as per my ArchWiki link, then share the returned URL here.

Epp wrote:

The generate command is from here:
https://gist.github.com/Brainiarc7/c2dfc75ce931491fe510
Found this looking for the correct syntax. Most likely not the correct syntax though.

It's better to consult the manpage rather than random gists. But in this case the edit is as simple as changing /boot to /boot/efi on the relevant line. No need to generate a whole new fstab. What does /etc/fstab look like now? Again, pipe the file to a pastebin and share the URL.

At any rate the installation guide actually gives the correct command. Did you follow the official guide?

Epp wrote:

Shouldn't the intend be here mounting a total new efi directory on p2?

The intention is to have the EFI system partition mounted under /boot/efi/ rather than /boot/.

Jin, Jîyan, Azadî

Offline

#20 2023-02-08 19:06:26

Epp
Member
Registered: 2022-07-11
Posts: 101

Re: Arch not in my bootloader(s)

Our posts (my edit) crossed. I placed a link to a foto copy.

The fstab is total empty.

There are only three uncommented lines.

# Static information about the filesystems
# See fstab(5) for details.

# <file systems> <dir> <type> <options> <dump> <pass>

Last edited by Epp (2023-02-08 19:07:14)

Offline

#21 2023-02-08 19:14:20

Head_on_a_Stick
Member
From: The Wirral
Registered: 2014-02-20
Posts: 9,003
Website

Re: Arch not in my bootloader(s)

Epp wrote:

I placed a link to a foto copy.

So your system is booting. You're having a graphics problem. Looks like you have both Intel & NVIDIA graphics, which I don't have any experience of. Check the Optimus & PRIME ArchWiki pages and open a new thread if you can't figure it out. This thread isn't about failure to launch a graphical desktop.

Epp wrote:

The fstab is total empty

The installation guide shows exactly how to generate a working fstab. You have read that, right?

Jin, Jîyan, Azadî

Offline

#22 2023-02-08 19:58:21

Epp
Member
Registered: 2022-07-11
Posts: 101

Re: Arch not in my bootloader(s)

Well before  I am going there, I still like to think it's just a grub thing.
Not installing Arch here.

Just ran the command as in the installation guide.

If it was because I was looking in the wrong fstab, or I did actually change it.

This is what I saw after that:

# Static information about the filesystems. See fstab(5) for details.

# <file system> <dir> <type> <options> <dump> <pass>

# /dev/nvme0n1p2
/dev/nvme0n1p2      	/         	ext4      	rw,relatime	0 1

# /dev/nvme0n1p1
/dev/nvme0n1p1      	/boot/efi 	vfat      	rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro	0 2

Booting still not working.

Can it not just be that grub is looking in the wrong folder (as I am doing and bumbing to this empty fstab)?

Offline

#23 2023-02-08 20:00:48

Head_on_a_Stick
Member
From: The Wirral
Registered: 2014-02-20
Posts: 9,003
Website

Re: Arch not in my bootloader(s)

Epp wrote:

Booting still not working

The timestamps on the journal content in your linked picture say otherwise. If you see a message from systemd then the bootloader has worked.

Jin, Jîyan, Azadî

Offline

#24 2023-02-08 20:03:29

Epp
Member
Registered: 2022-07-11
Posts: 101

Re: Arch not in my bootloader(s)

Well not really with success.

Offline

#25 2023-02-09 19:16:48

Epp
Member
Registered: 2022-07-11
Posts: 101

Re: Arch not in my bootloader(s)

For the future I already had in mind installing Arch again. Without the packages I hope not to need.

This while thinking that emptying, or removing the boot and efi contents and starting over with clean folders has to be a faster way. Anyway.

In the installation guide I read:

If you created an EFI system partition, format it to FAT32 using mkfs.fat(8).


Quotes Head on a stick:

Having said that I do agree with V1del's suggestion to mount /dev/nvme0n1p1 under /boot/efi/ instead of /boot/. Having /boot/ on a FAT filesystem is sub-optimal IMO.

The intention is to have the EFI system partition mounted under /boot/efi/ rather than /boot/.

While you speak of an EFI partition, it can not be that it's meant not to be another partition. For an EFI partition the guide says "format it to FAT32".
Can you please explain this a bit further?
Or did you just mean only "boot" as folder is not correct on a FAT file system?

Last edited by Epp (2023-02-09 19:17:29)

Offline

Pages: 1 2

Board footer

Powered by FluxBB