Unclear problem

It had to happen…

I was forced to update, which i wasn’t going to until the weekend.

Now the GRUB is gone.

Cannot enter TTY2.

Trying not to panic.

I thought I had made the necessary steps prior to sudo update -a

I updated GRUB before restarting my machine.

I looked into PRESETS=(‘default’ ‘fallback’) - it was correct.

I was mistaken - thats when haste happens.

WIndows 11 UEFI dual boot here. Secure Boot disabled.

There is a command under W11 to fix it, I tried but it didn’t work.

I think it cannot be done simply going into the Boot section and changing the boot priority:

1Windows Boot Manager

2 HDD

3 block*block

Please help.

Please take around 10-20 deep breaths, and tell us again what your issue is.

Be clear, be precise, so that others can help you without needing a :crystal_ball:.

To start with, please provide your system information as described (below) – I’m sure someone will help as soon as they are able to.

Regards.


What follows is from a standard template.

Welcome to the Manjaro community

As a new or infrequent forum user, please take some time to familiarise yourself with forum requirements, and the many ways to use the forum to your benefit.

Note: By virtue of using the Manjaro forum you acknowledge and agree to follow Rules and Guidelines outlined; so, you really should read them:

Required Reading
Highly Recommended

Work with us, not against us

It is important to provide as much actionable information as possible in your first post, rather than simply indicating there is a problem. Please also be prepared to provide output from commands if/when asked.

Simply waiting for others to ask you questions is counter-productive – typically, nobody has a :crystal_ball: at their disposal – and your clear, concise and accurate input is often relied upon in order to help you.

Please help others to make informed suggestions based on information you provide.


System Information

While information from *-fetch type apps might be fine for someone wishing to buy your computer, for Support purposes it’s better to ask your system directly; :eyes:

Output of the inxi command (with appropriate parameters, and formatted according to forum guidelines) will generate information useful for those wishing to help:

Suggested inxi command (use either):

inxi -zv8 (short-form)
inxi --filter --verbosity=8 (long-form)
inxi man pages (manual)
If running `inxi` within a `chroot` environment
  • Add --color=0 to the long-form command, or…
  • Change the short-form command to inxi -zv8c0
Your privacy is respected

Update Announcements


Technical Resources


1 Like

I cannot enter TTY by means of command Ctr+Alt+F2 or F3

My only option is to boot into Windows 11,

I need a flash drive with a bootable Manjaro to fix this - am I correct?

In such case - yes.

Without knowing the state of your system, all responses are tentative, at best.


1. It’s preferable to install using the latest available ISO. The ISOs on the “Download” page are still the old ISOs, but you can download the currently recommended Stable ISO from:


2. Also recommended – Create a Ventoy USB (A new bootable USB solution)

  • There is a Windows version of Ventoy – a Ventoy USB can be created in Windows. :eyes:

3. Important – Read through the Stable Update Announcement thread – particularly the Known Issues and Solutions section – before installing:

4. A final note – Manjaro now defaults to the btrfs filesystem:

You might prefer to still use the ext4 filesystem, in which case you must pay careful attention during install, and make sure to manually select ext4. Likewise with your preferred swap.


The following links may be helpful:

1 Like

You probably have mismatching EFI stubs, or put differently, /boot/efi/EFI/boot/bootx64.efi and /boot/efi/EFI/Manjaro/grubx64.efi should be identical, and they’re not.

The way to fix this is to install the install-grub script, which can be run manually but will also be run automatically after each major update.

Follow the instructions to boot up from a live USB and chroot into your installed system. Then, in the chroot, run… :backhand_index_pointing_down:

pacman -S install-grub && install-grub

Reboot and cross your fingers. :wink: :crossed_fingers:

1 Like

Am I doing it the right way here:

 **\~**  manjaro-chroot -a                                                                              ✔
grub-probe: error: cannot find a GRUB drive for /dev/sda1.  Check your device.map.
grub-probe: error: cannot find a GRUB drive for /dev/sda1.  Check your device.map.
**==> Mounting (ManjaroLinux) \[/dev/nvme0n1p6\]**
 **→ mount: \[/mnt\]**
 **→ mount: \[/mnt/boot/efi\]**
**\[manjaro /\]#** pacman -S install-grub && install-grub
resolving dependencies…
looking for conflicting packages…
>
Packages (1) install-grub-2:2.14rc1-3
>
Total Download Size:   0.01 MiB
Total Installed Size:  0.01 MiB
>
:: Proceed with installation? \[Y/n\]

Moderator edit: In the future, please use proper formatting: [HowTo] Post command output and file content as formatted text

2 Likes

Looks good to me. :smiley:

2 Likes

I wish to stay double-secured here… bear with me guys. RESTART now?


>
:: Proceed with installation? \[Y/n\] y 
:: Retrieving packages... 
 install-grub-2:2.14rc1-3-x86_64         5.8 KiB  58.9 KiB/s 00:00 \[####################################\] 100% 
(1/1) checking keys in keyring                                     \[####################################\] 100% 
(1/1) checking package integrity                                   \[####################################\] 100% 
(1/1) loading package files                                        \[####################################\] 100% 
(1/1) checking for file conflicts                                  \[####################################\] 100% 
(1/1) checking available disk space                                \[####################################\] 100% 
:: Processing package changes... 
(1/1) installing install-grub                                      \[####################################\] 100% 
:: Running post-transaction hooks... 
(1/2) Arming ConditionNeedsUpdate... 
(2/2) Refreshing PackageKit... 
Error connecting: Could not connect: No such file or directory 
error: command failed to execute correctly 
Grub will be installed on: EFI 
Installing for x86_64-efi platform. 
Installation finished. No error reported. 
Update UEFI Fallback file: /boot/efi/EFI/Manjaro/grubx64.efi 
Generating grub configuration file ... 
Found theme: /usr/share/grub/themes/manjaro/theme.txt 
Found linux image: /boot/vmlinuz-6.12-x86_64 
Found initrd image: /boot/intel-ucode.img /boot/initramfs-6.12-x86_64.img 
Found linux image: /boot/vmlinuz-6.1-x86_64 
Found initrd image: /boot/intel-ucode.img /boot/initramfs-6.1-x86_64.img 
Warning: os-prober will be executed to detect other bootable partitions. 
Its output will be used to detect bootable binaries on them and create new boot entries. 
ERROR: mkdir /var/lock/dmraid 
grub-probe: error: cannot find a GRUB drive for /dev/sda1.  Check your device.map. 
grub-probe: error: cannot find a GRUB drive for /dev/sda1.  Check your device.map. 
Adding boot menu entry for UEFI Firmware Settings ... 
Root filesystem isn't btrfs 
If you think an error has occurred, please file a bug report at " https://github.com/Antynea/grub-btrfs " 
Found memtest86+ image: /boot/memtest86+/memtest.bin 
/usr/bin/grub-probe: warning: unknown device type nvme0n1. 
done 
Warning: GRUB bootloader at '/boot/efi/EFI/Manjaro' was updated. 
Your booted entry '' is not the same as 'Manjaro'. 
This may be a rescue ISO, but if not check your EFI boot priority. 
**\[manjaro /\]#** 
>

Moderator edit: In the future, please use proper formatting: [HowTo] Post command output and file content as formatted text

Yes. But keep the live USB handy, just in case. :wink:

1 Like

I have removed the bootable USB,

I don’t see the GRUB

I cannot choose between Manjaro and W11

Secure boot - Disabled

Fast Boot - disabled

Boot Priority:

1 Windows Boot Manager

2 HDD SAmsung

3 block*block

Gentlemen, I failed. What can be done now?

I’d try moving Windows Boot Manager down the priority list. :slight_smile:

1 Like

I am taking a bow here…

Good night

1 Like

Boot up from the USB stick again and do the chroot again. Then, inside the chroot environment, bring up /etc/default/grub in nano. :backhand_index_pointing_down:

nano /etc/default/grub

Make sure that the third line near the top of the file reads… :backhand_index_pointing_down:

GRUB_TIMEOUT_STYLE=menu

… and not:backhand_index_pointing_down:

GRUB_TIMEOUT_STYLE=hidden

If you had to change the file, then you must save it — CtrlS, and CtrlX to leave nano. Then, run… :backhand_index_pointing_down:

update-grub
2 Likes

Gents,

What else can I say besides pinpointing your wisdom and patience, patience above all wink