Bug 10532

Summary: RedHat 6.2 destroys Solaris x86 partition
Product: [Retired] Red Hat Linux Reporter: Frank Liu <gfrankliu>
Component: installerAssignee: Michael Fulbright <msf>
Status: CLOSED DUPLICATE QA Contact:
Severity: high Docs Contact:
Priority: medium    
Version: 6.2CC: jturner
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2000-04-24 13:36:44 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Frank Liu 2000-04-03 03:03:54 UTC
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
reinstall?

Frank

Comment 1 Frank Liu 2000-04-03 18:25:59 UTC
Just browsed through www.redhat.com and found
http://www.redhat.com/support/docs/gotchas/6.1/gotchas-6.1-4.html
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.

Frank

Comment 2 Frank Liu 2000-04-03 23:05:59 UTC
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:
http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=10001
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"
column.


Frank

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