With the latest fixes on 13.10 I still fail to boot the OS, even with a larger FAT32 EFI partition in place. In other words the server cannot find anything to boot from and asks me to press F1 to try again, F11 to return to the EFI boot menu, etc.
**HOWEVER**
If I restart the installation and edit "/lib/partman/commit.d/50format_efi" prior the partitioning phase and adjust this line:
mkdosfs -F "${new_efi_fs#fat}" \
to look like this:
mkdosfs -s 1 -F "${new_efi_fs#fat}" \
We are dropped to a grub prompt after installation and reboot...so, I think how the fat partition getting created is one factor in this.
From the grub prompt, I can type the following commands and boot the OS:
grub> linux (hd0,gpt2)/vmlinuz root=/dev/sda2
grub> initrd (hd0,gpt2)/initrd.img
grub> boot
Also, I noticed in the logs if we use the original mkdosfs command *without* the -s 1 option a warning is logged:
WARNING: Not enough clusters for a 32 bit FAT!
Whereas I don't see this if I use -s 1.
I'll attach logs from both an install with the way things currently are and another set with the mkdosfs modifications in place.
With the latest fixes on 13.10 I still fail to boot the OS, even with a larger FAT32 EFI partition in place. In other words the server cannot find anything to boot from and asks me to press F1 to try again, F11 to return to the EFI boot menu, etc.
**HOWEVER**
If I restart the installation and edit "/lib/partman/ commit. d/50format_ efi" prior the partitioning phase and adjust this line:
mkdosfs -F "${new_efi_fs#fat}" \
to look like this:
mkdosfs -s 1 -F "${new_efi_fs#fat}" \
We are dropped to a grub prompt after installation and reboot...so, I think how the fat partition getting created is one factor in this.
From the grub prompt, I can type the following commands and boot the OS:
grub> linux (hd0,gpt2)/vmlinuz root=/dev/sda2 /initrd. img
grub> initrd (hd0,gpt2)
grub> boot
Also, I noticed in the logs if we use the original mkdosfs command *without* the -s 1 option a warning is logged:
WARNING: Not enough clusters for a 32 bit FAT!
Whereas I don't see this if I use -s 1.
I'll attach logs from both an install with the way things currently are and another set with the mkdosfs modifications in place.