Red Hat Bugzilla – Bug 234133
Kernel panic caused by failure in initrd after standard installation
Last modified: 2007-11-30 17:07:43 EST
Description of problem:
After a normal installation including software RAID of Red Hat Enterprise
Linux 5 (Server) at a HP rx2600 Itanium 2 server, the boot process ends with
the screenshot attached below.
/dev/md0 ext3 15202.1MB
(one disk as hotspare)
/dev/sda1 vfat 102MB (boot)
/dev/sda2 Software Raid 15202MB
/dev/sda3 swap 1992MB
/dev/sdb2 Software Raid 15202MB
/dev/sdb1 swap 2157MB
/dev/sdc2 Software Raid 15202MB
/dev/sdc1 swap 2157MB
Version-Release number of selected component (if applicable):
Standards from Red Hat Enterprise Linux 5 release.
Everytime on a HP rx2600 Itanium 2 server.
Non-bootable system after standard installation.
Bootable system after standard installation...
Created attachment 151011 [details]
Screenshot from kernel panic
Sounds like something is missing from the initrd image.
what does the initrd image looks like?
Unfortunately I'm only the man-in-the-middle (ex-colleague with the server
and myself with some knowledge and the interest to solves this problem, as HP
rx2600 Itanium 2 servers are common machines).
For now, I can provide you a "lspci -vvv" output from RHEL4 on the same
machine, because the box is a project machine and should work (which does
currently only with RHEL4). If there are any information, I'm able to obtain
when having RHEL4, let me know. I don't know, when there's time and the
possibility to re-install RHEL5 for another try and further information. And
please let me know, what is needed exactly for further debugging purposes.
Created attachment 151150 [details]
"lspci -vvv" output (using RHEL4 on the same machine)
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
Hum? Did I miss something? Where is the real fix for this problem?
Can you boot again without the "quiet" option and show the output from *that*,
so we'll have more than just the error messages?
Well, nice that you're willing to help nearly two months later when the machine
went to production use with RHEL4 :( But I'll see whether I can get another box
having this problem, too.
Development Management has reviewed and declined this request. You may appeal
this decision by reopening this request.