Bug 1386162 - F25 Beta unable to erase existing F24 partitions
Summary: F25 Beta unable to erase existing F24 partitions
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 25
Hardware: i686
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-18 10:13 UTC by Laurentiu Pancescu
Modified: 2017-12-12 10:54 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-12 10:54:23 UTC
Type: Bug


Attachments (Terms of Use)

Description Laurentiu Pancescu 2016-10-18 10:13:07 UTC
I tried to install F25 Beta XFCE from an USB stick, on an Atom netbook already having F24 XFCE installed (standard install without disk encryption).  In the partitioning phase, I left automatic partitioning checked.  Anaconda correctly detected that only 1.8MB free disk space is available and it started the Reclaim Space tool when clicking on "Done".  In that dialog, neither clicking "Delete all" nor deleting the two partitions individually didn't allow me to proceed: the "Reclaim space" button (bottom right) remained disabled.  I had use cfdisk from a Terminal to erase all partitions, and was then able to install F25 without any issues.

The existing F24 installation was a standard install, just 2 partitions created by Anaconda's F24 defaults: /boot and an unencrypted LVM containing the rest of the disk.

Comment 1 Kamil Páral 2016-11-21 14:28:48 UTC
You'll need to upload anaconda logs if developers are supposed to find the problem. The logs are usually in /tmp on Live images. This might also be specific to i686 architecture, because we definitely tested this use case thoroughly on x86_64. Removing CommonBugs until we can show that this is a more wide-spread and not a single-host issue.

Comment 2 Laurentiu Pancescu 2016-11-22 12:38:51 UTC
I just tested RC-1.3 x86_64 on another machine, and it worked as expected with existing partitions. It might indeed be an i686 issue.  I can try again i686 on the first machine once F25 is officially released and collect the logs.

Comment 3 Laurentiu Pancescu 2017-06-23 09:46:29 UTC
I just tried again with the latest nightly build of F26 Live Xfce. [1]  The calculated disk space after marking the two partitions as "delete" is shown as 4.5GB, which is wrong (only a 16MB partition remains allocated, from a 160GB disk), but the "Reclaim space" button becomes enabled, so it would be possible to continue with the installation.  I think this is bug #1165733 - not sure if it's just a cosmetic issue, or if it will calculate the partitions based on the displayed value, so I didn't continue.

As far as I'm concerned, please feel free to close this bug.

[1] https://kojipkgs.fedoraproject.org/compose/branched/Fedora-26-20170622.n.0/compose/Spins/i386/iso/Fedora-SoaS-Live-i386-26-20170622.n.0.iso

Comment 4 Fedora End Of Life 2017-11-16 19:50:50 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 5 Fedora End Of Life 2017-12-12 10:54:23 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.