Bug 28644 - Disk Druid won't allocate partitions where requested
Disk Druid won't allocate partitions where requested
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Michael Fulbright
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2001-02-21 12:59 EST by Doug Ledford
Modified: 2007-04-18 12:31 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-02-21 13:00:02 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 Doug Ledford 2001-02-21 12:59:59 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.76 [en] (X11; U; Linux 2.2.17-11 i686)

Given a machine with a /dev/hda, /dev/hdb, and /dev/sda, with /dev/hda
being completely full with information I want saved, anaconda's disk druid
wouldn't allow me to create partitions on /dev/hdb.  Instead, if I left
only /dev/hdb selected as an available disk when making a partition, it
would show up on /dev/sda instead.  If I selected only /dev/sda as the
available drive, then it showed up on /dev/sda like it should.  I had to go
back and use the manual fdisk method to create partitions on /dev/hdb

Reproducible: Always
Steps to Reproduce:
1.  Have system with at least three drives, hda, hdb, sda
2.  Have /dev/hda be totally full
3.  Try to create a partition on /dev/hdb for /boot

Actual Results:  Partition was created on /dev/sda instead of /dev/hdb

Expected Results:  Should have created a partition on /dev/hdb
Comment 1 Michael Fulbright 2001-02-21 17:56:14 EST
/boot has to go on one of the first two drives on your system as seen by the
kernel. It sees /dev/hda as your first drive, and /dev/sda as your second. You
will need to put a /boot on either of these, or you can use a boot floppy.
Comment 2 Doug Ledford 2001-02-21 18:33:01 EST
On the contrary, lilo has no such restriction on the placement of the /boot
partition.  It happily went onto /dev/hdb when I forced it there by using fdisk
instead of disk druid.  Furthermore, /dev/hdb *is* the second disk in the system
according to both the BIOS and the kernel.  /dev/sda is the third disk.  If this
is an aritificial limitation of disk druid, then so be it, but it should be
documented as such since the rest of lilo and the kernel are happy for things to
be set up differently.

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