New answers tagged

0

That is exactly what grub2-once does. Please try it. shiraz-1:~/:[0]# grub2-once --list 0 SLES 15-SP1 1 Advanced options for SLES 15-SP1>SLES 15-SP1, with Linux 4.12.14-195-default 2 Advanced options for SLES 15-SP1>SLES 15-SP1, with Linux 4.12.14-195-default (recovery mode) 3 Advanced options for SLES 15-SP1>SLES 15-SP1, with ...


0

Thanks to @rtaft and @mook765 for helping. I'm not very experiencing in grub internals, and actually I don't have much desire to read tons of documentation. In my case I have to HDD: /dev/sda - Debian /dev/sdb - Ubuntu. Both of these have their own copy of /boot/grub/grub.cfg. Let's say I login to Debian now, it means all commands like sudo grub-update ...


0

This is currently still an open issue at zfsonlinux/grub but I have posted a workaround there (and here) thanks to the github user tterpelle: What we are going to do is grabbing the grub scripts from Ubuntu 19.04 for our Ubuntu 18.04. Download grub-common_2.04-1ubuntu12_amd64.deb from https://packages.ubuntu.com/eoan/amd64/grub-common/download and extract ...


0

On pepperment "xubuntu" the simple copy of grub will not work when you switch boot from Bios, as sdb which has the grub copy became sda and many error messages then stop, however switching back will work with some error messages of files not found at where expected.


0

I was seeing this problem while trying to install Ubuntu yesterday after a run with MX Linux. Tried multiple OSes, partition options, and ways of creating the LiveUSB I was using. Turned out I had too many entries in the EFI portion of the NVRAM on my motherboard (nothing to do with the SSD or install options). I was able to fix it by opening a terminal ...


1

As to the login screen: try a static X11 configuration by creating a file /etc/X11/xorg.conf.d/10-monitor.conf with content such as Section "Device" Identifier "Configured Video Device" Driver "intel" EndSection Section "Monitor" Identifier "Configured Monitor" EndSection Section "Screen" ...


0

The Windows partition should be called (Windows SyS Drive) in Gnome Disks in Ubuntu!


0

I have looked at the images and the video, and we are talking about a very common error regarding ACPI BIOS, it allows you to discover computer hardware components and solving this error is not easy because it varies depending on the device in use. Here are the three main methods that are right for me, but don't follow all these methods, make sure that what ...


0

its sad no one helped here. in general I see a little help from the community for the crazy people who want to start a xen guest.


0

In my case, I had an Xubuntu 18.04 VM and after upgrading to 20.04, got the grub error. So I followed what's described here, which is for Kali, but should work for any Linux / grub installation: Using an Ubuntu / Xubuntu ISO Live enter live mode (I used Ubuntu 20.04 since I had it already downloaded in my computer). Once inside, I opened a terminal and ran:...


0

