# New grub update fix having problem with grub-install **URL:** \ **Category:** Newbie\ **Created:** [August 26, 2022, 3:56am UTC](https://forum.endeavouros.com/t/new-grub-update-fix-having-problem-with-grub-install/30723 "2022-08-26T03:56:43Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![rancour](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/r/a6a055/32.png) [@rancour](https://forum.endeavouros.com/u/rancour)\ **Post date:** [August 26, 2022, 3:56am UTC](https://forum.endeavouros.com/t/new-grub-update-fix-having-problem-with-grub-install/30723/1 "2022-08-26T03:56:43Z")
> [@The latest grub package update needs some manual intervention](https://forum.endeavouros.com/t/the-latest-grub-package-update-needs-some-manual-intervention/30689): > > (Grub 2:2.06.r322.gd9b4638c5-1) Grub Update Causing Unbootable OS On UEFI Systems A grub update today is causing boot issues on UEFI systems. It will make most systems unbootable so take care! with no intervention, the system will just boot directly into Firmware with no way to boot the OS. If you have this issue follow these instructions: First boot onto an EndeavourOS Live ISO. Ensure that you are booting the ISO via UEFI mode. Follow these instructions to chroot into your install: [htt…](https://discovery.endeavouros.com/system-rescue/arch-chroot-for-efi-uefi-systems/2021/03/) I am following this post and I am stuck at step 3 after verifying that it is UEFI I went ahead with the instructions. Running os-prober is giving me this error. and grub install is giving me another error. I looked around for solutions and found few but I haven’t tried them yet because I am not sure which drive to use them on. nvme0n1p7 is my linux partition in the fdisk output. When install EOS I went with the replace partition option. ```auto [root@EndeavourOS /]# os-prober grub-probe: error: cannot find a GRUB drive for /dev/sda1. Check your device.map. ``` ```auto [root@EndeavourOS /]# sudo grub-mkconfig -o /boot/grub/grub.cfg Generating grub configuration file ... Found theme: /boot/grub/themes/EndeavourOS/theme.txt Found linux image: /boot/vmlinuz-linux-g14 Found initrd image: /boot/amd-ucode.img /boot/initramfs-linux-g14.img Found fallback initrd image(s) in /boot: amd-ucode.img initramfs-linux-g14-fallback.img Found linux image: /boot/vmlinuz-linux Found initrd image: /boot/amd-ucode.img /boot/initramfs-linux.img Found fallback initrd image(s) in /boot: amd-ucode.img initramfs-linux-fallback.img Warning: os-prober will be executed to detect other bootable partitions. Its output will be used to detect bootable binaries on them and create new boot entries. grub-probe: error: cannot find a GRUB drive for /dev/sda1. Check your device.map. Adding boot menu entry for UEFI Firmware Settings ... done [root@EndeavourOS /]# grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=EndeavourOS-grub Installing for x86_64-efi platform. ``` ```auto [root@EndeavourOS /]# sudo parted -l Model: SanDisk Ultra (scsi) Disk /dev/sda: 15.4GB Sector size (logical/physical): 512B/512B Partition Table: msdos Disk Flags: Number Start End Size Type File system Flags 2 1825MB 1934MB 109MB primary fat16 esp Model: INTEL SSDPEKNU512GZ (nvme) Disk /dev/nvme0n1: 512GB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags: Number Start End Size File system Name Flags 1 1049kB 274MB 273MB fat32 EFI system partition boot, esp 2 274MB 290MB 16.8MB Microsoft reserved partition msftres 3 290MB 413GB 413GB ntfs Basic data partition msftdata 7 413GB 487GB 73.7GB ext4 root 4 487GB 488GB 1101MB ntfs Basic data partition hidden, diag 5 488GB 512GB 23.6GB ntfs Basic data partition hidden, msftdata 6 512GB 512GB 210MB fat32 Basic data partition hidden, diag ``` ```auto [root@EndeavourOS /]# fdisk -l Disk /dev/nvme0n1: 476.94 GiB, 512110190592 bytes, 1000215216 sectors Disk model: INTEL SSDPEKNU512GZ 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: gpt Disk identifier: F16D0B72-37F6-4901-A8EE-D027DA59D1F3 Device Start End Sectors Size Type /dev/nvme0n1p1 2048 534527 532480 260M EFI System /dev/nvme0n1p2 534528 567295 32768 16M Microsoft reserved /dev/nvme0n1p3 567296 807617166 807049871 384.8G Microsoft basic data /dev/nvme0n1p4 951517184 953667583 2150400 1G Windows recovery environment /dev/nvme0n1p5 953667584 999804927 46137344 22G Microsoft basic data /dev/nvme0n1p6 999804928 1000214527 409600 200M Windows recovery environment /dev/nvme0n1p7 807617167 951517183 143900017 68.6G Linux filesystem Partition table entries are not in disk order. Disk /dev/sda: 14.32 GiB, 15376000000 bytes, 30031250 sectors Disk model: Ultra 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: 0x593e4509 Device Boot Start End Sectors Size Id Type /dev/sda1 * 64 3564735 3564672 1.7G 0 Empty /dev/sda2 3564736 3777727 212992 104M ef EFI (FAT-12/16/32) Disk /dev/loop0: 1.6 GiB, 1714974720 bytes, 3349560 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 ``` ---
**Author:** ![ricklinux](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/ricklinux/32/110798_2.png) [@ricklinux](https://forum.endeavouros.com/u/ricklinux)\ **Post date:** [August 26, 2022, 4:10am UTC](https://forum.endeavouros.com/t/new-grub-update-fix-having-problem-with-grub-install/30723/2 "2022-08-26T04:10:21Z")
Did you arch-chroot on the live ISO? `sudo mount /dev/nvme0n1p7 /mnt` `sudo mount /dev/nvme0n1p1 /mnt/boot/efi` `arch-chroot /mnt` Then run the commands as per the instructions. ---
**Author:** ![rancour](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/r/a6a055/32.png) [@rancour](https://forum.endeavouros.com/u/rancour)\ **Post date:** [August 26, 2022, 4:15am UTC](https://forum.endeavouros.com/t/new-grub-update-fix-having-problem-with-grub-install/30723/3 "2022-08-26T04:15:48Z")
Oh thanks for pointing it out I didn’t run the second command 😅. ---
**Author:** ![ricklinux](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/ricklinux/32/110798_2.png) [@ricklinux](https://forum.endeavouros.com/u/ricklinux)\ **Post date:** [August 26, 2022, 4:19am UTC](https://forum.endeavouros.com/t/new-grub-update-fix-having-problem-with-grub-install/30723/4 "2022-08-26T04:19:12Z")
Did this work for you then? ---
**Author:** ![rancour](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/r/a6a055/32.png) [@rancour](https://forum.endeavouros.com/u/rancour)\ **Post date:** [August 26, 2022, 4:38am UTC](https://forum.endeavouros.com/t/new-grub-update-fix-having-problem-with-grub-install/30723/5 "2022-08-26T04:38:56Z")
Yes. ---
**Author:** ![system](https://forum.endeavouros.com/uploads/default/original/2X/9/9ea52f9fd5ef8e609e593c362d61a36295f48be8.png) [@system](https://forum.endeavouros.com/u/system)\ **Post date:** [August 28, 2022, 4:39am UTC](https://forum.endeavouros.com/t/new-grub-update-fix-having-problem-with-grub-install/30723/6 "2022-08-28T04:39:27Z")
Closed on August 28, 2022, 4:39am UTC This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.