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

  • How To Add Windows 7 8 10 11 to GRUB Boot List Dual Booting
  • How to configure OpenDKIM on Linux with Postfix and setup bind zonefile
  • Debian Ubuntu 10/11/12 Linux how to get tftpd-hpa server setup tutorial
  • efibootmgr: option requires an argument -- 'd' efibootmgr version 15 grub-install.real: error: efibootmgr failed to register the boot entry: Operation not permitted.
  • Apache Error Won't start SSL Cert Issue Solution Unable to configure verify locations for client authentication SSL Library Error: 151441510 error:0906D066:PEM routines:PEM_read_bio:bad end line SSL Library Error: 185090057 error:0B084009:x509 certif
  • Linux Debian Mint Ubuntu Bridge br0 gets random IP
  • redis requirements
  • How to kill a docker swarm
  • docker swarm silly issues
  • isc-dhcp-server dhcpd how to get longer lease
  • nvidia cannot resume from sleep Comm: nvidia-sleep.sh Tainted: Linux Ubuntu Mint Debian
  • zfs and LUKS how to recover in Linux
  • [error] (28)No space left on device: Cannot create SSLMutex Apache Solution Linux CentOS Ubuntu Debian Mint
  • Save money on bandwidth by disabling reflective rpc queries in Linux CentOS RHEL Ubuntu Debian
  • How to access a disk with bad superblock Linux Ubuntu Debian Redhat CentOS ext3 ext4
  • ImageMagick error convert solution - convert-im6.q16: cache resources exhausted
  • PTY allocation request failed on channel 0 solution
  • docker error not supported as upperdir failed to start daemon: error initializing graphdriver: driver not supported
  • Migrated Linux Ubuntu Mint not starting services due to broken /var/run and dbus - Failed to connect to bus: No such file or directory solution
  • qemu-system-x86_64: Initialization of device ide-hd failed: Failed to get