Bug 621001 - Unable to boot new kernel 2.6.33.6-147.2.4.fc13.x86_64 for fedora 13
Summary: Unable to boot new kernel 2.6.33.6-147.2.4.fc13.x86_64 for fedora 13
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: dracut
Version: 13
Hardware: x86_64
OS: Linux
low
urgent
Target Milestone: ---
Assignee: Harald Hoyer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Keywords: Reopened
: 621344 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-03 22:54 UTC by Michael D Parker
Modified: 2010-08-05 06:53 UTC (History)
2 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2010-08-04 19:59:19 UTC


Attachments (Terms of Use)

Description Michael D Parker 2010-08-03 22:54:27 UTC
Description of problem:

After starting the boot process, I get the message

dracut: FATAL: osr: Cannot find parameter file /tmp/osr.nodeid.  This parameter is required and not set.
dracut: Refusing to continue

Signal caught!

Boot has failed, sleeping forever.


Version-Release number of selected component (if applicable):


How reproducible:
happens always

Steps to Reproduce:
1. simply install the 2.2.6.33.6-147.2.4.fc13.x86_64 kernel package
3.
  
Actual results:


Expected results:
The kernel 2.2.6.33-147 continues to boot just fine.

Additional info:

Comment 1 Harald Hoyer 2010-08-04 08:12:42 UTC
You installed osr-dracut-module-cluster ...

Why did you do that? Do you have an osr cluster? 
If yes, you have to configure the cluster.

If you don't have an osr cluster and blindly installed all packages with "dracut" in the name, then:

# yum remove osr-dracut-module osr-dracut-module-chroot \
  osr-dracut-module-cluster dracut-fips dracut-modules-olpc 

and recreate your initramfs image

# dracut -f /boot/initramfs-2.2.6.33.6-147.2.4.fc13.x86_64.img \
  2.2.6.33.6-147.2.4.fc13.x86_64

Comment 2 Michael D Parker 2010-08-04 19:41:22 UTC
*** Bug 621344 has been marked as a duplicate of this bug. ***

Comment 3 Michael D Parker 2010-08-04 19:51:22 UTC
I tried your suggestions and I still get the same result at reboot.

Comment 4 Michael D Parker 2010-08-04 19:59:05 UTC
There were typos in the command line as given by Mr. Hoyer.  The recreate of the initramfs image should be edited as follows :  s/2.2.6/2.6/g

Things now work correctly.

Comment 5 Harald Hoyer 2010-08-05 06:53:18 UTC
(In reply to comment #4)
> There were typos in the command line as given by Mr. Hoyer.  The recreate of
> the initramfs image should be edited as follows :  s/2.2.6/2.6/g
> 

sorry, I blindly copy & pasted the version from comment 1


Note You need to log in before you can comment on or make changes to this bug.