Centos 5.5 RAID 1 boot issue

I installed 5.5 with a 300GB RAID 1 partition (boot is also on this partition).  It booted up fine the first few times until after I used a Live CD and accessed the array, and it became named /dev/md127 for some reason.

Now whenI boot into CentOS I get a kernel panic and different errors, once I got "invalid superblock", even though the array is fine (it didn't happen again, probably because I was sure to dismount and stop the mdadm array properly).

Here's what I get when booting (the /dev/md127 is the problem I think):

raid1: raid set md127 active with 2 out of 2 mirrors
md: ... autorun DONE.
Trying to resume from LABEL=SWAP-sda2
No suspend signature on swap, no tresuming.
Creating root device.
Mounting root filesystem.
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
unmountin gold /proc
unmounting old/sys
switchroot: mount fialed: No such file or directory
Kernel panic -no syncing: Attempted to kill init!

I have tried specifying the root with UUID= with /dev/md0 and /dev/md127 without any different result. I'm really getting frustrated and stuck.  I also wonder if the issue might be that I used a very new 3.1.2 mdadm to access the array on my boot disc, could that have caused some incompatiblity problem with a different and likely older version of mdadm that Centos uses?

 

Solved

I think that when I accessed the raid array and it became md127, this screwed up all the initrd's or something else.  I don't know how to explain it.

I got the idea to use single user mode and it booted fine.  Then I just made an initrd:

mkinitrd /boot/yournewinitrd `uname -r` and make sure you boot with that initrd, I was able to boot again.  This should serve as a warning for anyone booting with RAID 1.  DON'T ACCESS THE RAID ARRAY WITH A LIVE CD UNLESS YOU USE THE SAME MD DEVICE.  I really think this is a Centos and mdadm bug in one.


Tags:

centos, raid, issuei, installed, gb, partition, booted, accessed, array, dev, md, wheni, kernel, errors, quot, invalid, superblock, didn, dismount, mdadm, booting, active, mirrors, autorun, resume, label, swap, sda, suspend, tresuming, creating, mounting, filesystem, mount, filesystems, fs, setuproot, directory, fstab, sys, defaults, proc, switching, init, unmounting, unmountin, switchroot, fialed, syncing, specifying, uuid, frustrated, disc, incompatiblity, initrd, user, mode, mkinitrd, yournewinitrd, uname,

Latest Articles

  • Linux Ubuntu Cannot Print Large Images
  • Cannot Print PDF Solution and Howto Resize
  • Linux Console Login Screen TTY Change Message
  • Apache Cannot Start Listening Already on 0.0.0.0
  • MySQL Bash Query to pipe input directly without using heredoc trick
  • CentOS 6 and 7 / RHEL Persistent DHCP Solution
  • Debian Ubuntu Mint rc-local service startup error solution rc-local.service: Failed at step EXEC spawning /etc/rc.local: Exec format error
  • MySQL Cheatsheet Guide and Tutorial
  • bash script kill whois or other command that is running for too long
  • Linux tftp listens on all interfaces and IPs by DEFAULT Security Risk Hole Solution
  • python import docx error
  • Cisco Unified Communications Manager Express Cheatsheet CUCME CME
  • Linux Ubuntu Debian Missing privilege separation directory: /var/run/sshd
  • bash how to count the number of columns or words in a line
  • bash if statement how to test program output without assigning to variable
  • RTNETLINK answers: Network is unreachable
  • Centos 7 how to save iptables rules like Centos 6
  • nfs tuning maximum amount of connections
  • qemu-kvm error "Could not initialize SDL(No available video device) - exiting"
  • Centos 7 tftpd will not work with selinux enabled