Device Start End Sectors Size Type
/dev/sda1 2048 1050623 1048576 512M EFI System
/dev/sda2 1050624 837228543 836177920 398.7G Linux filesystem
/dev/sda3 1452748800 1465147391 12398592 5.9G Linux swap
/dev/sda4 837228544 1452748799 615520256 293.5G Microsoft basic data
Partition table entries are not in disk order.
Disk /dev/sdb: 14.6 GiB, 15636364800 bytes, 30539775 sectors
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: dos
Disk identifier: 0x00378159
Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 2048 30539774 30537727 14.6G c W95 FAT32 (LBA)
I am kinda lost here. I am not very experienced with ubuntu and might need a little detailed solution. I installed Windows 10 after ubuntu 16.10 and when I try to reinstall grub2 and it gives me the following error:
Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
Please help!
asked Nov 25, 2016 at 13:49
10
Try this:
Boot the Ubuntu Live Usb-Dvd.
Open a terminal,
Press Ctrl+Alt+T
Run it:
sudo -i
mount /dev/sda2 /mnt
mount /dev/sda1 /mnt/boot/efi
grub-install --boot-directory=/mnt/boot --bootloader-id=ubuntu --target=x86_64-efi --efi-directory=/mnt/boot/efi
reboot
answered Nov 25, 2016 at 15:28
kyodakekyodake
14.9k3 gold badges38 silver badges45 bronze badges
5
The root cause of your problem is Temporary failure resolving 'al.archive.ubuntu.com
This means that when you attempted this process the server was temporarily unavilable. You have 2 options.
1) Try again
2) Choose a different mirror By Opening Software & Updates and selecting a different server in the Download from drop down menu. (Choosing Other will run a series of tests to determine which is the best server for you.)
answered Nov 25, 2016 at 16:07
Elder GeekElder Geek
35.3k25 gold badges94 silver badges179 bronze badges
grub, mx linux
0
1
На ноуте HP были установлены MX и SUSE. Временно понадобилось установить Win7 на sda1. Она установилась только после преобразования какой-то виндовой софтиной диска в gpt. Теперь пытаюсь с live-cd MX переустановить GRUB, ни в какую, перепробовал и в MBR и в ESP и в корневой. Все равно только Win7 грузится. Может теперь надо преобразовать утилитой виндовой для диска обратно из gpt в другой исходный тип? Только желательно чтобы винда какое то время еще пожила, нужен временный dual boot.
- Ссылка
Вы не можете добавлять комментарии в эту тему. Тема перемещена в архив.
I recently dual-boot kali-linux-2016.2-amd64 with windows 10. After sometime I updated my windows 10 and due to this windows might have removed grub from the boot menu. Now I can’t boot kali-linux from the boot menu because it doesn’t appear there anymore.
So I decided to re-install grub by booting into Live-kali(Persistent) from USB. I entered the following command in the terminal:
fdisk -l
sudo mount /dev/sda* /mnt
sudo mount --bind /dev /mnt/dev
sudo mount --bind /proc /mnt/proc
sudo mount --bind /sys /mnt/sys
sudo chroot /mnt
grub-install /dev/sda
CTRL + D
sudo umount /mnt/dev
sudo umount /mnt/proc
sudo umount /mnt/sys
sudo umount /mnt
After the 7th command-line I got this error:
asked Oct 31, 2016 at 5:42
It’s very hard to help you because you don’t know basic commands… but I’ll try okay?
- With
fdisk -l
you list your current partition, like your image. - With your image I can see that you have /dev/sda1 as EFI System, /dev/sda10 as Linux filesystem and /dev/sda11 as Linux swap. Keep this information.
-
When you boot with a live cd you must do a
chroot
for access your system, in other words, an operation that changes the apparent root directory for the current running process and its children. Lets go: -
mount your system at /mnt. Remember? Linux filesystem? Yes. It’s /dev/sda10. So do command:
sudo mount /dev/sda10 /mnt
.You are using
sudo
because you must have administrator permissions to do it. -
So, mount the temporary filesystems needed for programs work, with the commands:
sudo mount --bind /dev /mnt/dev
sudo mount --bind /dev/pts /mnt/dev/pts
sudo mount --bind /proc /mnt/proc
sudo mount --bind /sys /mnt/sys
-
You are modifying your boot, so you need your /boot partition too. Some systems uses the same partition for the /boot directory and system root (/). If you don’t know what is your case, so at this point check if you have files in the folder /mnt/boot/ (you will find your kernel images, configurations , etc).
— If the /mnt/boot folder is empty, so you need mount the /boot partition. The only other possibly usable partition on your case is /dev/sda1, so will be it. Mount at /mnt/boot.
— If you found the files, so the another partition at /dev/sda1 should be really the EFI Filesystem, and it must be mounted at /mnt/boot/EFI.
-
With all mounted,change root directory using:
sudo chroot /mnt /bin/bash
-
Now, inside chroot, you can install grub:
sudo grub-install /dev/sda
answered Oct 31, 2016 at 6:03
4
You must log in to answer this question.
Not the answer you’re looking for? Browse other questions tagged
.
Not the answer you’re looking for? Browse other questions tagged
.
I just now encountered this issue. I booted a rescue USB stick. Let me describe the fix that worked for me.
Prowling around with gdisk -l /dev/sda
I can see that my original root partition is /dev/sda2
. To access it, I type sudo mount /dev/sda2 /mnt
So far, so good. Let me first describe what didn’t work, and then a solution. Some pages advise chroot /mnt
and then grub-install
, but this won’t work; giving the grub-install: error: cannot find EFI directory.
error.
Following other suggestions, I see that my EFI partition is /dev/sda1
so I try sudo mount /dev/sda1 /mnt/boot/efi
and chroot again. Now, grub complains about missing /dev
so I mount --bind /dev/ /mnt/dev
. … But then grub complains about something else. It’s snowballing out of control. chroot
is not the answer.
What did work was this: grub-install -d /mnt/usr/lib/grub/x86_64-efi --boot-directory=/mnt/boot /dev/sda
Note that the -d
flag is mandatory, as otherwise, grub tries to use /usr/lib/grub/i386-pc
from the rescue image, which does not contain the correct stuff.
Yayy! My system is now bootable again!
#1 2020-01-10 16:42:32
- light9876
- Member
- Registered: 2020-01-05
- Posts: 113
[SOLVED] grub-install: error «cannot find EFI directory»
I never had the following problem when I used to install Arch on an HDD.
But not on my new SSD, this is what I’m doing (note that when I do fdisk -l I can see the SSD has a GPT partitioning table):
1. I have been reading the following guides all day (and I’m following them):
https://wiki.archlinux.org/index.php/Installation_guide
https://wiki.archlinux.org/index.php/Partitioning
https://wiki.archlinux.org/index.php/Arch_boot_process
2. cgdisk /dev/sda and I create 3 partitions:
sda1; 2GB, code:ef00, name=efi
sda2; 200GB, code:8300, name=root
sda3; ~750GB, code:8302, name=home
3. I format all 3 partitions:
mkfs.ext4 /dev/sda1
mkfs.ext4 /dev/sda2
mkfs.ext4 /dev/sda3
4. Mount root:
mount /dev/sda2 /mnt
5. Install base:
pacstrap /mnt base base-devel linux grub efibootmgr
mkinitcpio -p linux
6. : All of the following commands give the same error: grub-install: error «cannot find EFI directory»
grub-install /dev/sda
grub-install —target=x86_64-efi /dev/sda
grub-install —efi-directory=/boot/efi —target=x86_64-efi /dev/sda
Can someone tell me what I am doing wrong please?
Last edited by light9876 (2020-01-10 18:37:40)
#2 2020-01-10 17:09:51
- Head_on_a_Stick
- Member
- From: London
- Registered: 2014-02-20
- Posts: 6,991
- Website
Re: [SOLVED] grub-install: error «cannot find EFI directory»
You forgot to mount the EFI system partition, it should be FAT-formatted (not ext4) and you should (arch-)chroot in before running the GRUB commands.
Step 4 should be
# mount /dev/sda2 /mnt
# mkdir -p /mnt/boot/efi
# mount /dev/sda1 /mnt/boot/efi
And step 6 should start with
Note that the UEFI grub-install command doesn’t need a block device.
EDIT: and the mkinitcpio command should be run from the chroot (although you probably don’t need to run it at all).
Last edited by Head_on_a_Stick (2020-01-10 17:11:24)
#3 2020-01-10 17:15:38
- light9876
- Member
- Registered: 2020-01-05
- Posts: 113
Re: [SOLVED] grub-install: error «cannot find EFI directory»
Thank you, I will try this immediately!
I am already doing arch-chroot /mnt but I forgot to mention it.
I will try now to format correctly and to mount /mnt/boot/efi
Last edited by light9876 (2020-01-10 17:15:58)
#4 2020-01-10 18:46:02
- light9876
- Member
- Registered: 2020-01-05
- Posts: 113
Re: [SOLVED] grub-install: error «cannot find EFI directory»
Thank you so much everything works okay now!
Only for future reference: the information you provided is written here:
https://wiki.archlinux.org/index.php/GR … allation_2
One final question:
I installed lxde and lxdm; then I logged in my user account. Now the partition /dev/sda3 that I created for /home, is not mounted at /home.
Instead, /home directory and all of its contents are resident on /dev/sda2
How can I fix this please?
Last edited by light9876 (2020-01-10 18:46:36)
#5 2020-01-10 18:58:31
- Head_on_a_Stick
- Member
- From: London
- Registered: 2014-02-20
- Posts: 6,991
- Website
Re: [SOLVED] grub-install: error «cannot find EFI directory»
light9876 wrote:
How can I fix this please?
Create an fstab line to mount /home correctly then move the contents over to the new partition.
If you need more help with that then please open a new thread, it is off-topic here.
#6 2020-01-10 20:09:57
- light9876
- Member
- Registered: 2020-01-05
- Posts: 113
Re: [SOLVED] grub-install: error «cannot find EFI directory»
Thank you so much! I am very happy with the generous support you and everyone else have given me! : ) God bless you!
Last edited by light9876 (2020-01-10 20:10:39)