So I have win 11 and pop os dual installed on the same drive. I switched between them from boot menu, but suddenly I couldn't find pop os in the menu, probably because of my corrupted USB flasg drive I removed without ejecting while it was getting scanned by a badblocks command. I tried to access my pop os partition from windows through a program, and my files were there but the /boot/efi folder was empty.So I'm trying to add a new bootloader in the ESP That was already there by trying to install new pop os, but without erasing my root partition. But I'm afraid to continue sinvlce the option says erase and install. Do you think I should continue?

I would like to make the menu titles of grub2 shorter for them to fit in my theme. Namely, Fedora 38 rescue instead of Fedora Linux (0-rescue-7ad84fe099814e3388129347d2a46891) 38 (KDE Plasma) and Fedora 38 (6.2.13-300) instead of Fedora Linux (6.2.13-300.fc38.x86_64) 38 (KDE Plasma) If I am not mistaken, I should need to edit by hand the file /etc/grub.d/10_linux, which is not a trivial task. And, more importantly, this file will be changed by an update of grub2-tools package. This is not practical, I want a 'maintenance free' thing. Is there any way to configure a different grub2 menu title in a persistent way? I use the 40_custom file for my menu entries, but the kernel entries are handled automatically.

I've recently installed Deepin by creating a partition on my SSD (50% each). I already had Windows 10 installed, then I installed Deepin 20.3 from a bootable USB and it went without a problem. When the installation finished I had to restart it (as requested by Deepin). The problem is that now I don't get any boot menu or anything like that - Windows automatically boots up without any way to change it. I'm using an old Optiplex 3

