It is not possible to boot into the PVCfL 4.7 kernel on CentOS 5.x after upgrading to PVCfL 4.7 if the root is placed on software RAID built with dmraid.
A similar output may be observed on the server console: `switchroot mount failed: No such file or directory.
[3.668771] Kernel panic - not syncing. Attempted to kill init! [3.668887] Pid: 1, comm: init veid2 0 Not tainted 2.6.32—042stab044.11 #1 [3.669000] Call Trace2 [3.669111] [<ffffffff814ca02c>] ? panic+0x78/0x143 [3.669228] [<ffffffff8106f229>] ? do_exit+0x909/0x910 [3.669401] [<ffffffff8106f288>] ? do_group_exit+0x58/0xd0 [3.669515] [<ffffffff8106f317>] ? sys_exit_group+0x1?/0x20 [3.669632] [<ffffffff8100b242>] ? system_call_fastpath+0x16/0x1b`
initrd contains following commands to detect
dmraid on boot:
echo Scanning and configuring dmraid supported devices dmraid -ay -i -p --rm_partitions "ddf1_RootVG" kpartx -a -p p "/dev/mapper/ddf1_RootVG"
These commands fail to detect
dmraid which causes boot to fail.
This behavior was reported as a product issue #PCLIN-31691.
Until the fix for PCLIN-31691 is released, please use one of the following workarounds:
- Re-install the OS to CentOS 6 to gain full support for
- Split the software RAID and use separate physical disks.
It is strongly recommended to use first suggestion (to re-install the host OS) as CentOS 6 is a native environment for 2.6.32 kernel family, and CentOS 5 cannot be as reliable as CentOS 6 while running on 2.6.32 kernel.
You might want to check following related article: