The Manjaro partition is not recognized

Support
61

There were times when I forgot chroot, but I did after. I did it earlier, and I have exactly the same feedback as on this previous message:

62

Note

If you get something like

EFI variables are not supported on this system.

Then install the efibootmgr , dosfstools and grub packages and try steps 4 and 5 again.

If it still doesn’t work, then try exiting the chroot environnment by typing exit , then loading the efivarfs module:

sudo modprobe efivarfs

and IN THE CHROOT

mount -t efivarfs efivarfs /sys/firmware/efi/efivars

And if you get something like

grub-install: error: failed to get canonical path of `union’.

means that probably you forgot to chroot.

64

:astonished:

Boot0000* manjaro
Installation finished. No error reported.

But after reboot > Grub rescue

When I boot UEFI HDD (windows), do not start and go to the next one, before I had grub rescue as for manjaro.

65

Good so far. First guess from above was that grub couldn’t find a kernel. Did you run sudo update-grub after sudo grub-install ?

IN CHROOT
Is the kernel correctly installed? Reinstall it…

66

Of course, that’s was missing!

67 
[manjaro@manjaro ~]$ sudo modprobe efivarfs
[manjaro@manjaro ~]$ sudo manjaro-chroot -a
==> Mounting (ManjaroLinux) [/dev/nvme0n1p4]
 --> mount: [/mnt]
 --> mount: [/mnt/boot/efi]
 --> mount: [/mnt/mnt/Windows]
mount: special device /dev/disk/by-uuid/90A457A0A457881C does not exist
 --> mount: [/mnt/mnt/HDD_500Go_interne]
The disk contains an unclean file system (0, 0).
Metadata kept in Windows cache, refused to mount.
Failed to mount '/dev/sda1': Operation not permitted
The NTFS partition is in an unsafe state. Please resume and shutdown
Windows fully (no hibernation or fast restarting), or mount the volume
read-only with the 'ro' mount option.
 --> mount: [/mnt/mnt/Stockage]
The disk contains an unclean file system (0, 0).
Metadata kept in Windows cache, refused to mount.
Failed to mount '/dev/sdb1': Operation not permitted
The NTFS partition is in an unsafe state. Please resume and shutdown
Windows fully (no hibernation or fast restarting), or mount the volume
read-only with the 'ro' mount option.

[manjaro /]# mount -t efivarfs efivarfs /sys/firmware/efi/efivars
[manjaro /]# grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=manjaro --recheck --verbose
Installing for x86_64-efi platform.
grub-install: info: cannot open `/boot/grub/device.map': No such file or directory.
grub-install: info: /dev/nvme0n1p2 is not present.
grub-install: info: Looking for /dev/nvme0n1p2.
grub-install: info: /dev/nvme0n1 is a parent of /dev/nvme0n1p2.
grub-install: info: /dev/nvme0n1p2 starts from 923648.
grub-install: info: opening the device hostdisk//dev/nvme0n1.
grub-install: info: drive = 0.
grub-install: info: the size of hostdisk//dev/nvme0n1 is 488397168.
grub-install: info: drive = 0.
grub-install: info: the size of hostdisk//dev/nvme0n1 is 488397168.
grub-install: info: Scanning for DISKFILTER devices on disk hostdisk//dev/nvme0n1.
grub-install: info: Scanning for mdraid1x devices on disk hostdisk//dev/nvme0n1.
grub-install: info: Scanning for mdraid09_be devices on disk hostdisk//dev/nvme0n1.
grub-install: info: Scanning for mdraid09 devices on disk hostdisk//dev/nvme0n1.
grub-install: info: Scanning for dmraid_nv devices on disk hostdisk//dev/nvme0n1.
grub-install: info: Scanning for ldm devices on disk hostdisk//dev/nvme0n1.
grub-install: info: scanning hostdisk//dev/nvme0n1 for LDM.
grub-install: info: no LDM signature found.
................................
grub-install: info: adding a relocation entry for 0x129b8.
grub-install: info: adding a relocation entry for 0x129c8.
grub-install: info: adding a relocation entry for 0x129d0.
grub-install: info: adding a relocation entry for 0x129e0.
grub-install: info: adding a relocation entry for 0x129e8.
grub-install: info: adding 48 padding fixup entries.
grub-install: info: writing 528 bytes of a fixup block starting at 0x12000.
grub-install: info: reading /usr/lib/grub/x86_64-efi/fshelp.mod.
grub-install: info: reading /usr/lib/grub/x86_64-efi/ext2.mod.
grub-install: info: reading /usr/lib/grub/x86_64-efi/part_msdos.mod.
grub-install: info: kernel_img=0x556f42223870, kernel_size=0x1e000.
grub-install: info: the core size is 0x22738.
grub-install: info: writing 0x25000 bytes.
grub-install: info: copying `/boot/grub/x86_64-efi/core.efi' -> `/boot/efi/EFI/manjaro/grubx64.efi'.
grub-install: info: Registering with EFI: distributor = `manjaro', path = `\EFI\manjaro\grubx64.efi', ESP at hostdisk//dev/nvme0n1,msdos2.
grub-install: info: executing efibootmgr --version </dev/null >/dev/null.
grub-install: info: executing modprobe -q efivarfs.
grub-install: info: executing efibootmgr -c -d /dev/nvme0n1 -p 2 -w -L manjaro -l \EFI\manjaro\grubx64.efi.
BootCurrent: 000F
Timeout: 2 seconds
BootOrder: 0000,000F,000D,000E
Boot0008* CD/DVD Drive
Boot000D* Hard Drive
Boot000E* CD/DVD Drive
Boot000F* UEFI: ASUS    BW-16D1HT
Boot0000* manjaro
Installation finished. No error reported.

