I found and fixed this problem and it has nothing to do with the kernel. Intel RAID is *extremely* finicky and I remembered that it required two tweaks to the initrd build process. I originally implemented those tweaks in a couple of the MDADM 'hook' files under /usr/share. That was my mistake. These MDADM hooks were overwritten sometime between the installation of 3.2.0-49 and 3.2.0-51 on my PC. (I assume there was an update to the mdadm package). Without my tweaks in initrd.img-3.2.0-51-generic, the RAID won't start and, once that's fixed, the RAID only starts in read-only mode.
I dug through the '/usr/sbin/mkinitramfs' script to see if there's a better way to customize the construction of initrd and found that my changes should have been implemented under /etc/udev/rules.d and /etc /initramfs-tools/hooks. I've made those changes, re-ran update- initramfs, and now 3.2.0-51 is working fine. So, my bad. Thanks to the Ubuntu team for your help looking at this from the perspective that it was a kernel regression. P.S. I need to find a blog someplace to document all this. Intel RAID can work, but it takes lots of customization. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1210104 Title: Intel FakeRAID *Regression* in Kubuntu 12.04 with Linux 3.2.0-51 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1210104/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
