[Bug 1840857] Re: Couldn't run grub-install on created EFI partition. Doesn't like boot on an NTFS
martyfranchuk@gmail.com
1840857 at bugs.launchpad.net
Wed Aug 21 06:53:09 UTC 2019
I concur. Some idiot shipped this computer with Windows 10 installed as
legacy system.
I will need to work on the resolution.
Thanks for pointing me.
On Tue, Aug 20, 2019, 9:40 PM Chris Guiver <guiverc at gmail.com> wrote:
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better.
>
> This is not a bug I suspect.
>
> The EFI spec states the format should be FAT12, FAT16, or FAT32 as I
> read
>
> https://uefi.org/sites/default/files/resources/UEFI_Spec_2_8_final.pdf#G17.1019485
>
> The bug is more whomever installed your system in a non-EFI
> specification compatible mode, not with Ubuntu which is following the
> EFI specifications.
>
> The following is quoted from EFI specification link provided :-
>
> 13.3 File System Format
> The file system supported by the Extensible Firmware Interface is based on
> the FAT file system. EFI
> defines a specific version of FAT that is explicitly documented and
> testable. Conformance to the EFI
> specification and its associate reference documents is the only definition
> of FAT that needs to be
> implemented to support EFI. To differentiate the EFI file system from pure
> FAT, a new partition file
> system type has been defined.
> EFI encompasses the use of FAT32 for a system partition, and FAT12 or
> FAT16 for removable media. The
> FAT32 system partition is identified by an OSType value other than that
> used to identify previous versions
> of FAT. This unique partition type distinguishes an EFI defined file
> system from a normal FAT file system.
> The file system supported by EFI includes support for long file names.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1840857
>
> Title:
> Couldn't run grub-install on created EFI partition. Doesn't like boot
> on an NTFS
>
> Status in grub-installer package in Ubuntu:
> New
>
> Bug description:
> Couldn't run grub-install on created EFI partition. Doesn't like boot
> being on a small NTFS. Wants it to be vfat.
> I can't change that without wiping out existing Win 10 Pro install. Not
> going to mess with that.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 19.04
> Package: ubiquity 19.04.9
> ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
> Uname: Linux 5.0.0-13-generic x86_64
> ApportVersion: 2.20.10-0ubuntu27
> Architecture: amd64
> CasperVersion: 1.405
> Date: Tue Aug 20 19:50:36 2019
> InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz
> file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash ---
> LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
> SourcePackage: grub-installer
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1840857/+subscriptions
>
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grub-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1840857
Title:
Couldn't run grub-install on created EFI partition. Doesn't like boot
on an NTFS
Status in grub-installer package in Ubuntu:
New
Bug description:
Couldn't run grub-install on created EFI partition. Doesn't like boot being on a small NTFS. Wants it to be vfat.
I can't change that without wiping out existing Win 10 Pro install. Not going to mess with that.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: ubiquity 19.04.9
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CasperVersion: 1.405
Date: Tue Aug 20 19:50:36 2019
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: grub-installer
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1840857/+subscriptions
More information about the foundations-bugs
mailing list