[BlueOnyx:19049] Re: New RAID drive gives a “Kernel panic - not syncing - Attempted to kill init”

Fri Jan 22 09:40:48 -05 2016

*Update*  I found this post which sounds exactly like my issue.

https://www.centos.org/forums/viewtopic.php?t=6738

The problem in this case was the version of dracut had a bug.  Changing 
versions corrected the issue for him but I have not attempted that yet.

> Some more outputs;
>
> =============================
>
> [admin at bluequartz ~]$ cat /etc/fstab
>
> #
> # /etc/fstab
> # Created by anaconda on Sun Apr 29 19:44:32 2012
> #
> # Accessible filesystems, by reference, are maintained under
> '/dev/disk'
> # See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for 
> more
> info
> #
> /dev/mapper/VolGroup00-root / ext3 defaults 1 1
> UUID=fbbc174c-b6b9-4ccd-b8e1-0465f9a605b0 /boot ext3 defaults 1 2
> /dev/mapper/VolGroup00-home /home ext3 defaults,usrquota,grpquota 1 2
> /dev/mapper/VolGroup00-tmp /tmp ext3 noexec,nosuid,rw 1 2
> /dev/mapper/VolGroup00-var /var ext3 defaults 1 2
> /dev/mapper/VolGroup00-swap swap swap defaults 0 0
> tmpfs /dev/shm tmpfs noexec,nosuid,rw 0 0
> devpts /dev/pts devpts gid=5,mode=620 0 0
> sysfs /sys sysfs defaults 0 0
> proc /proc proc defaults 0 0
>
> =================================
>
> [admin at bluequartz ~]$ uname -r
> 2.6.32-220.7.1.el6.x86_64
>
> [admin at bluequartz ~]$ cat /proc/version
> Linux version 2.6.32-220.7.1.el6.x86_64 (mockbuild at sl6.fnal.gov) (gcc
> version 4.4.6 20110731 (Red Hat 4.4.6-3) (GCC) ) #1 SMP Tue Mar 6
> 15:45:33
> CST 2012
>
>> Hi, I'd appreciate some help if anyone has ran into this issue 
>> before.
>> I have a blueonyx server with raid1. One of the drives was 
>> complaining
>> of SMART errors so proactively I decided to replace the drive. When 
>> I
>> do, the server freezes during the boot and displays "Kernel panic -
> not
>> syncing - Attempted to kill init". If I put the failing drive back 
>> in
>> the server boots normally again. I think I have replaced drives
>> previously without issue. Should I be using mdadm to remove the
> failing
>> drive first? Here is some output that I thought may be useful from
>> googling other posts about similar issues.
>> ============================= ==================== [root at bluequartz
> /]#
>> cat /proc/mdstat Personalities : [raid1] md0 : active raid1 sda1[0]
>> sdb1[1] 511988 blocks super 1.0 [2/2] [UU] md1 : active raid1 
>> sdb2[1]
>> sda2[0] 1953000316 blocks super 1.1 [2/2] [UU] bitmap: 4/15 pages
>> [16KB], 65536KB chunk unused devices:
>> =================================================== [root at bluequartz
>> /]# lvm lvdisplay --- Logical volume --- LV Path 
>> /dev/VolGroup00/root
>> LV Name root VG Name VolGroup00 LV UUID
>> PE6bGm-Wjd0-D5wn-mT3r-3SMU-7Efg-eDnaac LV Write Access read/write LV
>> Creation host, time , LV Status available # open 1 LV Size 6.00 GiB
>> Current LE 192 Segments 1 Allocation inherit Read ahead sectors auto 
>> -
>> currently set to 256 Block device 253:0 --- Logical volume --- LV 
>> Path
>> /dev/VolGroup00/swap LV Name swap VG Name VolGroup00 LV UUID
>> oqcXOO-Jnxd-37I9-eDsc-oqiy-cbHf-5AbbaB LV Write Access read/write LV
>> Creation host, time , LV Status available # open 1 LV Size 4.00 GiB
>> Current LE 128 Segments 1 Allocation inherit Read ahead sectors auto 
>> -
>> currently set to 256 Block device 253:1 --- Logical volume --- LV 
>> Path
>> /dev/VolGroup00/tmp LV Name tmp VG Name VolGroup00 LV UUID
>> WVg15b-4bzg-L1ak-dlDu-tcrH-6FbS-VMqGwV LV Write Access read/write LV
>> Creation host, time , LV Status available # open 1 LV Size 2.00 GiB
>> Current LE 64 Segments 1 Allocation inherit Read ahead sectors auto 
>> -
>> currently set to 256 Block device 253:2 --- Logical volume --- LV 
>> Path
>> /dev/VolGroup00/var LV Name var VG Name VolGroup00 LV UUID
>> PxHXCv-ZOpe-w0gX-MzXF-96hS-qa0O-Ceoj1r LV Write Access read/write LV
>> Creation host, time , LV Status available # open 1 LV Size 4.00 GiB
>> Current LE 128 Segments 1 Allocation inherit Read ahead sectors auto 
>> -
>> currently set to 256 Block device 253:3 --- Logical volume --- LV 
>> Path
>> /dev/VolGroup00/home LV Name home VG Name VolGroup00 LV UUID
>> YhuHTx-sBXN-WxIp-mnog-Y3Bm-6GcZ-3Ur4Br LV Write Access read/write LV
>> Creation host, time , LV Status available # open 1 LV Size 1.80 TiB
>> Current LE 59088 Segments 1 Allocation inherit Read ahead sectors 
>> auto
>> - currently set to 256 Block device 253:4
>> ============================================= [root at bluequartz /]# 
>> cat
>> /boot/grub/grub.conf # grub.conf generated by anaconda # # Note that
>> you do not have to rerun grub after making changes to this file #
>> NOTICE: You have a /boot partition. This means that # all kernel and
>> initrd paths are relative to /boot/, eg. # root (hd0,0) # kernel
>> /vmlinuz-version ro root=/dev/mapper/VolGroup00-root # initrd
>> /initrd-[generic-]version.img #boot=/dev/sda default=0 timeout=5
>> splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title BlueOnyx
>> (2.6.32-220.7.1.el6.x86_64) root (hd0,0) kernel
>> /vmlinuz-2.6.32-220.7.1.el6.x86_64 ro 
>> root=/dev/mapper/VolGroup00-root
>> rd_LVM_LV=VolGroup00/root
>> rd_MD_UUID=778b9da0:789a9d17:cbd18758:ae67ab25
>> rd_LVM_LV=VolGroup00/swap rd_NO_LUKS rd_NO_DM LANG=en_US.UTF-8
>> SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us 
>> crashkernel=auto
>> rhgb quiet initrd /initramfs-2.6.32-220.7.1.el6.x86_64.img
>> ============================================== [root at bluequartz /]#
> cat
>> /etc/grub.conf # grub.conf generated by anaconda # # Note that you 
>> do
>> not have to rerun grub after making changes to this file # NOTICE: 
>> You
>> have a /boot partition. This means that # all kernel and initrd 
>> paths
>> are relative to /boot/, eg. # root (hd0,0) # kernel /vmlinuz-version
> ro
>> root=/dev/mapper/VolGroup00-root # initrd
> /initrd-[generic-]version.img
>> #boot=/dev/sda default=0 timeout=5
>> splashimage=(hd0,0)/grub/splash.xpm.gz serial --unit=0 --speed=38400
>> --word=8 --parity=no --stop=1 terminal --timeout=0 serial console
>> hiddenmenu title Scientific Linux (2.6.32-573.12.1.el6.x86_64) root
>> (hd0,0) kernel /vmlinuz-2.6.32-573.12.1.el6.x86_64 ro
>> root=/dev/mapper/VolGroup00-root rd_LVM_LV=VolGroup00/root
>> rd_MD_UUID=778b9da0:789a9d17:cbd18758:ae67ab25
>> rd_LVM_LV=VolGroup00/swap rd_NO_LUKS rd_NO_DM LANG=en_US
>> SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us 
>> crashkernel=auto
>> rhgb quiet console=tty0 console=ttyS0,38400 initrd
>> /initramfs-2.6.32-573.12.1.el6.x86_64.img title Scientific Linux
>> (2.6.32-573.3.1.el6.x86_64) root (hd0,0) kernel
>> /vmlinuz-2.6.32-573.3.1.el6.x86_64 ro 
>> root=/dev/mapper/VolGroup00-root
>> rd_LVM_LV=VolGroup00/root
>> rd_MD_UUID=778b9da0:789a9d17:cbd18758:ae67ab25
>> rd_LVM_LV=VolGroup00/swap rd_NO_LUKS rd_NO_DM LANG=en_US
>> SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us 
>> crashkernel=auto
>> rhgb quiet console=tty0 console=ttyS0,38400 initrd
>> /initramfs-2.6.32-573.3.1.el6.x86_64.img title BlueOnyx
>> (2.6.32-220.7.1.el6.x86_64) root (hd0,0) kernel
>> /vmlinuz-2.6.32-220.7.1.el6.x86_64 ro 
>> root=/dev/mapper/VolGroup00-root
>> rd_LVM_LV=VolGroup00/root
>> rd_MD_UUID=778b9da0:789a9d17:cbd18758:ae67ab25
>> rd_LVM_LV=VolGroup00/swap rd_NO_LUKS rd_NO_DM LANG=en_US.UTF-8
>> SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us 
>> crashkernel=auto
>> rhgb quiet console=tty0 console=ttyS0,38400 initrd
>> /initramfs-2.6.32-220.7.1.el6.x86_64.img
>> =============================================== [root at bluequartz /]#
>> rpm -q kernel kernel-2.6.32-220.7.1.el6.x86_64
>> kernel-2.6.32-573.3.1.el6.x86_64 kernel-2.6.32-573.12.1.el6.x86_64
>> _______________________________________________ Blueonyx mailing 
>> list
>> Blueonyx at mail.blueonyx.it [1]
>> http://mail.blueonyx.it/mailman/listinfo/blueonyx [2]

-- 

Sent using Hay Webmail!!!

Links:
------
[1] mailto:Blueonyx at mail.blueonyx.it
[2] http://mail.blueonyx.it/mailman/listinfo/blueonyx