seems to be a widespread problem. you might look into this post: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835660 Somebody there suggests to change lz4 to gzip (comment #73) in the file mentioned by you /etc/initramfs-tools/initramfs Pls update because I have the same problem


0

That is going to take a LONG time and it is going to warn you that it is risky because it has to move 3 partitions to the right (the swap and two microsoft partitions)... If the unallocated space was on the right directly next to the partition you wanted to grow, then it ('shifting it to the left') would go fairly fast and with less risk.... BUT it is an ...


1

This behaviour is experienced in both Ubuntu 18.04 and 20.04 and even though some of the other answers has solutions that work as expected, either files that has on the header an "do not edit this file" notice such as the /boot/grub/grub.cfg are manually edited, or the changes are not persistent after system updates or regenerating grub ...


0

None at all. The installation is automated, so the bootloader settings and such will be configured by themselves. The only thing that will be different in the boot process is an OS picker, where you can choose to boot into Lubuntu or Windows.


1

If you look in /etc/default/grub, you'll find a GRUB_BADRAM= parameter where you can identify what bad memory locations there are. # Uncomment to enable BadRAM filtering, modify to suit your needs # This works with Linux (no patch required) and with any kernel that obtains # the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...) #GRUB_BADRAM=&...


0

Add GParted menuentry to GRUB If all else fails, put your GParted ISO in a folder named ISOs in the root directory and boot using GRUB2 and the following menuentry: menuentry "GParted 64-bit ISO" { set root=(hd0,1) set isofile="/ISOs/gparted-live-1.1.0-5-amd64.iso" loopback loop $isofile linux (loop)/live/vmlinuz boot=live config ...


1

Thanks @PonJar for the link. Using askubuntu.com/questions/1028375/deleted-ubuntu-efi I was able to fix it. If you face this error grub-install: error: /boot/efi doesn't look like an EFI partition during grub installation step, just do mount /dev/sdaxy /boot/efi again. This will fix it.


0

I finally managed to fix it. It was a long ride. I think (while I'm not sure) that it was due to several issues : Grub that installed both as UEFI and Legacy boot Corrupted Grub that would not entirely uninstall, and would generate bad configuration files at each update Corrupted EFI partition resulting from attemps to fix it Corrupted kernel headers in my /...


0

This thread didn't solve my problem. I had to add pci=nomsi just before resume=. take a look at this: Ubuntu 16.04 doesn't hibernate


1

I recently had the exact same issue with Kubuntu 20.04. The problem is that the /boot partition has run out of spare space to update the kernel properly. Hence it repeatedly fails on each retry (i.e. sudo apt upgrade). You can check this by running df-H and if the Avail space is low (say under 100MB) for the /boot mount then you may run into the issue you ...


0

I had this issue and fixed it accidentally. I restarted my computer and before letting anything happen, I held F2 , F10 and F12. Pretty sure one of them did the job, but I don't know which one. I hope this works for you, too.


0

Lets see details, use ppa version with your live installer (2nd option) or any working install, not older Boot-Repair ISO: Please copy & paste the pastebin link to the Boot-info summary report ( do not post report), do not run the auto fix till reviewed. https://help.ubuntu.com/community/Boot-Repair Your "Windows" boot entry was modified to ...


0

So Yeah I had resolved this few days ago just wanted to post and update how I resolved it. Narrow down the problem. Step1: I removed the old HDD from the laptop now only SSD was available. Step2: I made the /dev/sda2 as NTFS and marked a boot flag on it. After that, I tried multiple times recommended boot repair by ubuntu but that didn't help and it ...


2

Booting ISO files Ubuntu 20.04 rmmod tpm is necessary for booting ISO files with Ubuntu 19.10 and later, (due to the use of GRUB 2.04. You might also want to get rid of the Disk Check every boot and maybe speed things up by booting toram, (optional). menuentry "Ubuntu 20.04 ISO" { rmmod tpm set root=(hd0,3) set isofile="/isos/...


0

Those additional options (toram) are related to casper, which is a ramfs wrapper I believe. http://manpages.ubuntu.com/manpages/focal/man7/casper.7.html toram attempts to place the ISO in its entirety into memory. It's almost always better to do this. You can even remove the USB drive after it's booted. Other options are kernel parameters and boot ...


0

grub-pc's postinst decides whether to ask this question. In my case, I've tracked it down to the following condition: elif test -z "$2" || test -e /boot/grub/core.img || \ test -e /boot/grub/i386-pc/core.img || \ test "$UPGRADE_FROM_GRUB_LEGACY" || test "$wubi_device"; then So if /boot/grub/...


2

I found the solution to my problem. It was as simple as pcie_aspm=off.


1

windows require an exFAT and installs from NFTS, Ubuntu is ext4 3 2 and exFAT and install from FAT64 or FAT32, and Manjaro is ext4 3 2 and exFAT and install from FAT 32 but this should not be a problem but if you are having trouble with choosing the OS from boot that is a different question. EDIT: if you are having trouble with loading the other OSes then ...


1

There is an issue with terminus (and bitmap fonts in general) in recent Ubuntu. The issue is of both technical and personal nature. Technical part is that old formats of bitmap fonts are difficult to maintain, so pango developers decided to drop them. Political part is that many people believe that for hi-dpi monitors pixel fonts are no longer needed, so ...


0

(Shameless plug) There is Matter which is a customizable theme. It is a quick way to have a decent looking grub, with the possibility to customize some of its parts if you want to.


0

One way to make this fully automated is to make a script that makes regex replacements in your auto-generated grub.cfg to add the --classes you want. And then modifying grub-mkconfig (/usr/sbin/grub-mkconfig in Ubuntu derivatives) to run it at the end. I use this idea on Matter, a grub theme/tool that you may like (shameless plug). Based on that, you could ...


0

Here is what I did to solve the problem. The first solution might be required, but it might be worth testing if you have the same problem. I reinstalled Ubuntu following this answer to create a second EFI part for my Linux to boot independently from Windows: https://askubuntu.com/a/843649 I also disabled fastboot and secure boot previously as said in this ...


0

I just formatted my original ubuntu partition and them booted from the external hard disk restored partition. It booted !!!


1

A hard reset can sometimes break a system quite badly and damage the file system. You managed to bring your system back to life, but that does not ensure that all damage is repaired. The most secure way to revert to an integer system would be to fully reinstall, i.e., back up user data, reinstall fresh and put the data back. Second possibility, less sure, it ...


0

I can't guarantee that it works for every error of this kind but you ought to be able to use your Ubuntu USB if it is a Live Ubuntu USB. In that case: Boot from your Live USB stick and select “Try Ubuntu”. Open a terminal and enter the following commands: sudo add-apt-repository -y ppa:yannubuntu/boot-repair sudo apt-get update sudo apt install -y boot-...


1

BIOS HP Probook 640 G1 You have BIOS version 1.47. A newer BIOS is available, version 1.50, and can be downloaded here. Note: Some HP computers allow you to update the BIOS directly from your current BIOS. Note: Verify that I have the correct web page for your model #. Note: Have good backup before updating the BIOS. efibootmgr Regarding the boot problem... ...


0

I had the same problem is an old notebook when trying to install ubuntu. the solution was to take it apart and clean the sata port. then everything worked correctly.


0

With BIOS & gpt partitioned drives, you need a bios_grub partition for grub to correctly install & boot. You can create the tiny 1 or 2MB unformatted partition with bios_grub flag if using gparted/parted or use code ef02 if using gdisk to create it. It can be anywhere within the first 2TiB of your drive. Do not really know RAID, but you probably need ...


2

With BIOS and multiple drives, you do not run the auto fix in Boot-Repair as you do not want one grub in every MBR. You really want Windows BIOS boot loaders in MBR of sda & sdb as those are Windows only drives and grub only in sdc. Grub also only boots working Windows 10, so after Windows updates which turn fast start up back on, you normally have to ...


1

Do you get the Grub screen when you boot. If so then boot with the oldest kernel you have. If that fails then drop to recovery, enable networking and then update and upgrade and then sudo dpkg --configure -a. and or sudo apt install -f


3

LUKS or Full Encryption Options in the Installer Install to USB as you would to HDD. It is recommended that you remove the HDD before proceeding, especially in UEFI mode. They have done a good job of hiding encryption options in the Live installer. It is located on the install page, just above Something else. Tag "Erase disk and install Ubuntu" and ...


0

Creating a Full install USB the Easiest way Download Image File: https://phillw.net/isos/linux-tools/uefi-n-bios/dd_unb_ubuntu-20.04_15GB_2020-06-26.img.xz Download Rufus: https://github.com/pbatard/rufus/releases/download/v3.11/rufus-3.11.exe Double click Rufus exe file. Select USB2 Target drive in Rufus. Select Image File in Rufus. Click Rufus start ...


0

Okay i solved the problem with this commands: sudo add-apt-repository ppa:yannubuntu/boot-repair sudo apt-get update sudo apt-get install -y boot-repair && (boot-repair &)


1

If you delete Windows thoroughly then it should also vanish from the Grub menu after sudo update grub (or after a kernel update, which uses the same command eventually). In some cases it might leave an entry in the UEFI menu but that shouldn't be hard to delete.


1

I've encountered this problem after playing with my Intel drivers on my laptop. I used a third-party PPA to install the drivers and that went wrong, since I only had one graphics card, the integrated one, I couldn't boot. To solve the issue I've booted in recovery mode, removed the third party PPA and reinstalled the drivers. sudo dpkg --purge --force-all ...


0

I do it using YUMI Multiboot USB creator (you can download it from Pendrivelinux.com). It is used to put multiple operating systems on 1 pen drive. I have one that is set up for UEFI and one that is set for Legacy BIOS (Version YUMI-2.0.7.2 is legacy, version YUMI-UEFI-0.0.2.3 for UEFI (obviously). This has worked for me on older systems, if I wish a legacy ...


0

I did not determine what was wrong, but the Ubuntu boot repair tool seemed to fix things.


2

Since you have windows installed it might have over written boot loader. try grub-install /dev/sdX, where /dev/sdX is the drive where your boot partition resides. If you are able to boot into Ubuntu then run and then sudo os-prober and finally sudo update-grub. This should solve the problem. Post the results after doing the above. If you are not able to boot ...


0

Sometimes, it is actually due to having the installer and the OS in the same computer but in different disks and you are booting from the OS. It can not properly detect which is the OS and therefore gives you a GRUB menu. This mostly happens in Android x86. If this happens, please eject the installer disk. If it still happens even if you have ejected it or ...


0

From the comments... Normally, on UEFI computers, disks are formatted with GPT partition tables (mandatory on disks 2TB or larger). Normally, on multi-boot computers, operating systems are installed the same way, that is, UEFI/GPT, or BIOS/MBR. You had your Windows SSD (/dev/sda) as GPT, but your Ubuntu SSD (/dev/sdb) as MBR. This caused GRUB to get confused....


Top 50 recent answers are included