Bug 1466851

Summary: Fedora fails to recognize Windows 7’s system mirrored partition as well as unformatted free space.
Product: [Fedora] Fedora Reporter: ricky.tigg
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 28CC: anaconda-maint-list, g.kaviyarasu, jonathan, mkolman, vanmeeuwen+fedora, vponcova
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-05-28 19:49:41 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Above:in Windows, the original partition set. Down: Fedora's interpretation of the Windows partition's set. none

Description ricky.tigg 2017-06-30 14:39:44 UTC
Created attachment 1293253 [details]
Above:in Windows, the original partition set. Down: Fedora's interpretation of the Windows partition's set.

Description of problem:
In a test case aimed for creating a dual booted system with the obsolete Windows 7 and Fedora, Fedora fails to recognize some partitions made in Windows 7.

Version-Release number of selected component (if applicable):

How reproducible:
Steps to Reproduce:
1. On Qemu/KVM, create a two identical disk set (IDE) virtual machine,then install Windows 7, and mirror its system, Then shut down the system.
2. Boot with Fedora-Workstation-netinst-x86_64-26_Beta-1.4.iso and see partition tasks.

Actual results:
Fedora does not recognize Windows 7’s system mirrored partition as well as unformatted free space.

Expected results:
To have support for all partitions made in Windows 7.

Additional info:
Case accomplished on Qemu/KVM. Windows 7 was installed first. While attempting to install Fedora, disks buses’ type was kept the same as for the installation of Windows, which was IDE,

Comment 1 ricky.tigg 2018-04-04 15:59:37 UTC
Issue alive all the way from v. 26 to v. 28.

Fedora-Workstation-Live-x86_64-28_Beta-1.3.iso

Teste as virtual machine on QEMU-KVM virtualisation platform.

Comment 2 Martin Kolman 2018-04-04 16:06:13 UTC
The rpogressbar issue should be fixed in current Rawhide and next (28.22.3) F28 Anaconda release.

Comment 3 Martin Kolman 2018-04-05 10:35:13 UTC
Looks like I've mixed this bug up with bug 1463295, so I'm reopening this again and closing bug 1463295.

Comment 4 Ben Cotton 2019-05-02 19:21:31 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. 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 '28'.

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 28 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 Ben Cotton 2019-05-02 21:58:16 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. 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 '28'.

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 28 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 6 Ben Cotton 2019-05-28 19:49:41 UTC
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.