Manjaro Architect lands in grub>

$ sudo grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=manjaro --recheck
$ sudo update-grub

output from

$ cat /etc/fstab
[manjaro-gnome /]# sudo grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=manjaro --recheck
Installing for x86_64-efi platform.
Installation finished. No error reported.
[manjaro-gnome /]# sudo update-grub
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/manjaro/theme.txt
grub-probe: error: cannot find a GRUB drive for /dev/sda1.  Check your
grub-probe: error: cannot find a GRUB drive for /dev/sda1.  Check your
Found Solus (4.1) on /dev/nvme0n1p8
Found memtest86+ image: /boot/memtest86+/memtest.bin
/usr/bin/grub-probe: warning: unknown device type nvme0n1.

[manjaro-gnome /]# cat /etc/fstab
# /dev/nvme0n1p9
UUID=2bb2b05c-656b-47bf-af81-9a7028695bc9	/         	ext4      	rw,noatime	0 0

# /dev/nvme0n1p1 LABEL=ESP
UUID=B812-4C37      	/boot/efi 	vfat      	rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro	0 0

any chance :wink:

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

no.. same issue... no boot

Are you still in chroot?
If yes, do

sudo cp /boot/grub/x86_64-efi/core.efi /boot/efi/EFI/boot/bootx64.efi
sudo efibootmgr -c -d /dev/nvme0n1 -p 1 -L "manjaro" -l "\EFI\Manjaro\grubx64.efi"

If you have exited and no longer booted.
You said..

lands in the grub menu & doesn't boot.

Does that mean when you start computer, you have a grub menu?
If yes, then at the grub menu, go to grub prompt (grub> ) by pressing 'c'
Do not have the install usb or any other drives attached.

grub> ls

does that give output of ?
(hd0) (hd0,gpt1)(hd0,gpt2)...... (hd0,gpt9)

Proceed as follows..

grub> set root=(hd0,9)
grub> probe -u $root --set=abc
grub> linux /boot/vmlinuz-5.4-x86_64 root=UUID=$abc rw
grub> initrd /boot/initramfs-5.4-x86_64.img
grub> boot

Does that boot to your installed OS?
If it does, at terminal, do

sudo pacman-mirrors -f5
sudo pacman -Syu

sudo grub-install 
sudo update-grub

sudo cp /boot/grub/x86_64-efi/core.efi /boot/efi/EFI/boot/bootx64.efi
sudo efibootmgr -c -d /dev/nvme0n1 -p 1 -L "manjaro" -l "\EFI\Manjaro\grubx64.efi"

reference : this first post.

i'm back live & chrooted.
will first try the first step you mentioned & report back later

first step didn’t work. Am back in grub & going to try out the rest of the steps

Please confirm the first grub command.. root should be set to (hd1,9) rather than (hd0,9) right?

at grub> ls
anything with (hdx,0) to (hdx,9) should be the correct disk.
As your nvme has 9 partitions. use ehatever the (hdx) gives 9 partitions..
That's why I ask you to ppull out all drives so we don't get confused with the disks.

Oh..noted your post above.

I suggest reinstalling kernels again before grub-install and after pacman -Syu
I suggest a new kernel linux 55


sudo pacman -S linux55
sudo mkinitcpio -P

Between 'sudo pacman -Syu' and 'grub-install' commands above.

There had been some problems with some kernels not booting , I'm unsure what the problems are.

sudo pacman-mirrors -f5
sudo pacman -Syu

sudo pacman -S linux55
sudo mkinitcpio -P

sudo grub-install 
sudo update-grub

sudo cp /boot/grub/x86_64-efi/core.efi /boot/efi/EFI/boot/bootx64.efi
sudo efibootmgr -c -d /dev/nvme0n1 -p 1 -L "manjaro" -l "\EFI\Manjaro\grubx64.efi"

yes it is (hd1,9)

third command didn’t work as file /boot/vmlinuz-5.4-x86_64 doesn’t exist.

I’m not sure which kernels are installed. Is it possible to find that out from grub or do I need to chroot again & check?

grub> ls /boot/
grub> ls ($root)/boot/
grub> ls (hd1,9)/boot/

BTW, what's (hd0) ? the usb?

To clarify

If grub> ls gives
(hd0) (hd0,msdos2) (hd0,msdos1) (hd1) (hd1,gpt9) (hd1,gpt8).......(hd1,gpt1)

Then Yes! set root=(hd1,9) !!
grub> set root=(hd1,9)

And then
grub> ls ($root)/boot/

gives kernels in it.
UNLESS you have a separate /boot partition but from the earliwer posts, I do not see any separate /boot partition.

understood. Thanks for clarifying. Will proceed the way you suggested & check

you are right. There is no separate /boot

yes (hd0) is the usb

there are linux*.kver files for kernels 4.19 & 5.5.
Assuming these are the kernels, i proceeded with the command but got “premature end of file...kver” error

So should I chroot back, reinstall kernels & try the rest of the steps?

There are no initramfs-4.19-x86_64.img nor vmlinuz-4.19-x86_64 ??!
Or initramfs-5.4-x86_64.img or vmlinuz-5.4-x86_64 ?

Do you know what happen that they can disappear?

[pop@Dec ~]$ ls /boot/
amd-ucode.img                      intel-ucode.img
efi                                intelmanjaro.img
grub                               linux54-x86_64.kver
initramfs-5.4-x86_64-fallback.img  linux55-x86_64.kver
initramfs-5.4-x86_64.img           memtest86+
initramfs-5.5-x86_64-fallback.img  vmlinuz-5.4-x86_64
initramfs-5.5-x86_64.img           vmlinuz-5.5-x86_64
initramfs-manjaro.img              vmlinuz-manjaro
[pop@Dec ~]$ 

You can try. But wait, we can try first to think why you lost these.
You can help us by recalling what you did.

Probably at chroot. I think. Did you do anything at chroot before you type 'exit'
Did you exit chroot?

no there are no initramfs* or vmlinuz* files for any of the kernels.

[manjaro-gnome boot]# ls -ltr
total 3104
drwxr-xr-x 4 root root    4096 Jan  1  1970 efi
-rw-r--r-- 1 root root 3121152 Dec 11 18:02 intel-ucode.img
-rw-r--r-- 1 root root   31232 Jan 22 17:47 amd-ucode.img
-rw-r--r-- 1 root root      20 Jan 27 15:08 linux55-x86_64.kver
-rw-r--r-- 1 root root      22 Jan 27 22:05 linux419-x86_64.kver
drwxr-xr-x 2 root root    4096 Feb  5 17:16 memtest86+
-rw-r--r-- 1 root root     444 Feb  5 23:33 refind_linux.conf
drwxr-xr-x 5 root root    4096 Feb  6 18:31 grub

i have no idea why they aren't there. This is a fresh M-A install & everything was normal. Nothing was deleted accidently. I did a minimal rather than a full install but that shouldn't matter i believe?

Okay, we have no idea how that happen.
Yiou can try to chroot and install kernels.
Use pacman -S linux n (and then do mkinitcpio -P)
not mhwd-kernel

(some issues that we don't understand)

But if all else fails, be preepared to reinstall the whole OS.
BTW, I have not good experiences with manjaro-architect
and normally I don't answer questions about installation, particularly on architect installs.
(I install in a 'funny' way, I don't make install media but never mind for now)

1 Like

That worked. So it seems M-A didn’t install kernels properly. Will try with a full install again.

Thank you so much for the help!!!!

1 Like

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

Forum kindly sponsored by