Had a hard drive (second drive) with no primary partition,
although there was 0.4Mb free in this area.
There where two extended partitions with one 50Mb for windows
swap and 300Mb for dos backup, wanted to use the remaining
~60Mb for Linux swap.
DiskDruid where told to create a new partition with the size
of free space.
RESULT: DiskDruid allocated a partition starting in the
primary partition part, thereby overwriting data in existing
Lucky me, I stopped the installation and checked the
partition tables before any formating was done.
Fixed the problem by deleting this erroneus partition with
DOS fdisk, created the partition with Partition Magic (that
reported the problem) and changed the type with Linux fdisk.
For information: OS/2 fdisk has this same kind of problem.
Due to this small free space in the primary partition part.
This is the programmer behavior of Disk Druid. Users that want to control where
partitions reside on a drive are encouraged to use fdisk.
I didn't know it was the intended behaviour of DiskDruid to thrash other
partitions content, if so, please show that in bold face on your distribution
Please have someone that understand partitions tables to review this
bug. (I mailed jturner about his comment, but he didn't seem to
understand the problem).
What installation option did you use? Did you elect to use automatic
partitioning at all? This should all be resolved in the new code in the next
version. You can preview it in the Red Hat Linux Roswell beta at