Bug 38173
Summary: | Installer overwrote existing partition with swap | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Need Real Name <alphajim> |
Component: | anaconda | Assignee: | Brent Fox <bfox> |
Status: | CLOSED NOTABUG | QA Contact: | Brock Organ <borgan> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 7.1 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2001-05-14 20:08:47 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
Need Real Name
2001-04-28 05:13:47 UTC
I'm not really sure what the problem is here. During an upgrade, if the installer detects that you do not have enough existing swap (about 2 times the amount of RAM you have), then it will create a swap file on the partition of your choice. The installer does *not* create swap partitions during upgrades, so I'm pretty confused by the behavior that you saw. While making the swap file, it clobbered the partition and rendered the system unbootable and the partition unreadable. It was the only linux native part on the disk. How much free space was available before it tried to make the 400MB swap file? It would of been close to all the available space. Maybe even more. Not sure, and I don't have a good backup of the system just prior to the install. It was a "throw-away" install that I wanted to test the new version on. Since you have reformatted the machine, there's not much hope of knowing exactly what went wrong. When you used Partition Magic to create the swap partition, did you reboot into the 6.1 system and run mkswap? If you didn't, the installer probably didn't know what to make of your existing partition table. There is a good chance that your partition table after using Partition Magic is no longer in sync with your /etc/fstab file. The installer probably got confused when it read an /etc/fstab file that no longer described the hard drive's partition table. Closing due to inactivity. Please reopen if you have more information. |