[manjaro /]# sudo update-grub
Generating grub configuration file ...
    Found theme: /usr/share/grub/themes/manjaro/theme.txt
    Found linux image: /boot/vmlinuz-5.7-x86_64
    Found initrd image: /boot/amd-ucode.img /boot/initramfs-5.7-x86_64.img
    Found initrd fallback image: /boot/initramfs-5.7-x86_64-fallback.img
    Found linux image: /boot/vmlinuz-5.4-x86_64
    Found initrd image: /boot/amd-ucode.img /boot/initramfs-5.4-x86_64.img
    Found initrd fallback image: /boot/initramfs-5.4-x86_64-fallback.img
    Found linux image: /boot/vmlinuz-4.19-x86_64
    Found initrd image: /boot/amd-ucode.img /boot/initramfs-4.19-x86_64.img
    Found initrd fallback image: /boot/initramfs-4.19-x86_64-fallback.img
    Found linux image: /boot/vmlinuz-4.14-x86_64
    Found initrd image: /boot/amd-ucode.img /boot/initramfs-4.14-x86_64.img
    Found initrd fallback image: /boot/initramfs-4.14-x86_64-fallback.img
    Adding boot menu entry for UEFI Firmware Settings ...
    Found memtest86+ image: /boot/memtest86+/memtest.bin
    /usr/bin/grub-probe: warning: unknown device type nvme0n1.
    done

and… Grub recue after reboot

68

The last line above says:

  /usr/bin/grub-probe: warning: unknown device type nvme0n1.

Could that be a problem?

I will redo everything with a reinstallation of the kernel.

69

No, that’s a known glitch of the memtest86+ part of update-grub. It’s harmless

70

Do you get some error message why are you being thrown to rescue mode?

71

Yes! Please give us a boot log :slight_smile:

journalctl -b -0 > boot.0.log && curl --upload-file boot.0.log https://aptget.xyz && rm boot.0.log
1 Like
72

Hey @megavolt, very handy that service! The command can be simplified a bit though:

journalctl -b -0 | curl --upload-file - https://aptget.xyz/boot.0.log

(It took some tries to find that :smiley:)

Anyway, do you have access to to system log in rescue mode? If I understand it correctly, rescue mode is when grub can not boot the Linux system: " GRUB 2 is unable to find the grub folder or its contents are missing/corrupted. The grub folder contains the GRUB 2 menu, modules and stored environmental data."

