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

  • FreePBX 17 How To Add a Trunk
  • Docker Container Onboot Policy - How to make sure a container is always running
  • FreePBX 17 How To Add Phones / Extensions and Register
  • Warning: The driver descriptor says the physical block size is 2048 bytes, but Linux says it is 512 bytes. solution
  • Cisco How To Use a Third Party SIP Phone (eg. Avaya, 3CX)
  • Cisco Unified Communication Manager (CUCM) - How To Add Phones
  • pptp / pptpd not working in DD-WRT iptables / router
  • systemd-journald high memory usage solution
  • How to Install FreePBX 17 in Linux Debian Ubuntu Mint Guide
  • How To Install Cisco's CUCM (Cisco Unified Communication Manager) 12 Guide
  • Linux Ubuntu Redhat How To Extract Images from PDF
  • Linux and Windows Dual Boot Issue NIC Won't work After Booting Windows
  • Cisco CME How To Enable ACD hunt groups
  • How to install gns3 on Linux Ubuntu Mint
  • How to convert audio for Asterisk .wav format
  • Using Cisco CME Router with Asterisk as a dial-peer
  • Cisco CME How To Configure SIP Trunk VOIP
  • Virtualbox host Only Network Error Failed to save host network interface parameter - Cannot change gateway IP of host only network
  • Cisco CME and C7200 Router Testing and Learning Environment on Ubuntu 20+ Setup Tutorial Guide
  • Abusive IP ranges blacklist