Page 2 of 2 FirstFirst 12
Results 51 to 82 of 82

Thread: Executing 'grub-install dummy' failed.

  1. #51
    Join Date
    2019-Jul
    Posts
    2
    Quote Originally Posted by Anonymous_47 View Post
    I am have done everything as you show but it still show input/output error please somebody help😭😭😭🙏🏻🙏🏻🙏🏻
    i try all the same and don't work for me.. (grub screw all after try to upgrade my kali)..

    finaly, run usb on rescue mode.
    try to force install grub on efi partition > failed, fatal error
    try to instal grub on /dev/sda > failed, fatal error

    run command line on /dev/sda1 (my kali partition)
    #mount /dev/sda3 /boot/efi -o rw
    #update-initramfs -u
    #update-grub
    detect all systems (kali, slackware, w10, debian jessie on my laptop) and write all data on EFI sys.
    #reboot
    and this work for me.-

  2. #52
    Join Date
    2019-Sep
    Posts
    2
    I followed same, But... I am getting this error

    grub-install: warning: Cannot set EFI variable Boot0004.
    grub-install: warning: vars_set_variable: write() failed: No space left on device. grub-install: warning: _efi_set_variable_mode: ops->set_variable() failed: No such file or directory.
    grub-install: error: failed to register the EFI boot entry: No such file or directory.

  3. #53
    Join Date
    2016-Oct
    Location
    /dev/sda
    Posts
    1,012
    This temporary fix may work: https://unix.stackexchange.com/quest...llation-failed

    I'll soon add this fix to make proper instructions.

    Else, try this @AlexZander

    Boot into kali live,

    mount /dev/sda* /mnt
    mount --bind /dev /mnt/dev
    mount --bind /proc /mnt/proc
    mount --bind /sys /mnt/sys
    mkdir /mnt/sys/firmware/efi/efivars
    mount --bind /sys/firmware/efi/efivars /mnt/sys/firmware/efi/efivars
    rm /sys/firmware/efi/efivars/dump-*
    mkdir /mnt/boot/efi
    mount /dev/sda+ /mnt/boot/efi
    mount -o remount,rw /dev/sda+ /mnt/boot/efi
    mkdir /mnt/hostrun
    mount --bind /run /mnt/hostrun
    chroot /mnt
    mkdir /run/lvm
    mount --bind /hostrun/lvm /run/lvm
    grub-install /dev/sda
    update-grub
    exit
    umount /mnt/dev
    umount /mnt/proc
    umount /mnt/sys/firmware/efi/efivars
    umount /mnt/sys
    umount /mnt/boot/efi
    umount /mnt/hostrun
    umount /mnt/run/lvm
    umount /mnt
    REBOOT


    /dev/sda* is your linux filesystem. Like mine is /dev/sda6
    /dev/sda+ is your EFI partition which is most likely /dev/sda1.
    Use fdisk -l to list all partitions.

  4. #54
    Join Date
    2019-Sep
    Posts
    2
    I have followed above command, Now... I am able to install grub Successfully, But.... While "update-grub"


    Generating grub configuration file ...
    Found background image: /usr/share/images/desktop-base/desktop-grub.png
    Found linux image: /boot/vmlinuz-4.19.0-kali4-amd64
    Found initrd image: /boot/initrd.img-4.19.0-kali4-amd64
    WARNING: Device /dev/loop0 not initialized in udev database even after waiting 10000000 microseconds.
    WARNING: Device /dev/sda not initialized in udev database even after waiting 10000000 microseconds.
    WARNING: Device /dev/sda1 not initialized in udev database even after waiting 10000000 microseconds.
    WARNING: Device /dev/sda2 not initialized in udev database even after waiting 10000000 microseconds.
    WARNING: Device /dev/sda3 not initialized in udev database even after waiting 10000000 microseconds.
    WARNING: Device /dev/sda4 not initialized in udev database even after waiting 10000000 microseconds.
    WARNING: Device /dev/sda5 not initialized in udev database even after waiting 10000000 microseconds.
    WARNING: Device /dev/sda6 not initialized in udev database even after waiting 10000000 microseconds.
    WARNING: Device /dev/sda7 not initialized in udev database even after waiting 10000000 microseconds.
    WARNING: Device /dev/sda8 not initialized in udev database even after waiting 10000000 microseconds.
    WARNING: Device /dev/sda9 not initialized in udev database even after waiting 10000000 microseconds.
    WARNING: Device /dev/loop0 not initialized in udev database even after waiting 10000000 microseconds.
    WARNING: Device /dev/sda1 not initialized in udev database even after waiting 10000000 microseconds.
    WARNING: Device /dev/sda2 not initialized in udev database even after waiting 10000000 microseconds.
    WARNING: Device /dev/sda3 not initialized in udev database even after waiting 10000000 microseconds.
    WARNING: Device /dev/sda4 not initialized in udev database even after waiting 10000000 microseconds.
    WARNING: Device /dev/sda5 not initialized in udev database even after waiting 10000000 microseconds.
    WARNING: Device /dev/sda6 not initialized in udev database even after waiting 10000000 microseconds.
    WARNING: Device /dev/sda7 not initialized in udev database even after waiting 10000000 microseconds.
    WARNING: Device /dev/sda8 not initialized in udev database even after waiting 10000000 microseconds.
    WARNING: Device /dev/sda9 not initialized in udev database even after waiting 10000000 microseconds.
    Adding boot menu entry for EFI firmware configuration
    done



    don't know what the above error mean

  5. #55
    Join Date
    2019-Sep
    Posts
    1
    Quote Originally Posted by _defalt View Post
    You can skip installation of grub. After your installation is complete boot into kali-live and run these commands:

    sudo mount /dev/sda* /mnt
    mount --bind /dev /mnt/dev
    mount --bind /proc /mnt/proc
    mount --bind /sys /mnt/sys
    mount /dev/sda+ /mnt/boot/efi
    mount -o remount,rw /dev/sda+ /mnt/boot/efi
    mkdir /mnt/hostrun
    mount --bind /run /mnt/hostrun
    chroot /mnt
    mkdir /run/lvm
    mount --bind /hostrun/lvm /run/lvm
    grub-install /dev/sda
    update-grub
    exit
    umount /mnt/dev
    umount /mnt/proc
    umount /mnt/sys
    umount /mnt/boot/efi
    umount /mnt/hostrun
    umount /mnt/run/lvm
    umount /mnt


    Replace * in sudo mount /dev/sda* /mnt with your linux filesystem name. Like mine is /dev/sda6
    Replace + in sudo mount /dev/sda+ /mnt/boot/efi with your EFI partition name. Mine is /dev/sda1
    Use fdisk -l to list all partitions.
    I tried this. But I get this error when executing this line "grub-install /dev/sda".

    This errors pops-up:
    grub-install: warning: Cannot set EFI variable BootOrder.
    grub-install: warning: vars_set_variable: write() failed: No space left on device.
    grub-install: warning: _efi_set_variable_mode: ops->set_variable() failed: No such file or directory.
    grub-install: error: failed to register the EFI boot entry: No such file or directory.

  6. #56
    Join Date
    2016-Oct
    Location
    /dev/sda
    Posts
    1,012
    Don't follow my post on page 1. My last post on this page contains updated instructions. Run them.

    Ignore warnings from update-grub command.

    What exactly is the issue you are facing?

    Have you tried this way?

    https://forums.kali.org/showthread.p...ption-disapear
    Last edited by _defalt; 2019-09-11 at 16:47.

  7. #57
    Join Date
    2019-Nov
    Posts
    1
    1574068890802.jpg

    how to fix this error???

  8. #58
    Join Date
    2016-Oct
    Location
    /dev/sda
    Posts
    1,012
    Quote Originally Posted by kabir View Post
    1574068890802.jpg

    how to fix this error???
    Reinstall grub: -UEFI-How-to-repair-kali-linux-grub-dual-boot-with-Windows-10

  9. #59
    Join Date
    2020-Jan
    Posts
    1
    oot@kali:~# sudo mount /dev/sda7 /mnt
    root@kali:~# mount --bind /dev /mnt/dev
    root@kali:~# mount --bind /proc /mnt/proc
    root@kali:~# mount --bind /sys /mnt/sys
    root@kali:~# mount /dev/sda1 /mnt/boot/efi
    root@kali:~# mount -o remount,rw /dev/sda1 /mnt/boot/efi
    root@kali:~# mkdir /mnt/hostrun
    root@kali:~# mount --bind /run /mnt/hostrun
    root@kali:~# chroot /mnt
    root@kali:/# mkdir /run/lvm
    root@kali:/# mount --bind /hostrun/lvm /run/lvm
    root@kali:/# grub-install /dev/sda
    Installing for x86_64-efi platform.
    grub-install: warning: Cannot set EFI variable Boot0004.
    grub-install: warning: vars_set_variable: write() failed: No space left on device.
    grub-install: warning: _efi_set_variable_mode: ops->set_variable() failed: No such file or directory.
    grub-install: error: failed to register the EFI boot entry: No such file or directory.

    I am stuck here from a week now!
    Please help me out

  10. #60
    Join Date
    2014-Mar
    Posts
    48
    I have the same issue Installing Kali. I'm installing on a Winbook TW802. It originally had Windows on it, and I have no desire to dual boot. I was encouraged that deleting the .efi file changed symptoms somewhat, but didn't get things working. I used gparted to delete all partitions, including the EFI partition, and reinstalled, but I still get the grub dummy failure. I have tried the instructions above, but when booting to live Kali, the Kali flash drive is sda1, and the internal drive is mmcblk1p, and the EFI partition is mmcblk1p1. I tried modifying the directions, but I get the same errors as the message above. I've been working on this for days, and I'm out of ideas.

  11. #61
    Join Date
    2014-Mar
    Posts
    48
    After more research, this problem, at least for me, may be because of the Bay Trail Atom in my tablet. A number of people have had problems installing any Linux on these machines. It seems related to the 32 bit UEFI, and apparently adding, or replacing the bootia32.efi on the .ISO is supposed to fix it, but I can't figure out how to do that. The only program I have that can edit ISOs is PowerISO, and every time I make any change, it creates a non-bootable ISO. If I try to edit the USB drive, there's no room, and I've been unsuccessful resizing the partition.
    If it helps anyone solve their problem, here's the links I gathered:

    https://www.***********************MEf4GXdQ3IQ - Not showing up, it's Youtube.com plus /watch?v=MEf4GXdQ3IQ

    https://www.***********************nsp8XFcAS7o - TS100 Youtube, same as above, plus /watch?v=nsp8XFcAS7o

    https://web.archive.org/web/20180203...buntu-tw700-1/

    https://web.archive.org/web/20180202...mer-book-t100/

    http://www.jfwhome.com/2016/01/04/la...e-asus-t100ta/

    https://github.com/jfwells/linux-asu...t/bootia32.efi

    https://github.com/jfwells/linux-asu...ee/master/boot
    Last edited by RChadwick; 2020-02-13 at 03:17. Reason: Links

  12. #62
    Join Date
    2020-Feb
    Posts
    2
    Quote Originally Posted by _defalt View Post
    This temporary fix may work: https://unix.stackexchange.com/quest...llation-failed

    I'll soon add this fix to make proper instructions.

    Else, try this @AlexZander

    Boot into kali live,

    mount /dev/sda* /mnt
    mount --bind /dev /mnt/dev
    mount --bind /proc /mnt/proc
    mount --bind /sys /mnt/sys
    mkdir /mnt/sys/firmware/efi/efivars
    mount --bind /sys/firmware/efi/efivars /mnt/sys/firmware/efi/efivars
    rm /sys/firmware/efi/efivars/dump-*
    mkdir /mnt/boot/efi
    mount /dev/sda+ /mnt/boot/efi
    mount -o remount,rw /dev/sda+ /mnt/boot/efi
    mkdir /mnt/hostrun
    mount --bind /run /mnt/hostrun
    chroot /mnt
    mkdir /run/lvm
    mount --bind /hostrun/lvm /run/lvm
    grub-install /dev/sda
    update-grub
    exit
    umount /mnt/dev
    umount /mnt/proc
    umount /mnt/sys/firmware/efi/efivars
    umount /mnt/sys
    umount /mnt/boot/efi
    umount /mnt/hostrun
    umount /mnt/run/lvm
    umount /mnt
    REBOOT


    /dev/sda* is your linux filesystem. Like mine is /dev/sda6
    /dev/sda+ is your EFI partition which is most likely /dev/sda1.
    Use fdisk -l to list all partitions.
    @_defalt Thank you for your work! Your updated post was working for me.

    People, please, don't use post on top of the first page, this one is up-to-date and should work.

    I was installing Kali 2020.1 over Debian 8 and during installation the problem with "Unable to install grub in dummy" came up.

    note: I also removed (in Kali Live cmd) /mnt/EFI/kali/grubx64.efi after mounting #mount /dev/sda2 /mnt (sda2 is my EFI part.), but I don't think it took any effect, since installation was unsuccessful even for 2nd attempt.

  13. #63
    Join Date
    2020-Feb
    Posts
    2
    And as was mentioned somewhere above, after successful GRUB installation, you need to do update-grub command again in installed Kali in order to find Windows bootloader.

  14. #64
    Join Date
    2020-Feb
    Posts
    3
    Hey guys i have both WIN 10 and kali linus but dont have grub bootloader.
    Win 10 is in SSD ( /dev/sda )
    Kali linux is in HDD in a created partition( /dev/sdb5 )
    .
    Now my question is that i should install grub bootloader in EFI partition of SSD or HDD
    ,I mean sda1 or sdb1 .

  15. #65
    Join Date
    2014-Mar
    Posts
    48
    I'm glad it's working for you.
    When I get to the grub-install, I get these errors-
    sudo grub-install /dev/mmcblk1
    installing for i386-efi platform
    grub-install Warning Cannot set EFI Variable Boot0000
    grub-install Warning vars_set_variable Write() failed no space left on device
    grub-install Warning _efi_set_variable_mode ops->set_variable() failed No such file or directory
    grub-install error failed to register the EFI boot entry No such file or directory

  16. #66
    Join Date
    2020-Feb
    Posts
    3
    Similar message occurs when I try installing in my SSD where Windows is located.
    I am talking about installing in HDD .
    When I install in [ /dev/sdb ]
    It shows installing for 86_64 efi platform.
    But nothing happens even after waiting for long.
    😭😭😭

  17. #67
    Join Date
    2020-Apr
    Posts
    2
    is this problem able to overcome the grub password

  18. #68
    Join Date
    2020-Apr
    Posts
    2
    is this problem can overcome to forgot grub password
    Quote Originally Posted by _defalt View Post
    You can skip installation of grub. After your installation is complete boot into kali-live and run these commands:

    sudo mount /dev/sda* /mnt
    mount --bind /dev /mnt/dev
    mount --bind /proc /mnt/proc
    mount --bind /sys /mnt/sys
    mount /dev/sda+ /mnt/boot/efi
    mount -o remount,rw /dev/sda+ /mnt/boot/efi
    mkdir /mnt/hostrun
    mount --bind /run /mnt/hostrun
    chroot /mnt
    mkdir /run/lvm
    mount --bind /hostrun/lvm /run/lvm
    grub-install /dev/sda
    update-grub
    exit
    umount /mnt/dev
    umount /mnt/proc
    umount /mnt/sys
    umount /mnt/boot/efi
    umount /mnt/hostrun
    umount /mnt/run/lvm
    umount /mnt


    Replace * in sudo mount /dev/sda* /mnt with your linux filesystem name. Like mine is /dev/sda6
    Replace + in sudo mount /dev/sda+ /mnt/boot/efi with your EFI partition name. Mine is /dev/sda1
    Use fdisk -l to list all partitions.

  19. #69
    Join Date
    2020-Jul
    Posts
    1
    worked perfectly until this part:
    mount --bind /hostrun/lvm /run/lvm
    I get the following error:
    mount: /run/lvm: special device /hostrun/lvm does not exist.
    Any idea on how to fix this?

  20. #70
    Join Date
    2020-Jul
    Posts
    9
    Same problem here.

  21. #71
    Join Date
    2020-Jul
    Posts
    9
    Yea! It no work for me to

  22. #72
    Join Date
    2020-Jul
    Posts
    9
    Mkdir /hostrun/lvm

  23. #73
    Join Date
    2016-Oct
    Location
    /dev/sda
    Posts
    1,012
    The error grub-install dummy failed comes when you already have grub installed from earlier kali installation. I've updated the post along with the source thread.

    If you have dual booted kali with Windows and you are installing kali in different storage unit like HDD and your Windows is in SSD, then your EFI partition is already present in SSD so this is where grub will also be installed. So don't give the name of HDD while installing grub.

    Regarding /hostrun/lvm, I've to see it. You can try skipping it.

  24. #74
    Join Date
    2020-Jul
    Posts
    9
    Quote Originally Posted by _defalt View Post
    The error grub-install dummy failed comes when you already have grub installed from earlier kali installation. I've updated the post along with the source thread.

    If you have dual booted kali with Windows and you are installing kali in different storage unit like HDD and your Windows is in SSD, then your EFI partition is already present in SSD so this is where grub will also be installed. So don't give the name of HDD while installing grub.

    Regarding /hostrun/lvm, I've to see it. You can try skipping it.


    I?ve completely wiped my SSD and HDD drive with a disk wipe tool, and I am installing Kali Linux only on SSD, yet I still receive same error.

  25. #75
    Join Date
    2016-Oct
    Location
    /dev/sda
    Posts
    1,012
    Quote Originally Posted by Temporaryusername View Post
    I?ve completely wiped my SSD and HDD drive with a disk wipe tool, and I am installing Kali Linux only on SSD, yet I still receive same error.
    You might have left EFI partition in SSD. Boot into kali-live through USB live boot and delete all partitions in SSD. You can use Gparted tool for that. Then install kali.

  26. #76
    Join Date
    2020-Jul
    Posts
    9
    Quote Originally Posted by _defalt View Post
    You might have left EFI partition in SSD. Boot into kali-live through USB live boot and delete all partitions in SSD. You can use Gparted tool for that. Then install kali.
    I have. Many times.

  27. #77
    Join Date
    2020-Jul
    Posts
    9
    Quote Originally Posted by _defalt View Post
    You might have left EFI partition in SSD. Boot into kali-live through USB live boot and delete all partitions in SSD. You can use Gparted tool for that. Then install kali.
    I?ve deleted every partition from every harddrive.
    I have booted live and through EFIBOOTMGR i have deleted every efi entry.

    Yet it keeps giving me a boot grub failed on installation. No matter what.

    Over and over and over again.

  28. #78
    Join Date
    2016-Oct
    Location
    /dev/sda
    Posts
    1,012
    Go to UEFI settings and see if there's an entry of kali there? Which PC are you using? In HP, UEFI loads enteries of bootloader from EFI everytime on boot. In Dell, it keeps the entry persistent.

  29. #79
    Join Date
    2020-Jul
    Posts
    9
    Quote Originally Posted by _defalt View Post
    Go to UEFI settings and see if there's an entry of kali there? Which PC are you using? In HP, UEFI loads enteries of bootloader from EFI everytime on boot. In Dell, it keeps the entry persistent.
    I have an intel motherboaed so i cant secure boot to remove entries

  30. #80
    Join Date
    2016-Oct
    Location
    /dev/sda
    Posts
    1,012
    Quote Originally Posted by Temporaryusername View Post
    I have an intel motherboaed so i cant secure boot to remove entries
    Go to your UEFI settings. Explore options there. You will find something related else post screenshots.

  31. #81
    Join Date
    2020-Jul
    Posts
    9
    Quote Originally Posted by _defalt View Post
    Go to your UEFI settings. Explore options there. You will find something related else post screenshots.
    There is nothing at all.

  32. #82
    Join Date
    2016-Oct
    Location
    /dev/sda
    Posts
    1,012
    Quote Originally Posted by Temporaryusername View Post
    There is nothing at all.
    Then follow the guide I posted earlier to reinstall grub.

    Can you show the output of fdisk -l?

    Also post screenshots of your UEFI settings.

Similar Threads

  1. [Fix]"grub-pc failed to install into /target/"[Fix]
    By n0bul4r in forum How-To Archive
    Replies: 8
    Last Post: 2016-02-06, 13:19
  2. Replies: 13
    Last Post: 2014-07-14, 15:29
  3. Grub failed on install to USB
    By Beasleyboy in forum Installing Archive
    Replies: 3
    Last Post: 2013-12-03, 21:14

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •