Broken grub, stuck in grub rescue, "error: no such partition"

entered it, it had no output, i’m guessing it did something

Let’s check. Provide the output of:

cat /etc/default/grub

…again, please.

sir i personally wouldn’t know either, i specialize in huffing glue, all i know is my system is uefi and x86_64

1 Like

this is the output of cat /etc/default/grub:

GRUB_CMDLINE_LINUX_DEFAULT="quiet apparmor=1 security=apparmor  udev.log_priority=3g splash vt.global_cursor_default=0"

# If you want to enable the save default function, uncomment the following
# line, and set GRUB_DEFAULT to saved.

# Uncomment to disable submenus in boot menu

# Preload both GPT and MBR modules so that they are not missed
GRUB_PRELOAD_MODULES="part_gpt part_msdos"

# Uncomment to enable booting from LUKS encrypted devices

# Uncomment to use basic console

# Uncomment to disable graphical terminal

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command 'videoinfo'

# Uncomment to allow the kernel use the same resolution used by grub

# Uncomment if you want GRUB to pass to the Linux kernel the old parameter
# format "root=/dev/xxx" instead of "root=/dev/disk/by-uuid/xxx"

# Uncomment to disable generation of recovery mode menu entries

# Uncomment this option to enable os-prober execution in the grub-mkconfig command

# Uncomment and set to the desired menu colors.  Used by normal and wallpaper
# modes only.  Entries specified as foreground/background.

# Uncomment one of them for the gfx desired, a image background or a gfxtheme

# Uncomment to get a beep at GRUB start
#GRUB_INIT_TUNE="480 440 1"

# Uncomment to ensure that the root filesystem is mounted read-only so that
# systemd-fsck can run the check automatically. We use 'fsck' by default, which
# needs 'rw' as boot parameter, to avoid delay in boot-time. 'fsck' needs to be
# removed from 'mkinitcpio.conf' to make 'systemd-fsck' work.
# See also Arch-Wiki:


It seems to have successfully removed it, then.

Now let’s update it. Still in the chroot environment, run the following:


If there were no errors, exit the chroot:


And reboot your PC.

I don’t know if it’ll work, but at least you won’t be worse off. I think.

But even if it does, I recommend that you backup your stuff :tm: and reinstall everything.

Could be the grub from the ventoy partition, did you choose a 32-bit version of ventoy?

(I’m not sure if it makes a difference to the Manjaro boot …)

alright, trying rn

ventoy is on a usb, i only plugged it in after grub went into grub rescue

it’s still in grub rescue and doesn’t boot

In that case, my knowledge has been depleted and I don’t know further. Personally, I’d have skipped all this, and just reinstalled everything.


i have a lot of programs and settings installed and games and passwords all saved there, isn’t there any way to completely remove grub and reinstall it, or any way of moving all my data? reinstalling and moving everything is going to take at least a whole week

There is a way to rescue it, most likely, but I don’t know more than we’ve done, so I honestly don’t know how to do it, or even what “it” is for that matter. I’ve given you all the links I could find here and I don’t have or know anything extra. Sorry.


Did you follow steps in GRUB/Restore the GRUB Bootloader - Manjaro ?

Looking at it, there are steps for BIOS vs EFI, the BIOS step has

root # grub-install --force --target=i386-pc --recheck --boot-directory=/boot /dev/sdy

whereas the EFI step has

root # grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=manjaro --recheck

I think the BIOS step would end up with the error shown …

Did you follow the EFI step?

hello, it’s been a couple of days, it said that EFI variables are not supported on this system so efibootmgr failed to register the boot entry

can you recheck all option in your UEFI motherboard
create a profile for linux if possible

SecureBoot off
Fast Boot off
No Legacy
all disks on AHCI
fTPM off ( Amd Ryzen )

for USB live iso
boot only on UEFI:<partition 1> → EFI install manjaro

you can check in terminal , before chroot

inxi  -Fxza
test -d /sys/firmware/efi && echo efi || echo bios
sudo lsblk -fs
sudo efibootmgr -v
sudo parted -l 

so you are sure is it safe to apply those settings? i don’t want to break my system even more than it already is

