On Sun, 2014-12-14 at 13:51 +0530, Ritesh Raj Sarraf wrote: Thanks for the report.
> grub-install: error: cannot open `/boot/efi/EFI/BOOT/BOOTX64.EFI': File > exists. The code uses GRUB_UTIL_FD_O_CREATTRUNC which == O_CREAT | O_TRUNC, to open the destination file, so overwriting should be fine. > Failed: grub-install --target=x86_64-efi --force-extra-removable Perhaps you could run this by hand under strace (as root). Might give some clue. > Looking at that path: > > rrs@learner:~$ ls /boot/efi/EFI/BOOT/BOOTX64.EFI > ls: cannot access /boot/efi/EFI/BOOT/BOOTX64.EFI: No such file or > directory > 13:49 ♒♒♒ ☹ => 2 > rrs@learner:~$ ls /boot/efi/EFI/BOOT/bootx64.efi > /boot/efi/EFI/BOOT/bootx64.efi* > 13:49 ♒♒♒ ☺ I wonder if this is a case-sensitivity thing (BOOTX64.EFI vs bootx64.efi) and an oddity of vfat? Steve, perhaps the answer is to remove the existing file first (which I assume/hope due to the quirks of VFAT will work regardless of which case is used). Other EFI code doesn't bother, but in general it is dealing with paths which we control, e.g. /boot/efi/EFI/Debian. /boot/efi/EFI/BOOT could be expected to have stuff written by another OS in it I suppose. > /dev/sda2 on /boot/efi type vfat > (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=utf8,shortname=mixed,errors=remount-ro) Did all of these options come from somewhere standard like d-i or did you set them? I don't see them in current partman-efi. Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
