Bug 85631 - Cannot install Phoebe with Smart Boot Manager
Cannot install Phoebe with Smart Boot Manager
Status: CLOSED WONTFIX
Product: Red Hat Linux
Classification: Retired
Component: parted (Show other bugs)
9
i386 Linux
medium Severity low
: ---
: ---
Assigned To: Matt Wilson
Brock Organ
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-03-05 04:36 EST by Kazutoshi Morioka
Modified: 2007-04-18 12:51 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-06-25 14:56:05 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Kazutoshi Morioka 2003-03-05 04:36:34 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.8 (X11; Linux i686; U;) Gecko/20030212

Description of problem:
I'm using Smart Boot Manager (SBM) as a bootmanager.
Phoebe installer failed to detect patition table on my machine using SBM.
My machine's partition type was not detected correctly as msdos,
but as "loop" patition type (like a filesystem on floppy).
This is SBM's fault. not a bug of Phoebe installer nor GNU parted.
SBM incorrectly put a fat filesystem signature, "FAT12" in offset 0x36
bytes from beginning of disk.
So, GNU parted will think this is a raw FAT filesystem.
I tried to clear from offset 0x36 to 0x3a with SPACE code, 0x20.
Then, I can successfully install Phoebe.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Install SBM into Master Boot Record.
2. Try to install Phoebe.
3. Proceed to disk-druid.
    

Actual Results:  Incorrect partition type "loop" is detected, and failed to install.

Expected Results:  Correctly detect "msdos" partition table, and diskdruid is
showing up.

Additional info:

What to be fixed is SBM.
Editing partition table with hexedit is easy for me,
But there is no other out-of-the-box solution for this problem.
Uninstalling SBM leave a FAT signature on the MBR.
So that, uninstalling SBM dose not solve this.
At least, please mention this in the RELEASE-NOTES.

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