4

raid not autostarting after kernel update

view full story
linux-howto

http://forums.fedoraforum.org – Howdy. I updated my fc12 x86_64 server today, and one of the updated included kernel 2.6.31.12-174.2.3.fc12.x86_64 from the previous one of kernel-2.6.31.9-174.fc12.x86_64. When I boot with that kernel, it stops when my logical volumes that are built on a raid 5 array (linux software raid built using mdadm) are not there. I can start them afterward with mdadm --auto-detect which seemingly loads the appropriate modules and starts the array, but I have never had to do this before. Reading the mdadm man page, it mentions that this is generally done by the initrd. So, I am guessing the initrd that came with the new kernel is missing something. Help? (HowTos)

robot1's picture
Submitted by robot1 on 01/25/2010 – Made popular on 01/25/2010

Stories similar to raid not autostarting after kernel update

I'm sure there is a thread on this somewhere, but after looking though the first 100+ search results, I can't seem to find it.

After a kernel update today, I noticed that new kernels are not being added to my grub menu.lst (so consequently, I was running an older kernel).

The latest update changed the default boot from 0 to 1 and added extra parameters to the new kernel boot line. ################################################## ### default=1 timeout=8 splashimage=(hd0,7)/boot/grub/splash.xpm.gz # hiddenmenu

title Fedora (2.6.31.6-145.fc12.x86_64) root (hd0,7)

I have the following grub.conf

Code: default=0 timeout=5 splashimage=(hd0,13)/boot/grub/splash.xpm.gz hiddenmenu title Fedora (2.6.31.1-56.fc12.x86_64)         root (hd0,13)

As I understand it, it's best practice to set the drive flags as "raid" before adding them to a mdadm raid array. Okay fine, but I also heard people say that they didn't do this and mdadm worked fine. Does mdadm auto-add the raid flag once you add the drives to the array and begin building? Is there any benefit to using the raid flag since it appears mdadm seems to work with or without it?

After a restart which stalled, I did a hard reboot and now mdadm can't see the RAID 6 array anymore, LVM can't find the volume which was on that raid array.

Hi everyone. I'm new to Fedora, but not new to Linux.

I have 250Gb, 500Gb and 1Tb drives concatenated together as one volume group (span) with a logical volume (spanvol). Under kernel 2.6.31.5-127.fc12.x86_64 it mounts totally fine. However, under 2.6.31.6-145.fc12.x86_64, I get this:-

[root@undertaker ~]# mount -t ext4 /dev/mapper/span-spanvol /home

I am a bit confused about my current kernel/kmod-nvidia update situation. When I run "yum check-update" I am confronted with the output below:

Sound lost after recent update 3 years 23 weeks ago

I lost my sound after a recent update. The last time I am positive that I had sound working was Friday night (December 4th) -- watched a bunch of episodes of "Modern Family" from Hulu.

Don' boot with kernel 2.6.31 3 years 42 weeks ago

Hi... I have installed fedora rawhide on a test partition, and after the update (I have disable all F11 repo and enable rawhide repo + rpm-fusion free and nonfree rawhide) when I want to boot on a 2.6.31 kernel, I see the progression bar, but after nothing appear... I test with 2.6.31-0.76.rc3.git4.fc12.x86_64 and 2.6.31-0.81.rc3.git4.fc12.x86_64 kernel for same result.