Created attachment 409232 [details] Kernel boot messages. Description of problem: Have a two node GFS2 cluster running RHEL 5.4+errata. I recently upgrade one node to 5.5 and rebooted. Near the end of the bootup process, I see the following: mount: could not find filesystem '/dev/root' Setting up other filesystems. Setting up new root fs setuproot: moving /dev failed: No such file or directory no fstab.sys, mounting internal defaults setuproot: error mounting /proc: No such file or directory setuproot: error mounting /sys: No such file or directory Switching to new root and running init. unmounting old /dev unmounting old /proc unmounting old /sys switchroot: mount failed: No such file or directory Kernel panic - not syncing: Attempted to kill init! <0>Rebooting in 180 seconds.. Version-Release number of selected component (if applicable): kernel-2.6.18-194.el5 mkinitrd.5.1.19.6-61.ppc64 mkinitrd.5.1.19.6-61.ppc How reproducible: Always Steps to Reproduce: 1. Boot from kernel-2.6.18-194.el5 Actual results: Unable to mount /dev/root Expected results: System boots normally. Additional info: I had been running a dev kernel from support on this cluster: kernel-2.6.18-185.el5. This kernel boots up fine (with the rest of the RHEL 5.5 userspace). The hardware is a JS20 POWER blade. We are attaching to two FC LUN's with multipath -- but the OS is installed on a local IDE disk. "root" in the yaboot.conf file references the LV path.
yaboot.conf: # yaboot.conf generated by anaconda boot=/dev/hda1 init-message=Welcome to Red Hat Enterprise Linux Server!\nHit <TAB> for boot options partition=2 timeout=80 install=/usr/lib/yaboot/yaboot delay=5 enablecdboot enableofboot enablenetboot nonvram fstype=raw image=/vmlinuz-2.6.18-194.el5 label=2.6.18-194.el5 read-only initrd=/initrd-2.6.18-194.el5.img root=/dev/VolGroup00/LogVol00 append="console=hvc0" image=/vmlinuz-2.6.18-185.el5 label=2.6.18-185.el5 read-only initrd=/initrd-2.6.18-185.el5.img root=/dev/VolGroup00/LogVol00 append="console=hvc0"
I filed this against mkinitrd since it seemed other "similar" bugs (though none on POWER) were related to it. Perhaps it's the kernel though.
Please close as NOTABUG per http://kbase.redhat.com/faq/docs/DOC-29361