[Bug 1065281] Re: Installer crashed when trying to partition 4k/4k sector hard disks

[Colin Watson]

Aha, got it: the efidisk module is working but the FAT file system
support isn't quite right, so it's just the EFI System Partition that
GRUB has trouble reading.  The missing commit is this one, which is in
2.00 thus explaining why this works in more recent releases:

http://git.savannah.gnu.org/gitweb/?p=grub.git;a=commitdiff;h=daa59f47f6818d2a2c90526be5b2b38a11770dc1

Doing a full boot loader test is awkward due to the involvement of a
signed image, but I've confirmed the bug with grub-fstest and grub-
mount, and built versions of those tools with that patch which can
successfully read all the files under /EFI/ubuntu/.  I'll prepare a
backport.

** Changed in: grub2 (Ubuntu Precise)
       Status: Fix Committed => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to efibootmgr in Ubuntu.
https://bugs.launchpad.net/bugs/1065281

Title:
  Installer crashed when trying to partition 4k/4k sector hard disks

Status in The Dell PowerEdge project:
  In Progress
Status in OEM Priority Project:
  Fix Committed
Status in OEM Priority Project precise series:
  In Progress
Status in OEM Priority Project quantal series:
  In Progress
Status in OEM Priority Project raring series:
  Fix Released
Status in Release Notes for Ubuntu:
  Invalid
Status in Release Notes for Ubuntu quantal series:
  Triaged
Status in “dosfstools” package in Ubuntu:
  Fix Released
Status in “efibootmgr” package in Ubuntu:
  Fix Released
Status in “grub2” package in Ubuntu:
  Fix Released
Status in “grub2-signed” package in Ubuntu:
  Fix Released
Status in “partman-auto” package in Ubuntu:
  Fix Released
Status in “partman-base” package in Ubuntu:
  Fix Released
Status in “partman-basicfilesystems” package in Ubuntu:
  Fix Released
Status in “partman-efi” package in Ubuntu:
  Fix Released
Status in “ubiquity” package in Ubuntu:
  New
Status in “dosfstools” source package in Precise:
  Fix Released
Status in “efibootmgr” source package in Precise:
  Fix Committed
Status in “grub2” source package in Precise:
  In Progress
Status in “grub2-signed” source package in Precise:
  Fix Committed
Status in “partman-auto” source package in Precise:
  Fix Released
Status in “partman-base” source package in Precise:
  Fix Committed
Status in “partman-basicfilesystems” source package in Precise:
  Fix Released
Status in “partman-efi” source package in Precise:
  Fix Committed
Status in “ubiquity” source package in Precise:
  Fix Committed
Status in “dosfstools” source package in Quantal:
  Fix Released
Status in “efibootmgr” source package in Quantal:
  Triaged
Status in “grub2” source package in Quantal:
  Triaged
Status in “grub2-signed” source package in Quantal:
  Triaged
Status in “partman-auto” source package in Quantal:
  Triaged
Status in “partman-base” source package in Quantal:
  Triaged
Status in “partman-basicfilesystems” source package in Quantal:
  Fix Released
Status in “partman-efi” source package in Quantal:
  Triaged
Status in “ubiquity” source package in Quantal:
  Won't Fix

Bug description:
  partman_server crashes on Ubuntu 12.10 server for amd64 when trying to
  partition an Advanced Format (4k / 4k sector) hard disk.

  Disks that utilize 4k sectors with 512 emulation work fine.  The
  installer has no problems with those.

  Steps to Reproduce:
  1) Begin the installation in EFI mode. 
  2) At the disk partitioning stage, select "Guided use Entire Disk" or "Manual"
  3) Review and accept the proposed partitioning scheme and write changes to disk. 

  Actual Results:
  The system will attempt to create a the EFIboot partition.  At this stage the installer appears to hang.   Pressing Ctrl+AltF4 reveals that parted_server has crashed with the following message:

  parted_server[13865]: segfault at 22fa000 ip 00007fa6eb74bee7 sp
  00007fffec3ab500 error 4 in libparted.so.0.0.1[7fa6eb735000+64000]

  Expected results:
  Installation should carry on without a crash.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-poweredge/+bug/1065281/+subscriptions