this is the output of inxi -Fxza before chroot (as in inside the live usb’s terminal)

  Kernel: 5.15.60-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 12.1.1
    parameters: BOOT_IMAGE=/boot/vmlinuz-x86_64 lang=en_US keytable=us tz=UTC
    misobasedir=manjaro misolabel=MANJARO_XFCE_2137 quiet
    systemd.show_status=1 apparmor=1 security=apparmor driver=nonfree
    nouveau.modeset=0 i915.modeset=1 radeon.modeset=1 rdinit=/vtoy/vtoy
  Desktop: Xfce v: 4.16.0 tk: Gtk v: 3.24.29 info: xfce4-panel wm: xfwm
    v: 4.16.1 vt: 7 dm: LightDM v: 1.32.0 Distro: Manjaro Linux
    base: Arch Linux
  Type: Desktop Mobo: Gigabyte model: B450M DS3H V2 v: x.x
    serial: <superuser required> BIOS: American Megatrends LLC. v: F61
    date: 07/13/2021
  Info: model: AMD Ryzen 5 3500 bits: 64 type: MCP arch: Zen 2 gen: 3
    built: 2020-22 process: TSMC n7 (7nm) family: 0x17 (23)
    model-id: 0x71 (113) stepping: 0 microcode: 0x8701021
  Topology: cpus: 1x cores: 6 smt: <unsupported> cache: L1: 384 KiB
    desc: d-6x32 KiB; i-6x32 KiB L2: 3 MiB desc: 6x512 KiB L3: 16 MiB
    desc: 2x8 MiB
  Speed (MHz): avg: 2172 high: 2344 min/max: 2200/4120 boost: enabled
    scaling: driver: acpi-cpufreq governor: schedutil cores: 1: 2344 2: 2052
    3: 2053 4: 2196 5: 2195 6: 2196 bogomips: 43134
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: retbleed mitigation: untrained return thunk; SMT disabled
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl and seccomp
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
  Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, STIBP:
    disabled, RSB filling, PBRSB-eIBRS: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
  Device-1: NVIDIA GP107 [GeForce GTX 1050 Ti] vendor: Micro-Star MSI
    driver: nvidia v: 515.65.01 alternate: nouveau,nvidia_drm non-free: 515.xx+
    status: current (as of 2022-07) arch: Pascal code: GP10x
    process: TSMC 16nm built: 2016-21 pcie: gen: 3 speed: 8 GT/s lanes: 16
    bus-ID: 06:00.0 chip-ID: 10de:1c82 class-ID: 0300
  Display: x11 server: X.Org v: 21.1.4 compositor: xfwm v: 4.16.1 driver:
    X: loaded: nvidia gpu: nvidia display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1680x1050 s-dpi: 96 s-size: 445x278mm (17.52x10.94")
    s-diag: 525mm (20.66")
  Monitor-1: HDMI-0 res: 1680x1050 hz: 60 size: N/A modes: N/A
  Message: Unable to show GL data. Required tool glxinfo missing.
  Device-1: NVIDIA GP107GL High Definition Audio vendor: Micro-Star MSI
    driver: snd_hda_intel v: kernel bus-ID: 1-4:2 chip-ID: 03f0:0b92 pcie:
    class-ID: 0300 gen: 3 speed: 8 GT/s serial: <filter> lanes: 16
    bus-ID: 06:00.1 chip-ID: 10de:0fb9 class-ID: 0403
  Device-2: AMD Starship/Matisse HD Audio vendor: Gigabyte
    driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
    bus-ID: 08:00.4 chip-ID: 1022:1487 class-ID: 0403
  Device-3: HP HyperX Virtual Surround Sound type: USB
    driver: hid-generic,snd-usb-audio,usbhid
  Sound Server-1: ALSA v: k5.15.60-1-MANJARO running: yes
  Sound Server-2: JACK v: 1.9.21 running: no
  Sound Server-3: PulseAudio v: 16.1 running: yes
  Sound Server-4: PipeWire v: 0.3.56 running: yes
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: Gigabyte driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
    lanes: 1 port: f000 bus-ID: 04:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: enp4s0 state: up speed: 100 Mbps duplex: full mac: <filter>
  Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) type: USB
    driver: btusb v: 0.8 bus-ID: 3-3:3 chip-ID: 0a12:0001 class-ID: e001
  Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends
  Device-2: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) type: USB
    driver: btusb v: 0.8 bus-ID: 3-4:4 chip-ID: 0a12:0001 class-ID: e001
  Report: ID: hci1 rfk-id: 1 state: up address: N/A
  Local Storage: total: 1.17 TiB used: 0 KiB (0.0%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Toshiba model: HDWD110
    size: 931.51 GiB block-size: physical: 4096 B logical: 512 B
    speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter> rev: A8R0
    scheme: GPT
  ID-2: /dev/sdb maj-min: 8:16 vendor: Samsung model: MZ7PD256HCGM-000H7
    size: 238.47 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    type: SSD serial: <filter> rev: 6H6Q scheme: GPT
  ID-3: /dev/sdc maj-min: 8:32 type: USB vendor: Toshiba model: TransMemory
    size: 14.45 GiB block-size: physical: 512 B logical: 512 B type: N/A
    serial: <filter> rev: 1.00 scheme: MBR
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
  ID-4: /dev/sdd maj-min: 8:48 type: USB model: N/A size: 7.5 GiB
    block-size: physical: 512 B logical: 512 B type: N/A serial: <filter>
    rev: 2.00
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
  ID-5: /dev/sde maj-min: 8:64 type: USB vendor: Generic model: Flash Disk
    size: 7.5 GiB block-size: physical: 512 B logical: 512 B type: SSD
    serial: <filter> rev: 8.07 scheme: MBR
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
  Message: No partition data found.
  Alert: No swap data was found.
  System Temperatures: cpu: 47.6 C mobo: N/A gpu: nvidia temp: 38 C
  Fan Speeds (RPM): N/A gpu: nvidia fan: 45%
  Processes: 258 Uptime: 23m wakeups: 0 Memory: 15.56 GiB used: 3.66 GiB
  (23.5%) Init: systemd v: 251 default: graphical tool: systemctl
  Compilers: gcc: 12.1.1 clang: 14.0.6 Packages: pacman: 1156 lib: 320
  flatpak: 0 Shell: Bash v: 5.1.16 running-in: xfce4-terminal inxi: 3.3.20

“test -d /sys/firmware/efi && echo efi || echo bios” 's output:


the output of sudo lsblk -fs

NAME    FSTYPE   FSVER            LABEL             UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
loop0   squashfs 4.0                                                                           0   100% /run/miso/sfs/livefs
loop1   squashfs 4.0                                                                           0   100% /run/miso/sfs/mhwdfs
loop2   squashfs 4.0                                                                           0   100% /run/miso/sfs/desktopfs
loop3   squashfs 4.0                                                                           0   100% /run/miso/sfs/rootfs
sda1    ext4     1.0                                15bcc38a-c5fd-402c-a04d-6bb8e3a0d676                
sda2    ext4     1.0                                634b77fc-47d7-4969-bcec-9e2ec94d8907                
sda7    ext4     1.0              p3                9b98e355-79d1-473a-b03a-a7a3d3b2c314                
sda8    ext4     1.0                                71a2b10d-4f8e-4acb-bcd5-49227782de2f                
sdb1    vfat     FAT32            NO_LABEL          D2C5-272C                                           
sdb2    ext4     1.0              MOOOON            a07ad4de-42e0-4649-858a-266965f2e1aa                
sdb3    swap     1                swap              11e0da9a-9c9c-4711-8847-bc08ac54f8c9                
sdc2    vfat     FAT16            VTOYEFI           C559-2E5D                                           
sdd     ext4     1.0                                31ce81ea-f3ea-40ba-8b2a-367bf6134ad9                
sde1    vfat     FAT32                              32EE-A032                                           
ventoy  iso9660  Joliet Extension MANJARO_XFCE_2137 2022-08-16-12-55-20-00                     0   100% /run/miso/bootmnt
└─sdc1  exfat    1.0              Ventoy            EBC0-A722                                           

running sudo efibootmgr -v gives:

EFI variables are not supported on this system.
error trace:

and sudo parted -l gives:

EFI variables are not supported on this system.
error trace:

and i also ran fdisk -l /dev/sdb (sdb is my root directory’s disk) which gave me this:

Disk /dev/sdb: 238.47 GiB, 256060514304 bytes, 500118192 sectors
Disk model: SAMSUNG MZ7PD256
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: A4005191-8973-1747-ABD1-48BEA97D5D8B

Device         Start       End   Sectors   Size Type
/dev/sdb1       4096    618495    614400   300M EFI System
/dev/sdb2     618496 481648510 481030015 229.4G Linux filesystem
/dev/sdb3  481648511 500103449  18454939   8.8G Linux swap

and when i open gparted i see that i have fat32 partition on my disk (which has my root directory which i’m trying to boot into) with it’s flags being: “boot, esp”

you have booted in Bios , not UEFI as required , also there is update four your motherboard
see GIGABYTE B450M DS3H V2 Motherboard|GIGABYTE
( it should be F62 or F63 ) , not forget to reset settings

create a USB live iso with DD ( be very careful before that , always recheck sudo fdisk -l for name /dev/sdX )

i’m using a manjaro live usb, my actual system is uefi, also do i really need to update my bios? power tends to go out a lot where i live with no notice and i don’t want my system to be turned into expensive paper weight

what is “DD”?

@stephane ?

so for your understanding

  • you have first installed in UEFI , becaause sdb is GPT and there is /boot/efi with flag boot&esp
  • your options in boot UEFI motherboard is bad for your Live USB iso , so you force to boot in Bios mode,
    for that you CANT restore GRUB in UEFI , and you CANT install bios on GPT

question 1 : are you using a USB live iso ?
question 2 : is it a ventoy install or something else
question 3 : in case of ventoy without GPT and efi ( see ventoy -h) , can you get another USB live iso with GPT and Efi boot?

you have to boot your USB live iso in UEFI for Restore GRUB in UEFI.