Exploring CPUs, motherboards, overclocking, building your own PC, case mods, PC brands, handhelds, peripherals of all types, DVDs, CD burners, hardware-specific software, device drivers, and anything else related to hardware.
The The Restaurant at the Edge of the Universe, previously known as The Water Cooler, is a place to post stuff that has absolutely nothing at all to do with computers, broadband, Scot's Newsletter, or anything that's "supposed" to be here.
I don't know anything about Refracta either. Just a few points maybe already made, but in summary.
ESP (EFI System Partition) needs to be FAT32 and flagged as "esp" with partition editor. I usually do "boot" flag too but don't think Linux needs that, maybe Windows does.
There's no point in a separate /boot partition unless / is encrypted. It's only where GRUB files live but initial boot happens from ESP.
I was hesitant to try using UEFI until about 4 years ago with a new PC so I did some reading and installed Win 10 and siduction. It's easier than MBR system as long as you use GPT partition scheme. I've installed/reinstalled quite a few OSs since then. Just did Debian Buster netinstall twice (one for main system and one for possibly destructive testing. I have broken it already 😈 ) last week and it easily picked up the ESP and used it.
Happy to answer any direct Debian questions if you ask. I'm afraid I got lost in all the words above so may have missed something. Possibly attributable to several classes of a nice shiraz last night closing with a Canadian Club shot. 😵
The internet is kinda funny sometimes...you can't look someone in the eye, so all the non-verbal cues get cut from the message. Just wanted to make sure I'm not coming across as an "askhole"....that person who always asks what to do, but never does any of it. I just haven't seen any dots connected yet (if they did, I missed it) as to why the installer can't/won't read the EFI partition for grub installation. I may be way off, but it just seems like something should be in that EFI partition to be read, in order for grub to get configured; but there isn't, so the installer fails.
Your comment about the refracta installer is a fair one. But now you've got me thinking, maybe I should attempt a vanilla Debian installation with the Debian installer and see how that turns out? If that works, I'll know its an issue with refractainstaller, but maybe I can install MY remix in a dual-boot configuration and the installer will finish because it found the EFI files/variables that vanilla Debian installed?
Or maybe I should install my Win7 Pro that came with the machine, in a UEFI configuration, duplicating the setup that the machine came with when I bought it? Then install my remix in dual-boot, just like I like with Lubuntu on old disk?
Hmmm....in the absence of a veritable "i know what's going on and here's how you fix it" scenario, the dual-boot installations sound promising. Seems like if SOMETHING was in that EFI partition to be read, everything might fall into place? Ya got me thinking again...