Comment 79 for bug 1418706
Revision history for this message
| Phillip Susi (psusi) wrote Re: Vivid: UEFI: blank drive incorrectly detected as existing BIOS-mode install | #79 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
So my earlier analysis on this bug was correct, as evidenced by the new bug #1547286. The real underlying problem is still that the init.d scripts are executing *after* the commit.d scripts have written the partitions to the disk, and they are not intended to. Matthie's attempt at fixing this worked around the problem by allowing the script to see the newly created ESP so it concludes that there is already an EFI booting OS installed on the disk and does not complain. This isn't really true, but it at least stops the warning. In the case of this new bug, no ESP was created, and so the init.d script still erroneously concludes that some non EFI booting OS is already installed and the broken message pops up and hangs the install.