Description of problem:
nash unable to boot a Promise FastTrack RAID array with Fedora kernel > 2.6.16
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. install FC5 on a system with a Promise FastTrack RAID array and run pup to
upgrade to a kernel > 2.6.16
system hangs after printing the nash version
system to boot as it did after installing FC5
After consulting Bugzilla bugs 196556 and 196626, I grabbed
parted-1.7.1-9.1.src.rpm from the 5.91 development SRPMS directory and built it
and installed it. Then I rebuilt mkinitrd-5.0.32-1 and reinstalled it.
Finally, I remade the initrd*.img files and then I could boot a 2.6.17 kernel.
This has been broken for me for weeks and weeks and weeks! Please consider
releasing a parted-1.7.1 errata for FC5, ASAP.
Thanks for the report and additional research. That will save me some time.
I'll get a parted-1.7.1 update out for FC-5, but you'll also need a new mkinitrd
(maybe). You should open a bug for that and reference this bug. The maintainer
of mkinitrd can determine if a new one needs to be released or not.
parted-1.7.1-15.fc5 has been pushed for fc5, which should resolve this issue. If these problems are still present in this version, then please make note of it in this bug report.
Yes, I already prodded bug 189708 to rebuild the current mkinitrd against
parted-1.7.1 when it's released. I'll prod again when I see parted-1.7.1 arrive
as an update.
I pushed parted-1.7.1-15 to the FC-5 testing updates repository:
Please let me know if that one works for you and I'll move it to final. The guy
who builds mkinitrd sits across from me, so I'll see if he can get an update out
for FC-5 soon.
Works for me!
Moving to final.
And rebuilding mkinitrd against this parted is essential. And thanks for the
prompt response! It's really appreciated!!
Excuse me for the dumb question, but how do I rebuild mkinitrd?
Get the mkinitrd SRPM from FC5 or rawhide, and then do:
rpmbuild --rebuild name-of-src.rpm
I've rebuilt mkinitrd after installing parted-1.7.1-15 and parted-devel.
I then install the new mkinitrd rpm file using rpm -Uvh --force, reboot, still
Re: Comment 11
Did you install the new kernel before or after updating to the new mkinitrd?
If before you will probably need to rebuild your kernel image file using the new
#mv /boot/initrd-2.6.17-1.2174_FC5.img /boot/initrd-2.6.17-1.2174_FC5.img.old
#mkinitrd /boot/initrd-2.6.17-1.2174_FC5.img 2.6.17-1.2174_FC5
If necessary, replace "2.6.17-1.2174_FC5" with the your kernel name.
Alternatively you could try uninstalling and then reinstalling the 2.6.17 kernel
Ah thanks for that. It works now.
I did install the kernel before updating to the new mkinitrd.
A simple yum erase and yum install fixed it. All good now!!
Jafar - Happy now running kernel 2.6.17
On my "everything installed" FC5, I can't rpm -U parted-1.7.1 because "pyparted"
depends on libparted-1.6.
Never mind... I see pyparted-1.7.3 in testing/5. Maybe tomorrow with mkinitrd?
Keeping fingers crossed.
I've done updates for pyparted and mkinitrd. Did those on Wednesday. They are
both still sitting in testing/5 updates rather than final. Releng will be
moving them to final updates soon.
parted, pyparted, and mkinitrd updates have all been pushed to FC5 updates
final. The versions:
Closing this report. Thanks to all for testing!