Red Hat Bugzilla – Bug 28644
Disk Druid won't allocate partitions where requested
Last modified: 2007-04-18 12:31:38 EDT
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
/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.
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.