Bug 523268 - anaconda kickstart removing NTFS partitions
Summary: anaconda kickstart removing NTFS partitions
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: anaconda
Version: 5.4
Hardware: x86_64
OS: Linux
low
high
Target Milestone: ---
: ---
Assignee: Anaconda Maintenance Team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-09-14 16:46 UTC by Murray Anderegg
Modified: 2009-09-14 17:15 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-09-14 17:15:21 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Murray Anderegg 2009-09-14 16:46:45 UTC
Description of problem:

anaconda clearpart --linux is removing non-linux partitions from selected drive.


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

RHEL 5.4 


How reproducible:

This has happened repeatedly on systems with an NTFS/HPFS (type 7) partition both with and without actual NTFS filesystems.


Steps to Reproduce:
1. Clear partitions on drive hda.
2. Create one primary partition in partition 1 of type 7 on drive hda.
3. Kickstart and include the following directives:

zerombr
clearpart --linux --initlabel --drives=hda

Actual results:
Partition 1 is removed and disk is partitioned according to requested partitioning scheme.


Expected results:
Partition 1 should have been left intact and the Linux partitions should have been in later partitions on drive hda.

Additional info:
This occurred on both i386 and x86_64 systems.
This occurred on drives with one Windows partition of type 7 and two Windows partitions of type 7.

Enclosed find /tmp/part-include

Comment 1 Chris Lumens 2009-09-14 17:15:21 UTC
According to http://fedoraproject.org/wiki/Anaconda/Kickstart, clearpart --initlabel creates a new disklabel on the drives specified.  This is why you are losing the non-linux partitions.


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