Bug 438420

This bug is continued from #429937
In the above bug report, Jeremy Katz introduced a change in mkinitrd which
should solve the problems reported in that bug report. However, since that
change (mkinitrd-6.0.34-1,
http://koji.fedoraproject.org/koji/buildinfo?buildID=41744) my computer became
unbootable.

These are the last lines which were produced :

device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.13.0-ioctl (2007-10-18) initialised: dm-devel
device-mapper: table: 253:0 linear: dm-linear: Device lookup failed
device-mapper: ioctl: error adding target to table
device-mapper: reload ioctl failed: Invalid argument
device-mapper: table ioctl failed: No such device or address
device-mapper: deps ioctl failed: No such device or address
init[1]: segfault at 10 ip 00a5b10a sp bfa1640c error 4 in
libdevmapper.so.1.02[a4d000+15000]
nash received SIGSEGV! Backtrace (14):
/bin/nash[0x805365a]
[0x11040c]
/usr/lib/libnash.so.6.0.34(nashDmDevGetName+0x5a)[0x11f40e]
/usr/lib/libnash.so.6.0.34[0x11b7e7]
/usr/lib/libnash.so.6.0.34[0x11b911]
/usr/lib/libnash.so.6.0.34(nashBdevIterNext+0x109)[0x11bd9b]
/usr/lib/libnash.so.6.0.34[0x11c037]
/usr/lib/libnash.so.6.0.34(nashFindFsByName+0x6e)[0x11c130]
/usr/lib/libnash.so.6.0.34(nashAGetPathBySpec+0xa5)[0x11c24a]
/bin/nash[0x804f2fb]
/bin/nash[0x80534c5]
/bin/nash[0x8053bcd]
/lib/libc.so.6(__libc_start_main+0xe6)[0x16f606]
/bin/nash[0x804afa1]

If I revert back to mkinitrd-6.0.33-1 and regenerate the initrd.img my system
boots fine. This problem is still occuring with mkinitrd-6.0.39-1,
http://koji.fedoraproject.org/koji/buildinfo?buildID=43199.

My hardware specifications:

Pentium 4 2.4Ghz
1GB RAM
Fedora Rawhide i386

The motherboard itself only has PATA connections. I've installed a
SATA-PCI-controller in my computer.

Fedora is installed on a SATA drive. Due to the fact that I can't directly boot
off this SATA drive I have a /boot partition on a PATA drive.

Another thing I found out is that if I boot anaconda's rescue mode and let it
search for existing Linux installations, then anaconda crashes. I think this
might be related to this bug. I don't have the exact backtrace anymore, but I
can regenerate it if necessary. This was with anaconda-11.4.0.52-1