Description of problem: There is a partitionable array md_d0 (raid1) with 9 partitions which should be available during system boot up. But the raidautorun of nash does not start it properly and the system fails to start up with stock initrd. Manual intervention is necessary: one has to add mdadm.static to the initrd filesystem and insert proper (mdadm) command line into the init nash script to revive the system. Version-Release number of selected component (if applicable): 4.2.15-1 How reproducible: 100% Steps to Reproduce: 1. Create partitionable array with a handfull of partitions in it. 2. Use those partitions in the system layout. 3. Add appropriate `raidautorun' line to init nash script (within initrd) 4. Reboot the system and see if raidautorun starts that partitionable array. Actual results: raidautorun does not create correct partition layout and correspondent block devices. Expected results: Partitionable array should be started with correct partition layout and correspondent block devices (per partition). Additional info: 1. It looks like madadm itself has the same bug: without explicit command line option (-ap9) it does not create correct number of devices for partitions within a partitionable array. 2. I have tried to update the system to fc5 and fc6 but failed, as the upgrade scripts failed to startup correct filesystem layout. So it looks like the problem is still there. 3. The necessity of such layout (partitionable array with 9 partitoions in it) has been caused by the (%*^#%&!) 15 partitions restriction in fdisk (added there by redhat for a reason I still refuse to understand). And, btw, fc6 rescue-cd and cd1 do not contain sfdisk which could be used as a (manual) workaround over that stupid restriction. (sorry, I despise druid and similar tools).
This report targets the FC3 or FC4 products, which have now been EOL'd. Could you please check that it still applies to a current Fedora release, and either update the target product or close it ? Thanks.
The problem is still there, at least in FC5. Haven't tried it in FC6 yet, as the machine runs in production mode (frequent changes are deprecated).
Fedora apologizes that these issues have not been resolved yet. We're sorry it's taken so long for your bug to be properly triaged and acted on. We appreciate the time you took to report this issue and want to make sure no important bugs slip through the cracks. If you're currently running a version of Fedora Core between 1 and 6, please note that Fedora no longer maintains these releases. We strongly encourage you to upgrade to a current Fedora release. In order to refocus our efforts as a project we are flagging all of the open bugs for releases which are no longer maintained and closing them. http://fedoraproject.org/wiki/LifeCycle/EOL If this bug is still open against Fedora Core 1 through 6, thirty days from now, it will be closed 'WONTFIX'. If you can reporduce this bug in the latest Fedora version, please change to the respective version. If you are unable to do this, please add a comment to this bug requesting the change. Thanks for your help, and we apologize again that we haven't handled these issues to this point. The process we are following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp We will be following the process here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this doesn't happen again. And if you'd like to join the bug triage team to help make things better, check out http://fedoraproject.org/wiki/BugZappers
> > We strongly encourage you to upgrade to a current Fedora release. > To my regret I cannot upgrade to a later Fedora release as since Fedora 7 PATA disks are always treated as SCSI disks and SCSI disks cannot contain more than 15 partitions, while I do have more than twenty of them. It seems I should have to switch to some other Linux distribution.
Thank you for taking the time to give us an update.