yum -y install samba vi /etc/samba/smb.conf https://www.kernel.org/pub/linux/utils/boot/syslinux/syslinux-6.03.zip mkdir syslinux;cd syslinux;unzip syslinux-6.03.zip mkdir -p /tftpboot/libs/ cp bios/com32/modules/linux.c32 /tftpboot/libs/ cp bios/com32/libutil/libutil.c32 /tftpboot/libs/ cp bios/com32/lib/libcom32.c32 /tftpboot/libs/ #add lib path echo "PATH libs" >> /tftpboot/pxeli........

high IO wait 424 root 39 19 1900 848 552 D 0.0 0.0 0:00.91 updatedb root 424 0.0 0.0 1900 848 ? DN Mar11 0:00 /usr/bin/updatedb -f sysfs?rootfs?bdev?proc?cpuset?binfmt_misc?debugfs?sockfs?usbfs?pipefs?anon_inodefs?futexfs?tmpfs?inotifyfs?eventp........

md: Autodetecting RAID arrays. md: autorun ... md: considering sdb1 ... md: adding sdb1 ... md: adding sda1 ... md: created md0 md: bind md: bind md: running: md: kicking non-fresh sda1 from array! md: unbind md: export_rdev(sda1) raid1: raid set md0 active with 1 out of 2 mirrors The md0 raid kicked sda1 ou........

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........