Thanks for testing mate!
Please do post the installation log for me to take a look at. It's at "/var/log/installation.log".
you can probably axe the 'proc' line as well.
I think that /proc is actually a must for the "update-grub" to find partitions/mount info.
At least I was never able to restore/reinstall GRUB from a live system without binding it to the mounted root first ( eg mount --bind /proc /path/to/root/partition/proc ).
I am perplexed.. I can successfully install and on the first reboot from the installation V-Box sees grub and efi and all is good...
Does the efi partition need to be anything special other than fat16? Does it need to be sda or sda1? Does it need to be flagged as a boot device from gparted?
- AFAIK, it should be (any) FAT, most likely because every BIOS will support it.
- Should be a first one ( sdX1, nvmeXnXp1 etc ), though not a must, however the same "support issue" as above still applies.
- Yes, it needs "esp" flag to be set, which is what Parted/Gparted actually does when you set a "boot" flag.
Installer-wise, it sets the "boot" flag using parted itself, so that's unlikely to be the cause ( see here
, @line 509 )
And there is nothing I can do to change it during the installation.. it is something that needs to be added or edited after the install
That won't be too hard to implement as preseed ( including the entire "options" part of "fstab" for every file system available ).
I have finished building and testing a new ISO for testing uEFI hardware and it has been uploaded to the test download page
Btw, should another build be required while we're debuging these issues, may I ask you to build with VBox Guest Additions ( I'm sorely missing the shared clipboard when fixing/testing installer stuff on a live system )?