From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux 2.4.2-2 i686; en-US; rv:0.9)
Description of problem:
I've created partitions 5-18 on a few disks, using fdisk. The last few
partitions failed to work because no devices were created for them in /dev.
Devices were up to /dev/hda16, but I needed /dev/hda17 and /dev/hda18.
Steps to Reproduce:
1.Create 14 logical partitions in a single disk
2.Install the system on it
3.Note that the system will be missing /dev/hda17 and /dev/hda18.
Actual Results: /dev/hda17 and /dev/hda18 are missing.
Expected Results: They should exist, so that the partitions in them could
I had included these partitions in RAID devices. The RAID devices were
created correctly, at installation time. I'm not sure they were usable
after the system boot, though, and I ended up having to re-install the system.
I think that the kernel can only address up to 16 partitions on an IDE drive.
There is the problem that Disk Druid and fdisk will let you create more than 16
partitions...that is addressed in bug #44115. But this particular bug is more
of a limitation of the kernel than anything else.
Well, perhaps it can't address more than 16 partitions, but I don't have 16
partitions: I've got hda1 as an extended partition and hda5-18, and, after I
created the devices, they started working. Perhaps this limitation is no longer
present in kernel 2.4?
I will try to reproduce this at work tomorrow, but I will be surprised if the
kernel can talk to partitions above hd*16, considering that the devices in the
/dev directory only go up to hd*16.
I am unable to get the kernel to mount or otherwise communicate with partitions
over hd*16. For example, I have partitions on an IDE drive /dev/hda1 -
/dev/hda20. The kernel will not mount partitions above /dev/hda16. The error
message I get when I try 'mount /dev/hda18 /mnt/foo' is:
'mount: special device /dev/hda17 does not exist'
To me, this seems more like a limitation of the kernel than a bug with the
I have partitions hda1 and hda5-hda18. After mknoding /dev/hda17 and
/dev/hda18, they worked fine. The only problem was that the installer didn't
create the devices, and this is the problem I'm reporting. Perhaps having more
than 16 partitions won't work, but I don't have more than 16 partitions, I have
``only'' 15, an extended partition and 14 logical ones.
this will take a bit of work, I'll do it first thing next cycle.
ide: 64 minors
scsi: 16 minors
dac960: 8 minors
ataraid: 16 minors
i20: 16 minors
cpqarray/cciss: 16 minors
*** Bug 56874 has been marked as a duplicate of this bug. ***
Deferred to future release.
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.