I can't test 3.2.46 because there are no amd64 packages available in http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2.46-precise. (There were no Intel CPU packages at all). I did test 3.2.47 and 3.2.48 images and *both* of them fail to detect my Intel fakeraid array.
I also looked into updating my BIOS, as suggested by penalvch, and I've decided *not* to upgrade. Too many horror stories about broken systems after doing the upgrade including really basic stuff like detecting Nvidia video cards, overclock failures, higher CPU temps, etc. I'm also concerned that a BIOS upgrade will wipe the Intel raid state from the BIOS and hence force me to rebuild the array from scratch. I'd rather not do that either. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1210104 Title: Intel FakeRAID *Regression* in Kubuntu 12.04 with Linux 3.2.0-51 Status in “linux” package in Ubuntu: Incomplete Bug description: I have been using Intel FakeRAID on an Asus Z77 motherboard on Kubuntu 12.04 for months. I'm using the MDADM version and not DMRAID. It has been working fine other than a couple minor issues with clean shutdowns that I fixed by tweaking a couple of the scripts under /etc. I upgraded to the latest Linux kernel (3.2.0-51) and my FakeRAID stopped working, probably because auto-detection failed to see the RAID array. Everything works fine with the previous kernel image, 3.2.0-49. Here is /proc/mdstat with the 3.2.0-49 generic kernel image: Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10] md126 : active raid1 sdb[1] sdc[0] 976758784 blocks super external:/md127/0 [2/2] [UU] md127 : inactive sdb[1](S) sdc[0](S) 6306 blocks super external:imsm The /proc/mdstat file is empty (other than listing personalities) in 3.2.0-51. Note that the sdb and sdc drives are recognized by 3.2.0-51, and their partition tables look reasonable, so I don't see any issues with 3.2.0-51 actually seeing the physical drives. The problem appears to be that the MD driver doesn't detect the external RAID (aka 'imsm') metadata created by Intel fakeraid. Here's the additional data requested for new bug reports: lsb_release -rd Description: Ubuntu 12.04.2 LTS Release: 12.04 apt-cache policy linux-image-3.2.0-51-generic linux-image-3.2.0-51-generic: Installed: 3.2.0-51.77 Candidate: 3.2.0-51.77 Version table: *** 3.2.0-51.77 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages 100 /var/lib/dpkg/status FWIW, here's the apt-cache data on the previous kernel where fakeraid worked correctly: apt-cache policy linux-image-3.2.0-49-generic linux-image-3.2.0-49-generic: Installed: 3.2.0-49.75 Candidate: 3.2.0-49.75 Version table: *** 3.2.0-49.75 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 100 /var/lib/dpkg/status I will attach the kernel.log for booting 3.2.0-49 and 3.2.0-51. I've looked at them and all I see is that 3.2.0-49 'binds' the RAID array components and 3.2.0-51 doesn't. Here's a snippet from 3.2.0-49 where it starts my RAID. This is absent in 3.2.0-51. Aug 6 06:53:46 canopus kernel: [ 2.088509] md: bind<sdb> Aug 6 06:53:46 canopus kernel: [ 2.150987] md: bind<sdc> Aug 6 06:53:46 canopus kernel: [ 2.151022] md: bind<sdb> Aug 6 06:53:46 canopus kernel: [ 2.151746] md: raid1 personality registered for level 1 Aug 6 06:53:46 canopus kernel: [ 2.152167] bio: create slab <bio-1> at 1 Aug 6 06:53:46 canopus kernel: [ 2.152239] md/raid1:md126: active with 2 out of 2 mirrors Aug 6 06:53:46 canopus kernel: [ 2.152249] md126: detected capacity change from 0 to 1000200994816 Aug 6 06:53:46 canopus kernel: [ 2.153111] md126: p1 p2 p3 p4 < p5 p6 p7 > Any suggestions on how to troubleshoot and/or fix this? There's no point bisecting the kernel images given the regression has just appeared in 3.2.0-51 and, AFAIK, there was never a release of a '3.2.0-50' kernel. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu17.3 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: bmccann 2893 F.... pulseaudio /dev/snd/controlC0: bmccann 2893 F.... pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf7430000 irq 51' Mixer name : 'Realtek ALC892' Components : 'HDA:10ec0892,104384fb,00100302' Controls : 44 Simple ctrls : 21 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xf7080000 irq 17' Mixer name : 'Nvidia GPU 41 HDMI/DP' Components : 'HDA:10de0041,14622871,00100100' Controls : 24 Simple ctrls : 4 DistroRelease: Ubuntu 12.04 HibernationDevice: RESUME=UUID=ce0ec46d-5a8e-4ba4-9049-ed08a896696b InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120424) MachineType: System manufacturer System Product Name MarkForUpload: True NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/tcsh ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-49-generic root=UUID=90c7fb84-e571-4f25-b91a-0a8e9915763f ro quiet splash nomodeset vt.handoff=7 ProcVersionSignature: Ubuntu 3.2.0-49.75-generic 3.2.46 RelatedPackageVersions: linux-restricted-modules-3.2.0-49-generic N/A linux-backports-modules-3.2.0-49-generic N/A linux-firmware 1.79.6 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no StagingDrivers: mei Tags: precise staging Uname: Linux 3.2.0-49-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserAsoundrc: # ALSA library configuration file # Include settings that are under the control of asoundconf(1). # (To disable these settings, comment out this line.) </home/bmccann/.asoundrc.asoundconf> UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo WifiSyslog: Aug 8 07:15:09 canopus NetworkManager[1547]: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889) Aug 8 07:20:08 canopus NetworkManager[1547]: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889) dmi.bios.date: 02/14/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0704 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0704:bd02/14/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-V:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1210104/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp