My best guess (having "tested" this theory several times personally) is that you added several disks (maybe two?) to the system and added them into LVM groups, but forgot to edit modprobe.conf and execute the mkinitrd and zipl following the additions.
This is guaranteed to give varying weird results such as what you are now seeing. -- Robert P. Nix Mayo Foundation .~. RO-OE-5-55 200 First Street SW /V\ 507-284-0844 Rochester, MN 55905 /( )\ ----- ^^-^^ "In theory, theory and practice are the same, but in practice, theory and practice are different." On 4/26/10 8:00 AM, "Frank M. Ramaekers" <[email protected]> wrote: > There was a normal shutdown of RHEL 5 on Friday, but today: > > > > Waiting for driver initialization. > > > Scanning and configuring dmraid supported devices > > > Scanning logical volumes > > > Reading all physical volumes. This may take a while... > > > Couldn't find device with uuid > 'ogvezr-vkSF-BPI5-mGBq-tKY5-1NOz-GOVHot'. > > Couldn't find device with uuid > '5vu4wT-amMD-6LEm-Q59g-uAxb-POZu-VI5cN1'. > > Couldn't find device with uuid > 'ogvezr-vkSF-BPI5-mGBq-tKY5-1NOz-GOVHot'. > > Couldn't find device with uuid > '5vu4wT-amMD-6LEm-Q59g-uAxb-POZu-VI5cN1'. > > Couldn't find device with uuid > 'ogvezr-vkSF-BPI5-mGBq-tKY5-1NOz-GOVHot'. > > Couldn't find device with uuid > '5vu4wT-amMD-6LEm-Q59g-uAxb-POZu-VI5cN1'. > > Couldn't find device with uuid > 'ogvezr-vkSF-BPI5-mGBq-tKY5-1NOz-GOVHot'. > > Couldn't find device with uuid > '5vu4wT-amMD-6LEm-Q59g-uAxb-POZu-VI5cN1'. > > Found volume group "VolGroup01" using metadata type lvm2 > > > Activating logical volumes > > > Couldn't find device with uuid > 'ogvezr-vkSF-BPI5-mGBq-tKY5-1NOz-GOVHot'. > > Couldn't find device with uuid > '5vu4wT-amMD-6LEm-Q59g-uAxb-POZu-VI5cN1'. > > Couldn't find device with uuid > 'ogvezr-vkSF-BPI5-mGBq-tKY5-1NOz-GOVHot'. > > Couldn't find device with uuid > '5vu4wT-amMD-6LEm-Q59g-uAxb-POZu-VI5cN1'. > > Couldn't find device with uuid 'ogvezr-vkSF-BPI5-mGBq-tKY5-1NOz-GOVHot'. > > > Couldn't find device with uuid '5vu4wT-amMD-6LEm-Q59g-uAxb-POZu-VI5cN1'. > > > Couldn't find device with uuid 'ogvezr-vkSF-BPI5-mGBq-tKY5-1NOz-GOVHot'. > > > Couldn't find device with uuid '5vu4wT-amMD-6LEm-Q59g-uAxb-POZu-VI5cN1'. > > > Couldn't find device with uuid 'ogvezr-vkSF-BPI5-mGBq-tKY5-1NOz-GOVHot'. > > > Couldn't find device with uuid '5vu4wT-amMD-6LEm-Q59g-uAxb-POZu-VI5cN1'. > > > Refusing activation of partial LV LogVol00. Use --partial to override. > > > Couldn't find device with uuid 'ogvezr-vkSF-BPI5-mGBq-tKY5-1NOz-GOVHot'. > > > Couldn't find device with uuid '5vu4wT-amMD-6LEm-Q59g-uAxb-POZu-VI5cN1'. > > > 1 logical volume(s) in volume group "VolGroup01" now active > > > eating root device. > > > unting root filesystem. > > > unt: could not find filesystem '/dev/root' > > > tting up other filesystems. > > > tting up new root fs > > > tuproot: moving /dev failed: No such file or directory > > > fstab.sys, mounting internal defaults > > > tuproot: error mounting /proc: No such file or directory > > > tuproot: error mounting /sys: No such file or directory > > > itching to new root and running init. > > > mounting old /dev > > > mounting old /proc > > > mounting old /sys > > > switchroot: mount failed: No such file or directory > > > Kernel panic - not syncing: Attempted to kill init! > > > HCPGIR450W CP entered; disabled wait PSW 00020001 80000000 00000000 > 0010C04A > > > > (Sorry, but my RHEL 5 is not supported...the THIRTY DAY trial ran out at > the end of last month.) > > > > Frank M. Ramaekers Jr. > > > > Systems Programmer > > MCP, MCP+I, MCSE & RHCE > > American Income Life Insurance Co. > > Phone: (254)761-6649 > > 1200 Wooded Acres Dr. > > Fax: (254)741-5777 > > Waco, Texas 76701 > > > > > > > _____________________________________________________ > > This message contains information which is privileged and confidential and is > solely for the use of the > > intended recipient. If you are not the intended recipient, be aware that any > review, disclosure, > > copying, distribution, or use of the contents of this message is strictly > prohibited. If you have > > received this in error, please destroy it immediately and notify us at > [email protected]. > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO LINUX-390 or visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
