Public bug reported:
A user with a Packard Bell EasyNote TE found that the installer failed
(hung with no apparent activity) after the partitioning step.
/var/log/syslog reports:
wrong fs type, bad optio, bad superblock on /dev/sda1
/var/log/kern.log reports:
FAT-fs (sda1) can't find valid fat system
The system came with a Windows installation. The user booted the Ubuntu
installer from USB, erased the Windows partitions, and told the
installer to use the entire disk for Ubuntu. The partitioning reported
failure to mount boot partition. The user rebooted and tried again. The
same happened.
>From a terminal we found the EFI SP was NTFS not FAT:
$ sudo blkid /dev/sda1
Label="recovery" UUID="XXXXXXXXXX" TYPE="ntfs" PARTBALE="EFI System PArtition"
PARTUUID="XXXXXXXXX"
We worked around the issue with:
$ sudo mkfs.vfat /dev/sda1
However, if this were required to be a multiboot system it sounds as if the
installer would be broken by there being an unexpected NTFS EFI System
Partition.
** Affects: ubiquity (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1509059
Title:
NTFS EFI System Partition causes failure to mount /boot partition
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1509059/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