I am UEFI dual booting Win 10 with Manjaro using Grub2. Here are my bootloaders: [flex@mylaptop ~]$ efibootmgr --verbose BootCurrent: 0001 Timeout: 0 seconds BootOrder: 0001,0004,0000 Boot0000* Windows Boot Manager HD(1,GPT,91383c96-901f-403a-8de5-363c8eb6f581,0x800,0x32000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)RC Boot0001* Grub Menu HD(1,GPT,91383c96-901f-403a-8de5-363c8eb6f581,0x800,0x32000)/File(\EFI\manjaro\grubx64.efi) Boot0002* UEFI Onboard LAN IPv4 PciRoot(0x0)/Pci(0x1c,0x0)/Pci(0x0,0x0)/MAC(qwerty123,0)/IPv4(0.0.0.00.0.0.0,0,0)RC Boot0003* UEFI Onboard LAN IPv6 PciRoot(0x0)/Pci(0x1c,0x0)/Pci(0x0,0x0)/MAC(qwerty123,0)/IPv6([::]:[::]:,0,0)RC Boot0004* Windows Boot Manager HD(1,GPT,91383c96-901f-403a-8de5-363c8eb6f581,0x800,0x32000)/File(\EFI\manjaro\grubx64.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...6................ By the way what's with all those extra characters at the end of the Boot0004* Windows Boot Manager entry? The two Windows Boot Manager entries get auto generated, I didn't make them. I only made the Grub Menu using efibootmgr. When I let the laptop boot itself I get the Grub menu just fine I guess because this bootloader is loaded because it points to Grub: Boot0001* Grub Menu HD(1,GPT,91383c96-901f-403a-8de5-363c8eb6f581,0x800,0x32000)/File(\EFI\manjaro\grubx64.efi) However if I hit F12 to get in to the BIOS and then select the same "Boot0001* Grub Menu" bootloader from there then the Grub Menu will not show. When the timeout expires the last OS that I had selected from the Grub menu loads. It's like the graphics don't work in Grub when I select a \EFI\manjaro\grubx64.efi bootloader manually from the UEFI BIOS bootloader select menu screen. I can see a think line at the top of the screen with garbled text... but no Grub Menu. Is this a limitation of my BIOS firmware maybe? I tried re-creating the "Boot0001* Grub Menu" bootloader entry as "Boot0001* Windows Boot Manager" but I get the same result. I also tried various things in the Grub config file such as with the fx graphics (currently set to auto) but that didn't make any difference either. This is my /etc/default/grub GRUB_DEFAULT=saved GRUB_TIMEOUT=5 #GRUB_TIMEOUT_STYLE=hidden GRUB_TIMEOUT_STYLE=menu GRUB_DISTRIBUTOR="Manjaro" GRUB_CMDLINE_LINUX_DEFAULT="quiet apparmor=1 security=apparmor udev.log_priority=3" #GRUB_CMDLINE_LINUX_DEFAULT="apparmor=1 security=apparmor udev.log_priority=3" GRUB_CMDLINE_LINUX="" # If you want to enable the save default function, uncomment the following # line, and set GRUB_DEFAULT to saved. GRUB_SAVEDEFAULT=true # 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 #GRUB_ENABLE_CRYPTODISK=y # Uncomment to use basic console #GRUB_TERMINAL_INPUT=console # Uncomment to disable graphical terminal #GRUB_TERMINAL_OUTPUT=console # 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' GRUB_GFXMODE=auto #GRUB_GFXMODE=1024x768 # Uncomment to allow the kernel use the same resolution used by grub GRUB_GFXPAYLOAD_LINUX=keep # 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" #GRUB_DISABLE_LINUX_UUID=true # Uncomment to disable generation of recovery mode menu entries GRUB_DISABLE_RECOVERY=true # Uncomment this option to enable os-prober execution in the grub-mkconfig command GRUB_DISABLE_OS_PROBER=false # Uncomment and set to the desired menu colors. Used by normal and wallpaper # modes only. Entries specified as foreground/background. GRUB_COLOR_NORMAL="light-gray/black" GRUB_COLOR_HIGHLIGHT="green/black" # Uncomment one of them for the gfx desired, a image background or a gfxtheme #GRUB_BACKGROUND="/usr/share/grub/background.png" GRUB_THEME="/usr/share/grub/themes/manjaro/theme.txt" # 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: https://wiki.archlinux.org/index.php/Fsck#Boot_time_checking #GRUB_ROOT_FS_RO=true **My question** How can I make the Grub menu appear when I select Boot0001* Grub Menu OR Boot0001* Windows Boot Manager from the UEFI BIOS bootloader menu? Thank you in advance!

Following on the ["maintenance free" question here](https://ubuntuforums.org/archive/index.php/t-2076205-p-3.html) , I know there are ways to automatically generate grub2 menu entries, but I need to manually edit/add them from time to time, like - to a live-Linux system, or - when adding a new ISO boot entry (that exists on another disk). Almost all grub2 intro docs use the form of set root=(hd2,gpt7) which I know will fail in my case, as I need to shuffle my HDs around between my machines from time to time, and the above format will surely break when that happens. Despite the likelihood that [I can't specify my root fs with a UUID](https://unix.stackexchange.com/questions/93767/) (and [failed here](https://ubuntuforums.org/showthread.php?t=1373394) too), I don't want to use UUID either, because when I format a partition (when installing a new OS), that partition's UUID will change. So what are the better options? 1. Foremost, the **GPT partition label** is the best candidates, as I can make sure they are unique throughout all my machines, even when I shuffle my HDs around. However, [there seems to be problem doing that](https://serverfault.com/questions/713698/) : _"I'm unable to mount the device using PARTLABEL"_. But, it should be promising, as I can [see](https://unix.stackexchange.com/a/93777/374303) > Since 4.20, there's also support for PARTLABEL , which I think is really convenient. Perhaps update the answer. – equaeghe Jan 20 2. Second best would be **PARTUUID**. However, there are some confusing/conflicting answers floating on the Internet. * [Here](https://unix.stackexchange.com/a/151483/374303) it says the format is PARTUUID=SSSSSSSS-PP, but it doesn't give an example what exactly it looks like, * the [next answer](https://unix.stackexchange.com/a/93777/374303) gives an example but it says the format is root=PARTUUID=666c2eee-193d-42db-a490-4c444342bd4e So, would using PARTLABEL or PARTUUID possible with the latest grub2?

I use **systemd-boot** as boot manager. I have the menu with many entries but 90% of time I choose entry #3. Is there a way to hide the menu as default? In this way when I want to boot #3, it skips timeout and menu is not shown. While if I want to choose anything else, keep pressing a key i.e. shift to show the menu?

I was using CentOS 8 in my Laptop dual with Windows 10 Pro, recently I made an update and the Menu is not shown, only boot on Windows 10 Pro directly. The Boot Mode Originally was in UEFI mode. I don't changed! I changed the Boot Priority Order From To I restarted, But the Menu doesn't appears! Later, I selected Legacy Options Restarted, but it change doesn’t works This one doesn’t work either. Originally Security Boot was Enabled Later I disabled some Security options like: Security Boot and Security Chip I update to Disabled I would like to recover the menu, in order to select which OS I want to use (CentOS 8, or Windows 10 PRO). Unfortunately, that Changes doesn't works! My Laptop is a Lenovo, but I'm not sure what BIOS settings I need to select in order to recover the Menu. **What settings boot options should I select?** Thanks for your Help. **EDIT 3**: Previously I had this settings https://unix.stackexchange.com/q/654060/400726 And I had the previous Issue https://unix.stackexchange.com/q/607292/400726 Now I have C:\Users λ bcdedit /enum firmware Firmware Boot Manager --------------------- identifier {fwbootmgr} displayorder {1fa1f7db-9958-11ea-a843-806e6f6e6963} {1fa1f7e0-9958-11ea-a843-806e6f6e6963} {bootmgr} {1fa1f7dd-9958-11ea-a843-806e6f6e6963} {1fa1f7de-9958-11ea-a843-806e6f6e6963} {1fa1f7df-9958-11ea-a843-806e6f6e6963} {1fa1f7e1-9958-11ea-a843-806e6f6e6963} {1fa1f7e2-9958-11ea-a843-806e6f6e6963} {1fa1f7e3-9958-11ea-a843-806e6f6e6963} timeout 0 Windows Boot Manager -------------------- identifier {bootmgr} device partition=\Device\HarddiskVolume1 path \EFI\Microsoft\Boot\bootmgfw.efi description Windows Boot Manager locale es-ES inherit {globalsettings} default {current} resumeobject {a8801e99-ce19-11ea-aa82-c858c03abd0c} displayorder {current} toolsdisplayorder {memdiag} timeout 0 Firmware Application (101fffff) ------------------------------- identifier {1fa1f7d9-9958-11ea-a843-806e6f6e6963} description Setup badmemoryaccess Yes Firmware Application (101fffff) ------------------------------- identifier {1fa1f7da-9958-11ea-a843-806e6f6e6963} description Boot Menu badmemoryaccess Yes Firmware Application (101fffff) ------------------------------- identifier {1fa1f7db-9958-11ea-a843-806e6f6e6963} description NVMe: SKHynix_HFM512GDHTNI-87A0B badmemoryaccess Yes Firmware Application (101fffff) ------------------------------- identifier {1fa1f7dc-9958-11ea-a843-806e6f6e6963} description UEFI Diagnostics badmemoryaccess Yes Firmware Application (101fffff) ------------------------------- identifier {1fa1f7dd-9958-11ea-a843-806e6f6e6963} description ATA HDD: badmemoryaccess Yes Firmware Application (101fffff) ------------------------------- identifier {1fa1f7de-9958-11ea-a843-806e6f6e6963} description ATA HDD: badmemoryaccess Yes Firmware Application (101fffff) ------------------------------- identifier {1fa1f7df-9958-11ea-a843-806e6f6e6963} description ATAPI CD: badmemoryaccess Yes Firmware Application (101fffff) ------------------------------- identifier {1fa1f7e0-9958-11ea-a843-806e6f6e6963} description USB HDD: SanDisk Ultra Fit badmemoryaccess Yes Firmware Application (101fffff) ------------------------------- identifier {1fa1f7e1-9958-11ea-a843-806e6f6e6963} description PCI LAN: badmemoryaccess Yes Firmware Application (101fffff) ------------------------------- identifier {1fa1f7e2-9958-11ea-a843-806e6f6e6963} description USB FDD: badmemoryaccess Yes Firmware Application (101fffff) ------------------------------- identifier {1fa1f7e3-9958-11ea-a843-806e6f6e6963} description USB CD: badmemoryaccess Yes C:\Users λ **EDIT 2**: I was using a USB3.0 HDMI Video Capture, I'm using OBS I was able to record a video when I tried to check with https://sourceforge.net/projects/supergrub2/files/2.04s2-beta2/super_grub2_disk_2.04s2-beta2/supergrub2-2.04s2-beta2-multiarch-USB.img.zip/download Here the videos. https://drive.google.com/file/d/1fpidK2-fujdPwT7PhoFL40cuRfy8rPQ6/view https://drive.google.com/file/d/1IHiZBCssViHakxLly3HudC4eKiShvAzM/view **NOTE 1**: I have access to Read/Write from Windows 10 over Linux Partitions using EXT4 FileSystem.

I installed several operating systems on my computer in a multiboot configuration (Ubuntu, Linux Mint, Windows, ...). When I turn on my PC, the boot menu appears with a timeout. Sometimes, I don't focus on it (I turn on my PC and then I go to the fridge to get a soft drink, for example) so that I miss the boot menu so I cannot chose my desired OS. Because of that, I must restart my computer and choose my desired OS again. Is there anyway to remove the timeout. I mean when the boot menu appear, so that there is no timeout, no OS will boot until I chose my desired OS. I am using Ubuntu and Linux Mint.

The patch notes of Mint 19.3 showed [this new boot menu](https://www.linuxmint.com/pictures/screenshots/tricia/grub.png) . I've upgraded from 19.2. However I don't see the new boot menu but just the good ol' minimal GRUB. I even ran sudo grub-update but nothing changed. How do I change this?

I am trying to boot Linux from my usb drive but it doesn't seem to show USB as an option in the bios or boot menu. pics of bios and boot menu ! Any help would be appreciated!

I'd like to edit the Grub menu that comes up, to move one line and remove others. I have an Inspiron 1420 that came with Ubuntu 7.10. When it needed a new drive, I installed Windows 7, the original OS, and then it seemed that 10.04 wanted its own partition. I probably should have checked exactly what I was doing first (famous last words). What I'd like to do is remove the 7.10 lines entirely, so I can blow away everything in that partition and use it as /home for 10.04. I'd also like to move the Windows 7 line up to second from the top, so booting in Windows would be a quick two keystrokes rather than following the line all the way down. Hitting the Grub edit key came up with unclear instructions, and since this is the boot loader I'd kind of rather not screw it up too bad. So, what's the best way to do this?

I have just updated a remote machine which is running Ubuntu Server 12.04. I have only access through SSH and now it's asking for a reboot. I'm guessing a new kernel was installed. I need to make it boot in a very specific kernel, otherwise it will just hang. Is there any way to check (from the command line, since I am connecting through SSH) what GRUB2 is going to do on the next reboot? I mainly need to make sure that: 1. The machine is going to boot on the right kernel (Which now may have been moved into the "Previous Linux Versions" submenu) 2. The GRUB2 menu is going to "obey" my timeout request (in some occasions I found machines that would just get stuck with the GRUB2 boot menu, despite of having a GRUB_TIMEOUT parameter specified in /etc/default/grub) So is there any way to "simulate" or diagnose what GRUB2 is going to do on the next reboot? Some way to check things like "*It is going to boot kernel yaddayaddayadda and it has a timeout activated of yadda seconds*" I know it's a long shot, but maybe there is something like a diagnose tool (which is going to have to be command line... I don't even have X-Windows on the computer I'm connecting to) Thank you in advance!

I have a couple of years of experience with ubuntu, but this is my first time with a non-ubuntu based distribution. I managed to successfully install Crunchbang from a bootable usb stick, created with unetbootin (my hom laptop's cd drive is dead) and at the end of installation, it asked me whether I wanted to install grub. It said that it detected the windows operating system that was already there and that it should be fine if all my operating systems are listed. So, I let it install grub and now when I boot into my machine only a couple of Crunchbang listings appear in the grub boot menu. My windows has become inaccessible. With the little experience I had, I tried to look for the menu.lst file which I expect to list the entries that would be shown in the grub boot menu. But I couldn't find that file. Perhaps crunchbang puts it in a different location? I want to get my windows be listed in the grub boot menu. Any ideas? **Edit:** From a comment on the question https://unix.stackexchange.com/questions/1578/editing-grub-menu I came to know the location of the boot menus, as /boot/grub/grub.cfg and that file exists on my crunchbang system. I now need to know how and what to add to it to get my windows. **Edit 2:** From the same question as above, I learned to do sudo update-grub which did put my windows entry in my grub boot listing and everything is fine. But I would still like to know... why wasn't it there initially when crunchbang did detect it and said that it would be added. Thanks.