Bug 77223 - A FreeBSD partition is destroyed when RH 8.0 is installed
A FreeBSD partition is destroyed when RH 8.0 is installed
Product: Red Hat Linux
Classification: Retired
Component: parted (Show other bugs)
i686 Linux
medium Severity high
: ---
: ---
Assigned To: Jeremy Katz
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2002-11-03 11:29 EST by Marian-Nicolae ION
Modified: 2007-04-18 12:48 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-11-04 09:00:36 EST
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 Marian-Nicolae ION 2002-11-03 11:29:14 EST
From Bugzilla Helper: 
User-Agent: Mozilla/5.0 (compatible; Konqueror/3; Linux 2.4.20-pre11-mni; X11; 
i686; , en_US.UTF-8, en_US, en) 
Description of problem: 
After the partition phase of the installation, when RH assigns mount points, 
it badly reports a FreeBSD partition (type 0xa5) as a "reiserfs" partition. 
Once the installation is finished, FreeBSD does not boot anymore and one 
should completely reinstall it. 
Version-Release number of selected component (if applicable): 
FreeBSD 4.7; RedHat 8.0 - both on a Pentium III PC. 
How reproducible: 
Steps to Reproduce: 
1. install FreeBSD 
2. install RH 8.0 
3. add the following lines in /boot/grub/menu.lst 
title FreeBSD 
        root (hd1,0,a) 
        kernel /boot/loader 
4. try to boot again in FreeBSD - GRUB displays "bad partition" (or something 
like that) 
Actual Results:  I couldn't boot in FreeBSD anymore! 
Expected Results:  To normally boot in my FreeBSD! Once reinstalled, using the 
same GRUB menu.lst file, it normally booted! 
Additional info:
Comment 1 Jeremy Katz 2004-06-25 14:40:44 EDT
Does this still happen with newer releases?
Comment 2 Jeremy Katz 2004-11-04 09:00:36 EST
Closing due to inactivity.  Please reopen this bug if you have further
information to add to the report.

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