I've got a linux appliance running on an IBM X3850 X5 type 7143
box. CentOS 5.
It has a RAID 5 configuration with 6 drives. 2 of the drives went down. One was bad and needed to be replaced. The other was just offline and came back online.
The array came back online after the offline drive was back up and at that point we replaced the other drive so it could rebuild. At this point, all drives are showing as being online and the RAID array is showing a healthy status in the MegaRAID BIOS.
All that being said, I'm still getting errors when I try to boot CentOS. Specifically, I'm seeing:
Loading dm-message.ko module
Loading dm-raid45.ko module
device-mapper: dm-raid45: initialized v0.25941
Waiting for driver initialization.
Scanning and configuring dmraid supported devices
Creating root device.
Mounting root filesystem.
kjournald starting. Commit interval 5 seconds.
EXT3-fs: mounted filesystem with ordered data mod.
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
ERROR opening /dev/console: No such file or directory
Trying to use fd 0 instead
WARNING: can't access (null)
exec of init ((null)) failed!!!: Bad address
Kernel panic - not syncing: Attempting to kill init!
Any thoughts on what could be going on here and how to troubleshoot it? I'm not sure why CentOS would have issues if the RAID array was successfully rebuilt.