1 Like
73

Your computer is correctly booting your UEFI’s Manjaro entry. Grub is installed, but it throws you to rescue mode. It seems that usually that is caused by a faulty /boot/grub folder. Can you show that folder from chroot?

ls -al /boot/grub

Can you also upload the full grub-install report (from chroot and with efivars enabled):

sudo grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=manjaro --recheck --verbose 2>&1 | curl --upload-file  - https://aptget.xyz/grub-install
74

I updated the system to be able to reinstall the kernel, but:

[manjaro /]# sudo mhwd-kernel -i linux58
:: Synchronizing package databases...
 core                                                          169.2 KiB   289 KiB/s 00:01 [#####################################################] 100%
 extra                                                        2013.0 KiB   287 KiB/s 00:07 [#####################################################] 100%
 community                                                       6.2 MiB   289 KiB/s 00:22 [#####################################################] 100%
 multilib                                                      194.3 KiB   297 KiB/s 00:01 [#####################################################] 100%
error: no targets specified (use -h for help)

[manjaro /]# sudo mhwd-kernel -li
Currently running: 4.4.33-1-MANJARO (linux44)
The following kernels are installed in your system:
   * linux414
   * linux419
   * linux54
   * linux57
   * linux58

[manjaro /]# sudo mhwd-kernel -i linux57
:: Synchronizing package databases...
 core                                                          169.2 KiB   290 KiB/s 00:01 [#####################################################] 100%
 extra                                                        2013.0 KiB   285 KiB/s 00:07 [#####################################################] 100%
 community                                                       6.2 MiB   288 KiB/s 00:22 [#####################################################] 100%
 multilib                                                      194.3 KiB   301 KiB/s 00:01 [#####################################################] 100%
error: no targets specified (use -h for help)
75 
[manjaro /]# ls -al /boot/grub
total 48
drwxr-xr-x 5 root root  4096 Sep 20 13:19 .
drwxr-xr-x 5 root root  4096 Sep 20 13:19 ..
drwxr-xr-x 2 root root  4096 Aug 30  2019 fonts
-rw------- 1 root root 12300 Sep 20 13:19 grub.cfg
-rw-r--r-- 1 root root  1024 Sep  6  2019 grubenv
drwxr-xr-x 3 root root  4096 Aug 30  2019 themes
drwxr-xr-x 2 root root 12288 Sep 19 23:45 x86_64-efi
76

http://aptget.xyz/oMii6/grub-install

I remember talking about “challenge” when talking about my problem, I didn’t think so much!

77

Your grub-install report seems fine and I think it is copying correctly the files needed by grub to boot, so the question is why are you been thrown to rescue mode? Do you get some error message at boot that can explain that?

When you are in grub rescue mode, what do you whet with ls command?

78 
error : No such partition
entering rescue mode...
grub rescue :

i try

79

In grub resue with “ls” i have :
(hd0,msdos1) (hd1,msdos1) (hd2,msdos1,2,3and4)
and with “set” i have found
“ext2 partition” (hd0,msdos3)/boot/grub
after i did:
set boot=(hd0,msdos3)
set prefix=(hd0,msdos3)/boot/grub
insmod normal
error : no such partition
ps: sorry, on android box

1 Like
80

I think your nvme drive is hd2. So EFI partition is (hd2,msdos2) and your Manjaro root partition is (hd2,msdos4). Try to confirm that the grub directory can be reached with

ls (hd2,msdos4)/boot/grub

You can try to boot your linux manually with the help of this guide: Grub2/Troubleshooting - Community Help Wiki

Let’s see where it leads

81

I would try to search where the grub partition is:

ls (hd0,1)/
ls (hd1,1)/

…etc

if you found the the correct partition then:

set the root partition:

set root=(hd0,1)

set the boot partition:

set prefix=(hd1,1)/boot/grub

then try to load the modules:

insmod normal

if everything goes well, then:

normal

to start the grub menu