Bug 10532 - RedHat 6.2 destroys Solaris x86 partition
RedHat 6.2 destroys Solaris x86 partition
Status: CLOSED DUPLICATE of bug 5539
Product: Red Hat Linux
Classification: Retired
Component: installer (Show other bugs)
All Linux
medium Severity high
: ---
: ---
Assigned To: Michael Fulbright
Depends On:
  Show dependency treegraph
Reported: 2000-04-02 23:03 EDT by liug
Modified: 2008-05-01 11:37 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-04-24 09:36:44 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description liug 2000-04-02 23:03:54 EDT
It's a common knowledge that Solaris x86 and Linux swap have
the same partition id. RedHat 6.1 seems to be fine but yesterday
when I installed RedHat 6.2, I can no longer boot my Solaris x86
partition. During the RedHat 6.2 (I used "expert text") installation, there
is no way I can choose which of the two swap partitions (one of
which is Solaris x86 of course) I want to use, installer automatically
format(?) both paritions as linux swap.
Is there a way I can recover my Solaris x86 partition without

Comment 1 liug 2000-04-03 14:25:59 EDT
Just browsed through www.redhat.com and found
it talks about this problem under item 4.12.

I am surprised to see the problem was there since 6.1 (I don't know
why I didn't noticed it) and am wondering why it isn't fixed in 6.2.
Or at least in the expert mode, it should give me a choice to use (or not use)
which swap partitions.

Comment 2 liug 2000-04-03 19:05:59 EDT
I remember it now. I had the same problem back when I was installing
redhat 6.1. I managed to recover my Solaris partition without re-installing.
I will do the same trick again and see if I can get my Solaris partition
back. Still it is bad to see a bug in 6.1 not fixed in 6.2.
By the way, I just found the same bug reported in bugzilla:
The reason I didn't find it when I originally submitted my bug report is
because bug 10001 is marked as "CLOSED" and won't be in the search
by default. I have to explicitly check search for "CLOSED" in the "Status"

Comment 3 Jay Turner 2000-04-24 09:36:59 EDT
*** This bug has been marked as a duplicate of 5539 ***

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