Description of problem:
Specifically, I have a Promise FastTrak 376 controller (20376) controller with a
Parallel IDE hard drive connected using the PATA/IDE port of this otherwise SATA
The controller is in the sda position with a logical partition in sda5.
The dmraid system, recognizes it as: /dev/pdc_ccdejaib and /dev/pdc_ccdejaib5
However, the rc.sysinit script calls 'dmraid.static -ay -i -p -t' which only
discovers and activates the device itself (pdc_ccdejaib) but not the partition
As a result, when fsck tries to check the /dev/pdc_ccdejaib5 partition cited in
my fstab, it barfs since that device is non-existent being that the partition
has not yet been activated.
I can "solve" the problem by adding a line 'dmraid.static -ay -i' to the
rc.sysinit file but that seems like a kluge.
Not sure what the right way to fix this is...
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Have something like a Promise Raid FastTrack controller (on /dev/sda)
2. Add entry into fstab of form:
/dev/mapper/pdc_ccdejaib5 /mnt/mydrive ext3 defaults 1 2
3. Boot linux
Crashes on fsck of the above partition
Use "/dev/mapper/pdc_ccdejaibp5" instead of "/dev/mapper/pdc_ccdejaib5" --
initscripts is using "kpartx -a -p p /dev/mapper/pdc_ccdejaib" to build the
It's done this way because some tools use the separator and some tools don't for
various device-mapper devices, so this makes it _more_ consistent, even though
it's slightly less obvious :/
To be clear, are you saying that I should just add the letter "p" before the
partition number (5). Because, I just tried that and it didn't help.
Indeed, /dev/mapper only shows the following devices:
And running: kpartx -l -p p /dev/mapper/pdc_ccdejaib
pdc_ccdejaibp5 : 0 398283354 /dev/mapper/pdc_ccdejaib 126
Still seems to be a bug. Solution suggested by Peter Jones did not resolve issue.
I would be happy to help troubleshoot...
Not sure if this is relevant, but I notice that every time my kernel starts up,
it gives me the following error message in /var/log/messages:
kernel: device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised:
kernel: device-mapper: table: 253:0: linear: dm-linear: Device lookup failed
kernel: device-mapper: ioctl: error adding target to table
Also, on the boot screen, I see the following message:
device-mapper: reload ioctl failed: Invalid argument
Does this help shed any light on the problem?
Still NOT FIXED!
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.
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
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:
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
This bug is open for a Fedora version that is no longer maintained and
will not be fixed by Fedora. Therefore we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen thus bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.