LinuxQuestions.org
Visit the LQ Articles and Editorials section
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Server
User Name
Password
Linux - Server This forum is for the discussion of Linux Software used in a server related context.

Notices



Reply
 
Search this Thread
Old 01-21-2012, 09:08 PM   #1
misterpat
LQ Newbie
 
Registered: Dec 2011
Distribution: Debian
Posts: 10

Rep: Reputation: Disabled
CentOS 6.2 upgrade kernel mdadm not starting on reboot


Hello all,

I upgraded to the 3.2.0 kernel on CentOS 6.2 and everything seemed to go fine. I was messing around with Folding@home and noticed my raid array wasn't mounted. In fact mdadm wasn't even running.

If I issue this command, It will spit this back to me. This was entered right after it rebooted.

Code:
login as: root
root@*********** password:
Last login: Sat Jan 21 16:58:20 2012 from 192.168.1.199
[root@Mega-Nas ~]# cat /proc/mdstat
Personalities :
unused devices: <none>
[root@Mega-Nas ~]# mdadm --assemble --scan -v
mdadm: looking for devices for /dev/md0
mdadm: /dev/sda1 is identified as a member of /dev/md0, slot 0.
mdadm: /dev/sdb1 is identified as a member of /dev/md0, slot 1.
mdadm: /dev/sdc1 is identified as a member of /dev/md0, slot 2.
mdadm: /dev/sdd1 is identified as a member of /dev/md0, slot 3.
mdadm: /dev/sdf1 is identified as a member of /dev/md0, slot 6.
mdadm: /dev/sdg1 is identified as a member of /dev/md0, slot 5.
mdadm: /dev/sde1 is identified as a member of /dev/md0, slot 4.
mdadm: /dev/sde1 is identified as a member of /dev/md0, slot 4.
mdadm: /dev/sdh1 is identified as a member of /dev/md0, slot 7.
mdadm: /dev/sda1 is identified as a member of /dev/md0, slot 0.
mdadm: /dev/sdf1 is identified as a member of /dev/md0, slot 6.
mdadm: added /dev/sdb1 to /dev/md0 as 1
mdadm: added /dev/sdc1 to /dev/md0 as 2
mdadm: added /dev/sdd1 to /dev/md0 as 3
mdadm: added /dev/sde1 to /dev/md0 as 4
mdadm: added /dev/sdg1 to /dev/md0 as 5
mdadm: added /dev/sdf1 to /dev/md0 as 6
mdadm: added /dev/sdh1 to /dev/md0 as 7
mdadm: added /dev/sda1 to /dev/md0 as 0
mdadm: /dev/md0 has been started with 8 drives.
mdadm: looking for devices for /dev/md/0
mdadm: cannot open device /dev/sda1: Device or resource busy
mdadm: cannot open device /dev/sdb1: Device or resource busy
mdadm: cannot open device /dev/sdc1: Device or resource busy
mdadm: cannot open device /dev/sdd1: Device or resource busy
mdadm: cannot open device /dev/sdf1: Device or resource busy
mdadm: cannot open device /dev/sdg1: Device or resource busy
mdadm: cannot open device /dev/sde1: Device or resource busy
mdadm: cannot open device /dev/sde1: Device or resource busy
mdadm: cannot open device /dev/sdh1: Device or resource busy
mdadm: cannot open device /dev/sda1: Device or resource busy
mdadm: cannot open device /dev/sdf1: Device or resource busy
mdadm: looking for devices for /dev/md/0
mdadm: cannot open device /dev/sda1: Device or resource busy
mdadm: cannot open device /dev/sdb1: Device or resource busy
mdadm: cannot open device /dev/sdc1: Device or resource busy
mdadm: cannot open device /dev/sdd1: Device or resource busy
mdadm: cannot open device /dev/sdf1: Device or resource busy
mdadm: cannot open device /dev/sdg1: Device or resource busy
mdadm: cannot open device /dev/sde1: Device or resource busy
mdadm: cannot open device /dev/sde1: Device or resource busy
mdadm: cannot open device /dev/sdh1: Device or resource busy
mdadm: cannot open device /dev/sda1: Device or resource busy
mdadm: cannot open device /dev/sdf1: Device or resource busy
[root@Mega-Nas ~]# cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4]
md0 : active raid6 sda1[10] sdh1[9] sdf1[11] sdg1[5] sde1[8] sdd1[3] sdc1[2] sdb1[1]
      5860557696 blocks super 1.2 level 6, 64k chunk, algorithm 2 [8/8] [UUUUUUUU]

unused devices: <none>
Notice that after running 'mdadm --assemble --scan -v' and all those errors, I can run 'cat /proc/mdstat' and the array is fine then. I can mount and use it without problem until reboot.

I have been rebooting back to the older kernel, the one the array was built on and the problem still remains.

Any help with this would be greatly appreciated.
 
Old 01-22-2012, 02:03 PM   #2
smallpond
Senior Member
 
Registered: Feb 2011
Location: Massachusetts, USA
Distribution: CentOS 6 (pre-systemd)
Posts: 1,773

Rep: Reputation: 454Reputation: 454Reputation: 454Reputation: 454Reputation: 454
See if it is being started:

Code:
/sbin/chkconfig --list mdmonitor
If it is supposed to be on for your current runlevel, then check for startup errors:

Code:
grep md /var/log/messages
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Kernel Panic when starting Centos guest mmmmmmm Linux - Virtualization and Cloud 2 12-22-2010 06:19 AM
cannot reboot my laptop after kernel upgrade drkstr Slackware 6 08-27-2006 03:00 PM
Kernel upgrade stops at Busy Box v.1.01 on reboot chas Linux - Kernel 0 05-09-2006 05:59 PM
mdadm changes do not survive reboot blackdragonblood Linux - Software 4 02-12-2006 10:58 PM
2.6.10 upgrade - speedtouch 330 adsl - reboot - usbdevfs not supported by kernel lets-eat-gary Fedora 2 01-25-2005 11:17 AM


All times are GMT -5. The time now is 11:14 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration