Bug 167436
Summary: | Adding partitions kills W2k when setting up dual boot on same drive | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Michael Wiktowy <michael.wiktowy> |
Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> |
Status: | CLOSED WONTFIX | QA Contact: | Mike McLean <mikem> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | Keywords: | FutureFeature |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-09-06 15:20:10 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Michael Wiktowy
2005-09-02 16:27:30 UTC
There's not really much of anything we can do to workaround this, AFAICT. Well ... like I said, this isn't really Fedora's fault and there isn't anything that anaconda can do to fix this situation. However, Fedora will get unfairly and silently blamed and Fedora will lose potential new users and lose reputation ... after all, Windows worked before and it doesn't after Fedora installation. Most people will not look further into it other than blowing away the whole disk and reinstalling Windows and never touching Linux again. So the least that could be done is to detect this potentially harmful situation (single ntfs partition + >137GB drive + dual boot installation on the same drive) and have anaconda pop up a simple warning to direct the user to make sure that Windows displays free space after the Windows partition and, if not, install and run the drive manufacturers diagnostic utility from within Windows before proceding. A mention in the release notes or some sort of pre-installation checklist would be worthwhile. It is a corner case now but it is one that will become more prevalent as the average size drives grow bigger. You may not care about their Windows partition, but obviously they do. Otherwise they would have blown it away an not bothered to try to dual-boot. The only post installation fixes that I can think of are: 1) remove all other partitions other than the Windows one 2) possibly the DOS versions of the Drive utilities will fix this (most of them are found on UBCD) 3) It is likely just a simple registry key that is added. I have no doubt that there are offline Windows registry editors out there that can add these keys if they are known. Unfortunately, I didn't analyze the registry before and after to see what Western Digital Lifeguard added. So I couldn't tell you. |