@Stefan: --scan command might be useless but thanks anyway since it helped me noticing the issue that make me solve it :)
Here is the output of the scan command and the relevant content of the config file: $ sudo mdadm --misc --scan --detail ARRAY /dev/md0 level=raid1 num-devices=2 metadata=01.02 name=alan-desktop:0 UUID=d5119bd2:7491e0f3:df5db333:6e036bee ARRAY /dev/md3 level=raid1 num-devices=2 metadata=01.00 name=pca3:3 UUID=154f648b:6076c08b:76f5610a:9fbce7c7 $ cat /etc/mdadm/mdadm.conf | grep ARRAY ARRAY /dev/md/0 level=raid1 metadata=1.2 num-devices=2 UUID=d5119bd2:7491e0f3:df5db333:6e036bee name=pca3:1 ARRAY /dev/md/3 level=raid1 metadata=1.0 num-devices=2 UUID=154f648b:6076c08b:76f5610a:9fbce7c7 name=pca3:3 As you can see there is a mismatch in the configured and scanned names, the latter coming from the array creation since long ago. Now, I have no idea why they differ however changing the one in the config file to match the scanned one made the array build up at boot again. Just confirmed with 2.6.32-50-generic So, to reproduce the issue its probably enough to change the array name into mdadm.conf. A last notice/recommendation: I do not understand why there is a need for array information to be placed into a configuration file and even more why to rely so much on it, such a config file will belong to a single system while arrays would be used also in multi-boot environments or have to be read also from recovery system used to boot a machine. I think relying on metadata on the drives only to be a far better approach. Thank you for helping in solving the issue and let me know if you need more info for further development. -- 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/1209423 Title: [STAGING] 2.6.32-47 kernel update on 10.04 breaks software RAID at boot Status in “linux” package in Ubuntu: Incomplete Bug description: After update from 2.6.32-46 to 2.6.32-47 one of the md arrays does not start anymore at boot time. The RAID 1 md0 now causes message "Continue to wait; or Press S to skip mounting or M for manual recovery" at boot. I used "S" to create this report as requested in a similar bug report (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1190295) by user "penalvch" Booting back into 2.6.32-46 the md devices are correctly set up and the system boots normally. See the linked bug for further details, such as: The array that does not start anymore has the following config: level=raid1 metadata=1.2 num-devices=2 While a second array with metadata=1.0 seems to be recognized and started correctly. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: linux-image-2.6.32-50-generic 2.6.32-50.112 Regression: Yes Reproducible: Yes ProcVersionSignature: Ubuntu 2.6.32-50.112-generic 2.6.32.61+drm33.26 Uname: Linux 2.6.32-50-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: alan 1991 F.... pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf6220000 irq 22' Mixer name : 'Realtek ALC888' Components : 'HDA:10ec0888,80860034,00100202' Controls : 28 Simple ctrls : 16 Date: Thu Aug 8 02:01:09 2013 HibernationDevice: RESUME=UUID=b1649a13-fffd-4e98-b42b-a5e9ea98f9fc InstallationMedia: Ubuntu 10.04.4 LTS "Lucid Lynx" - Release amd64 (20120214.2) ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-50-generic root=UUID=e69dddfa-14a0-499f-9267-edca27fbd7a4 ro quiet splash ProcEnviron: PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash RelatedPackageVersions: linux-firmware 1.34.14 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux StagingDrivers: r8192s_usb Title: [STAGING] dmi.bios.date: 04/19/2010 dmi.bios.vendor: Intel Corp. dmi.bios.version: WBIBX10J.86A.0293.2010.0419.1819 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: DP55WB dmi.board.vendor: Intel Corporation dmi.board.version: AAE64798-207 dmi.chassis.type: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrWBIBX10J.86A.0293.2010.0419.1819:bd04/19/2010:svn:pn:pvr:rvnIntelCorporation:rnDP55WB:rvrAAE64798-207:cvn:ct2:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1209423/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
