Error Grub rescue

Hello everyone,

I’ve been using Windows for school work since October and haven’t accessed Manjaro during this period. Now, as I try to switch back to Manjaro, I’m encountering this boot error.

error: unknown filesystem.
Entering rescue mode...
grub rescue>

I found a user, iamwafffel360, with a similar problem. He could still enter manjaro using these commands:

set root=(hd0,gpt2)
set prefix=(hd0,gpt2)/boot/grub
insmod normal

We have similar issues. Although in his case, the problem arose after modifying partitions, whereas mine have remained untouched for months. Attempts at resolving the issue by disabling CSM, as suggested in the forum, were unsuccessful. Windoze might not be the issue here, because they are on separate ssd’s and since my fresh installation of windows I did not encounter any problems (up until today). I have been able to update my system

sudo pacman -Syu

Could Windows updates have affected Manjaro’s boot process, or might there be another cause? Any insights or suggestions would be greatly appreciated.

Here are some information.

  Kernel: 6.1.69-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
    clocksource: hpet Desktop: KDE Plasma v: 5.27.10 tk: Qt v: 5.15.11
    wm: kwin_x11 vt: 2 dm: SDDM Distro: Manjaro Linux base: Arch Linux
  Type: Desktop System: Gigabyte product: B450M DS3H v: N/A
    serial: <superuser required>
  Mobo: Gigabyte model: B450M DS3H-CF serial: <superuser required>
    BIOS: American Megatrends LLC. v: F64 date: 06/08/2023
  Device-1: hidpp_battery_0 model: Logitech G304 Lightspeed Wireless Gaming
    Mouse serial: <filter> charge: 100% (should be ignored) rechargeable: yes
    status: discharging
  Info: 6-core model: AMD Ryzen 5 1600 bits: 64 type: MT MCP smt: enabled
    arch: Zen+ rev: 2 cache: L1: 576 KiB L2: 3 MiB L3: 16 MiB
  Speed (MHz): avg: 1806 high: 3320 min/max: 1550/3200 boost: enabled cores:
    1: 3320 2: 1372 3: 1550 4: 1550 5: 1550 6: 1550 7: 3210 8: 1377 9: 1550
    10: 1550 11: 1550 12: 1550 bogomips: 76690
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Device-1: NVIDIA GA106 [GeForce RTX 3060] vendor: Gigabyte driver: nvidia
    v: 545.29.06 arch: Ampere pcie: speed: 8 GT/s lanes: 16 bus-ID: 07:00.0
    chip-ID: 10de:2503 class-ID: 0300
  Display: x11 server: X.Org v: 21.1.10 with: Xwayland v: 23.2.3
    compositor: kwin_x11 driver: X: loaded: nvidia gpu: nvidia display-ID: :0
    screens: 1
  Screen-1: 0 s-res: 4480x1440 s-dpi: 92 s-size: 1237x402mm (48.70x15.83")
    s-diag: 1301mm (51.21")
  Monitor-1: DP-0 pos: primary,right res: 2560x1440 dpi: 109
    size: 597x336mm (23.5x13.23") diag: 685mm (26.97") modes: N/A
  Monitor-2: HDMI-1 pos: left res: 1920x1080 hz: 60 dpi: 92
    size: 531x298mm (20.91x11.73") diag: 609mm (23.97") modes: N/A
  API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2
    drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia x11: drv: nvidia
    inactive: wayland,device-1
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 545.29.06
    glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 3060/PCIe/SSE2
  API: Vulkan v: 1.3.274 layers: 11 surfaces: xcb,xlib device: 0
    type: discrete-gpu driver: nvidia device-ID: 10de:2503
  Device-1: NVIDIA GA106 High Definition Audio vendor: Gigabyte
    driver: snd_hda_intel v: kernel pcie: speed: 8 GT/s lanes: 16
    bus-ID: 07:00.1 chip-ID: 10de:228e class-ID: 0403
  Device-2: AMD Family 17h HD Audio vendor: Gigabyte driver: snd_hda_intel
    v: kernel pcie: speed: 8 GT/s lanes: 16 bus-ID: 09:00.3 chip-ID: 1022:1457
    class-ID: 0403
  API: ALSA v: k6.1.69-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator
  Server-1: sndiod v: N/A status: off
  Server-2: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    4: pw-jack type: plugin
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: Gigabyte driver: r8169 v: kernel pcie: speed: 2.5 GT/s lanes: 1
    port: f000 bus-ID: 05:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: enp5s0 state: up speed: 100 Mbps duplex: full mac: <filter>
  Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) driver: btusb
    v: 0.8 type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 bus-ID: 3-1:2
    chip-ID: 0a12:0001 class-ID: e001
  Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends
  Local Storage: total: 2.26 TiB used: 338.57 GiB (14.7%)
  ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 980 1TB size: 931.51 GiB
    speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter> fw-rev: 2B4QFXO7
    temp: 41.9 C scheme: GPT
  ID-2: /dev/sda vendor: Kingston model: SA400S37480G size: 447.13 GiB
    speed: 6.0 Gb/s tech: SSD serial: <filter> fw-rev: 0102 scheme: GPT
  ID-3: /dev/sdb vendor: Crucial model: CT1000BX500SSD1 size: 931.51 GiB
    speed: 6.0 Gb/s tech: SSD serial: <filter> fw-rev: 061 scheme: GPT
  ID-1: / size: 413.22 GiB used: 338.57 GiB (81.9%) fs: ext4
    dev: /dev/nvme0n1p2
  Alert: No swap data was found.
  System Temperatures: cpu: 49.8 C mobo: 35.0 C gpu: nvidia temp: 48 C
  Fan Speeds (rpm): N/A gpu: nvidia fan: 0%
  Processes: 278 Uptime: 21m wakeups: 0 Memory: total: 24 GiB
  available: 23.39 GiB used: 4.4 GiB (18.8%) Init: systemd v: 254
  default: graphical Compilers: gcc: 13.2.1 clang: 16.0.6 Packages: 1495
  pm: pacman pkgs: 1478 pm: flatpak pkgs: 14 pm: snap pkgs: 3 Shell: Zsh
  v: 5.9 default: Bash v: 5.2.21 running-in: konsole inxi: 3.3.31

fdisk -l

Disk /dev/sda: 447.13 GiB, 480103981056 bytes, 937703088 sectors
Disk model: KINGSTON SA400S3
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: gpt
Disk identifier: 4987D8A8-A794-1B43-9111-0BD26A15FD7F

Device     Start       End   Sectors   Size Type
/dev/sda1   2048 937701375 937699328 447.1G Microsoft basic data

Disk /dev/sdb: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: CT1000BX500SSD1 
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: gpt
Disk identifier: 3D8CE3E2-DD50-47C3-A34F-10B85B0421C9

Device          Start        End    Sectors   Size Type
/dev/sdb1        2048     206847     204800   100M EFI System
/dev/sdb2      206848     239615      32768    16M Microsoft reserved
/dev/sdb3      239616 1952141311 1951901696 930.7G Microsoft basic data
/dev/sdb4  1952141312 1953521663    1380352   674M Windows recovery environment

Disk /dev/nvme0n1: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: Samsung SSD 980 1TB                     
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 16384 bytes / 131072 bytes
Disklabel type: gpt
Disk identifier: 3B14A996-5D4E-4734-81AF-A0F0E1595CDA

Device         Start        End    Sectors   Size Type
/dev/nvme0n1p2  2048 1953523711 1953521664 931.5G EFI System

Disk /dev/loop0: 63.46 MiB, 66547712 bytes, 129976 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

Disk /dev/loop1: 63.91 MiB, 67014656 bytes, 130888 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

Disk /dev/loop2: 40.84 MiB, 42827776 bytes, 83648 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

Disk /dev/loop3: 40.86 MiB, 42840064 bytes, 83672 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


like other people mentioned there are some issues with the drives. The kingston one is from a old windows installation that went wrong. The samsung drive is failed dual booting attempt (I forgot to search a solution for it).
The grub rescue problem came way after these, so I don’t think it has something to do with it.

also I’m in Europe.

There does not seem to be any linux installation, but seems to be 2 windows installations. One on KINGSTON SA400S3 and one on CT1000BX500SSD1. Both the same partition structure but different sizes.
On the nvme there is a 420GB big efi boot system.

Sorry, your manjaro seems to be gone at least if this is all the drives you have.

Could you please provide the output of lsblk?
(sudo isn’t needed)

It looks like the OP dumped their questions and logged out.
Think I’ll pass.

On the samsung drive, half of the space is missing and the other half is in the efi partition. Smells like a problem/mistake making/resizing/deleting partitions.

More like a borked GPT.

sorry for the late response, I went to the gym. Here is the lsblk

loop0         7:0    0  63.5M  1 loop /var/lib/snapd/snap/core20/2015
loop1         7:1    0  63.9M  1 loop /var/lib/snapd/snap/core20/2105
loop2         7:2    0  40.8M  1 loop /var/lib/snapd/snap/snapd/20092
loop3         7:3    0  40.9M  1 loop /var/lib/snapd/snap/snapd/20290
sda           8:0    0 447.1G  0 disk 
└─sda1        8:1    0 447.1G  0 part 
sdb           8:16   0 931.5G  0 disk 
├─sdb1        8:17   0   100M  0 part 
├─sdb2        8:18   0    16M  0 part 
├─sdb3        8:19   0 930.7G  0 part 
└─sdb4        8:20   0   674M  0 part 
nvme0n1     259:0    0 931.5G  0 disk 
└─nvme0n1p2 259:1    0 931.5G  0 part /

also half of the ssd is missing because once i was booting windows and manjaro on the same drive. Then I had some problems with windows and decided to do a fresh install on another drive. To be honest I totally forgot to search a solution. Sorry again for the late response.

I should add that the grub rescue issues is since yesterday. For about a year nothing happened. So i don’t think that has something to do with it (not excluding the possibility though).

To answer @/bedna, yes in these 2 drives is no linux installation. It is installed in on the samsung 1tb nvme ssd.

edit: i fixed the drives now it is better and manjaro still work like before (with grub issue).

The partition type is wrong - depending on what you expect to be on the disk it should not be EFI System (0xEF00) but either Microsoft (0x0700) or Linux (0x8300).

IF this is your Linux root - you may be able to rescue the install by using a live ISO.

When booted - launch a terminal

To become root (don’t enter the prefix $ or #)

$ su


# cgdisk /dev/nvme0n1

Select the partition and press t then enter 8300 as type code and press enter

To save the change press w and enter yes and press enter.

Press q to exit.

Reinstall grub using the EFI partition on /dev/sdb1

# mount /dev/nvme0n1p2 /mnt
# mount /dev/sdb1 /mnt/boot/efi
# grub-install --target=x86_64-efi --efi-directory /mnt/boot/efi bootloader-id=Manjaro --recheck
# grub-mkconfig -o /mnt/boot/grub/grub.cfg

Then reboot.

Thank you for responding,

So I mounted nvme0n1p2 and sdb1, but the grub-install command did not work. here is the output

grub-install --target=x86_64-efi --efi-directory /mnt/boot/efi bootloader-id=Manjaro --recheck
Installing for x86_64-efi platform.
grub-install: error: failed to get canonical path of `overlay'.

I am not sure if I should still proceed with the last command. I will wait for your response. also I loaded from a usb drive not sure if this is what you were saying.

I was also wondering shouldn’t it be directory=/mnt/boot/efi?

I think it may be caused by not being in a chroot - you can change the sequence

# mount /dev/nvme0n1p2 /mnt
# mount /dev/sdb1 /mnt/boot/efi

Enter a chroot

# manjaro-chroot /mnt /bin/bash

Then remove the reference to /mnt

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


# exit
# reboot
1 Like

Thank you, it worked.

I have another question. When i was in my BIOS I saw that there is another partition created on the windows drive. Can’t I put it in the manjaro drive?

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