![]() This iso file can be cloned directly into a USB drive to make a bootable memtest86+ system and it works both in UEFI mode and the old BIOS mode alias legacy mode.Įdit 2: I saved this page, so I know how to do it when I get rid of Windows.Memtest86+ version 6 (and newer) can be downloaded as a standalone zip file, which contains an iso file. From Kubuntu I could export my 'nf´ to the 'My Documents'-partition ( NTFS, so Win10 can read that ) and imported it in Grub2Win. ![]() What I did is install Grub2Win in my Win10 installation. Like Organic Marble commented 'MBR doesn't sound right for a UEFI system', he is right. I had my Windows Bootloader in partition 1 and grub2 in another EFI partition ( 8 )( didn't want to mess up Windows Bootloader ), so every time I wanted to use my Kubuntu ( daily ) or Mint OS I had to press F11, wait, select USB ( don't ask me why ), select Ubuntu, then wait again for Grub and then select my Linux based OS. I don't use Linux based OS's that long ( 7 or 8 months now ), and if I have to write everything down to use in the command-line, it not only takes a long time ( mostly the writing down ), but I can make errors that way. I know some of you don't like this program, but in some cases it comes in very handy ( renaming Ubuntu in Kubuntu ( don't have to do that in 'etc/grub.d/10_Linux_Proxy' ), add a theme, or in this case. I guess /sys/firmware/efi/efivars does not exist in chroot or maybe it's read only. The zfs-fuse error seems not to matter but for Efivars I had to add one more mount : mount -bind /sys/firmware/efi/efivars /mnt/sys/firmware/efi/efivars Grub-install: warning: read_file: could not read from file: Input/output error. Please make sure that the zfs-fuse daemon is runningĪnd grub-install: warning: Cannot read EFI Boot* variables. (Anybody knows what is exactly the difference between -bind and -rbind / -make-rslave btw ?)īut today I got two errors in chroot from grub2, I never experienced before : connect: No such file or directory In gentoo I used to create mounts from a live-system like this: mount -t proc /proc /mnt/proc Instead of a mount -bind they use mount -rbind followed by mount -make-rslave for sys and dev and proc gets simply mounted again. It is similar to the approach in the gentoo-guide. I can't comment (not enough reputation), but Pereira's answer is the way to go in an EFi or multiboot situation. If you created a new EFI partition, you may have to add it to /etc/fstab to have update-grub working correctly. You may have to tell your BIOS which drive to use, or which EFI partition to use, or which EFI binary to use. Sudo grub-install -target=x86_64-efi /dev/sda -efi-directory=/media/efi -boot-directory=/media/root/boot Sudo mkdir /media/efi & sudo mount /dev/sda1 /media/efi Sudo mkdir /media/root & sudo mount /dev/sda2 /media/root # now assuming that the Ubuntu partition is `/dev/sda2` and the (possibly new) EFI partition is `/dev/sda1` # - set the flag esp on this partition (the flag boot will also be selected) ![]() # creating the EFI partition at the end of the free space). # move or resize some paritions, anticipate that (for instance by # (in general the one that host the Ubuntu partition). # - create a FAT 32 partition of around 100 MB on the disk of your choice ![]() # if you have currently no EFI partition (maybe it was deleted, # boot on a live Ubuntu, I used 18.04 but more recent should work This is how I did it on a standard x86_amd64 EFI desktop, without chrooting, assuming you have a partition containing Ubuntu on your hard drive and possibly an EFI partition where GRUB should be installed. To identify the partitions use GParted, the tool is included in the installation medium.Īfter having run the commands, GRUB will be installed in the separate EFI partition. Note : sdX = disk | sdXX = efi partition | sdXY = system partition ![]() To avoid possible unexpected issues, properly unmount the file systems afterwards. Try the following while still in the chroot environment (Thanks to - the step was necessary in Ubuntu 22.10) : mount -t efivarfs none /sys/firmware/efi/efivarsĪfterwards execute the grub-install command again : grub-install /dev/sdX Note: If the grub-install command reports an error, it cannot find efivars. Once you are on the Live desktop, open a terminal and execute these commands : sudo mount /dev/sdXY /mntįor i in /dev /dev/pts /proc /sys /run do sudo mount -B $i /mnt$i done (Boot your install medium in EFI mode, select the Ubuntu entry with UEFI in front.) īoot from the Ubuntu installation medium and select 'Try Ubuntu without installing'. Reinstall the GRUB boot loader to your Ubuntu installation in EFI mode this way. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |