Bug#777647: marked as done (partman-efi always complains when installing from usb)
Your message dated Tue, 17 Feb 2015 23:02:12 +0000
with message-id <20150217230212.GG12370@einval.com>
and subject line Re: Bug#777647: partman-efi always complains when installing from usb
has caused the Debian Bug report #777647,
regarding partman-efi always complains when installing from usb
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
777647: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777647
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: partman-efi
Version: 59
partman-efi uses flawed logic that trips up when installing from usb.
init.d/efi scans the system and counts the number of efi system
partitions, and the number of non efi system partitions. If it does not
find an EFI system partition, but does find at least one non ESP, then
it throws the non_efi_system warning/question. The problem is that when
installing to a disk that does not already have an efi system partition,
the script *always* detects a non EFI system partition, and throws the
warning. This may be connected to a recent change in libparted.
Looking at the partman logs and the output after adding a set -x to the
init.d/efi script, it appears to me that what is happening is that the
system asks libparted to create a new partition on the hard disk that
will become an EFI system partition. Either init.d/efi runs before the
partition has been formatted with a fat filesystem, or parted_server is
still running and is keeping the "ext2" fs type cached from before it
was formatted. Either way, the script decides it sees an ext2
filesystem on the drive, and that counts as a non EFI system partition,
and so it throws the message.
Forwarding this from launchpad bug #1418706 in Ubuntu.
--- End Message ---
--- Begin Message ---
On Tue, Feb 17, 2015 at 12:56:07PM -0500, Phillip Susi wrote:
>On 2/17/2015 1:37 AM, Steve McIntyre wrote:
>> Any futher clues on this at all? I have next to no knowledge about how
>> the Ubuntu installer code uses the d-i packages, which makes it
>> difficult for me to comment much more.
>
>I emailed a log with my attempt at analyzing it to Colin Watson the
>other day and am still waiting to hear back from him. I think you can
>close this bug now as I'm fairly certain it is an Ubiquity issue. I
>looked at some logs from older releases and indeed they all seem to run
>all of the init.d scripts first, and only later process the visual.d and
>other scripts, so somehow ubiquity must be running things wrongly and
>getting the visual.d scripts to run before the init.d ones and that is
>the cause of the problem.
Right, OK. Closing!
>I do still wonder though, why the script doesn't trip up when installing
>from a USB stick. Is there some logic somewhere I don't see that causes
>all of partman to ignore/forget about the disk you are installing from,
>so that the efi script doesn't see that and count it as a non ESP?
Yes, I think there is - but don't ask me to find it just now! :-)
Presumably the bit where we detected and mount the "CD" that's
included on the USB stick...
--
Steve McIntyre, Cambridge, UK. steve@einval.com
"Because heaters aren't purple!" -- Catherine Pitt
--- End Message ---
Reply to: